Instance crash on db2 v 8.1.5

[Lana Zapornikova]

We are using DB2 Workgroup Server, v. 8.1, fixpack 5 under Windows
2003
Standart Edition.
There were series of similar instance crashes. At the begining, some
errors appeared in the db2diag.log like:

=================
2004-06-06-17.21.48.671000 Instance:DB2 Node:000
PID:2348(dbm.exe) TID:1696 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:2348 TID:1696 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.
=================
and after a while the instance crashes without additional logging into
the
db2diag.log.

Crash recovery went fine after instance restart.

I opened PMR, and received an answer

The one message that is appearing over and over again is the first
one listed above. That ZRC code indicatest that this is a "Resource
Capacity Error" in buffer pool services. Specifically, this is an
"SQLZ_RC_BPFULL" which means that there are no available buffer pool
pages. The associated SQLCODE is:
SQL1218N There are no pages currently available in bufferpool "".
Could you please tune your bufferpool size and then please let me
know if these messages persist? Thank you.

It sounds to me as a formal answer, which doesn't solve the problem at
all.

Actually, we have 2 separate bufferpools (each about 500 Mb) for
indexes
and data. The bufferpool for indexes is large enough to cache them
all, and
the bufferpool for data can cashe more than 25% of data. All update
transactions are pretty small (not more than 10-20 rows) and only one
application processes them, all heavy selects are issued by
applications
with UR isolation level. We are monitoring
SQL_ELM_POOL_ASINC_DATA/INDEXES_WRITES and
SQL_ELM_POOL_DATA/INDEXES_WRITES
on a regular basis and even before crashes they were still almost
equal, so
as far as I understand, it means that there are a lot of pages that
could be removed from a bufferpool at any given moment.

Occasionally, I changed db2ntworkset from DB2NTWORKSET=1024,2560 to
DB2NTWORKSET=1024,3072, and since that changes everything works fine,
although I did not change any bufferpools parameters.

I am not sure if it is a coincedence or it does cure the problem.

Does enyone have an idea or advice?

[Mark A]

"Lana Zapornikova" <fo******@hotmail.com> wrote in message
news:74**************************@posting.google.c om...

We are using DB2 Workgroup Server, v. 8.1, fixpack 5 under Windows
2003
Standart Edition.
There were series of similar instance crashes. At the begining, some
errors appeared in the db2diag.log like:

=================
2004-06-06-17.21.48.671000 Instance:DB2 Node:000
PID:2348(dbm.exe) TID:1696 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:2348 TID:1696 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.
=================
and after a while the instance crashes without additional logging into
the
db2diag.log.

Crash recovery went fine after instance restart.

I opened PMR, and received an answer

The one message that is appearing over and over again is the first
one listed above. That ZRC code indicatest that this is a "Resource
Capacity Error" in buffer pool services. Specifically, this is an
"SQLZ_RC_BPFULL" which means that there are no available buffer pool
pages. The associated SQLCODE is:
SQL1218N There are no pages currently available in bufferpool "".

Could you please tune your bufferpool size and then please let me
know if these messages persist? Thank you.

It sounds to me as a formal answer, which doesn't solve the problem at
all.

Actually, we have 2 separate bufferpools (each about 500 Mb) for
indexes
and data. The bufferpool for indexes is large enough to cache them
all, and
the bufferpool for data can cashe more than 25% of data. All update
transactions are pretty small (not more than 10-20 rows) and only one
application processes them, all heavy selects are issued by
applications
with UR isolation level. We are monitoring
SQL_ELM_POOL_ASINC_DATA/INDEXES_WRITES and
SQL_ELM_POOL_DATA/INDEXES_WRITES
on a regular basis and even before crashes they were still almost
equal, so
as far as I understand, it means that there are a lot of pages that
could be removed from a bufferpool at any given moment.

Occasionally, I changed db2ntworkset from DB2NTWORKSET=1024,2560 to
DB2NTWORKSET=1024,3072, and since that changes everything works fine,
although I did not change any bufferpools parameters.

I am not sure if it is a coincedence or it does cure the problem.

Does enyone have an idea or advice?

Did you tell IBM support about the changes you made, and that it fixed the
problem?

[Fan Ruo Xin]

Sorry if you already told us. What is your physical mem size?

"Lana Zapornikova" <fo******@hotmail.com> wrote in message
news:74**************************@posting.google.c om...

We are using DB2 Workgroup Server, v. 8.1, fixpack 5 under Windows
2003
Standart Edition.
There were series of similar instance crashes. At the begining, some
errors appeared in the db2diag.log like:

=================
2004-06-06-17.21.48.671000 Instance:DB2 Node:000
PID:2348(dbm.exe) TID:1696 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:2348 TID:1696 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.
=================
and after a while the instance crashes without additional logging into
the
db2diag.log.

Crash recovery went fine after instance restart.

I opened PMR, and received an answer

The one message that is appearing over and over again is the first
one listed above. That ZRC code indicatest that this is a "Resource
Capacity Error" in buffer pool services. Specifically, this is an
"SQLZ_RC_BPFULL" which means that there are no available buffer pool
pages. The associated SQLCODE is:
SQL1218N There are no pages currently available in bufferpool "".

