IBM Platform Analytics 9.1.2.3 Fix 437856 Readme

Abstract

P102067 Fix for the issue where the value of pending time (PEND, job_pend_time) is incorrect for requeued jobs.

Description

Readme documentation for IBM Platform Analytics 9.1.2.3 Fix 437856 including installation-related instructions, prerequisites and co-requisites, and list of fixes. This fix addresses the following issue:
For requeued jobs, the Pending Time value in Analyticsis different from the value shown in LSF, due to an incorrect calculation.

Readme file for: IBM® Platform Analytics
Product/Component Release: 9.1.2.3
Update Name: Fix 437856
PMR/APAR: 05507,000,766/P102067
Fix ID: build437856_node_linux-x86_64, build437856_server_all, build437856_schema
Publication date:  30 Jan 2017
Last modified date: 30 Jan 2017

Contents:

• List of fixes
• Download location
• Product notifications
• Products or components affected
• System requirements
• Installation and configuration
• List of files
• Copyright and trademark information

• List of fixes

P102067

• Download Location

Download Fix 437856 from the following location: http://www.ibm.com/eserver/support/fixes/

• Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes.

• Products or components affected

Analytics Node

Analytics Server

Analytics Database

• System requirements
  

Linux_x86-64

Window Server 2008 R2 Enterprise Service Pack 1

• Installation and configuration

• In this document, ANALYTICS_NODE_TOP describes the top-level Platform Analytics node installation directory.

           For example, this directory may refer to the following:
              * /opt/PlatformAnalytics

