IBM Support

IC73359: DB2GOV START WITH FULL PATH OF LOG FILE ON DPF SYSTEM DOES NOT LOG ERROR IN LOG FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The 'db2gov start' command should not specify the full path of
    the log file. Error
      "GOV1014N  Unable to open log file."
    is returned if the full path to the log file is used. However,
    in a DPF environment, the error is not returned.
    
    Example:
    db2gov start sample /db2home/db2inst1/governor/db2gov.cfg
      /db2home/db2inst1/sqllib/log/db2gov.log
    
    The output:
    =====================
    
    db2gov deamons have been started on all nodes.
    
    Please check the corresponding log files for status!
    
    
    Note: The log files are stored in the /tmp/db2inst1 directory.
    File names are
    db2gov_start.nodenumber.
    
    The /tmp/db2inst1/db2gov_start looks like:
    
    =======================================
    hostname01: db2gov start SAMPLE... completed ok
    
    Error that should have been logged:
    db2govd: GOV1014N  Unable to open log file
    "/db2home/db2inst1/sqllib/log/sample_gov.log". RC = ""
    

Local fix

  • Use log file name, no need to supply full path.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 Governor users on DPF environment                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * On DPF system, GOV1014N error is missing when db2gov start   *
    * command specifies the full path log file.                    *
    * And it states that governor is started successfully when it  *
    * is not.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to version v9.7 FP5                                  *
    ****************************************************************
    

Problem conclusion

  • Problem first fixed in Version 9.7 Fix Pak 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC73359

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-17

  • Closed date

    2012-01-11

  • Last modified date

    2012-01-11

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

    IC73272

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       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":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
11 January 2012