By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,487 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

Unable to restart DB2 Instance

P: n/a
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

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Kamlesh wrote:
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

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
Nov 12 '05 #2

P: n/a
What platform are you running on?

Kamlesh wrote:
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

Nov 12 '05 #3

P: n/a
He said he is on AIX.

Larry wrote:
What platform are you running on?

Kamlesh wrote:
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


Nov 12 '05 #4

P: n/a
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.

We*********@gmail.com wrote:
He said he is on AIX.

Larry wrote:
What platform are you running on?

Kamlesh wrote:
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


Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.