IBM Tivoli Monitoring for Virtual Environments, Version 7.2 Fix Pack 3

Installation and configuration problems

Use the installation problems table to troubleshoot errors you might encounter when you install and configure the Dashboard for VMware, Performance and Capacity Management Reports, Capacity Planner for PowerVM®, and Capacity Planner for VMware.

Table 1. Capacity Planner installation and configuration problems.
Problem	Solution
Capacity Planner for VMware A problem occurred when you run the heterogeneous federation (with Oracle Server) scripts for Capacity Planner for VMware on the Windows operating system. The log displays the following error messages: `SQL1822N Unexpected error code`-1 `received from data source` "`WHSERV`". `Associated text and tokens are`"`Do not have permission to read Oracle Client Libraries`"`. SQLSTATE=560BD.`	Set the following Environment Variables or Permissions for heterogeneous federation with Oracle on the Windows operating system. In the System Variables, set a value for ORACLE_HOME. In the User Variables, set the values for DB2LIBPATH and ORACLE_HOME. Provide all permissions to the db2 instance owner for the lib directory in $ORACLE_HOME. Add the details for the following parameters in the db2dj.ini file: ORACLE_HOME DB2LIBPATH
The DBinstaller is looking for bash and failing on AIX®.	Bash is a prerequisite on AIX, but is not available by default on AIX. You can download it from IBM® AIX Toolbox download (http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html). See also IBM developerWorks® System Administration Toolkit: Get the most out of bash (http://www.ibm.com/developerworks/aix/library/au-satbash.html).

Table 2. Linux Kernel-based Virtual Machines agent installation and configuration problems
Problem	Solution
Report installation fails on Linux systems with the following error found in the logs: `The` `fileset` `type doesn't support the` "erroronmissingdir" attribute.	The Linux environment has another version of ANT earlier than 1.8.1 configured as the default. Set the following environment variables and run the installer again: `export PATH=Install_dir\reports\lib\ apache-ant-1.8.1\bin:$PATH export ANT_HOME=Install_dir\reports\lib\ apache-ant-1.8.1 export CLASSPATH=Install_dir\reports\lib\ apache-ant-1.8.1\bin:$CLASSPATH` Before you start the installer again, run ant -version to check that the returned results show ant 1.8.1 compiled.
You get errors when you run the reports installer.	The report installer completes the following 3 steps: Imports reports Defines the Tivoli® Data Warehouse data source in Cognos® Makes schema updates by running scripts against the Tivoli Data Warehouse (adding and populating Time Dimension tables, creating indexes if history is enabled on the attribute groups). Check the following logs on Windows systems at C:\Documents and Settings\Administrator or on Linux or UNIX systems at $HOME: Report_Installer_InstallLog.log Report_Installer_For_TCR_Output.txt
When you install reports, the installer fails with error messages similar to the following error message: `JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait. .. .. JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError". CTGTRQ010E Processing has ended because of an unexpected error.`	This problem is a known problem with Tivoli Common Reporting. For more information, see the Tivoli Common Reporting technote (OutOfMemoryError exception occurs when issuing trcmd command).

Table 3. Reports installation and configuration problems
Problem	Solution
In the Reports Installer, when you complete the following steps to install reports, you have some problems: On the Choose the reports for the installation page, select all reports that you want to install, and then click Next. The Cognos Engine Configuration page is displayed. On the Cognos Engine Configuration page, click Previous to return to the Choose the Installation Folder page. On the Choose the Installation Folder page, click Next Problem: The Choose the reports for the installation page that contains selected check boxes for all reports is displayed, and Next is disabled. Clear all check boxes for the reports, and select the reports to install again. The Next button becomes available. Click Next. Problem: The following message is displayed on the next page: `THERE ARE NO ITEMS SELECTED FOR THE INSTALLATION.`	Restart the Reports Installer.
Labels are not displayed on the installation panels or in the dialog boxes on an AIX operating system with Turkish locales when the Report Installer was run on Java™ 6.	This problem occurs because both the background color and the font color are white. Use one of the following workarounds: Change the style palette to defaultmono when the Report Installer is running (if it is not set to defaultmono by default). This solution works for Java 5 and Java 6 and is the solution that is preferred. Run the Report Installer by using Java 5. You can specify Java by using the following command: `setup_aix.bin lax_vm /opt/ibm/java5/jre/bin/java`

Table 4. VMware agent reports problems
Problem	Solution
You get errors when you run the reports installer.	The report installer completes the following 3 steps: Imports reports Defines the Tivoli Data Warehouse data source in Cognos Makes schema updates by running scripts against the Tivoli Data Warehouse (adding and populating Time Dimension tables, creating indexes if history is enabled on the attribute groups). Check the following logs on Windows systems at C:\Documents and Settings\Administrator or on Linux or UNIX systems at $HOME: Report_Installer_InstallLog.log Report_Installer_For_TCR_Output.txt

Analyzing the report installer log

Review the Report_Installer_For_TCR_Output.txt file (on Windows systems under C:\Documents and Settings\Administrator; on Linux and UNIX systems under $HOME.) to identify the step on which the installer failed.

Sample log output

========================================
INSTALLATION COMPLETED.
========================================
The status of installation steps:
TCRRunDBScripts(runDbScript): FAILED
INFORMATION: /tmp/450480.tmp/reports/itmfvs/build.xml:31:
The <fileset> type doesn't support the "erroronmissingdir" attribute. 
InstallReportsAction(IBM Tivoli Monitoring for 
Virtual Environments Reports v7.1): SUCCESS
CognosDataSource(TDW): SUCCESS
========================================

Analysis

In the sample log, the success or failure of each step is evident:

InstallReportsAction (Step 1 - Importing Reports) succeeded.
CognosDataSource(TDW) (Step 2 - Defining the Tivoli Data Warehouse data source in Cognos) succeeded.
RunDBScripts (Step 3 - Updating schema by running scripts against the Tivoli Data Warehouse) failed.

Step 2: Define the Tivoli Data Warehouse data source in Cognos.

Possible causes of the failure:

The database alias that is specified during installation did not match the cataloged DB2® database alias, the Oracle local TNS service name, or the MS SQL Server ODBC data source name.
The credentials are incorrect for connecting to the Tivoli Data Warehouse.

Solution:

Ensure that you installed the database client on the same server as Tivoli Common Reporting and cataloged the database. If you are using Oracle, the TNS service name in the tnsnames.ora file must be defined. If you are using MS SQL server, an ODBC data source must be defined. See Connecting to the Tivoli Data Warehouse using the database client over ODBC (http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/adminuse/tcr_tdwconnect.htm) in the IBM Tivoli Monitoring Administrator's Guide. If you already have a Tivoli Data Warehouse data source defined, adding another one overwrites the existing data source.

Step 3: Make schema updates

Possible causes of failure:

Database administrative privileges (such as db2admin or sys) are required for this step; if user ITMUSER is specified, the schema cannot be updated.
Database issues like connectivity problems, full logs, space issues, or any other performance problems that prevents writing to the database.

Solution:

An error at Step 3 is accompanied by an informational message that contains SQL errors with SQL codes. You can search on the SQL code to determine the problem.
If Time Dimension tables are present in the database, you can choose to skip the schema update (JDBC) step when you run the dashboard installer. If you want to create time dimension with a different granularity, you must edit the following sql file:
1. Go to reports package\reports\cognos_reports\itmfvs\db_scripts.
2. Open call_proc_DB2.sql , call_proc_MSSQL.sql, or call_proc_ORACLE.sql depending on the database used.
3. Edit the last parameter in the call to IBM_TRAM.CREATE_TIME_DIMENSION.

Notes

The Database scripts for creating indexes are provided for enhanced reporting performance in the Tivoli Data Warehouse. If your data warehouse is not prepared with history before installation, this step is skipped by the installer. You can manually run one the following scripts, depending on your database type:
```
create_index_DB2.sql 
```
```
create_index_MSSQL.sql 
```
```
create_index_ORACLE.sql
```
For more information, see Creating and populating the time dimensions tables(http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/adminuse/tcr_reports_dimensionsshared.htm).
Although indexes help enhance report performance, some limitations apply: Use indexes only on large tables with thousands of rows; because indexes degrade the performance of insert, update, and delete operations on a table.
You can run a script to drop these indexes if you run into either of these performance issues:
```
drop_index_DB2.sql
```
```
drop_index_MSSQL.sql
```
```
drop_index_ORACLE.sql
```
Connections under the Tivoli Data Warehouse are overwritten by the report installer. This is a limitation of the current installer.
The privileges that are required when you run the installer are ITMUSER (database user) for the Tivoli Data Warehouse creation step and ADMIN (database administrator) for the schema update step. The Database Test connection for the schema update panel does not check for privileges of the database user. Installation fails at the schema update step if the database user does not have administrative privileges.

Dashboard Health Checks logs

After you install and configure the Dashboard for VMware, the Dashboard Health Checks is installed and configured with the Dashboard for VMware.

You can view the runtime log for Dashboard Health Checks in the ITMDHC_LOGYYYYMMDDHHMMSS.log file at the following location:
TIP_INSTALL_DIR\IBM\JazzSM\profile\logs\
You can view the configuration for Dashboard Health Checks in the ITMDHCHealthChecker.cfg file at the following location:
TIP_INSTALL_DIR\IBM\JazzSM\profile\installedApps\JazzSMNode01Cell\isc.ear\ITMDHC.war\WEB-INF\config

Dashboard Health Checks configuration parameters and their descriptions:

ITMcDP_PROVIDER_TYPE

The type of IBM Tivoli Monitoring Dashboard data provider. The value of the ITMcDP_PROVIDER_TYPE parameter is IBMTivoliMonitoringServices for IBM Tivoli Monitoring V6.3 or later.

COMMON_TEPS_PING_TIME_OUT

The Tivoli Enterprise Portal Server ping timeout value, in seconds. This value indicates the maximum amount of time the Tivoli Enterprise Portal Server Ping check must take. If the operation times out before a response, the Tivoli Enterprise Portal Server is deemed unreachable. The default value is 15 seconds.

Feedback