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

SQL1224N.....SQLSTATE=55032 Problem.

P: n/a
ja
Hello,
When I run the following query:

select count(*)
from table111
where pf = 'F' and
pet = 'Y'

I get the following error message:

"SQL1224N A database agent could not be started to service a request,
or was terminated as a result of a database system shutdown or a force
command. SQLSTATE=55032"

Does anybody have any idea how to solve this problem?

db2 8.1 workgroup unlimited
win 2003 server

tia

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


P: n/a

"ja" <ja@aol.com> wrote in message
news:0d********************************@4ax.com...
Hello,
When I run the following query:

select count(*)
from table111
where pf = 'F' and
pet = 'Y'

I get the following error message:

"SQL1224N A database agent could not be started to service a request,
or was terminated as a result of a database system shutdown or a force
command. SQLSTATE=55032"

Does anybody have any idea how to solve this problem?

db2 8.1 workgroup unlimited
win 2003 server


When I had that problem a few weeks ago and investigated it, it turned out
that the agent in question was NPIPES or maybe TCPIP; I don't recall which
now. The problem occurred after I had used the FORCE command to kill a few
DB2 applications and followed the FORCE with a db2stop/db2start. I never
managed to figure out why the agent hadn't started but I found that
everything was working fine again after my next reboot. In fact, I found
that everything I tried worked fine *despite* the error message, even before
the reboot. However, in your case, you are clearly having a problem as a
result of an agent which didn't (re)start.

In short, I don't know why your agent wouldn't start but a reboot would
probably solve your problem, assuming a reboot is possible in your
environment. If you can't reboot because it is a production server, I can
only suggest a db2stop followed by a db2start but I don't guarantee that
this will work. Also, there may be better ways to handle the problem that a
db2start/db2stop. It would probably be best if you waited for a few more
replies to see if someone else can come up with a better idea.

Rhino
Nov 12 '05 #2

P: n/a
-1224 is usually not good!! It's a trap most probably because of
memory corruption and it brings the db2 instance down so it stops the
db2 anyway.
I suggest you contact IBM support, however under db2dump directory
there should
be trap files (t*), if you paste them here someone should be able to
give you
more detail.
Amar.
"Rhino" <rh****@NOSPAM.sympatico.ca> wrote in message news:<IB********************@news20.bellglobal.com >...
"ja" <ja@aol.com> wrote in message
news:0d********************************@4ax.com...
Hello,
When I run the following query:

select count(*)
from table111
where pf = 'F' and
pet = 'Y'

I get the following error message:

"SQL1224N A database agent could not be started to service a request,
or was terminated as a result of a database system shutdown or a force
command. SQLSTATE=55032"

Does anybody have any idea how to solve this problem?

db2 8.1 workgroup unlimited
win 2003 server


When I had that problem a few weeks ago and investigated it, it turned out
that the agent in question was NPIPES or maybe TCPIP; I don't recall which
now. The problem occurred after I had used the FORCE command to kill a few
DB2 applications and followed the FORCE with a db2stop/db2start. I never
managed to figure out why the agent hadn't started but I found that
everything was working fine again after my next reboot. In fact, I found
that everything I tried worked fine *despite* the error message, even before
the reboot. However, in your case, you are clearly having a problem as a
result of an agent which didn't (re)start.

In short, I don't know why your agent wouldn't start but a reboot would
probably solve your problem, assuming a reboot is possible in your
environment. If you can't reboot because it is a production server, I can
only suggest a db2stop followed by a db2start but I don't guarantee that
this will work. Also, there may be better ways to handle the problem that a
db2start/db2stop. It would probably be best if you waited for a few more
replies to see if someone else can come up with a better idea.

Rhino

Nov 12 '05 #3

P: n/a
ja wrote:
Hello,
When I run the following query:

select count(*)
from table111
where pf = 'F' and
pet = 'Y'

I get the following error message:

