IBM Support

IT20324: DB2: SILENT INSTALLATION MIGHT FAIL WITH SEGV IN ENCODEPASSWORD->STRCPY IF CRYPT() RETURNS AN ERROR (E.G. WITH FIPS_ENABLED)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Silent installation of DB2 (db2setup) or instance setup
    (db2isetup) using response file might fail with no error
    returned to the installation log file due to a segmentation
    fault (SEGV). The SEGV might be logged to the operating system
    log file (errpt, messages) indicating a failure of db2iure
    executable, e.g.:
    
    db2iure[28993]: segfault at 0 ip 00007f51f7f7b748
    sp00007ffc1b897108 error 4 in
    libdb2ure.so.1[7f51f7c1e000+4b0000]
    
    A core file will show that error is triggered with following
    functions on the top of the stack:
    
    __intel_sse2_strcpy
    UserManager::encodePassword
    UserManager::setPassword
    IUser::setPassword
    UREInstance::initializeSettings
    TaskBuildInstanceList::execute
    URE::start()
    
    Problem will be observed in the environments where libc crypt()
    function, used to encode the password in response file, returns
    an error, which might happen in the environments where FIPS mode
    is enforced on the system. On Linux, where problem  originally
    reported, this can be checked by verifying value of
    /proc/sys/crypto/fips_enabled:
      EPERM  /proc/sys/crypto/fips_enabled has a nonzero value, and
    an
             attempt was made to use a weak encryption type, such as
    DES.
    

Local fix

  • Install DB2 and set up instance in the interactive mode or
    temporarily disable FIPS during installation.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 3 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT20324

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-23

  • Closed date

    2018-03-19

  • Last modified date

    2018-03-19

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

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

    IT22430

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
19 March 2018