DB2 10.5 FP8 issues same messages milliions of times in a day

Skip to first unread message


Jul 13, 2020, 7:46:52 AM7/13/20
All -

DB2 for LUW, 10.5 FP8 under Aix 7.1, HADR enabled

So I restored a database to the production environment on a Saturday afternoon 3 weeks ago... the restore failed and immediately I get this millions of times a day generating gigabytes of errors...

This is production... can't just start and stop at anytime.

The DB2 instance diag log file /home/db2inst1/sqllib/db2dump/db2diag.log obviously grows enormously so I wrote a script that essentially removes db2diag.log file to keep from filling the file system.

I'm thinking that something whacked the binaries and that

"db2iupgrade -u db2fenc1 db2inst1"

will fix it... essentially push the IBM supplies binaries.

Of course we're out-of-support on 10.5 like so many users but I warned management 15 months ago to upgrade. Problem is Oracle (publishers of E1/OpenWorld) hasn't specified which 11.1 release will be supported so management decided to wait. I can't fault them for the decision but probably any 11.1 fix pack would be ok.

What's your thought... will "db2iupgrade -u db2fenc1 db2inst1" fix this? I bet it will...

We could also fail-over to the HADR standby but E1/OpenWorld doesn't fail-over automatically and we have to actually uncatalog/catalog the node/database entries to get this to work.

Getting desperate.

2020-07-12- I12396633A415 LEVEL: Error
PID : 66715660 TID : 1 PROC : db2
INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
FUNCTION: DB2 UDB, command line process, clp_send_bpreq, probe:4
MESSAGE : Error returned from SQLOWQUE:
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFCB90 : 870F 003E ...>

2020-07-12- E12397049A670 LEVEL: Error (OS)
PID : 53543182 TID : 1 PROC : db2
INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
FUNCTION: DB2 UDB, oper system services, sqlowqueInternal, probe:40
MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad Queue Handle"
DIA8555C An invalid message queue handle was encountered.
CALLED : OS, -, msgsnd
OSERR : EINVAL (22) "Invalid argument"
DATA #1 : system V message queue identifier., PD_TYPE_SYSV_QUEUE_ID, 4 bytes
DATA #2 : Pointer, 8 bytes
DATA #3 : unsigned integer, 8 bytes


Jul 14, 2020, 10:26:20 AM7/14/20
Upgrade will not help.
Did you clean up the failed database? It looks like issue communicating with db2 command line processor. Is the old restore script still running?
Look for the PID of the process generating the error and see if this is db2 agent or clp (reference using db2pd -edu )
Its always best to restore to a new instance (for future reference).
Reply all
Reply to author
0 new messages