Re: db2 error ( Agent not allocated, sqlcode = -1225 )

From: Michael Austin <maustin_at_firstdbasource.com>
Date: Tue, 11 Mar 2008 04:31:18 GMT
Message-ID: <qWnBj.13749$5K1.13512@newssvr12.news.prodigy.net>


DA Morgan wrote:

> oracle_db2_dba wrote:

>> Hi,
>>
>> We are getting following errors in diaglog. We have 4096 value as
>> MAXAGENTS and 512 for maxuproc
>> I am confused as which value we are hitting. are we hitting OS
>> ( maxuproc ) value or MAXAGENTS.
>> is there anything else i am missing which need to be looked into ?
>> -----------------------------------------------------------
>> 2008-03-07-10.41.59.535278-300 I46678299C345 LEVEL: Severe
>> PID : 307324 TID : 1 PROC : db2tcpcm 0
>> INSTANCE: db2inst1 NODE : 000
>> FUNCTION: DB2 UDB, oper system services, sqloCreateEDU, probe:5
>> MESSAGE : DiagData
>> DATA #1 : Hexdump, 4 bytes
>> 0x2FF194E8 : 0000 000B ....
>>
>> 2008-03-07-10.41.59.543759-300 I46678645C343 LEVEL: Severe
>> PID : 307324 TID : 1 PROC : db2tcpcm 0
>> INSTANCE: db2inst1 NODE : 000
>> FUNCTION: DB2 UDB, base sys utilities, sqleCreateNewAgent, probe:25
>> RETCODE : ZRC=0x870F00F2=-2029059854=SQLO_NORES
>> "no resources to create process or thread"
>>
>> 2008-03-07-10.41.59.544311-300 I46678989C351 LEVEL: Severe
>> PID : 307324 TID : 1 PROC : db2tcpcm 0
>> INSTANCE: db2inst1 NODE : 000
>> FUNCTION: DB2 UDB, base sys utilities, sqleGetAgentFromPool, probe:30
>> MESSAGE : DiagData
>> DATA #1 : Hexdump, 4 bytes
>> 0x2FF19984 : FFFF FB37 ...7
>>
>> 2008-03-07-10.41.59.544469-300 I46679341C282 LEVEL: Error
>> PID : 307324 TID : 1 PROC : db2tcpcm 0
>> INSTANCE: db2inst1 NODE : 000
>> FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70
>> MESSAGE : Agent not allocated, sqlcode = -1225
>>
>> 2008-03-07-10.41.59.560744-300 E46679624C421 LEVEL: Error
>> PID : 307324 TID : 1 PROC : db2tcpcm 0
>> INSTANCE: db2inst1 NODE : 000
>> FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:
>> 125
>> MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol
>> support.
>> A possible cause is that the maximum number of agents has
>> been
>> exceeded.
>> ------------------------------------------------------------------------------------------------------
>>
>> regards
> 
> Well I'm confused as to why you think someone at c.d.oracle.server would
> know much about DB2 UDB.
> 
> Well I guess with Serge spending more time here than in the DB2 space
> perhaps you're right. <g>
> 
> Sorry but if you lob 'em over the net I just have to return 'em.

seems like the DB2 so-called DBA's have the same problem as a lot of dba's in this forum. The inability to use google.

http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&dc=DB520&uid=swg21202489&loc=en_US&cs=UTF-8&lang=enclass=

Hmmmmm will you look at that - that same error message on an IBM site of all places... Imagine that. Received on Mon Mar 10 2008 - 23:31:18 CDT

Original text of this message