DB2 Limitations

The following sections describe limitations associated with DB2.

The DB2 release notes formally listed this information under the title 'Known Issues'.

Known Issues on UNIX/Linux

• The DB2 username/password plug-in cannot authenticate any user when the machine is not joined to a zone or DirectControl agent is not running.

  The DB2 username/password plug-in uses a new way to authenticate local user, and this relies on the DirectControl agent. Therefore, if the machine is not joined or DirectControl agent is not running, the DB2 username/password does not work. (Ref: 64711).

Known Issues on AIX

• The single sign on can only work with Active Directory users.

  If you have an Active Directory user and local user with the same username and AIX is configured to use LAM, you may not be able to log in as an Active Directory user. If the user is not logged in as the Active Directory user, the DB2 GSSAPI plug-in for single sign on does not work. The DB2 GSSAPI plug-in only works with Active Directory user accounts. To ensure that single sign on always works, rename, or remove the local user account.

Known Issues on RHEL

• Install error when SELinux enabled – You may receive an error during installation of the Delinea DB2 package if you have SELinux enabled during installation. This may be avoided by one of the following two workarounds:

  • Temporarily disable SELinux. To disable SELinux, modify the /etc/selinux/config file as follows:

    SELINUX=disabled

  • Change the file context on the appropriate library:

    chcon -t textrel_shlib_t /home/release/335_ESE_LNXAMD26_64_NLV/db2/linux26/install/libimf.so