Discussion:
Unable to restart DB2 Instance
(too old to reply)
Kamlesh
2005-05-30 07:07:45 UTC
Permalink
Hello,

I am unable to do anything with a specific DB2 instance. However, my
other DB2 instances/databases on the same server are functioning well.
Please see the below commands and their outputs:

$ db2 list applications
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
$
$ db2stop
SQL6036N START or STOP DATABASE MANAGER command is already in
progress.
$


Is there any way I can fix this without restarting the OS. I am
running DB2 UDB 8.1 on AIX box.

Regards,
Kamlesh
indika
2005-05-30 13:14:35 UTC
Permalink
Post by Kamlesh
Hello,
I am unable to do anything with a specific DB2 instance. However, my
other DB2 instances/databases on the same server are functioning well.
$ db2 list applications
SQL30081N A communication error has been detected. Communication
protocol
being used: "*". Communication API being used: "*". Location where
the error
"create_agent".
Protocol specific error code(s): "54", "*", "*". SQLSTATE=08001
$
$ db2stop
SQL6036N START or STOP DATABASE MANAGER command is already in
progress.
$
Is there any way I can fix this without restarting the OS. I am
running DB2 UDB 8.1 on AIX box.
Regards,
Kamlesh
Hi Kamlesh,

it can be that the db2sysc has to synchronize data packets. was there a
crash or something than it is normal that you cant shutdown till roll
forwarding is in progress or chrash recovery. this can take a while
depends on cpu ram. wait a day and try again to stop and start the instance.

if this doesnt help call the IBM support.

cu,

indika
Larry
2005-05-30 15:02:28 UTC
Permalink
What platform are you running on?
Post by Kamlesh
Hello,
I am unable to do anything with a specific DB2 instance. However, my
other DB2 instances/databases on the same server are functioning well.
$ db2 list applications
SQL30081N A communication error has been detected. Communication
protocol
being used: "*". Communication API being used: "*". Location where
the error
"create_agent".
Protocol specific error code(s): "54", "*", "*". SQLSTATE=08001
$
$ db2stop
SQL6036N START or STOP DATABASE MANAGER command is already in
progress.
$
Is there any way I can fix this without restarting the OS. I am
running DB2 UDB 8.1 on AIX box.
Regards,
Kamlesh
W***@gmail.com
2005-05-31 00:15:08 UTC
Permalink
He said he is on AIX.
Post by Larry
What platform are you running on?
Post by Kamlesh
Hello,
I am unable to do anything with a specific DB2 instance. However, my
other DB2 instances/databases on the same server are functioning well.
$ db2 list applications
SQL30081N A communication error has been detected. Communication
protocol
being used: "*". Communication API being used: "*". Location where
the error
"create_agent".
Protocol specific error code(s): "54", "*", "*". SQLSTATE=08001
$
$ db2stop
SQL6036N START or STOP DATABASE MANAGER command is already in
progress.
$
Is there any way I can fix this without restarting the OS. I am
running DB2 UDB 8.1 on AIX box.
Regards,
Kamlesh
Larry
2005-05-31 03:08:43 UTC
Permalink
Missed that.

Well ... you can either open up a support incident or if you want to
proceed at your own risk ... try using the db2stop force command and if
all else fails, db2_kill. Sounds like the previous stop is hung.

Larry E.
Post by W***@gmail.com
He said he is on AIX.
Post by Larry
What platform are you running on?
Post by Kamlesh
Hello,
I am unable to do anything with a specific DB2 instance. However, my
other DB2 instances/databases on the same server are functioning well.
$ db2 list applications
SQL30081N A communication error has been detected. Communication
protocol
being used: "*". Communication API being used: "*". Location where
the error
"create_agent".
Protocol specific error code(s): "54", "*", "*". SQLSTATE=08001
$
$ db2stop
SQL6036N START or STOP DATABASE MANAGER command is already in
progress.
$
Is there any way I can fix this without restarting the OS. I am
running DB2 UDB 8.1 on AIX box.
Regards,
Kamlesh
Loading...