• LSF_TOP describes the top-level LSF installation directory.

      For example, this directory may refer to the following:
         * /home/LSF

 • ANALYTICS_SERVER_TOP describes the top-level Platform Analytics server installation directory.

       For example, this directory may refer to the following:
         * C:\IBM\Platform Analytics


        6.1 Before installation

              6.1.1    Download the patch from Fix Central.
                   * For IBM Platform Analytics Node: build437856_node_linux-x86_64.zip
                   * For IBM Platform Analytics Server: build437856_server_all.zip
                   * For IBM Platform Analytics Database: build437856_schema.zip

        6.2 Installation steps

              6.2.1  Apply IBM Platform Analytics Database patch.

                 6.2.1.1 Stop each IBM Platform Analytics Node   
                            1. Log into the Analytics Node host with the same account used to install Analytics.                 

                            2. Source the environment for Analytics?
                                * For csh or tcsh:
                                    source ANALYTICS_NODE_TOP/conf/cshrc.perf

                                * For sh, ksh, or bash:
                                    . ANALYTICS_NODE_TOP/conf/profile.perf

                            3. Run the following command to stop the service:

                                 * Linux  ANALYTICS_NODE_TOP/perfadmin stop plc

                 6.2.1.2  Stop IBM Platform Analytics Server
                           1. Log into the IBM Platform Analytics Server as Analytics user.

                           2. Run the following command to stop IBM Platform Analytics service:

                               * Windows ANALYTICS_SERVER_TOP\bin\perfadmin.bat stop pats

                 6.2.1.3  Apply patch for IBM Platform Analytics Database patch to add a column for LSB_JOB_FINISH.
                            1. Log in to the Analytics database host and extract the following schema package:
                                build437856_schema.zip.

                            2. Run the vsql command.    
                                <VERTICA_ROOT>/bin/vsql -d ${database_name} -p ${port} -U ${user_name} -w ${password} "     
                                where:
                                  - <VERTICA_ROOT> is the Vertica installation directory. The default is /opt/vertica
                                  - ${database_name} is the name of the database.
                                  - ${port} is the port number to connect to the database. The default is 5433
                                  - ${user_name} is the name of the Analytics database user.
                                 - ${password} is the password for the Analytics database user.

                                 For example,                
                                /opt/vertica/bin/vsql -d analyticsdb -p 5454 -U userA -w mypasswd                                 

                            3. Run the following command to create the data schema:
                                \i build437856_schema/schema/SQL_Patch.sql


              6.2.2  Apply the IBM Platform Analytics Node patch with the patch installer for each node.
                           1. Log into the Analytics Node host with the same account used to install Analytics.

                           2. Extract the node package build437856_node_linux-x86_64.zip.                 

                           3. Run the following command and follow the prompts to apply the patch:

                                * Linux  ANALYTICS_NODE_TOP/patch_tools/pinstall.sh

             6.2.3   Modify the configuration files to support to collect events JOB_SIGNAL and JOB_START.

                          6.2.3.1 Modify the lsb.params to enable the exporting of extra LSF job event JOB_SIGNAL and JOB_START data to the lsb.stream file.
                             1. Log into a host in the LSF cluster.

                             2. Edit the lsb.params file.
                                 * Linux: $LSF_TOP/conf/lsbatch/cluster_name/configdir/lsb.params

                             3. In the lsb.params file, append the following allow event type to lsb.params if the events do not exist in parameter ALLOW_EVENT_TYPE
                                 ALLOW_EVENT_TYPE=.... JOB_SIGNAL  JOB_START

                             4. Reconfigure mbatchd to apply these changes:

                                  badmin mbdrestart

                             5. To verify that these changes are in effect, verify that the lsb.stream file exists.
                                 By default, lsb.stream is located at the following directories:

                                 * Linux: $LSB_SHAREDIR/cluster_name/logdir/stream
                                 If you defined the EVENT_STREAM_FILE parameter in lsb.params, check the specified file path for the lsb.stream file.

                          6.2.3.2 Modify the lsbevents.properties to enable IBM Platform Analytics Node to collect the events JOB_SIGNAL and JOB_START.
                             1. Log in to the Analytics Node host with the same account used to install Analytics.

                             2. Edit the file lsbevents.properties
                                 * Linux: $ANALYTICS_NODE_TOP/conf/dataloader/lsbevents.properties

                             3. In the lsbevents.properties, append the following allow event type to lsbevents.properties if the events do not exist in parameter ALLOW_EVENT_TYPE.
                                 # define the events type that allow the event loader loading into db
                                 ALLOW_EVENT_TYPE=... JOB_START JOB_SIGNAL

             6.2.4  Modify the configuration file lsbevents.xml to add a column
                             1. Edit the lsbevents.xml.
                                 * Linux:  $ANALYTICS_NODE_TOP/conf/dataloader/lsbevents.xml

                             2. In the lsbevents.xml, add an column "JOB_REQUEUE_TIME" with bold font only to LSB_JOB_FINISH
                                 <SQL Input="LSB_JOB_FINISH">
                                    <Statement><![CDATA[
                                       INSERT INTO LSB_JOB_FINISH(
                                       ....
JOB_REQUEUE_TIME
                                       )VALUES (?,?,?,?,?,?, ?,?,?,?,?,?,?,?, ?,?,?,?,?, ?,?, ?, ?,?,?,?, ?,?,?,?, ?,?,?,?,?,?,?,?, ?,?, ?,?,?,?,?)
                                       ...
<Field Name="jobRequeueTime" Column="JOB_REQUEUE_TIME" />
                                  </SQL>

              6.2.5  Apply the IBM Platform Analytics Server patch with the patch installer.
                             1. Log into the IBM Platform Analytics Server as Analytics user.

                             2. Extract the server package build437856_server_all.zip.                 

                             3. Run the following command and follow the prompts to apply the patch:
                                 * Windows ANALYTICS_SERVER_TOP\patch_tools\pinstall.bat 

              6.2.6  Start the service for IBM Platform Analytics Node and  IBM Platform Analytics Server.
                   6.2.6.1 Start the service for each IBM Platform Analytics Node
                         1. Log into the Analytics Node host with the same account used to install Analytics.                

                         2. Source the environment for Analytics?
                               * For csh or tcsh:
                                 source ANALYTICS_NODE_TOP/conf/cshrc.perf

                               * For sh, ksh, or bash:
                                . ANALYTICS_NODE_TOP/conf/profile.perf

                         3. Run the following command to start the service:

                              * Linux  ANALYTICS_NODE_TOP/perfadmin start plc

                    6.2.6.2 Start the service for IBM Platform Analytics Server
                         1. Log into the IBM Platform Analytics Server as Analytics user.

                         2. Run the following command to start IBM Platform Analytics service:

                              * Windows ANALYTICS_SERVER_TOP\bin\perfadmin.bat start pats

        6.3 After installation

              None

        6.4 Uninstallation
               Limitation: Can't remove the added column JOB_REQUEUE_TIME in LSB_JOB_FINISH when Uninstall this patch.

                6.4.1 Stop the services for IBM Platform Analytics Node and IBM Platform Analytics Server.
                    6.4.1.1 Stop the service for each IBM Platform Analytics Node
                         1. Log into the Analytics Node host with the same account used to install Analytics.
                         2. Source the environment for Analytics?
                              * For csh or tcsh:
                                 source ANALYTICS_NODE_TOP/conf/cshrc.perf   

                              * For sh, ksh, or bash:
                                 . ANALYTICS_NODE_TOP/conf/profile.perf

                         3. Run the following command to stop the service:

                              perfadmin stop plc

                   6.4.1.2 Stop the service for IBM Platform Analytics Server.
                          1. Log into the IBM Platform Analytics Server as Analytics user.

                          2. Run the following command to stop IBM Platform Analytics service:

                               * Windows ANALYTICS_SERVER_TOP\bin\perfadmin.bat stop pats

                6.4.2 Uninstall patch for IBM Platform Analytics Node using patch_tools for each node.
                          1. Log into the Analytics Node host with the same account used to install Analytics.

                          2. Run the following command and follow the prompts to uninstall the patch:

                              * Linux  ANALYTICS_NODE_TOP/patch_tools/puninst.sh

                6.4.3 Modify the lsb.params to disable the exporting of extra LSF job event JOB_SIGNAL and JOB_START data to the lsb.stream file.
                             1. Log into a host in the LSF cluster.

                             2. Edit the lsb.params file.
                                 * Linux: $LSF_TOP/conf/lsbatch/cluster_name/configdir/lsb.params

                             3. In the lsb.params file, remove the following allow event type in lsb.params if the events exist in parameter ALLOW_EVENT_TYPE
Original:
                                 ALLOW_EVENT_TYPE=.... JOB_SIGNAL  JOB_START
Update:
                                 ALLOW_EVENT_TYPE=....

                             4. Reconfigure mbatchd to apply these changes:

                                  badmin mbdrestart

                             5. To verify that these changes are in effect, verify that the lsb.stream file exists.
                                 By default, lsb.stream is located at the following directories:

                                 * Linux: $LSB_SHAREDIR/cluster_name/logdir/stream
                                 If you defined the EVENT_STREAM_FILE parameter in lsb.params, check the specified file path for the lsb.stream file.

                6.4.4 Modify the lsbevents.properties to disable IBM Platform Analytics Node to collect the events JOB_SIGNAL and JOB_START.
                             1. Log in to the Analytics Node host with the same account used to install Analytics.

                             2. Edit the file lsbevents.properties
                                 * Linux: $ANALYTICS_NODE_TOP/conf/dataloader/lsbevents.properties

                             3. In the lsbevents.properties, remove the following allow event type in lsbevents.properties if the events exist in parameter ALLOW_EVENT_TYPE.
Original:
                                 # define the events type that allow the event loader loading into db
                                 ALLOW_EVENT_TYPE=... JOB_START JOB_SIGNAL
Update:
                                 # define the events type that allow the event loader loading into db
                                 ALLOW_EVENT_TYPE=...

                6.4.5 Modify the configuration file lsbevents.xml to remove the column
                             1. Edit the lsbevents.xml.
                                 * Linux:  $ANALYTICS_NODE_TOP/conf/dataloader/lsbevents.xml

                             2. In the lsbevents.xml, remove the added column "JOB_REQUEUE_TIME"
Original:
                                 <SQL Input="LSB_JOB_FINISH">
                                    <Statement><![CDATA[
                                       INSERT INTO LSB_JOB_FINISH(
                                       ....
JOB_REQUEUE_TIME
                                       )VALUES (?,?,?,?,?,?, ?,?,?,?,?,?,?,?, ?,?,?,?,?, ?,?, ?, ?,?,?,?, ?,?,?,?, ?,?,?,?,?,?,?,?, ?,?, ?,?,?,?,?)
                                       ...
<Field Name="jobRequeueTime" Column="JOB_REQUEUE_TIME" />
                                  </SQL>
Update:
                                 <SQL Input="LSB_JOB_FINISH">
                                    <Statement><![CDATA[
                                       INSERT INTO LSB_JOB_FINISH(
                                       ....
                                       )VALUES (?,?,?,?,?,?, ?,?,?,?,?,?,?,?, ?,?,?,?,?, ?,?, ?, ?,?,?,?, ?,?,?,?, ?,?,?,?,?,?,?,?, ?,?, ?,?,?,?)
                                       ...
                                  </SQL>

                 6.4.6  Uninstall patch for IBM Platform Analytics Database.
                            1. Log in to the Analytics database host and extract the following schema package:
                                build437856_schema.zip.

                            2. Run the vsql command.   
                                <VERTICA_ROOT>/bin/vsql -d ${database_name} -p ${port} -U ${user_name} -w ${password} "    
                                where:
                                  - <VERTICA_ROOT> is the Vertica installation directory. The default is /opt/vertica
                                  - ${database_name} is the name of the database.
                                  - ${port} is the port number to connect to the database. The default is 5433
                                  - ${user_name} is the name of the Analytics database user.
                                 - ${password} is the password for the Analytics database user.

                                 For example,               
                                /opt/vertica/bin/vsql -d analyticsdb -p 5454 -U userA -w mypasswd                                

                            3. Run the following command to create the data schema:
                                \i build437856_schema/schema/SQL_Patch_rollback.sql

                 6.4.7  Uninstall patch for IBM Platform Analytics Server using patch_tools
                             1. Log into the IBM Platform Analytics Server as Analytics user.

                             2. Extract the server package build437856_server_all.zip.                

                             3. Run the following command and follow the prompts to apply the patch:
                                 * Windows ANALYTICS_SERVER_TOP\patch_tools\puninst.bat

                 6.4.8  Start the service for IBM Platform Analytics Node and  IBM Platform Analytics Server.
                        6.4.8.1 Start the service for each IBM Platform Analytics Node
                          1. Log into the Analytics Node host with the same account used to install Analytics.               

                          2. Source the environment for Analytics?
                             * For csh or tcsh:
                              source ANALYTICS_NODE_TOP/conf/cshrc.perf

                             * For sh, ksh, or bash:
                               . ANALYTICS_NODE_TOP/conf/profile.perf

                         3. Run the following command to start the service:

                            * Linux  ANALYTICS_NODE_TOP/perfadmin start plc

                        6.4.8.2 Start the service for IBM Platform Analytics Server
                           1. Log into the IBM Platform Analytics Server as Analytics user.

                           2. Run the following command to start IBM Platform Analytics service:

                              * Windows ANALYTICS_SERVER_TOP\bin\perfadmin.bat start pats


• List of files

build437856_node_linux-x86_64
├── lsf
│   └── 9.0
│       └── lib
│           └── perf_lsf_loader.jar
└── patch_install
    ├── filelist.db
    ├── fixlist.db
    └── patchinfo.txt

build437856_server_all
├── conf
│   └── datatransformer
│       └── flow
│           └── jobmart
│               └── raw
│                   └── RptJobmartLoader_vertica.xml
└── patch_install
    ├── filelist.db
    ├── fixlist.db
    └── patchinfo.txt

build437856_schema
├── SQL_Patch_rollback.sql
└── SQL_Patch.sql

• Copyright and trademark information

© Copyright IBM Corporation 2016

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml