Hitachi

Hitachi Advanced Database Messages


KFAA40002-E

An error occurred during access to the HADB system shared memory. (information = aa....aa) (M)

An error occurred when shared memory was accessed.

aa....aa: Cause of the error
  • System call error, system call = "bb....bb", errno = cc....cc

    A system call error has occurred.

    bb....bb: Name of system call in which the error occurred

    cc....cc: Error number

  • Shared memory management table overflow

    The amount of shared memory managed by HADB has exceeded the preset limit.

  • Shared memory address is not 4096 boundery

    The top address of the acquired shared memory area does not fall on a 4,096 byte boundary.

  • The system does not have the capability to use HugePages

    The system does not have the capability to use HugePages.

  • The system can not use HugePages

    The system cannot use HugePages.

  • RLIMIT_MEMLOCK error

    The size of shared memory that the HADB server attempted to obtain exceeds the value of kernel parameter RLIMIT_MEMLOCK. Alternatively, the user does not have privileges necessary to obtain the shared memory.

  • The value of adb_sys_memory_limit in the server definition exceeds the size of shared memory that is available as HugePages

    The value specified for the adb_sys_memory_limit operand in the server definition exceeds the size of shared memory to be allocated as HugePages.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message. Then, re-execute the command.

  • If the cause of the error indicated by aa....aa is System call error, system call = "bb....bb", errno = cc....cc

    Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error.

    This message might be displayed if a command is executed while the HADB server is starting or terminating. If this is the case, re-execute the command.

    If shmat is output for the system call name and EINVAL is output for the error number in an environment that uses HugePages, check the server definition's adb_sys_shm_huge_page_size operand. Check whether the value specified for this operand is an even multiple of the page size of HugePages as specified in the OS.

    If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

  • If the cause of the error indicated by aa....aa is Shared memory management table overflow

    The HADB server has acquired too much shared memory.

    There might be too many global buffers. Carefully review the number of server definition adbbuff operands and the values specified for these options.

  • If the cause of the error indicated by aa....aa is Shared memory address is not 4096 boundery

    Specify a multiple of 4,096 for kernel parameter SHMLBA.

  • If the cause of the error indicated by aa....aa is The system does not have the capability to use HugePages

    Specify the group ID of the group for the HugePages user for kernel parameter hugetlb_shm_group.

  • If the cause of the error indicated by aa....aa is The system can not use HugePages

    Carefully review whether the environment can use HugePages, the kernel version, and the appropriate settings.

  • If aa....aa is RLIMIT_MEMLOCK error

    Revise the value of kernel parameter memlock.

  • If the cause of the error indicated by aa....aa is The value of adb_sys_memory_limit in the server definition exceeds the size of shared memory that is available as HugePages

    Change the value specified for the adb_sys_memory_limit operand in the server definition so it is equal to or smaller than value-specified-for-kernel-parameter-vm.nr_hugepages × single-page-size-in-HugePages. Alternatively, increase the value specified for the kernel parameter vm.nr_hugepages.

For details about kernel parameters, see Estimating the kernel parameters in the HADB Setup and Operation Guide.