blixx SPI for MySQL Databases - Patch 1.21
(c) 2008 blixx GmbH
------------------------------------------
Version:		1.21
Release Date:		2008-04-30
Importance:		medium
Security Related: 	no

Problem:
Before peformance data can be stored with the HP Performance
Agent (Coda) the according metric definitions need to be
compiled. In some situations the compilation of the 
MYSQL_STATS performance class will silently fail.
The class will not be available in Coda and the SPI for
MySQL can not store it's performance values.

Fix:
The MySQL SPI generates a slightly modified MYSQL_STATS class 
definition that avoids this problem. 

Changed Files:
mysqlspi.jar - new version 1.21 for all platforms

------------------------------------------
HP Operations Manager for Unix (OMU aka OVO/U)

Prerequisites: SPI for MySQL Databases 1.20
               The patch can not be used with Version 1.0 or 1.10

Patch Installation:
   Download the patch file mysqlspi_patch_1_21.tar.gz from 
   http://www.blixx.com/download/products/mysqlspi/mysqlspi_patch_1_21.tar.gz
   to a temporary location at the OMU server.
   Create a patch subfolder and extract the tar package to this location:
     > mkdir /opt/OV/mysqlspi/server/patch
     > cd /opt/OV/mysqlspi/server/patch
     > gzip -cd /tmp/mysqlspi_patch_1_21.tar.gz | tar xvf -

   As user root execute the patch installation script. This script will
   update the mysqlspi.jar file in the instrumentation folders for the 
   different agent platforms:
     > ./install_mysqlspi_patch.sh

   Login as Administrator (opc_adm) to OMU and force a redistribution of
   the "Monitors" to the MySQL Servers.

   The MySQL SPI on the Agent will automatically detect the new 
   mysqlspi.jar and restart itself with the updated version. After the
   restart it will automatically compile the Performance classes.
   
   To verify if everything worked as planned, the Coda Object Model can be
   queried. Execute on the agent:
     > /opt/OV/bin/ovcodautil -obj
   (depending on the OM Agent version the command can be "codautil")
   and verify that now both DataSources are listed:
    MYSQL_STATS and MYSQL_STATS_COUNTERS


Patch De-Installation:
   To deinstall the patch and revert back to the old version, locate the 
   patch subfolder on the OMU server.
     > cd /opt/OV/mysqlspi/server/patch

   As user root execute the patch rollback script. This script will
   update the mysqlspi.jar file in the instrumentation folders for the 
   different agent platforms:
     > ./rollback_mysqlspi_patch.sh

   Login as Administrator (opc_adm) to OMU and force a redistribution of
   the "Monitors" to the MySQL Servers.
   
   
------------------------------------------
HP Operations Manager for Windows (OMW aka OVO/W)

Prerequisites: SPI for MySQL Databases 1.20
               The patch can not be used with Version 1.0 or 1.10
               The scripting host (cscript) must be available to
               execute the installation skript

Patch Installation:
   Download and unzip the patch file mysqlspi_patch_1_21.zip from 
   http://www.blixx.com/download/products/mysqlspi/mysqlspi_patch_1_21.zip
   to a patch subfolder e.g.
     C:\Program Files\HP OpenView\Data\shared\mysqlspi\patch

   As user with Administrative OMW rights execute the patch installation
   script. This script will update the mysqlspi.jar file in the 
   instrumentation folders for the different agent platforms:
     > ./install_mysqlspi_patch.vbs

   As user with Administrative OMW rights login to OMW and redistribute
   the "SPI for MySQLDB" instrumentation to the MySQL Servers.

   The MySQL SPI on the Agent will automatically detect the new
   mysqlspi.jar and restart itself with the updated version. After the
   restart it will automatically compile the Performance classes.
   
   To verify if everything worked as planned, the Coda Object Model can be
   queried. Execute on the agent:
    > "%OvAgentDir%\bin\codautil" -obj
   (depending on the OM Agent version the command can be "ovcodautil")
   and verify that now both DataSources are listed:
    MYSQL_STATS and MYSQL_STATS_COUNTERS


Patch De-Installation:
   To deinstall the patch and revert back to the old version, locate the 
   patch subfolder on the OMW server.
   As user with Administrative OMW rights execute the patch rollback
   script. This script will update the mysqlspi.jar file in the 
   instrumentation folders for the different agent platforms:
     > ./rollback_mysqlspi_patch.vbs

   As user with Administrative OMW rights login to OMW and redistribute
   the "SPI for MySQLDB" instrumentation to the MySQL Servers.