| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC81649 | Status: Closed |
DB2START FAILS WITH SQL10003 ON SOLARIS 10, SPARC T4 PROCESSOR WITH 2GB PAGE SIZE SUPPORT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
db2start fails with SQL10003 due to attaching the FMP memory set
to an invalid address on the Solaris 10 / Sparc T4 processor
combination with 2GB page size support. Solaris 10 update 4
(kernel patch 147440-04) enables 2GB pages by default.
The problem is due to an inconsistency in the way DB2 rounds up
shared segment sizes and then calculates the attach addresses of
"fixed address" segments. With 2GB page sizes available, DB2
tries to attach a shared memory segment at an address that is in
use by a previously attached segment. This is independent of
the actual backing page size used, it only matters what the
largest page size is determined to be available on the system
from the Solaris getpagesizes API.
expected db2diag.log messages:
2012-02-18-13.04.43.276604-360 I8210A728 LEVEL: Severe
PID : 17832 TID : 2 PROC : db2sysc
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap,
probe:60
MESSAGE : Failed to create the memory segment used for
communication with
fenced routines. If re-starting db2, ensure no db2fmp
processes were
on the instance prior to start. Otherwise, you can
adjust this value
through DB2_FMP_COMM_HEAPSZ db2set value, or by
decreasing your
ASLHEAPSZ setting.
DATA #1 : Hexdump, 8 bytes
0xFFFFFFFF603FCDB8 : 0000 0000 015E 8480
.....^..
...
2012-02-18-13.04.43.278198-360 I9653A320 LEVEL: Severe
PID : 17832 TID : 2 PROC : db2sysc
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2sysc
FUNCTION: DB2 UDB, oper system services, sqloWatchDogSetup,
probe:60
MESSAGE : ZRC=0xFFFFD8ED=-10003
...
2012-02-18-13.04.43.288489-360 I10469A906 LEVEL: Error
PID : 17827 TID : 2 PROC : db2wdog
0
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:10
MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
memory addr"
DIA8561C A invalid memory block was encountered.
DATA #1 : Pointer, 8 bytes
0x0000000000000000 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Hardware: SPARC T4 * * Software: Solaris 10 with 147440-04 patch installed. This * * patch (or any one above) enables 2 GB memory pages. * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 instance cannot be started with error message : * * SQL10003C There are not enough system * * resources to process the request. The request cannot be * * processed. * * SQL1032N No start database manager command was issued. * * SQLSTATE=57019 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
Problem first fixed in DB2 Version 9.7 Fix Pack 6 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC81653 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.02.2012 02.08.2012 07.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|