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 use DB2 9.7 adapter and using DB2 connect to the database. But lately we continuous have TCP/IP error but do not know why. Saw on the forum DB2 SQL ? command, I like to know what I'm getting back is this the WebFOCUS configuration or the configuration of DB2 Connect? Does someone has an idea or suggestion
This is the result of SQL DB2 ? :
(FOC1702) ODBC SOURCE IS -: DBM0144 (FOC1703) ODBC USER IS -: M857 (FOC1704) ODBC TIMEOUT IS -: 15 (FOC1707) ODBC ISOLATION IS -: RC (FOC1711) ODBC AUTODISCONNECT OPTION IS -: ON FIN (FOC1706) ODBC CONCUR IS -: RONLY (FOC1491) FETCH BUFFERING FACTOR - 100 (FOC1531) INSERT BUFFERING FACTOR - 1 (FOC1496) AUTODISCONNECT OPTION IS -: ON FIN (FOC1441) WRITE FUNCTIONALITY IS -: ON (FOC1445) OPTIMIZATION OPTION IS -: ON (FOC1763) IF-THEN-ELSE OPTIMIZATION IS -: ON (FOC1484) SQL ERROR MESSAGE TYPE IS -: DBMS (FOC1552) INTERFACE DEFAULT DATE TYPE -: NEW (FOC1446) DEFAULT dbspace IS -:
The error we get is (just testing the adapter) :
(FOC1394) CONNECT FAILURE (FOC1400) SQLCODE IS -30081 (HEX: FFFF8A7F) : [08001] [IBM][CLI Driver] SQL30081N A communication error has been dete : cted. Communication protocol being used: "TCP/IP". Communication API be : ing used: "SOCKETS". Location where the error was detected: "10.1.8.144 : ". Communication function detecting the error: "selectForRecvTimeout". : Protocol specific error code(s): "0", "*", "*". SQLSTATE=08001 (FOC1405) SQL PREPARE ERROR. (FOC1394) CONNECT FAILURE (FOC1400) SQLCODE IS -30081 (HEX: FFFF8A7F) : [08001] [IBM][CLI Driver] SQL30081N A communication error has been dete : cted. Communication protocol being used: "TCP/IP". Communication API be : ing used: "SOCKETS". Location where the error was detected: "10.1.8.144 : ". Communication function detecting the error: "selectForRecvTimeout". : Protocol specific error code(s): "0", "*", "*". SQLSTATE=08001 (FOC1405) SQL PREPARE ERROR.
Thanks,
MarkThis message has been edited. Last edited by: <Kathryn Henning>,
Go to the Control Center in DB2 Connect and click on the plus sign next to the target system, then the instance, then the database. Then click on the tables icon. Put in the same user and password that your IBI connection setting is using and see if it returns the list of tables in DB2. If not, it should return an error that you can evaluate to determine why you are getting a time out.
Thanks for your reaction. We installed a small version of DB2 connection, so I can't show the tables. But the weird thing is that mostly the connection works fine. I like to exclude that there's something wrong with the WF adapter, but I don't know how.
I found your post of 2014 with same error message I frequently get:
: [08001] [IBM][CLI Driver] SQL30081N A communication error has been dete : cted. Communication protocol being used: "TCP/IP". Communication API be : ing used: "SOCKETS". Location where the error was detected: "10.1.8.144 : ". Communication function detecting the error: "selectForRecvTimeout". : Protocol specific error code(s): "0", "*", "*". SQLSTATE=08001
Your post is indicated as [CLOSED], but I do not see any conclusion/resolution on what caused this error and how you solved it.
Do you still remember, and can you share with me?
I can normally access the data by retrieving sample data through the synonym, but sometimes it happens I get this error message.
Or maybe someone else recognizes this error message.
Martin.
WebFocus 8206M, iWay DataMigrator, Windows, DB2 Windows V10.5, MS SQL Server, Azure SQL, Hyperstage, ReportCaster