Friday, 15 March 2013

Detected kernel config that is incompatible with DB2 NUMA support

If you see: -

$ db2start

03/15/2013 13:57:23     0   0   SQL1042C  An unexpected system error occurred.
SQL1032N  No start database manager command was issued.  SQLSTATE=57019


$ cat /home/db2inst1/sqllib/db2dump/db2diag.log 

2013-03-15-13.57.23.036789+000 E3499E346           LEVEL: Severe
PID     : 25653                TID  : 140078121195296PROC : db2star2
INSTANCE: db2inst1             NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloKADetermineNUMASupport, probe:50
DATA #1 : <preformatted>
Detected kernel config that is incompatible with DB2 NUMA support.


when attempting to start DB2 9.7 ( with/out fix pack 7 ), it's possible that you've just got an incompatible Linux/kernel combination.

I saw this on a colleague's laptop today. He's running: -

$ cat /etc/redhat-release 

Red Hat Enterprise Linux Workstation release 6.3 (Santiago)

$ uname -a

Linux oc8250714684.ibm.com 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Nov 28 19:02:25 CET 2012 x86_64 x86_64 x86_64 GNU/Linux

I experimented with: -

$ db2set DB2_RESOURCE_POLICY=

following a bunch of IBM Technotes, including this one: -


but to no avail.

In the end, I took the wimp's way out, and installed DB2 10 instead.

There's probably a much simpler answer, but I couldn't work it out ……. and decided to triage my time, rather than spending hours and hours playing hacking working around it.


No comments: