db2diag.log error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Asphalt Blazer - 23 Jun 2006 20:31 GMT

2006-06-23-12.13.27.709127 Instance:db2inst1 Node:000

PID:3657742(db2agent (MCNVNET1) 0) TID:1
Appid:GA010520.A60B.027D43131542

access plan manager sqlra_cache_mem_please Probe:20
Database:MCNVNET1

ADM4500W A package cache overflow condition has occurred. There is no
error

but this indicates that the package cache has exceeded the configured
maximum

size. If this condition persists, you may want to adjust the
PCKCACHESZ DB

configuration parameter.

This is an error I got while looking in the db2diag.log. My databases
were not connecting and I had to do a db2stop and db2start to get
connected back. Does anybody know if this error is the reason and can
somebody suggest a workaround for this? thanks

Reply to this Message

Pierre Saint-Jacques - 24 Jun 2006 21:02 GMT

Alittle help as in: What DB2 are you using and what level. Please do a:
db2level to tell us.
No this should not be the cause of not being able to connect.
Thw W in the message no tells youits a warning.
The package cache is used to stored packages tied to applications as wells
as the compiled dynamic SQL stmts at execution.

In DB2 for LUW at V8, this parameter is dynamically changed as needed until
DB2 database_mmemory parm. is reached. Fronm then on, until packages and/or
statements can be flushed, DB2 will store compiled stmts in appl.
coordinator agent private memory.

Something else caused your db to become unconnectable.
HTH, P

Signature

Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515

> 2006-06-23-12.13.27.709127 Instance:db2inst1 Node:000
>
[quoted text clipped - 19 lines]
> connected back. Does anybody know if this error is the reason and can
> somebody suggest a workaround for this? thanks

Reply to this Message