Hi,

Has anyone come accross this error?

GetCounterValue: sqleatin - 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

The error code "54" has no discription in the IBM documentation either. Please provide inputs on this.

Regards,
Prashant

This is the stack of error in the db2diag.log which suggests the error is due to memory allocation failure.

2004-05-06-05.55.49.354342 Instance:db2pinst Node:001
PID:40080(db2agent (idle) 1) Appid:none
base_sys_utilities sqleAgentActivationInit Probe:10
DIA3605C Memory allocation failure occurred.

ZRC=0xFFFFD605

2004-05-06-05.55.49.465376 Instance:db2pinst Node:001
PID:40080(db2agent (idle) 1) Appid:none
base_sys_utilities sqleagnt Probe:3
DIA3605C Memory allocation failure occurred.

ZRC=0xFFFFD605

2004-05-06-05.55.49.507460 Instance:db2pinst Node:001
PID:29460(db2ipccm 1) Appid:none
base_sys_utilities sqleGetAgentFromPool Probe:117

DiagData
ffff d605 ....


2004-05-06-05.55.49.535825 Instance:db2pinst Node:001
PID:29460(db2ipccm 1) Appid:none
base_sys_utilities sqleGetAgent Probe:65

Unexpected return code. Remapping... = ffff d605 ....


2004-05-06-05.55.49.589319 Instance:db2pinst Node:001
PID:29460(db2ipccm 1) Appid:none
base_sys_utilities sqleGetAgent Probe:75

Agent not allocated, sqlcode = -1042

Let me know if any one has come across this and what can be the bottleneck?

Prashant -

Did you ever receive a reply or resolution to your SQL30081N / RC = 54 error? I'm asking because I receive this periodically for one of our DB2 instances. I'm thinking that it is related to max. number of agents being exceeded - as the communication function detecting the error is 'create_agent' - same as yours.

Please let me know what you've found. Thanks.