Can't connect to Database DB2

[Former Member]

Dear All

I try connect to Database DB2 but it is problem

"SQL1224N The database manager is not able to accept new requests, has

terminated all requests in progress, or has terminated your particular request

due to a problem with your request. SQLSTATE=55032"

This is my information system

Windows 2003 64bit,DB2 9.0 FP4,SAP ECC 6.0,SR3

Thanks

[Former Member]

Dear kiran kumar vej...

This is my db2diag.log

2008-09-30-14.19.31.984000+420 I47301380F406 LEVEL: Event

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 3104 0000 1...

2008-09-30-14.19.31.984000+420 I47301788F289 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2008-09-30-14.19.32.000000+420 E47302079F430 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST 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.

2008-09-30-14.19.32.000000+420 I47302511F395 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x000000000707FC44 : 36FB FFFF 6...

Thanks

[Former Member]

Hello Phuc,

It seems some memory problem in your machine. Please paste the log from db2diag.log it will help to help you.

Thanks,

Kiran.

[Former Member]

Dear Beck Tang

I use SAP DB2 on Windows 64 bit,don't use AIX,Please help me command line increase this parameter on Windows

Thanks

[malte_schuenemann]

maxuproc does not exist on Windows.

You talked about the SQL5005C error - can you run

db2 list db directory # I think this reproduces the SQL5005C, right =?

and show the entry in the db2diag.log from the time the error occurred ?

Regards, Malte

[former_member640873]

Hi Phuc,

Sorry I didn't read carefully the top part of your question.

Here is what your sqleGetAgent, probe:19 error mean:

The agent count has gone over the maxagents setting in the dbm config but a system application has been allowed to use an overflow agent. A system application could be something like online reorg, stmm, event monitor, etc.

The hex number dumped is the current agent count. In this case, the agent count was 1067, 1068, and 1069.

So, you may want to check your maxagent setting to see if you have enough agents. In database snapshot (db2 get snapshot for database on <sid>), you can find the following fields that tells you the high water mark of agents usage:

Maximum agents associated with applications= 22

Maximum coordinating agents = 22

You can check the database snapshot after a reasonable amount of workload is run to get an idea at most how many agents are needed in your system.

Regards,

[Former Member]

Dear Beck Tang

I can't find "AIX maxuproc" parameter.

Thanks

[former_member640873]

Hi Phuc,

You can check the current setting of maxuproc with the command:

lsattr -E -l sys0

and change the setting with:

chdev -l sys0 -a maxuproc='nn'

where nn is the new integer value of maxuproc

I found a website that talks about it:

[http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/maxuproc-on-f50-207349|http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/maxuproc-on-f50-207349]

Regards,

[Former Member]

Dear Sergiy Malikov

SAP Application can't connect DB2 database.Please help me

Thanks

[former_member640873]

Hi Phuc,

Have you checked the AIX maxuproc? If it is set too low, this problem may occur.

Regards,

[Former Member]

Hello,

is the database working at all (i.e., SAP system on top of it, connected SAP or DB2 users...) ??

It is strange that the connection to DB does not work, agents pool is empty (10 of max. 1000 agents), "list db directory" returns errors etc...

If the database was recently migrated/restored/reconfigured/..., could you please provide the details?

Thanks.

Kind regards,

Sergiy Malikov.

[Former Member]

Dear Frank

This is my problem "SQL5005C System Error" when run this parameter

Could I configure incorrect Configuration Assistant Tool

Please help me configure this tool

Thanks

[Former Member]

Dear Sergiy Malikov

2008-09-30-15.54.20.109000+420 I47428052F406 LEVEL: Event

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 2B04 0000 +...

2008-09-30-15.54.20.125000+420 I47428460F406 LEVEL: Event

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 2C04 0000 ,...

2008-09-30-15.54.20.125000+420 I47428868F406 LEVEL: Event

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 2D04 0000 -...

2008-09-30-15.54.20.125000+420 I47429276F406 LEVEL: Event

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 2E04 0000 ....

2008-09-30-15.54.20.140000+420 I47429684F406 LEVEL: Event

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 2F04 0000 /...

2008-09-30-15.54.20.140000+420 I47430092F406 LEVEL: Event

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 3004 0000 0...

2008-09-30-15.54.20.156000+420 I47430500F406 LEVEL: Event

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 3104 0000 1...

2008-09-30-15.54.20.156000+420 I47430908F289 LEVEL: Error

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2008-09-30-15.54.20.156000+420 E47431199F430 LEVEL: Error

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST 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.

2008-09-30-15.54.20.171000+420 I47431631F395 LEVEL: Error

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x0000000006E6FC44 : 36FB FFFF 6...

Thanks

[Frank-Martin]

Hi,

have you cataloged your database in an endless loop?

Please provide the output of the following commands:

db2 list db directory

db2 list node directory

Regards

Frank

[Former Member]

Hello,

this does not look like an overloaded system with many connections (agents pool is only used for approx. 1 percent! ).

If you try to connect again now, do you see the similar error messages as earlier?

If they are different from earlier messages, could you please post the new error messages from db2diag.log?

Thank you.

Kind regards,

Sergiy Malikov.

[Former Member]

Dear Sergiy Malikov

High water mark for agents registered 1074

