IBM
Platform
Analytics 9.1.2 Fix 415587 Readme
Abstract
P101806
Fix
to resolve failure of the script loader to work with build
410865. Records cannot be inserted into the database by the
script loader if CLUSTER_NAME is not defined as a PK Violation
in the customized table.
Description
Readme
documentation for IBM Platform Analytics 9.1.2 Fix 415587 including
installation-related instructions, prerequisites and co-requisites,
and list of fixes.
This
fix addresses the following issue:
The
script loader will not be PK Violation checked and all data from the
script loader will not be inserted into the database, if the
'CLUSTER_NAME' is not configured as a PK Violation for the script
loader raw table.
Readme file for: IBM® Platform
Analytics
Product/Component Release: 9.1.2
Update Name: Fix
415587
PMR/APAR: 83029,000,744/P101806
Fix ID: build415587_node_linux-x86_64,
build415587_schema
Publication date: 1 Aug 2016
Last modified date: 1
Aug
2016
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
P101806
- Download Location
Download Fix
415587 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
Affected components include:
Analytics Node
Analytics Database
- System requirements
5.1 Software requirements
- Analytics Node: Linux-x86_64
- Analytics Database: ALL
- 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
6.1 Before installation
6.1.1 Download the patch from Fix
Central.
* For IBM Platform Node: build415587_node_linux-x86_64.zip
* For IBM Platform Database: build415587_schema.zip
6.2 Installation steps
6.2.1 Apply the schema patch in IBM Platform Analytics DB
1. Log in to the Analytics database host and extract the following
schema package:
build415587_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 build415587_schema/schema/SQL_Patch.sql
6.2.2 Apply the IBM Platform Analytics Node patch with the
patch installer for each node.
1. Log in to the Analytics Node host with the same account used to
install Analytics.
2. Extract the server package build
415587_node_linux-x86_64.zip.
3. 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
4. Run the following command to stop the service:
perfadmin stop plc
5. Run the following command and follow the prompts to apply the patch:
* Linux ANALYTICS_NODE_TOP/patch_tools/pinstall.sh
6.3 After installation
None
6.4 Uninstallation
6.4.1 Uninstall patch for IBM Platform Analytics Node using patch_tools
for each node.
1. 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
2. Run the
following command to stop the service:
perfadmin stop plc
3.Run the following command and follow the prompts to uninstall
the patch:
* Linux ANALYTICS_NODE_TOP/patch_tools/puninst.sh
6.4.2 Roll back the database changes on the
Analytics database host
1. Log in to the Analytics database host as the Vertica database
administrator.
2. Navigate to the build415587_schema directory.
3. 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
4. Run the following command to roll back the data schema changes:
\i
build415587_schema/schema/SQL_Patch_rollback.sql
- List of files
build 415587_node_linux-x86_64
├── 1.2
│ └── lib
│ ├── perf_commons.jar
│ └── perf_dataloader.jar
└── patch_install
├── filelist.db
├── fixlist.db
└── patchinfo.txt
build415587_schema
└── 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