DB2 8.2
Windows Server 2000
3 GB RAM

Hi All,

I am having a problem with the offline backups that are running. In the output I receive a SQL0902C A system error (reason code = "242") occurred.

When looking at the db2diag.log I notice the recurring message saying "no resources to create process or thread"... The specs on this server are absolutely dismal - so its pretty tough trying to work with what I've got

I noticed the DBHEAP parameter is set to 4096, the UTIL_HEAP_SZ has been set to 500,000..... Would increasing the DBHEAP parameter help my situation?

Db2diag.log follows:

2011-08-20-23.47.20.390000+120 E58998545H384 LEVEL: Error
PID : 2036 TID : 5304 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
APPHDL : 0-876 APPID: *LOCAL.DB2.110820214716
FUNCTION: DB2 UDB, base sys utilities, sqleInstanceQuiesce, probe:2
MESSAGE : ADM7501W Instance quiesce request has completed successfully.

2011-08-20-23.47.27.062000+120 I58998931H376 LEVEL: Warning
PID : 2036 TID : 3228 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:2028
MESSAGE : Starting an offline db backup.

2011-08-21-02.34.12.968000+120 I58999309H434 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDirectRead, probe:830
RETCODE : ZRC=0x870F00F2=-2029059854=SQLO_NORES
"no resources to create process or thread"

2011-08-21-02.34.13.750000+120 I58999745H435 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDirectRead, probe:830
MESSAGE : Obj={pool:5;obj:2;type:1} State=x27 Page=540672 Cont=0 Offset=540672
BlkSize=12

2011-08-21-02.34.13.765000+120 I59000182H675 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
MESSAGE : SQLB_OBJECT_DESC
DATA #1 : Hexdump, 68 bytes
0x7F9D6E18 : 0500 0200 0500 0200 0100 0000 0524 31F0 .............$1.
0x7F9D6E28 : 5B19 0000 0000 0000 0000 0000 0000 0000 [...............
0x7F9D6E38 : 0000 0000 0101 0000 2700 0000 0000 0000 ........'.......
0x7F9D6E48 : 0010 0000 4000 0000 0400 0000 0500 0201 ....@...........
0x7F9D6E58 : F076 C549 .v.I

2011-08-21-02.34.13.781000+120 I59000859H431 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, buffer pool services, sqlbDirectRead, probe:830
RETCODE : ZRC=0x870F00F2=-2029059854=SQLO_NORES
"no resources to create process or thread"

2011-08-21-02.34.13.781000+120 I59001292H376 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, buffer pool services, sqlbDirectRead, probe:830
MESSAGE : Obj={pool:5;obj:2;type:1} State=x27

2011-08-21-02.34.13.796000+120 I59001670H675 LEVEL: Error
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
MESSAGE : SQLB_OBJECT_DESC
DATA #1 : Hexdump, 68 bytes
0x7F9D6E18 : 0500 0200 0500 0200 0100 0000 0524 31F0 .............$1.
0x7F9D6E28 : 5B19 0000 0000 0000 0000 0000 0000 0000 [...............
0x7F9D6E38 : 0000 0000 0101 0000 2700 0000 0000 0000 ........'.......
0x7F9D6E48 : 0010 0000 4000 0000 0400 0000 0500 0201 ....@...........
0x7F9D6E58 : F076 C549 .v.I

2011-08-21-02.34.13.812000+120 I59002347H432 LEVEL: Severe
PID : 2036 TID : 4148 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, database utilities, sqlubreadreg, probe:32
MESSAGE : DiagData
DATA #1 : Hexdump, 2 bytes
0x7F9D88E8 : 0500 ..

2011-08-21-02.34.30.953000+120 I59006434H351 LEVEL: Severe
PID : 2036 TID : 3228 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ECD
APPHDL : 0-870 APPID: *LOCAL.DB2.110820214720
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:140
MESSAGE : Backup Terminated.


Any help would be greatly appreciated.

Rich.

https://www-304.ibm.com/support/docv...id=swg21223949

Not an exact match, but close enough. Have you see this ?

Thank you for the quick responce. The server was rebooted on Monday, but i will give the DB2NTNOCACHE parameter a try..

If anything, it will make it worse. 500000 pages is almost 2 GB. Set it to 5000 and retry.

Thanks, which parameter must I change to 5000 though? DBHEAP or UTIL_HEAP_SZ?

Ok never mind - you obviously mean the UTIL_HEAP_SZ...

Hi Ya'll

Just wanted to say that we resolved this issue by getting the storage guys to add 500 GB disk space to the server, and backed up to disk instead of using their 3rd party software to backup to tape. I'm thinking that their software was creating too many agents on the server or something?

What a relief... except accidentally left the db in quiesce mode this morning - woops...

Anyway thanks for the responses.

If this error comes back, check the FILE SYSTEM CACHING option for your tablespaces ( you can use "db2pd -d <db name> -tab" ) and try disabling it as per the technote provided by sathyaram_s (exclude tablespaces with LOB/LF).

Thanks db2Girl! - that will helpful.

When I was checking the server today, I noticed there are like 50 processes called db2bp.exe running in Task Manager. If check in db2 with list applications there's only about 4 with application db2bp?

As I understand it, these processes would be created during the connection to the DB from the command line, but obviously they are not disconnecting from the DB correctly with the Terminate command?

What I would like to know is, would it be safe if I end these db2bp.exe processes in task manager?

They are taking up a lot of memory in my constrained environment, and the numbers of these processes seem to increase day by day.

if they are in uow waiting and last operation is commit - save to force

Hi Guys,

Just wanted to let you know that the problem returned (like db2girl said it would) and was getting progressively worse... I then updated the DB2NTNOCACHE parameter to yes, and since then it has worked ever since.

Thank you all for your help. Peace.