Db2 LUW Diag Log reports "Resource temporarily unavailable" in AIX machine
Hi All
I have noticed a OS error in my diag log and i also notice that HADR is not in sync during this period.
From error message, I am not completely clear which resource is unavailable ?
I suspect that Network is not good during that time.
Will there be chance for any other resources?
How to dig it further?
Its an AIX machine.
Below is the DIAG log piece.
2017-12-23-07.11.34.627255
PID : 57018777 TID : 200 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 258 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services, sqlorqueInternal, probe:9
MESSAGE : ZRC=0x870F0041=-2029060031
DIA8557C No message was sent using the message queue.
CALLED : OS, -, select
OSERR : EAGAIN (11) "Resource temporarily unavailable"
I have noticed a OS error in my diag log and i also notice that HADR is not in sync during this period.
From error message, I am not completely clear which resource is unavailable ?
I suspect that Network is not good during that time.
Will there be chance for any other resources?
How to dig it further?
Its an AIX machine.
Below is the DIAG log piece.
2017-12-23-07.11.34.627255
PID : 57018777 TID : 200 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 258 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services, sqlorqueInternal, probe:9
MESSAGE : ZRC=0x870F0041=-2029060031
DIA8557C No message was sent using the message queue.
CALLED : OS, -, select
OSERR : EAGAIN (11) "Resource temporarily unavailable"
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is the first I've heard of the error occurring on a 64 bit system. The 32-bit systems could have the message queue fill if the size of the queue exceeded the tuning parameter, but I thought that the 64-bit systems weren't subject to the same limitation.
Here's a link to some IBM documentation that describes some critical tuning parameters for DB2. MSGMAX (the size of the message queue) should be at least 65K. Though I suspect that no value is guaranteed large enough if, as you suspect, there is a network issue at the time the error is detected.
https://www.ibm.com/support/knowledgecenter/en/SSZJPZ_11.5.0/com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/wsisinst_kernel_parameters_linux_unix.html
Kent
Here's a link to some IBM documentation that describes some critical tuning parameters for DB2. MSGMAX (the size of the message queue) should be at least 65K. Though I suspect that no value is guaranteed large enough if, as you suspect, there is a network issue at the time the error is detected.
https://www.ibm.com/support/knowledgecenter/en/SSZJPZ_11.5.0/com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/wsisinst_kernel_parameters_linux_unix.html
Kent
ASKER
As per the given IBM link, for AIX default kernel values are suffice, and below are my ulimit values
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user) unlimited
Will that error message comes if there is network fluctuation?
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user) unlimited
Will that error message comes if there is network fluctuation?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!!! will check it out.
You're welcome!
ASKER
Thanks for your inputs.
ASKER
64