IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
data collector installation fails
The following content provides solutions when the data collector installation fails.
data collector installation fails when the system has a wrong mount
The problem: The data collector installation fails when the system has a wrong mount.
The solution: InstallShield uses the UNIX df command to check disk space on the target computer. User corrects the wrong mount indicated by the df command and restarts the installation process.
data collector installation or configuration fails
The problem: The directory DC_home/runtime is not created and the start-up script or other files on application server side are not modified for data collector support.
The solution: For a GUI installation, a message panel will pop up to show detailed error information. Check this message to find if the prerequisite conditions are not met.
For a silent installation, please check installation log files and find messages with log level ERROR or WARN.
Net Weaver data collector installation or configuration fails
The problem: The data collector for Net Weaver installation fails or fails to start after installation.
The reason: Verify that you have the correct configuration for Net Weaver, the following text outlines the names, details, and locations for Net Weaver configuration files:
- File: jvm_config.xml
- Details: Follow Net Weaver rules to define the JVM settings of data collector for Net Weaver into Database.
- Location: NetWeaver Server Home/j2ee/configtool
- File: default_jvm_config.xml
- Details: Follow Net Weaver rules to reserve the default JVM settings of Net Weaver Application Server before configuring data collector or unconfiguring data collector from Net Weaver Application Server.
- Location: NetWeaver Server Home/j2ee/configtool
- File: BatchConfig.bat/BatchConfig.sh
- Details: Use these scripts to import the JVM settings of data collector for Net Weaver into the database.
- Location: NetWeaver Server Home/j2ee/configtool
- File: sap.com~tivoli.sda
- Details: Tivoli service component to be deployed into Net Weaver server
- Location: NetWeaver Central Instance Home/SDM/program
- File: config.bat/config.sh/unconfig.bat/unconfig.sh
- Details: These scripts call Batchconfig.bat/BatchConfig.sh and deploy the Tivoli service component into the Net Weaver Application Server. They also config/unconfig all data collector settings for the Net Weaver server
- Location: NetWeaver Central Instance Home/SDM/program
- File: Tivoli Service Directory
- Details: This directory contains jar files packed in the Tivoli service component.
- Location: NetWeaver Central Instance Home/j2ee/cluster/server[N]/bin/services/tivoli
- File: config.log
- Details: The logs produced when configuring/unconfiguring the data collector for Net Weaver.
- Location: CYN_LOGS/config.log
The solution: If the std_server[N] log, reports Xrun library am_xx_xx.dll or am_xx_xx.so cannot be found:
- On Windows: Check if the dll path (DC_home/toolkit/lib/platform) is added into the Windows System Path.
- On UNIX/Linux: Check if the OS path of the data collector is appended with DIR_OS_LIBS in Net Weaver START_INSTANCE_NAME_HOST_NAME script.
Oracle data collector Installation/configuration fails
The problem: After installing the data collector, the Oracle instance cannot startup.
The solution: If the instance log reports that Xrun library am_xx_xx.dll or am_xx_xx.so cannot be found, make sure your Oracle instance is recycled properly.
If the Oracle instance is on Windows 2000 and the instance log file reports maximum command length exceeded, check your Java options in your opmn.xml and remove some unnecessary parameters. Another solution to exceeding maximum command length is to install your data collector with a shorter file system path like /opt/oracleDC or C:\DC\.
Parent topic:
data collector