Problem(Abstract)

ASLR or Address Space Layout Randomization is a feature that is activated by default on some of the newer linux distributions. It is designed to load shared memory objects in random addresses.

In DB2, multiple processes map a shared memory object at the same address across the processes. It was found that DB2 cannot guarantee the availability of address for the shared memory object when ASLR is turned on.
 

Symptom

This conflict in the address space means that a process trying to attach a shared memory object to a specific address may not be able to do so, resulting in a failure in shmat subroutine. However, on subsequent retry (using a new process) the shared memory attachment may work. The result is a random set of failures. Some processes that have been known to see this error are: db2pd, db2egcf, and db2vend.


Some of the behaviors seen include the following:
For the db2pd command, it will report no data found even through the instance / database is active:
Database SAMPLE not activated on database partition 0.

For the db2egcf process, used for HA monitoring, the db2egcf may incorrectly determine the instance is down and initiate a failover.

For the db2vend process, backup and log archive methods might fail with an error indicating a child process could not be started:
SQL2043N Unable to start a child process or thread.
 

Diagnosing the problem

When this problem is suspected, check db2diag.log for the shmat failure like the following. Note that the same error message can also occur for a different cause. Hence, it's important to note the process that reported this error.

FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:180
MESSAGE : ZRC=0x850F0005=-2062614523=SQLO_NOSEG
"No Storage Available for allocation"
DIA8305C Memory allocation failure occurred.
CALLED : OS, -, shmat OSERR: EINVAL (22)
 

Resolving the problem

Turn off the randomization by setting the following kernel parameter:

kernel.randomize_va_space=0

Or temporarily disable it and restart the db2 instance:

echo 0 > /proc/sys/kernel/randomize_va_space

Be aware that, although there is an effort to ease the pain of this limitation by supporting ASLR for "selective" executables for future releases of DB2, it is still recommended to turn off ASLR.

SOURCE:https://www-304.ibm.com/support/docview.wss?uid=swg21365583