SQL30081N - ipclean and DB2

10 July,2011 by Tom Collins

 SQL30081N A communication error has been detected. Communication protocol
being used: "*". Communication API being used: "*". Location where the error
was detected: "". Communication function detecting the error: "create_agent".
Protocol specific error code(s): "54", "*", "*". SQLSTATE=08001"

I checked the message queues and shared memory segments . This revealed a large amount of entries related to the instance.
I was attempting to do a "db2stop force" and this was hanging.
I cleared everything down with "ipclean" . This allowed the memory segments to be cleared.

Author: Jack Vamvas(http://www.dba-db2.com)
Author: Rambler(http://www.dba-db2.com)

Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on SQL30081N - ipclean and DB2

Comments are moderated, and will not appear until the author has approved them.


dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright