Cannot create DB2 index, getting SQL30081N error

Question

Trying to create an index (and run some long queries) on DB2 v9.1 and failing with the following error message:

SQL30081N (A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error...")

I have tried to follow advice given by IBM here regarding setting QUERYTIMEOUTINTERVAL=0- http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21164785 but it did not take.

any ideas? queries and commands seem to time out at about 15 minutes.

Fred Sobotka · Accepted Answer · 2009-06-16 19:04:17Z

1

You can rule out any network interference by running the DDL and SQL locally on the server. By using nohup on UNIX or schtasks on Windows, you can start a DB2 job that will run to completion even if the database server loses all network connectivity.

answered Jun 16, 2009 at 19:04

Fred Sobotka

5,33225 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Slava F Over a year ago

Fred, This is what we did as well after I posted the question. The indexing completed well. Thank you for your answer. I would upvote it, if I could, but I do not have the reputation points yet. thanks.

tekBlues · Accepted Answer · 2009-06-09 01:09:46Z

0

It seems like a network error, probably your client machine is losing the connection to the server. Are you over an unstable network connection, for example a VPN over the internet?

answered Jun 9, 2009 at 1:09

tekBlues

5,8031 gold badge31 silver badges32 bronze badges

Collectives™ on Stack Overflow

Cannot create DB2 index, getting SQL30081N error

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related