[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


SQL30081N - Protocol specific error code(s): "10055", "*", "*".  SQLSTATE=08001

Posted on 2009-12-29
Medium Priority
Last Modified: 2012-05-08
When I try connect to a cataloged DB I get this error:

QL30081N  A communication error has been detected.  Communication protocol
being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location
where the error was detected: "SERVER IP".  Communication function
detecting the error: "connect".  Protocol specific error code(s): "10055", "*",
"*".  SQLSTATE=08001

The database resides on AIX server. I have cataloged it on a windows server.
Question by:jsaravana
  • 2
  • 2
LVL 37

Expert Comment

ID: 26137070
were you able to connect to it in the past or is this a new database?

did you check that the instance is up and running?
did you check that your firewall does not block the ports used by DB2 ?

Author Comment

ID: 26137168
This is the first time we are cataloging this database.

The instance is up n running.

I am not sure if any firewall is blocking the connection
LVL 37

Accepted Solution

momi_sabag earned 2000 total points
ID: 26137225
the most simple approach to check:
using ip addr + port number, try this from your station:

telnet ip-addr port

if you can't use telnet, then your ports are probably blocked
you can also try to connect and in the same time run

netstat -an

if you see that your connect attemp (you can find it by the ip and port of the db2 serveR) has status SYN_SENT
it mean you have some kind of firewall blcok

Author Comment

ID: 26137412

Now I am able to connect, I had some tablespace issue in other database which was requesting for backup.
When I took offline backup and tried connecting I was able to connect.

Those were found in system error logs.

I will try and find out you suggestions as well. Will be useful for me.

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recursive SQL in UDB/LUW (you can use 'recursive' and 'SQL' in the same sentence) A growing number of database queries lend themselves to recursive solutions.  It's not always easy to spot when recursion is called for, especially for people una…
Recursive SQL in UDB/LUW (it really isn't that hard to do) Recursive SQL is most often used to convert columns to rows or rows to columns.  A previous article described the process of converting rows to columns.  This article will build off of th…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question