Table of contents

Security context constraints for Db2

Db2 requires the use of custom security context constraints (SCCs), which are created automatically when you install Db2.

Allows manipulation of reservations, memory allocations, and resource limits. Maximum memory allocation is still constrained by the memory cgroup (memcg) limit, which cannot be overridden by this sys-capability. The Db2 database engine needs this sys-capability to increase the resource limits (IE.ulimits).
Bypasses permission checks for operations on IPC objects. Even when the IPC kernel parameters are set to maximum values on the hosts/worker nodes, the Db2 engine still tries to dynamically throttle those values. This system capability is provided in addition to sharing IPC namespace with the host.
Allows changing process priorities. Because each container has its own PID namespace, this capability applies to that container only. The Db2 database engine relies on process thread prioritization to ensure that Work Load Management (WLM) and Fast Communications Manager (FCM) processing is prioritized over generic agent work.
Necessary to run chown to change ownership of files/directories in persistent volumes.
Bypasses permission checks for file read, write, and execute.
Prevents the clearing of the setuid and setgid mode bits when a file is modified.
Bypasses permission checks on operations that normally require the file system UID of the process to match the UID of the file (for example, chmod(2), utime(2)), excluding those operations that are covered by CAP_DAC_OVERRIDE and CAP_DAC_READ_SEARCH.
Necessary to run Db2 engine processes with escalated group privileges.
Necessary to run Db2 engine processes with escalated user privileges.
Used to set capabilities on files.
Used to set capabilities on processes.
Necessary to use the chroot command.
Bypasses permission checks for sending signals. Necessary for signal handling during process management.
Required to write records to the kernel auditing log when SELinux is enabled.