IBM Support

IZ20428: SQL1092N WHEN STARTING DAS FROM USERID WHICH BELONGS TO DASADM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Starting the DAS on Solaris may result in SQL1092N, even though
    the userID attempting to start the DAS belongs to the DASADM
    group:
    
    SQL1092N "db2as" does not have the authority to perform the
    requested command.
    
    When the DAS server is starting, it checks the shadow password.
    This is expected to fail for non-root users with access denied
    error.  This SQL1092N error is caused by the Solaris API
    getspnam_r(), which checks the shadow password.  It returns NULL
    and errno=0 for non-root user, but expected is NULL and errno=13
    (EACCES - access denied).  This problem seems to be specific to
    Solaris 10.  It does not happen for all user ids, which means
    the problem may or may not occur.
    
    The purpose of this APAR is to fix the problem, even though the
    main issue is with the Solaris API.
    

Local fix

  • Start the DAS as root
    

Problem summary

  • USERS AFFECTED:
    All users running DB2 on Solaris 10
    
    PROBLEM DESCRIPTION:
    Starting the DAS on Solaris 10 may result in SQL1092N, even
    though the userID attempting to start the DAS belongs to the
    DASADM group:
    
    SQL1092N "db2as" does not have the authority to perform the
    requested command.
    
    PROBLEM SUMMARY:
    When the DAS server is starting, it checks the shadow password.
    This is expected to fail for non-root users with access denied
    error.  This SQL1092N error is caused by the Solaris API
    getspnam_r(), which checks the shadow password.  It returns NULL
    and errno=0 for non-root user, but expected is NULL and errno=13
    (EACCES - access denied).  This problem seems to be specific to
    Solaris 10.  It does not happen for all user ids, which means
    the problem may or may not occur.
    
    The purpose of this APAR is to fix the problem, even though the
    main issue is with the Solaris 10 API.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 2 (s080811).
    

Temporary fix

  • Start the DAS as root
    

Comments

APAR Information

  • APAR number

    IZ20428

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-17

  • Closed date

    2008-08-26

  • Last modified date

    2008-08-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
26 August 2008