Could you please tune your bufferpool size and then please let me
know if these messages persist? Thank you.

It sounds to me as a formal answer, which doesn't solve the problem at
all.

Actually, we have 2 separate bufferpools (each about 500 Mb) for
indexes
and data. The bufferpool for indexes is large enough to cache them
all, and
the bufferpool for data can cashe more than 25% of data. All update
transactions are pretty small (not more than 10-20 rows) and only one
application processes them, all heavy selects are issued by
applications
with UR isolation level. We are monitoring
SQL_ELM_POOL_ASINC_DATA/INDEXES_WRITES and
SQL_ELM_POOL_DATA/INDEXES_WRITES
on a regular basis and even before crashes they were still almost
equal, so
as far as I understand, it means that there are a lot of pages that
could be removed from a bufferpool at any given moment.

Occasionally, I changed db2ntworkset from DB2NTWORKSET=1024,2560 to
DB2NTWORKSET=1024,3072, and since that changes everything works fine,
although I did not change any bufferpools parameters.

I am not sure if it is a coincedence or it does cure the problem.

Does enyone have an idea or advice?

[Mark Barinstein]

Hello.

I have seen this message ALWAYS on W2003 with both db2 v8.1 ESE and WSE
versions with all fixpacks including FP6 even I was issuing nothing than
fairly small test selects (but without instance crashes). I afraid such
messages and this is one of main reasons why we do not migrate to v8 from v7
because I don't like such situations when I can't understand what is
happening with my database...

Best regards,
Barinstein Mark

We are using DB2 Workgroup Server, v. 8.1, fixpack 5 under Windows
2003
Standart Edition.
There were series of similar instance crashes. At the begining, some
errors appeared in the db2diag.log like:

=================
2004-06-06-17.21.48.671000 Instance:DB2 Node:000
PID:2348(dbm.exe) TID:1696 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:2348 TID:1696 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.
=================
and after a while the instance crashes without additional logging into
the
db2diag.log.

[Lana Zapornikova]

> Did you tell IBM support about the changes you made, and that it fixed the

problem?

Yes, I told them. The comment was "Probably, it might help". Franckly,
I don't understand how, because we have never fallen in swap.

[Lana Zapornikova]

"Fan Ruo Xin" <fa*****@sbcglobal.net> wrote in message news:<FU**************@newssvr32.news.prodigy.com> ...

Sorry if you already told us. What is your physical mem size?

4 Gb with switch /3GB .

All other applicatins are using not more than 200 Mb all together.

Lana

[Lana Zapornikova]

We are running v.7 for about 3 years and v.8 (fixpacks 4 & 5) for
about 8 month on the same hardware under pretty similar load (up to
thousands transaction per minute). We had only one crash of v.7 and
about one crash per month with v.8 without any proper logging.

So, from my personal feelings, v8 is not quite stable till fixpack 5.

Lana

"Mark Barinstein" <ma**@NO.SPAM.ANY.MOREcrk.vsi.ru> wrote in message news:<cc**********@serv.vrn.ru>...

Hello.

I have seen this message ALWAYS on W2003 with both db2 v8.1 ESE and WSE
versions with all fixpacks including FP6 even I was issuing nothing than
fairly small test selects (but without instance crashes). I afraid such
messages and this is one of main reasons why we do not migrate to v8 from v7
because I don't like such situations when I can't understand what is
happening with my database...

Best regards,
Barinstein Mark

We are using DB2 Workgroup Server, v. 8.1, fixpack 5 under Windows
2003
Standart Edition.
There were series of similar instance crashes. At the begining, some
errors appeared in the db2diag.log like:

=================
2004-06-06-17.21.48.671000 Instance:DB2 Node:000
PID:2348(dbm.exe) TID:1696 Appid:none
oper system services sqloSSemClose Probe:20

Unexpected system error 0x6 has occurred.
This has been mapped to ZRC 0x83000006.

PID:2348 TID:1696 Node:000 Title: SYSTEM ERROR DESCRIPTION
The handle is invalid.
=================
and after a while the instance crashes without additional logging into
the
db2diag.log.

[Mark Barinstein]

We are running v7 at FP10a. It is quite stable at this level. FP11 was a
"fixbug" for our system because some queries worked fine started to crash
instance. After that a afraid to install any fixes without full testing of
the system.
v8 with FP4 also crashed on tests and now when FP6 was issued, we have
started to test our system again...

We are running v.7 for about 3 years and v.8 (fixpacks 4 & 5) for
about 8 month on the same hardware under pretty similar load (up to
thousands transaction per minute). We had only one crash of v.7 and
about one crash per month with v.8 without any proper logging.

So, from my personal feelings, v8 is not quite stable till fixpack 5.

Lana

[Fan Ruo Xin]

Sorry. Do you mean 4G physical mem + 3G switch or 1G physical mem + 3G
switch?

"Lana Zapornikova" <fo******@hotmail.com> wrote in message
news:74**************************@posting.google.c om...

"Fan Ruo Xin" <fa*****@sbcglobal.net> wrote in message

news:<FU**************@newssvr32.news.prodigy.com> ...

Sorry if you already told us. What is your physical mem size?

4 Gb with switch /3GB .

All other applicatins are using not more than 200 Mb all together.

Lana