"SQL1224N A database agent could not be started to service a request,
or was terminated as a result of a database system shutdown or a force
command. SQLSTATE=55032"

Does anybody have any idea how to solve this problem?


Did you stop/start DB2 right before the query (or kill the DB2 processes),
and possibly use implicit connect?

This error message can be returned if the background process (db2bp) of your
command line still thinks that it is talking to a db2agent process, but
that process went away. Either you run into a DB2 bug, in which case you
want to contact IBM support, or you did the kill-thing, in which case you
should be able to connect to the database again.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena
Nov 12 '05 #4

P: n/a
ja
Hello Amar,

The only thing that I can find is the db2diag.log. If this is what
you're suggesting as trap file, here are some lines of that log file
(14mb).....

2004-07-02-11.29.26.453000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2208 Appid:*LOCAL.DB2.01A582182403
relation data serv sqlr_subagent_router Probe:120 Database:XDB

0x036CF868 : 0x87040001 ...

PID:772 TID:2208 Node:000 Title: UCstate:
0x027F3F00 : 0x04000040 @...

2004-07-02-11.29.26.484000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
relation data serv sqlrr_rds_common_post Probe:140 Database:XDB

0x037CCD88 : 0x8012007E ~...

PID:772 TID:2212 Node:000 Title: UCstate:
0x037D18E0 : 0x04000142 B...

PID:772 TID:2212 Node:000 Title: SQLCA
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1034 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlrrco1~
sqlerrd : (1) 0x8012007E (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2004-07-02-11.29.26.515000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
base sys utilities sqlesrsp Probe:90 Database:XDB

DiagData
0x037CD13C : 0xFFFFFBF6

2004-07-02-11.29.26.531000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
base sys utilities sqlesrsp Probe:90 Database:XDB

0x037CD13C : 0xFFFFFBF6

2004-07-02-11.29.26.562000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
data protection sqlpthrd Probe:440 Database:XDB

DIA8427C The database has been marked as being damaged.
ZRC=0x8602001A

2004-07-02-11.29.26.578000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
buffer pool services sqlbTerminateAgent Probe:837 Database:XDB

DIA8427C The database has been marked as being damaged.
ZRC=0x8602001A

2004-07-02-11.29.26.593000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
base sys utilities sqleAgentDissociate Probe:90 Database:XDB

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x06000000".

2004-07-02-11.29.26.609000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
base sys utilities sqleTermDbConnect Probe:110 Database:XDB

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBF6".

2004-07-02-11.29.26.671000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
data protection sqlpterm Probe:3200 Database:XDB

Database shutdown with next LSN of 0000000094DDC00C.

2004-07-02-11.29.26.734000 Instance:DB2 Node:000
PID:772(db2syscs.exe) TID:2212 Appid:*LOCAL.DB2.01A582182403
DRDA Application Server sqljsCleanup Probe:60 Database:XDB

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBF6".

2004-07-02-11.29.26.937000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcReceive Probe:30

CCI Error:
0x0012EAE0 : 0x00000047 G...

2004-07-02-11.29.26.953000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcReceive Probe:30

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8136001C".

2004-07-02-11.29.27.203000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcSend Probe:10

CCI Error:
0x0012F1A8 : 0x00000047 G...

2004-07-02-11.29.27.234000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcSend Probe:10

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8136001C".

2004-07-02-11.29.27.281000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcSend Probe:10

CCI Error:
0x0012F054 : 0x00000047 G...

2004-07-02-11.29.27.281001 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Communication Manager sqljcSend Probe:10

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8136001C".

2004-07-02-11.29.27.296000 Instance:DB2 Node:000
PID:3380(db2bp.exe) TID:3364 Appid:*LOCAL.DB2.01A582182403
DRDA Application Requester sqljrDrdaArDisconnect Probe:10

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0x8136001C".
let me know, if you find anything.

thank you.

ja
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.