IBM Support

LI74162: DB2SYSC'S SUPPLEMENTARY GROUPS NOT SET IF NON-INSTANCE OWNER PERFORM DB2START

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • db2sysc's supplementary groups NOT set if non-instance owner
    perform db2start
    
    
    basin:~ # id jimyeung
    uid=22388(jimyeung) gid=7777(pdxdb2)
    groups=7777(pdxdb2),14(uucp),17(audio)
    basin:~ # id newton
    uid=1943(newton) gid=7777(pdxdb2) groups=7777(pdxdb2),200(build)
    
    
    If newton (non -instance owner) runs db2start, the ruid of
    db2sysc is newton, and it is changed to the instance owner
    (jimyeung), group-ID=7777. BUT  supplementary group IDs are
    still 7777,200. Although we are changing the userId, and group
    ID for db2 processes, but seems like we are forgetting about
    setting the supplementary group IDs
    
    
    newton@basin:/home/newton> /home/jimyeung/sqllib/adm/db2start
    SQL1063N  DB2START processing was successful.
    
    newton@basin:/home/newton> ps -ef | grep jimyeung| grep db2sysc
    jimyeung  7597  7595  2 21:44 pts/9    00:00:00 db2sysc
    
    newton@basin:/home/newton> cat /proc/7597/status
    Name:   db2sysc
    State:  S (sleeping)
    SleepAVG:       0%
    Tgid:   7597
    Pid:    7597
    PPid:   7595
    TracerPid:      0
    Uid:    22388   22388   22388   22388  <-uid of instance owner
    Gid:    7777    7777    7777    7777    <-gid of instance owner
    FDSize: 64
    Groups: 200 7777             <-secondary grp of newton
    VmSize:   851824 kB
    
    
    
    The instance should have the secondary groups of the instance
    owner, not whatever random SYSADM happened to call db2start.
    

Local fix

  • Workaround:
    
    - Ensure the instance owner start DB2.
    or
    - Ensure the user who starts DB2 belong to the same groups as
    the instance owner.
    

Problem summary

  • DB2SYSC'S SUPPLEMENTARY GROUPS NOT SET IF NON-INSTANCE OWNER
    PERFORM DB2START
    

Problem conclusion

  • First Fixed in DB2 LUW v9.5 Fixpack 5 and later.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI74162

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-11

  • Closed date

    2009-12-15

  • Last modified date

    2009-12-15

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

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

    LI74163

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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:
15 December 2009