Agents registered 10

Idle agents 9

High water mark for coordinating agents 1074

Agents stolen from another application 0

Max agents overflow 7

Thanks

[Former Member]

Hello,

and how do other parameters (agents high water mark, etc...) look like?

Is the amount of registered agents close to the "high water mark for agents" ?

Anyway, you can try to temporarily increase the MAXAGENTS and MAX_COORDAGENTS parameters by approx. 10-20% to see if this will help.

Another question: did you see some applications in the application snapshot which require lots of agents? Depending on the situation, such applications might need to be restarted.

Kind regards,

Sergiy Malikov.

[Former Member]

Dear Sergiy Malikov

I find this parameter

Agents stolen from another application = 0

Please help me,Must I change value of parameter???

Thanks

[Former Member]

update, another idea:

obtain the dbm snapshot:

db2 "get snapshot for database manager" > dbm.snap

...and look for the following lines:

(could you also post them here please?)

High water mark for agents registered

Agents registered

Idle agents

High water mark for coordinating agents

Agents stolen from another application

Max agents overflow

If you find that the counter "Agents stolen from another application" is non-zero, you can try to increase the number of agents available to the database manager ( MAXAGENTS and/or MAX_COORDAGENTS as appropriate).

You can update these parameters by issuing the following command:

db2 update db cfg for <database_name> using MAXAGENTS <larger_value>

db2 update dbm cfg using MAX_COORDAGENTS <larger_value>

Kind regards,

Sergiy Malikov.

[Former Member]

Hello,

you can issue the command

db2 activate db <database_name>

to activate the db prior to executing the db2pd command.

And try to take the application snapshot (i've described this command earlier in this thread) to look at the "Maximum associated agents", "Number of agents working on statement" and similar parameters which describe the number of agents which are reserved by every application.

Kind regards,

Sergiy Malikov.

[Former Member]

Dear Edgardo Koenig

values of the MAX_CONNECTIONS and MAX_COORDAGENTS

Max number of existing agents (MAXAGENTS) = 1024

Agent pool size (NUM_POOLAGENTS) = 10

Initial number of agents in pool (NUM_INITAGENTS) = 5

Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS

Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS

Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

Because MAX_CONNECTIONS assign 1024

Thanks

[Former Member]

Dear All

when i run this parameter " db2pd -db TST -dbcfg" which is problem

Database TST not activated on database partition 0.

Option -dbcfg requires -db <database> or -alldbs option and active database.

Thanks

[Former Member]

Dear All

This is my log

2008-09-30-14.19.31.984000+420 I47301380F406 LEVEL: Event

PID : 4796 TID : 6928 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19

DATA #1 : String, 37 bytes

Agent overflow for system application

DATA #2 : Hexdump, 4 bytes

0x000000000541E364 : 3104 0000 1...

2008-09-30-14.19.31.984000+420 I47301788F289 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70

MESSAGE : Agent not allocated, sqlcode = -1226

2008-09-30-14.19.32.000000+420 E47302079F430 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST 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.

2008-09-30-14.19.32.000000+420 I47302511F395 LEVEL: Error

PID : 4796 TID : 6924 PROC : db2syscs.exe

INSTANCE: DB2TST NODE : 000

FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126

MESSAGE : Return code from sqleGetAgent =

DATA #1 : Hexdump, 4 bytes

0x000000000707FC44 : 36FB FFFF 6...

Thanks

[Former Member]

Hello,

what is your MAXAPPLS setting ?

The possible problem reason is the low MAXAPPLS setting which prevents the database from opening new connections...

db2pd -db <database_name> -dbcfg

... and search for MAXAPPLS

Furthermore, you can get the application snapshot by issuing:

db2 get snapshot for all applications > appl_snap.out

... and then search the file appl_snap.out for the string "Maximum associated agents" to see whether one certain application is using too many agents.

Kind regards,

Sergiy Malikov.

[Former Member]

Hi Phuc,

From the last entries in your diag.log file, it seems, that your problem is caused because your reached the maximum number of agents available to handle connections to your database. See the description of the error message -1226:

db2 "? SQL1226N"


SQL1226N The maximum number of client connections are already
          started.

Explanation:

The number of client connections is already equal to the maximum
value defined in the system configuration file.

 The operation cannot be processed.

User Response:

Wait for other applications to disconnect from the database.  If
one or more applications are required to run concurrently,
increase the value for max_connections.  The new value takes
effect after the next successful database manager start. If the
value for max_connections is larger than the value for
max_coordagents, the concentrator feature is turned on.

 sqlcode :  -1226

 sqlstate :  57030

As your instance name is DB2TST, I would tend to assume that it is a test system and maybe the configuration of DB2 is not proper to handle many requests. Therefore, could you please provide the values of the MAX_CONNECTIONS and MAX_COORDAGENTS by issuing the command:

db2 get dbm cfg | grep MAX_

Hope this helps

Best regards, Edgardo

[Former Member]

Hello,

ist this problem reproducible? i.e., do you often get this error if you try to connect??

Usually this problem occurs once after one of the DB2 processes terminates, but after repeating the CONNECT statement everything works well...

Kind regards,

Sergiy Malikov.

[Frank-Martin]

Take a look at the latest db2diag.log entries.

Regards

Frank