=============================================================================== Abstract: Reduce allocation polling interval to one minute. Readme file for: IBM Platform Analytics Product/Component Release: 9.1.1.0 Update name: Solution 237505 Publication date: 11 July 2014 Last modified: 11 July 2014 By reducing allocation polling interval to one minute, allocation data can be collected for shorter running session. =============================================================================== ========================= CONTENTS ========================= 1. Abbreviations 2. About IBM Platform Analytics 3. Supported operating systems 4. Products or components affected 5. Installation and Configuration 6. Copyright ========================= 1. Abbreviations ========================= None. ========================= 2. About IBM Platform Analytics ========================= Solution 237505 ========================= 3. Supported operating systems ========================= All ========================= 4. Products or components affected ========================= IBM Platform Analytics Node IBM Platform Analytics Server IBM Platform Analytics Schema ========================= 5. Installation and Configuration ========================= In this document, ANALYTICS_TOP describes the top-level IBM Platform Analytics Server and Node installation directory. For example, this directory may refer to the following: C:\IBM\Platform Analytics 5.1 Installation 5.1.1 Download and extract the patch unzip build238354_server_all.zip unzip build238354_schema.zip 5.1.2 Configure the IBM Platform Analytics Node 1. Log into the Analytics note host with the same account used to install Analytics. 2. Reduce allocation loader interval to 1 minute. Modify ANALYTICS_TOP/conf/plc/plc_pa_ego.xml, set Interval as 60. 3. Restart alc service. 5.1.3 IBM Platform Analytics Schema upgrade. 1. Log in to the Analytics database host. 2. Navigate to the schema directory containing your database schema scripts. 3. Change the create_tables.sql manually in case the K-Safe level of your Vertica database is not 1. K-Safe level of your Vertica database is decided by the number of Vertica database nodes: Number of Vertica database nodes <3: K-Safe = 0 3<= number of Vertica database nodes <5: K-Safe = 1 Number of Vertica database nodes >5: K-Safe = 2 Based on the above settings, check the actual K-Safe level of your vertica database. 4. Open the SQL script create_tables.sql and go to the line \set K_SAFE 1 and change the value of K_SAFE to be the one you get in step 4. 5. Run vsql to connect to the database. /opt/vertica/bin/vsql -d -p -U -w where: * is the name of the database. * is the TCP port number or the local socket file extension in which the server is listening for connections. The default is port number 5433. * is the name of the user with which to connect to the database, instead of the default user (the database administrator). * is the password for the database user. Alternately, you can run vsql with no options to accept the defaults and specify the administrator password at the prompt. 6. Update database schema by using the create_tables.sql script under the extracted directory build238354_schema/schema/: From the vsql command line, run the create_tables.sql script to create a database schema. \i /create_tables.sql where: is the file path to the create_tables.sql file. For example, \i build238354_schema/schema/create_tables.sql 5.1.4 IBM Platform Analytics Server Patch Installation. 1. Log into the Analytics server host with the same account used to install Analytics. 2. Apply the patch with the patch installer. Run the following command and follow the prompts to apply the patch: * windows: ANALYTICS_TOP\patch_tools\pinstall.bat 5.2 Uninstallation 5.2.1 IBM Platform Analytics Server uninstallation. 1. Log into the Analytics server host with the same account used to install Analytics. 2. Run the following command and follow the prompts to uninstall the patch. * windows: ANALYTICS_TOP\patch_tools\puninst.bat 5.2.2 IBM Platform Analytics Schema uninstallation. 1. Log in to the Analytics database host. 2. Navigate to the schema directory containing your database schema scripts. 3. Run vsql to connect to the database. /opt/vertica/bin/vsql -d -p -U -w where: * is the name of the database. * is the TCP port number or the local socket file extension in which the server is listening for connections. The default is port number 5433. * is the name of the user with which to connect to the database, instead of the default user (the database administrator). * is the password for the database user. Alternately, you can run vsql with no options to accept the defaults and specify the administrator password at the prompt. 4. Update database schema by using the create_schema.sql script under the extracted directory build238354_schema/schema/: From the vsql command line, run the drop_tables.sql script to drop a database schema. \i /drop_tables.sql where: is the file path to the drop_tables.sql file. For example, \i build238354_schema/schema/drop_tables.sql ========================= 6. Copyright ========================= © Copyright IBM Corporation 2014 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.