IBM Support

JR40860: TRYING TO CONFIGURE ACTIVE/PASSIVE FAIL OVER USING LINUX CLUSTER. PROBLEMS FOUND WITH HA SCRIPTS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Trying to configure active / passive fail over using Linux
    Clustering.  Problems found with IBM HA scripts InfoSvrServices,
    ISFRepos, InfoSvrEngine scripts.
    

Local fix

Problem summary

  • Customer had difficulty getting our HA Scripts to work with
    Linux Cluster partly because the 8.5fp1
      install had overwritten the scripts and for some reason the
    DB2 install had failed to configure the
      db2 instance owner's profile to automatically source
    db2profile.
      The following issues were raised -
    
      1. 8.5.fp1 install overwrote HA Scripts with raw versions that
    did not have installation specific
         variable substitution.
      2. No db2 commands work in the HA scripts because the
    db2profile is not sourced.
      3. InfoSvrEngine stop(issued on the passive server) removes
    agent .pid files which relate to the
         active server this prevents a subsequent InfoSvrEngine stop
    on the active server from working.
      4. If InfoSvrEngine start is execute immediately after
    InfoSvrServices start agents fail to startup.
      5. InfoSvrEngine stop gives inaccurate message and exit status
      6. The InfoSvrServices start action hangs indefinitely because
    db2 is in an inconsistent state
      7. The InfoSvrEngine start action incorrectly determines the
    ASB agents are running on the failover
         server by looking just at two pid files.
    

Problem conclusion

  • 1. Fix to the patch installer/fixpack installer to do variable
    substitution when updating HA Scripts.
         This is addressed in version 8.5.0.290 of the update
    installer.
      2. The db2 installer should add lines to .profile or .bashrc
    of db2 instance owner to automatically
         source db2profile. This didn't happen on customer's
    installation so we modified the HA scripts to
         explicitly source db2profile just in case db2 installer
    didn't set this up.
      3. Fixed InfoSvrEngine stop action to only remove .pid files
    if those process were running on the
         local server and they were stopped.
      4. Modified InfoSvrServices start action to wait until
    AppServer is fully started before returning.
      5. Improved messages.
      6. Modified ISFRepos to prevent db2 'invalid state' error.
      7. Expanded test to check for running p[rocess with the
    specified pids.
    
    
    IMPORTANT: The installed HA Scripts will be overwritten when
    this fix is installed as a patch or fix pack.
    Please be sure to back them up if they have been modified, prior
    to installing the fix pack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR40860

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-12

  • Closed date

    2012-02-24

  • Last modified date

    2012-04-16

  • 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

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021