Re: db2 error ( Agent not allocated, sqlcode = -1225 )
Date: Tue, 11 Mar 2008 22:57:43 +0100
Message-ID: <47d70056$0$14346$e4fe514c@news.xs4all.nl>
Michael Austin wrote:
> 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.
Confused?
http://en.wikipedia.org/wiki/Soap_(TV_series)
You (Daniël) should have known by now there are DBA's administering more than one RDBMS.
>> >> Well I guess with Serge spending more time here than in the DB2 space >> perhaps you're right. <g>
This is like saying you (Daniël again) spend more time in the DB2 ng than in
this one.
As a mather of fact, Serge already answered this same question on
c.d.ibm-db2
>> >> 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.
A bold conclusion, based on just this one incident. And what's a "DB2 so-called DBA"?
> > 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.
Nope, not the same issue. Imagine that.
You probably googled for "ADM7009E"?
Unfortunately that's not sufficient, you also have to take the SQL error
code into account.
The link you provided leaves little doubt about the SQL code for which the given solution is applicable:
SQL1226N --> sqlcode = -1226
which isn't exactly the same as the OP is encountering:
sqlcode = -1225 --> SQL1225N
"The request failed because an operating system process, thread, or swap
space limit was reached".
Of course this can be easily found in the appropriate docs (given the version and paltform are supplied, which the OP failed to do), and/or via a simple Google--search for "SQL1225N" ... ;-)
Cheers.
-- Jeroen [DB2+Oracle DBA]Received on Tue Mar 11 2008 - 16:57:43 CDT