IBM Support

IT05885: CONFIGURATION OF FLASHCOPY MANAGER FOR A DB2 INSTANCE MAY FAIL WHEN USING SETUP_DB2.SH ON REDHAT 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When configuring Tivoli Storage FlashCopy Manager for Unix and
    Linux (FCM) for DB2 on RedHat 6.4the script setup_db2.sh may
    fail
    with the following output:
    
    If the daemons are not started yet:
    Failed to deactivate the IBM Tivoli Storage FlashCopy(R) Manager
    management daemon. Aborting.
    
    If the daemons are already running (in case of reconfigure):
    /db2/BW1/sqllib//acs/setup_db2.sh: line 370: return:
    utback3.boeblingen.de.ibm.com:: numeric argument required
    Failed to deactivate the IBM Tivoli Storage FlashCopy(R) Manager
    management daemon. Aborting.
    
    It is independent if this action is performed as root or DB2
    user.
    

Local fix

  • As a workaround the setuputil script could be modified as
    follows:
    Replace
       line 4924: if test $? -eq 0; then
       with
    if test $? -gt 1; then
    
    Result:
       4920 #echo "Deactivating TSM ACS management daemon.";
       4921 echo "";
       4922 print_msg 15052;
       4923 uninstallAgents;
       4924 if test $? -gt 1; then
       4925   #FMM15053T
       4926   #echo "Failed to deactivate the TSM ACS management
    daemon. Aborting.";
       4927   print_msg 15053;
       4928   DEBUG ENDFUNCTION setup_action;
       4929   exit 2;
       4930 fi
    
    This fix the main issue. If the daemons are running during setup
    script call the following message still apears but the script is
    able to stop the upstart jobs.
    Message:
    /db2/BW1/sqllib//acs/setup_db2.sh: line 370: return:
    utback3.boeblingen.de.ibm.com:: numeric argument required
    Failed to deactivate the IBM Tivoli Storage FlashCopy(R) Manager
    management daemon. Aborting.
    
    Because the setup script is able to stop the upstart jobs a
    rerun of the setup_db2.sh call will work fine with this fix.
    
    To work around also this behavior replace all RS and $RS with RC
    and $RC in setup_db2.sh script between line 338 and line 370:
    Result:
        338         RC=$?;
        339         DEBUG TRACE "RC=$RC";
        340       else
        341         DEBUG TRACE "${FCM_UTIL} -f uninstall 1";
        342         ${FCM_UTIL} -f uninstall;
        343         RC=$?;
        344         DEBUG TRACE "RC=$RC";
        345       fi
        346     else
        347       if test $? -gt 0; then
        348         # it looks like EEE is not configured correctly
    try to run unload only on local machine
        349         DEBUG TRACE "${FCM_UTIL} -f uninstall 2";
        350         ${FCM_UTIL} -f uninstall;
        351         RC=$?;
        352         DEBUG TRACE "RC=$RC";
        353         DEBUG ENDFUNCTION uninstallAgents;
        354         return $RC;
        355       else
        356         DEBUG TRACE "Return 0";
        357         DEBUG ENDFUNCTION uninstallAgents;
        358         return 0;
        359       fi
        360     fi
        361   else
        362     DEBUG TRACE "${FCM_UTIL} -f uninstall 3";
        363     ${FCM_UTIL} -f uninstall;
        364     RC=$?;
        365     DEBUG TRACE "RC=$RC";
        366   fi
        367 fi
        368 DEBUG TRACE "RC=$RC";
        369 DEBUG ENDFUNCTION uninstallAgents;
        370 return $RC;
    
        Please keep in mind that these changes should be deployed in
    the scripts in the install folder and also in the instance
    folder.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of IBM Tivoli Storage FlashCopy Manager for Unix       *
    * v4.1.1 which are using setup script for configuration of a   *
    * DB2 instance on RedHat 6.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available.  This fix is projected to *
    * be available in FlashCopy Manager for DB2 4.1.3.             *
    * Note: This is subject to change at the discretion of IBM.    *
    ****************************************************************
    *
    

Problem conclusion

  • IBM Tivoli Storage FlashCopy Manager for Unix will be fixed to
    perform correct setup actions.
    

Temporary fix

  • IBM Tivoli Storage FlashCopy Manager for Unix 4.1.1.1 on Linux.
    

Comments

APAR Information

  • APAR number

    IT05885

  • Reported component name

    FLSHCPY DB2 AGE

  • Reported component ID

    5608AC6DB

  • Reported release

    41A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-03

  • Closed date

    2015-03-24

  • Last modified date

    2015-03-24

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

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

Modules/Macros

  • SETUPDB2
    

Fix information

  • Fixed component name

    FLSHCPY DB2 AGE

  • Fixed component ID

    5608AC6DB

Applicable component levels

  • R41L PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS36V9","label":"Tivoli Storage FlashCopy Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"41A","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
08 January 2022