IBM Support

Analyzing Data for Db2 DAS SQL4401C error

Troubleshooting


Problem

This Analyzing data document explains how to debug the Db2 Database Administration Server (DAS) error SQL4401C, using the Collecting Data documents must gather information.

Resolving The Problem

Trouble Shooting Guide



Refer to the Collecting Data document for Db2 DAS SQL4401C error, which can be used to gather necessary diagnostic data. The following information will help you analyze the information collected.

Port 523 already in use:
  • Check the db2dasdiag.log file for messages of "LEVEL: Error" similar to this:

      • 2010-09-17-15.33.21.521065+480 I7999G341 LEVEL: Error
      PID : 24418 TID : 1088649024
      FUNCTION: DB2 Tools, DB2 administration server, dasRootInit, probe:10
      DATA #1 : String, 131 bytes
      DAS startup error. Failed to bind to port 523. Please ensure that no other applications are using this port. Then restart the DAS.

      2010-09-17-15.33.21.521226+480 I8341G219 LEVEL: Error
      PID : 24418 TID : 1088649024
      FUNCTION: DB2 Tools, DB2 administration server, dasRootInit, probe:10
      DATA #1 : Sint32, 4 bytes
      -2129723365

  • The error -2129723365 means SQLO_ADDR_IN_USE which indicates that the port 523 is already in use.

  • If you have encountered this message, check if Port 523 is still listening by using the following command:

      • netstat -an

      TCP       0.0.0.0:523      0.0.0.0:0         LISTENING

  • If it is not listening please ensure that port 523 is not being used by another application or is blocked by a firewall. Contact your network or system administrator to check why the port remains in use.

Unknown Host Name:
  • Check the db2dasdiag.log file for messages of "LEVEL: Error" similar to this:
      2010-07-16-18.44.03.264020-900 LEVEL: Error
      PID : 31596 TID : 3086935744
      FUNCTION: DB2 Tools, DB2 administration server, dasRootInit, probe:20
      DATA #1 : Sint32, 4 bytes
      -2129723342

  • The error -2129723342 means SQLO_HOST_UNKNOWN which indicates that the hostname is not correct.
  • If you have encountered this message, check the host name in the /etc/hosts file by performing the following steps:
  1. Verify the host name by issuing the 'hostname' command as user root:

    hostname
  2. Add the hostname and the fully-qualified domain name to the /etc/hosts file.

    For example,
      #/etc/hosts
      10.0.0.2 myserver

      Add the full domain name as such:

      #/etc/hosts
      10.0.0.2 myserver myserver.domain.com
Port 523 held open by abandoned process
  • Check for left over processes of the DAS listening on port 523 using the command:
        • AIX: lsof -i :523 | grep -i listen
        Linux: netstat -anp | grep -i listen
        Windows: netstat -abn

      If left over processes are found, remove the process and restart DAS.
    -2079391743 SQLO_ACCD "Access Denied"
    • Check the db2dasdiag.log file for messages of "LEVEL: Error" similar to this:
        2010-09-14-08.48.15.833050-300 I6897G219 LEVEL: Error
        PID : 1507 TID : 3069767808
        FUNCTION: DB2 Tools, DB2 administration server, dasRootInit, probe:10
        DATA #1 : Sint32, 4 bytes
        -2079391743

        2010-09-14-08.48.17.842952-300 I7117G219 LEVEL: Error
        PID : 1507 TID : 3069767808
        FUNCTION: DB2 Tools, DB2 administration server, db2dasSearchDscvInit,
        probe:30
        DATA #1 : Sint32, 4 bytes
        13
    The error -2079391743 means SQLO_ACCD "Access Denied"

    Verify that the db2dasrrm executable located in the $DASHOME\das\adm directory is owned by root and has the set-user-identifier (suid) bit set (that is to say, the executable is suid root). The permissions on db2dasrrm file should look like this: -rwsr-sr-x

    If the executable is not suid root, either this has been changed manually or the installation has failed. To resolve this, login as root, cd to the <install path>/instance directory and run the dasupdt script.

    If the db2dasrrm executable is suid root, it is possible that the filesystem on which the $DASHOME directory resides has the nosuid option enabled, which will prevent set-user-identifier and set-group-identifier bits from taking effect. If this is the case, you can resolve it by taking the following action:

    • Linux
      Change "nosuid" option to "suid" in the /etc/fstab file for the filesystem, then mount the filesystem and recreate the DAS using dasdrop and dascrt commands.
    • Solaris
      Change "nosuid" option to "suid" in the /etc/vfstab file for the filesystem, then mount the filesystem and recreate the DAS using dasdrop and dascrt commands.
    • AIX
      Change "nosuid" option to "suid" in the /etc/filesystems file for the filesystem, then mount the filesystem and recreate the DAS using dasdrop and dascrt commands.
    • HP-UX
      Change "nosuid" option to "suid" in the /etc/fstab file for the filesystem, then mount the filesystem and recreate the DAS using dasdrop and dascrt commands.

    [{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Instance(DAS)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1;10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

    Document Information

    Modified date:
    16 June 2018

    UID

    swg21442009

    Page Feedback