Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / May 2005

Tip: Looking for answers? Try searching our database.

Unable to restart DB2 Instance

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kamlesh - 30 May 2005 08:07 GMT
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 - 30 May 2005 14:14 GMT
> Hello,
>
[quoted text clipped - 21 lines]
> 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 - 30 May 2005 16:02 GMT
What platform are you running on?

> Hello,
>
[quoted text clipped - 21 lines]
> Regards,
> Kamlesh
Weiduo.Deng@gmail.com - 31 May 2005 01:15 GMT
He said he is on AIX.

> What platform are you running on?
>
[quoted text clipped - 23 lines]
> > Regards,
> > Kamlesh
Larry - 31 May 2005 04:08 GMT
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.

> He said he is on AIX.
>
[quoted text clipped - 25 lines]
>>>Regards,
>>>Kamlesh
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.