Hello,

i'm from germany and my english is not very good. But I hope you will understand a little bit.

I have a problem with ja DB2 on Solaris.
We had a rollback for 2 days and i think the rollback was not rolledback well.
So we restart the machine. Now if i want to say "db2start" or "db2stop"
it says the "SQL1026N The database manager is already active." or "SQL1032N No start database manager command was issued. SQLSTATE=57019".
If i want to activate the database there happens nothing at the first time.
Then i killed 2 "db2sysc" and then i retry.
Then i become the message "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"

Has anyone a little tip what i should do?

I hope you understand what i mean. If not i wil try to explain better.

Thank You.

Greets

Rolf

It would be good to know your OS and DB2 version... Also, have a look at your db2diag.log - there may be useful messages there.

Kill not such a great idea. Since you must be on unix or linux, there's a script in the IBM install directory, I think it's called ipclean or something like that... run it to clear up the shared memory and such.

try to do ipcs | grep instancename
if you see lot of message queues and shared memory segments clear them
using ipcrm -q queueid and ipcrm -m memorysegmentid

this should take care of it.

FYI, that's what ipclean does. A lot easier, since you may have a lot of entries.