IBM Support

JR30561: RUNNING DB2EXTSEC FOLLOWING COMPUTERNAME CHANGE RESULTS WITH ERROR: NO MAPPING BETWEEN ACCOUNT NAMES AND SECURITY IDS DONE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In V9, fp4 changes were made to db2extsec which result in
    problems when the computer name changes. After the computer name
    changes if you run:
    db2extsec.exe -a <new computer name>\DB2ADMNS -u <new computer
    name>/DB2USERSS
    
    you will receive
    DB2EXTSEC: No mapping between account names and security IDs was
    done.
    
    This is only a problem starting at V9 Fixpak 4.
    

Local fix

  • Issue the following commands to resolve the issue:
    
    Set environment variable:
    SET DB2_EXTSECURITY=NO
    
    Then set the DB2 Registry variables:
    DB2SET   DB2_ADMINGROUP=NEW_NAME\DB2ADMNS
    DB2SET   DB2_USERSGROUP=NEW_NAME\DB2USERS
    
    Then unset the environment variable:
    SET  DB2_EXTSECURITY=
    
    The command SET  DB2_EXTSECURITY=NO will override the
    DB2_EXTSECURITY setting in the DB2  registry.
    ( It is set to YES in the registry ).
    The SET DB2_EXTSECURITY=NO
    will not change the DB2_EXTSECURITY setting in the DB2 registry.
    
    At the end of this, the end result is that the DB2_ADMINGROUP
    and DB2_USERSGROUP changed to the new desired values.
    

Problem summary

  • Users Affected: Windows
    
    Problem Description:
    In V9, fp4 changes were made to db2extsec which result in
    problems when the computer name changes. After the computer name
    changes if you run:
    db2extsec.exe -a <new computer name>\DB2ADMNS -u <new computer
    name>/DB2USERSS
    
    you will receive
    DB2EXTSEC: No mapping between account names and security IDs was
    done.
    
    Problem Summary:
    In V9, fp4 changes were made to db2extsec which result in
    problems when the computer name changes. After the computer name
    changes if you run:
    db2extsec.exe -a <new computer name>\DB2ADMNS -u <new computer
    name>/DB2USERSS
    
    you will receive
    DB2EXTSEC: No mapping between account names and security IDs was
    done.
    

Problem conclusion

  • First fixed in Version 9.5 fixpak 4 (s090429)
    

Temporary fix

  • Issue the following commands to resolve the issue:
    
    Set environment variable:
    SET DB2_EXTSECURITY=NO
    
    Then set the DB2 Registry variables:
    DB2SET   DB2_ADMINGROUP=NEW_NAME\DB2ADMNS
    DB2SET   DB2_USERSGROUP=NEW_NAME\DB2USERS
    
    Then unset the environment variable:
    SET  DB2_EXTSECURITY=
    
    The command SET  DB2_EXTSECURITY=NO will override the
    DB2_EXTSECURITY setting in the DB2  registry.
    ( It is set to YES in the registry ).
    The SET DB2_EXTSECURITY=NO
    will not change the DB2_EXTSECURITY setting in the DB2 registry.
    
    At the end of this, the end result is that the DB2_ADMINGROUP
    and DB2_USERSGROUP changed to the new desired values.
    

Comments

APAR Information

  • APAR number

    JR30561

  • Reported component name

    DB2 UDB PE WIND

  • Reported component ID

    5724B5501

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-23

  • Closed date

    2009-06-04

  • Last modified date

    2009-06-04

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

    JR28440

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

Fix information

  • Fixed component name

    DB2 UDB PE WIND

  • Fixed component ID

    5724B5501

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:
04 June 2009