Page 1: Troubleshooting Guide
IBM Tivoli Monitoring Version 6.2.3 FP1 Troubleshooting Guide GC32-9458-05...
Page 3 IBM Tivoli Monitoring Version 6.2.3 FP1 Troubleshooting Guide GC32-9458-05...
Page 4 Before using this information and the product it supports, read the information in “Notices” on page 267. This edition applies to version 6, release 2, modification 3, fix pack 1 of IBM Tivoli Monitoring (product number 5724-C04 ) and to all subsequent releases and modifications until otherwise indicated in new editions.
Page 5: Table Of Contents
The portal server does not start or stops responding 15 Setting traces . . 43 Diagnosing that the portal server does not start Dynamically modify trace settings for an IBM Tivoli or stops responding . 15 Monitoring component . 53...
Page 6 General installation frequently asked questions directory . . 78 Windows installation frequently asked questions When attempting to install IBM Java 1.5.0 on UNIX-based systems installation frequently asked Windows 64 bit system nothing happens . 78 questions .
Page 7 Problems installing directly from the .zip file . . 88 Uninstallation is blocked by another process Installation hangs or loops after presenting initial that is using the IBM Tivoli Monitoring Eclipse splash screen . . 88 help server . . 108...
Page 8 Portal browser client when the number of protocols . . 147 workspace switches increases . . 134 Users who run the IBM HTTP Server do not have Help index and search text entry fields are permission to the content directory . . 147 disabled .
Page 9 Portal server performance is slow . 149 Some agents are displayed in the Service Cannot create a Tivoli Enterprise Portal Server Console list that are not accessible from that database . . 149 user interface . . 159 You receive a KFW error when a query is sent to tacmd login fails after hub monitoring server is more than 200 managed systems .
Page 10 . 175 appears incorrect . . 183 Unreadable tool tip information for Available EIF BAROC file is missing for IBM Tivoli Monitoring Receivers list of the Situation editor . . 175 5.x Endpoint situations .
Page 11 Agent configuration failed on remote deployment Custom defined workspace views do not handle while using single quotes for configuration symbol substitution as expected . . 197 properties . 187 Unresolved variables in custom queries . 198 New attributes missing . .
Page 12 Event synchronization installation and configuration troubleshooting . . 231 Chapter 12. Performance Analyzer Errors occur during installation of IBM Tivoli troubleshooting ..215 Monitoring event synchronization . 231 Enabling logging for the agent .
Page 13 . . 247 processes ... . . 257 Date and time format in IBM Tivoli Monitoring OS Agents reports not localized . 247 Documentation library ..259 Prompted to select report type when installing IBM Tivoli Monitoring library .
Page 14 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 15: Tables
Tables Location of log files for the IBM Tivoli Cannot connect to Tivoli Enterprise Portal Monitoring components. . . 36 Server . . 118 Installation log files . . 39 The Tivoli Enterprise Portal Server does not Upgrading from Tivoli Distributed start after installation .
Page 16 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 17: About This Information
About this information This guide provides problem determination and resolution information for the ® ® issues most commonly encountered with IBM Tivoli Monitoring components and related products. You can use this guide in conjunction with the other books for your product.
Page 18 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 19: Chapter 1. Introduction To Troubleshooting
For example, a performance problem might be caused by a limitation of your hardware. If you are unable to solve a problem on your own, contact IBM Software Support for a solution. See Chapter 2, “Logs and data collection for troubleshooting,”...
Page 20: Viewing The Ibm Support Portal
2. Enter your IBM user ID when prompted or, in the Quick start page or Support home, click Sign in to sign in with your IBM user ID or to register if you have not yet registered. 3. Enter a keyword or keywords for the information you want to find in the Quick Find or Search support fields.
Page 21 Results You begin receiving “IBM My notifications” emails about the products you have selected and at the interval you specified. Chapter 1. Introduction to troubleshooting...
Page 22 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 23: Chapter 2. Logs And Data Collection For Troubleshooting
Chapter 2. Logs and data collection for troubleshooting If you have a problem that you are unable to solve using the information in this guide or on the IBM Support Portal, gather the information that relates to the problem and contact IBM Software Support for further assistance.
Page 24: Locating The Core File
For example, if the failing process is the Tivoli Enterprise Portal Server server process, KfwServices, the core is created in the /opt/IBM/ITM/archtype/cq/bin/ directory. Procedure To retrieve information on where the core file is created, enter the errpt -a command.
Page 25: Getting Dr. Watson Dumps And Logs
STACK EXECUTION DISABLED --------------- Getting Dr. Watson dumps and logs Use the Dr. Watson debugger to get the information needed by IBM Support to diagnose problems on Windows systems. If you encounter errors or failures on your Windows system, collect the drwtsn32.log and user.dmp files if they are available.
Page 26: Sources Of Other Important Information
For example, KNTCMA.RAS is the Monitoring Agent for Windows OS the reliability, availability, and serviceability file. These files contain system dump information similar to the drWatson.log, but are generated by the IBM Tivoli Monitoring infrastructure. Sources of other important information You can collect important information from log files, such as trace or message logs that report system failures.
Page 27: Chapter 3. Common Problem Solving
For more information see “Support information” on page 263. I am trying to find out what software is supported Use resources in the IBM Tivoli Monitoring Installation and Setup Guide and the IBM website to determine the software that is supported. This enables you to find platform or database information for specific products.
Page 28: Workspaces Are Missing Or Views Are Empty
4. If your data is missing in an Oracle Agent workspace, see “Resolving Oracle DB Agent problems - diagnostic actions” on page 32. Similar problems might exist for other monitoring agents. 5. Check that application support has been added. See “Resolving application support problems” on page 11. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 29: Resolving Application Support Problems
What to do next For more information and instructions on installing application support see “Configuring application support for nonbase monitoring agents” in the IBM Tivoli Monitoring Installation and Setup Guide. For instructions on installing application Chapter 3. Common problem solving...
Page 30: Resolving Monitoring Server Problems
“Adding application support to a monitoring server on z/OS” in Configuring IBM Tivoli Enterprise Monitoring Server on z/OS. Resolving monitoring server problems Monitoring server problems are caused by a monitoring server that is not started or connectivity that is lost either between servers or between servers and agents.
Page 31: Status Of A Monitoring Agent Is Mismatched Between The Portal Client And Tacmd Command
3. If subnodes are online, are workspaces showing correct titles? v No: Verify that application support has been installed correctly and that buildpresentation.bat ran correctly. v Yes: Go to the next step. 4. If workspaces contains titles, is there a column heading? v No: Verify that application support has been installed correctly and that buildpresentation.bat ran correctly.
Page 32: Resolving Monitoring Agent Problems
To resolve monitoring server problems, you perform diagnostic and corrective actions. These actions include running tools, such as the ITMSUPER tools and correcting connectivity failures. Procedure Diagnostic and corrective actions 1. Check the Managed System Status workspacein the portal client. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 33: The Portal Server Does Not Start Or Stops Responding
To diagnose that the portal server does not start or stops responding, perform the following steps: Procedure Preliminary diagnostics 1. For more information about any messages received, see the IBM Tivoli Monitoring: Messages (http://publib.boulder.ibm.com/infocenter/tivihelp/ v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623_messages.htm) reference guide. Operator responses and general information are provided for each message.
Page 34: Resolving Database Problems - Missing Table Or Portal Server Database
Tivoli Enterprise Portal Server and verifying the user ID and password. The causes of database problems include: v Portal server database user password is out of sync. v User ID does not match the operating system logon user ID. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 35: Resolving Database Problems - Instance Not Started
v Password does not match the operating system password. v Registry does not have the correct password. About this task To resolve database problems, you perform diagnostic and corrective actions. These actions include reconfiguring the portal server and ensuring that your portal client user ID is the same as the logon user ID of your system.
Page 36: Diagnosing That Portal Server Logon Fails
To diagnose that the portal server logon Tivoli Enterprise Portal Logon fails, perform the following steps: Procedure Preliminary diagnostics 1. For a guide to the messages and operator responses, refer to IBM Tivoli Monitoring: Messages (http://publib.boulder.ibm.com/infocenter/tivihelp/ v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623_messages.htm). 2. Look in the portal server or portal client logs for more information concerning the message.
Page 37: Resolving Storage Or Memory Problems
CPU usage due to the Java process attempting to write to the screen. Procedure Disable DirectDraw by setting the sun.java2d.noddraw client variable to false. See the “Portal client configuration settings” topics in the IBM Tivoli Monitoring Administrator's Guide. Chapter 3. Common problem solving...
Page 38: Historical Data Is Missing Or Incorrect
What to do next For more information on actions that relate to these diagnostics, see the problem resolution tasks. See also the troubleshooting topics in the IBM Tivoli Warehouse Proxy Agent User's Guide (http://publib.boulder.ibm.com/infocenter/tivihelp/ v15r1/topic/com.ibm.itm.doc_6.2.3fp1/wpa/wpagent_user.htm) and IBM Tivoli Warehouse Summarization and Pruning Agent User’s Guide (http://...
Page 39: Resolving Warehouse Proxy Connection Problems
Monitoring server: – Consider using a high port number for connecting to the monitoring server. See the “Controlling port number assignments” topics in the IBM Tivoli Monitoring Installation and Setup Guide for more information on the COUNT and SKIP options for port number allocation.
Page 40: Resolving Warehouse Proxy Agent Problems - Connectivity
2. To perform a corrective action: v Update the configuration parameters. See “Environment variables” in the IBM Tivoli Monitoring Installation and Setup Guide. Resolving summarization and pruning agent problems Summarization and pruning agent problems, such as unexpected values for attributes can be resolved by reviewing the documentation for the monitoring agents that are producing the unexpected values.
Page 41: Resolving Persistent Data Store For Z/Os Problems
To understand how data is aggregated for various data types, see Tivoli Management Services Warehouse and Reporting (http:// www.redbooks.ibm.com/abstracts/sg247290.html). This IBM Redbooks publication describes aggregation methods used by the Summarization and Pruning Agent. 2. To perform a corrective action: v Review the documentation for the monitoring agents that are generating the unexpected values.
Page 42 RKLVLOG of an agent or monitoring server on z/OS: Error 8 trying to set up table <table-name>, KRAIRA000, Starting UADVISOR_Kpp_table-name, where pp is the two-character component or product code and table-name is the application table name. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 43: Historical Data Does Not Get Collected For Some Monitoring Server Attribute Groups
What to do next For more information about the persistent data store, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide. Historical data does not get collected for some monitoring server attribute groups...
Page 44: Resolving Situation-Specific Problems
KO41047 Situation CheckIfSituationCreated distribution Primary:KATE:NT added v Yes: See step 5. v No: Use (UNIT:kpxreqds all) to trace the distribution at the monitoring server for a situation. (4558D8CC.0033-1114:kpxreqds.cpp,621,"DetermineTargets") Active RAS1 Classes: EVERYT EVERYE EVERYU (4558D8CC.0034-1114:kpxreqds.cpp,661,"determineTargetsFromNodelist") IBM Tivoli Monitoring: Troubleshooting Guide...
Page 45 Active RAS1 Classes: EVERYT EVERYE EVERYU (4558D8CC.0035-1114:kpxreqds.cpp,661,"determineTargetsFromNodelist") Entry (4558D8CC.0036-1114:kpxreqds.cpp,669,"determineTargetsFromNodelist") Exit (4558D8CC.0037-1114:kpxreqds.cpp,821,"determineTargetsFromAccessList") Active RAS1 Classes: EVERYT EVERYE EVERYU (4558D8CC.0038-1114:kpxreqds.cpp,821,"determineTargetsFromAccessList") Entry (4558D8CC.0039-1114:kpxreqds.cpp,837,"determineTargetsFromAccessList") Calling KFA_GetAccessListNodes for NT_Paging_File_Critical, 5140 (4558D8cc.003A-1114:kpxreqds.cpp,852,"determineTargetsFromAccessList")Node #0 Primary:KATE:NT (4558D8CC.003B-1114:kpxreqds.cpp,891,"determineTargetsFromAccessList") Deleting NodeRecEntry: #0, node_entries @0x1B63B90, next @0xNULL, ptr_next @0xNULL (4558D8CC.003C-1114:kpxreqds.cpp,898,"determineTargetsFromAccessList") Exit 4.
Page 46: A Reflex Automation Script Does Not Run When It Should
7. Is there a MSG2 message indicating the situation raised? v Yes: Contact IBM Software Support. See Chapter 2, “Logs and data collection for troubleshooting,” on page 5 for information on what types of data to collect before contacting Support. Also consult the IBM Support Portal (http://www.ibm.com/support/entry/portal/software).
Page 47: High Cpu Usage On A Distributed System
To diagnose that CPU usage is high on a distributed system, perform the following steps: Procedure Preliminary diagnostics 1. Determine whether an IBM Tivoli Monitoring component is the root cause. Another application or process running on the system might be causing high CPU usage. Chapter 3. Common problem solving...
Page 48: Resolving Situation Problems - Diagnostic Actions
5. Does the situation contain any wildcard * characters against UTF8 columns? v Yes: See “Resolving situation problems - corrective actions” on page 31. 6. Switch between situations to see which one is causing the high CPU. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 49: Resolving Situation Problems - Corrective Actions
3. Turn on the RAS1 trace log to verify whether the monitoring agent has made a connection to the monitoring server. See “Setting traces” on page 43 for more information. Resolving firewall problems - corrective actions You can resolve firewall problems by contacting IBM Software Support. Chapter 3. Common problem solving...
Page 50: Resolving Oracle Db Agent Problems - Diagnostic Actions
Procedure 1. If you still have high CPU usage issues even after ensuring proper connectivity across firewalls, open a problem report with IBM Software Support or refer to the IBM Support Portal (http://www.ibm.com/support/entry/portal/ software). 2. For more information, see the “Firewalls” topics in the IBM Tivoli Monitoring Installation and Setup Guide.
Page 51 Procedure Corrective actions 1. Disable the problematic cursors by setting an environment variable: COLL_DISABLE_CURSORS a. Launch Manage Tivoli Enterprise Monitoring Services. b. Right-click the row that contains the name of the monitoring agent whose environment variables you want to set. c.
Page 52 Column : System TS Percent Free = 0 Situation: Oracle_DB_PctFree_Space_Low = always true Oracle_SystemTS_PctFree_Critica = always true Oracle_SystemTS_PctFree_Warning = always false 5. For more information on the cursors, see the Oracle Agent 6.2.0-TIV-ITM_ORA-LA0001 README or a higher version of the README. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 53: Chapter 4. Tools
If you cannot find the log files you need, restart the system and try again. Log file locations Log files are saved in log and component directories in your IBM Tivoli Monitoring installation. The log files have a certain format that includes a time stamp.
Page 54 Table 1. Location of log files for the IBM Tivoli Monitoring components. Component Windows UNIX-based systems Tivoli Enterprise install_dir\logs install_dir/logs/ Portal Server hostname_PC_timestamp.log where: install_dir Specifies the directory where the Tivoli Enterprise Portal Server was installed. hostname Specifies the name of the system hosting the product.
Page 55: Location Of Log Files For The Ibm Tivoli
Table 1. Location of log files for the IBM Tivoli Monitoring components. (continued) Component Windows UNIX-based systems Tivoli Enterprise install_dir\logs\hostnamePC_ install_dir/logs/hostname_PC_timestamp.log Monitoring HEXtimestamp-nn.log Server where: where: install_dir Specifies the directory where the Tivoli Enterprise install_dir Portal Server was installed. Specifies the directory...
Page 56 Table 1. Location of log files for the IBM Tivoli Monitoring components. (continued) Component Windows UNIX-based systems IBM Tivoli Not supported. install_dir\logs\hostname_PC_ Warehouse Proxy timestamp.log agent where Specifies the product code. hd is the product code for the IBM Tivoli Warehouse...
Page 57: Installation Log Files
Update synch_msg.log msg.log Forwarder Note: IBM Tivoli Enterprise Console Situation Update Forwarder logs are created on the IBM Tivoli Enterprise Console server. Installation log files Use the log files that are created during installation to help diagnose any errors or operational issues.
Page 58 The level can be set in configuration files or by exporting an environment variable called TRACE_LEVEL with one of the values mentioned above. Configuration of RAS settings is stored in the following files: v CH/config/ITMInstallRAS.properties (for installation) IBM Tivoli Monitoring: Troubleshooting Guide...
Page 59: Upgrading From Tivoli Distributed Monitoringtivoli Log File
*.stdout Tivoli Distributed Monitoring upgrade log file All upgrade actions performed by the IBM Tivoli Monitoring Upgrade Toolkit are recorded in a central log with an associated user ID and a time stamp. Upgrade actions taken outside of the Upgrade Toolkit are not recorded in the log.
Page 60: Reading Ras1 Logs
The Reusing connection handle messages indicates the ODBC provider is reusing resource to conserve memory. The ODBC data provider allocates a connection for each metafile with multiple attribute groups that connect to the same data source IBM Tivoli Monitoring: Troubleshooting Guide...
Page 61: Setting Traces
When you encounter an error with IBM Tivoli Monitoring that requires contacting IBM Software Support, you might be asked to submit a copy of the error log. The error log is part of the trace diagnostic tool in Tivoli Monitoring.
Page 62 1. Always backup the files before altering them. 2. From the Tivoli Enterprise Portal menu, select File > Trace Options. 3. Select a trace class from the list or as instructed by IBM Software Support (such as UNIT:Workspace ALL): v ALL provides data for all classes. Use the setting temporarily, because it generates large amounts of data.
Page 63 1. Always backup the files before altering them. 2. On the computer where the Tivoli Enterprise Monitoring Server is installed, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. 3. Right-click the Tivoli Enterprise Monitoring Server service.
Page 64 About this task On Windows systems: 1. On the computer where the Tivoli Enterprise Monitoring Server is installed, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. 2. Right-click the Tivoli Enterprise Monitoring Server service.
Page 65 Setting the trace option for the Warehouse Proxy agent Procedure 1. On Windows systems, on the computer where the Tivoli Enterprise Monitoring Server is installed, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. 2. Right-click Warehouse Proxy.
Page 66 Setting the trace option for the Summarization and Pruning Agent Use the IBM Tivoli Universal Agent trace facility to diagnose problems with the Summarization and Pruning Agent. See “Setting the trace option for the universal agent” on page 47. The Summarization and Pruning Agent uses C-based RAS1 tracing, Java-based RAS1 tracing and Java-based internal tracing.
Page 67 KBB_RAS1=ERROR (UNIT:ksy4 ALL) ResultSet level trace for summarization. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log). KBB_RAS1=ERROR (UNIT:ksy5 ALL) Column value level trace for summarization. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log). KBB_RAS1=ERROR (UNIT:ksysql ALL) Traces every SQL statement being executed. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log).
Page 68: Setting The Trace Option For The Tivoli
In order to debug KT1 as well, edit the line to be like the following example: KBB_RAS1=ERROR(UNIT:ksh all) (UNIT:kui all) (UNIT:kt1 all) Setting the trace option for the IBM Tivoli Monitoring upgrade toolkit Table 4. Setting the trace option for the Tivoli Monitoring upgrade toolkit...
Page 69 Setting the trace option for Tivoli Enterprise Console event forwarding If your monitoring environment is configured for IBM Tivoli Monitoring event forwarding, you can forward situation events to the Tivoli Enterprise Console and view events on the event server through the Tivoli Enterprise Portal. If you want...
Page 70 You can also view events on the event server through the Tivoli Enterprise Portal. If you want to forward situation events to and view updates from IBM Tivoli Enterprise Console in the Tivoli Enterprise Portal, you can set the trace for the Situation Update Forwarder on the IBM Tivoli Enterprise Console event server.
Page 71: Dynamically Modify Trace Settings For An Ibm Tivoli Monitoring Component
Dynamically modify trace settings for an IBM Tivoli Monitoring component You can access the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, almost all of the agents, and other IBM Tivoli Monitoring components from this utility. This method of modifying trace settings on an IBM Tivoli Monitoring component is the most efficient method since it allows you to do so without restarting the component.
Page 72 IP address of the system where the IBM Tivoli Monitoring component is running. The utility then appears with information about the components that are currently running on this system. For example, the component Tivoli Enterprise Portal Server shows as cnp, the Monitoring Agent for Windows OS shows as nt, and the Tivoli Enterprise Monitoring Server shows as ms.
Page 73: Using The Ibm Tivoli Monitoring Service Console
The IBM Tivoli Monitoring Service Console is uniquely identified by its service point name. All service consoles for a host are linked and presented on the IBM Tivoli Monitoring Service Index for that host. Point a browser to the HTTP port 1920 on a specific host (for example, http://goby:1920) to launch the IBM Tivoli Monitoring Service Index.
Page 74: Starting The Ibm Tivoli Monitoring Service Console
The IBM Tivoli Monitoring Service Index has links to service consoles for the components installed on the computers. Now, when you go to the Service Index, you will also see links to the Agent Service Interface. Use the Agent Service Interface to get reports for an installed agent, whether it is a Tivoli Enterprise Monitoring Agent or Tivoli System Monitoring Agent.
Page 75: Displaying Portal Server Tasks In The Command Prompt
5. Install a third party web server on each computer where you installed the Tivoli Enterprise Portal desktop client: a. From the Windows desktop select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. b. Right-click Tivoli Enterprise Portal desktop and select Reconfigure from the menu.
Page 76: Clearing The Jar Cache
/d TEPS2 /e "select id, name from kfwquery where id like ’zkum.%%’;" Clearing the JAR cache If you encounter problems, IBM Software Support might instruct you to uninstall and to clear the Java archive (JAR) cache. Procedure 1. If the Tivoli Enterprise Portal is running, exit by closing the browser window.
Page 77: Using The Uagent Application
Use the pdcollect tool to collect the most commonly used information from a system. Technicians in IBM Software Support use this information to investigate a problem. The pdcollect tool is used to gather log files, configuration information, version information, and other information to help solve a problem.
Page 78: Ras1Log Tool
Configure your terminal and "stty erase" to use the same key code for backspace. Consider using "^?" as the key code. Verify your configuration with the IBM Tivoli Monitoring distributed utility, Install: BackspaceCheckUtility. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 79: Build Teps Database Utility
Build TEPS Database utility About this task You can use this utility to build a blank database. Prior to the IBM Tivoli Monitoring v6.1 release, this utility would also populate the database with tables. Now, it is necessary to also run the BuildPresentation utility to build the tables in the database.
Page 80: Z/Os Systems
To use IBM Tivoli Monitoring Operations Logging on z/OS systems, complete the following procedure: 1. Create the log datasets. You must create at least one to use the new logging facility, but it is best to create three.
Page 81: Itmsuper
Monitoring Server on any platform. You can run the ITMSUPER tool from a Windows system without having other ITMSUPER software installed. The ITMSUPER Tools are included in the IBM Support Assistant (ISA), a free local software serviceability workbench that helps you resolve questions and problems with IBM software products.
Page 82 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 83: Chapter 5. Installation And Configuration Troubleshooting
Table 5. General frequently asked questions Question Answer Are fix packs required if a user Fix packs for CNP196 are delivered as each monitoring agent is migrated to IBM migrates Candle monitoring Tivoli Monitoring. agent to IBM Tivoli Monitoring. Note: The IBM Tivoli Monitoring download image or CD provides application fixpacks for the monitoring agents that are installed from that CD (for example, ®...
Page 84: Unix-Based Systems Installation Frequently Asked Questions
Table 6. Windows installation frequently asked questions (continued) Question Answer How can I diagnose problems 1. Select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli with product browse settings? Enterprise Monitoring Services. 2. Right-click the Windows agent and select Browse Settings. A text window displays.
Page 85: Frequently Asked Questions For Unix-Based Systems Installation
The backspace key appears to be backspace. Consider using "^?" as the key code. Verify your configuration with working correctly when entering the IBM Tivoli Monitoring distributed utility, Install: BackspaceCheckUtility. text, but you later find characters such as "^?" and "^H" in configuration files and your software malfunctions.
Page 86: General Installation Problems And Resolutions
This coding is required by the operating system in order to invoke a program object in authorized mode [root owned with UID]. The IBM Tivoli Monitoring Installation and Setup Guide documents installation on a single target location. However, by using local testing and configuration control, you can install to multiple target locations and run Tivoli Monitoring from all of them.
Page 87: Debugging Mismatched Application Support Files
Debugging mismatched application support files After upgrading your Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server to IBM Tivoli Monitoring V6.2.3 or higher, you might be warned that the portal server identified mismatched support files. Mismatched files are identified when you forget to upgrade the agent support files during your upgrade or you forget to upgrade the TEPS support, but upgrade the agent support files.
Page 88: Startup Center Shows Some System Types As "Unknown Operating System
OS agent installation does not detect system monitor agents Any agent released with IBMTivoli Monitoring v6.2.2 or before, other than agents built with the latest Agent Builder tool, should not be installed on top of the IBMTivoli Monitoring v6.2.2 System Monitor agents. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 89 @Endpoint\:\:east@EndpointClass\:TMF_Endpoint\:\:Endpoint=INCOMPLETE The only way to change the endpoint status in the status.properties file to INCOMPLETE is to perform a rollback on the upgrade of the item. See the IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring. Rolling back the upgrade: About this task You can use the rollback option (–r option) of the witmupgrade command to remove...
Page 90 GSK7 entry in the registry that can be found under My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\GSK7. Then rerun the IBM Tivoli Monitoring installation to allow the gskit to be reinstalled. Note: Create a backup of the registry before editing it.
Page 91: Upgrade Sql File Not Found When Installing Application Support On The Standby Hub
Seeding support for Monitoring Agent for Microsoft SharePoint Server [8 of 10] KCIIN1602E ERROR - file not found: /boadata/IBM/ITM/tables/cicatrsq/SQLLIB/kqp_upg.sql Option "-f install|upgrade" can be used with the "itmcmd support" command to force using the pristine installation or upgrade support file for the product’s application support.
Page 92: Many Files In The First Failure Data Capture Log Directory
GSKit. This issue occurs on local installations only. Remote installation (remote deploy) does not have this issue. If a system GSKit is installed on the managed system at a level supported by IBM Tivoli Monitoring, the monitoring agents continue to operate normally.
Page 93: Incorrect Behavior After An Uninstallation And Re-Installation
Incorrect behavior after an uninstallation and re-installation You might experience incorrect behavior if you uninstall then reinstall the product without rebooting. For example, you might experience the following problems: v Inability to create trace logs. v Agents do not start. v Agents data is corrupt.
Page 94: Agent Management Services Fails After Deployment On Linux Itanium And Xlinux With Kernel 2.4 Systems
Unable to deploy monitoring agents from the Tivoli Enterprise Portal Receive an error when attempting to deploy an monitoring agent from a previous version of IBM Tivoli Monitoring through the Tivoli Enterprise Portal: KFWITM291E An agent configuration schema was not found" error popup.
Page 95: Unable To Run Gsk7Ikm.exe
2. Get the IBM Java location by running the following script: CANDLEHOME/bin/ CandleGetJavaHome 3. Export variable JAV A_HOME to point to the IBM Java path. For 64bit, gsk7ikm has to be 64bit java. 4. Check the path for a local GSkit. This path is CANDLEHOME/config/ gsKit.config.
Page 96: Installing A Software Package Block (Spb) On Top Of An Existing, Running Ibm Tivoli Monitoring Agent
Recovery from a hard kill of the installer is currently not a supported scenario since the current installer does not have built-in rollback capability. Executing a hard stop of the installer will leave some or all IBM Tivoli Monitoring functions (including uninstall) in an unpredictable or disabled state.
Page 97: Backup Failure Message During A Remote Monitoring Server Upgrade
The agent action SETCONFIG failed with a return code of -1073741819 for product code ud. Remote configuration and installation of a database agent requires that IBM Global Security Kit (GSKit) be installed in directory C:\Program Files\ibm\gsk7, or that the GSKit directory be defined in the Windows System environment variable ICCRTE_DIR.
Page 98: The Agent Installation Log Shows Error Amxut7502E
Contact IBM Software Support if you cannot install the agent. See Chapter 2, “Logs and data collection for troubleshooting,” on page 5 for information on what types of data to collect before contacting Support. See the IBM Support Portal (http://www.ibm.com/support/entry/portal/software).
Page 99: Difficulty With Default Port Numbers
When installing a monitoring agent on top of the Systems Monitor Agent, you receive an error If you try to install a monitoring agent (that is not one of the agents built with IBM Tivoli Monitoring v6.2.2 Agent Builder) on top of the Systems Monitor Agent, you receive an error: install.sh failure: KCI1163E cannot read file "/opt/IBM/ITM/registry/imdprof.tbl".
Page 100: The Monitoring Server And Portal Server Automatically Start After Running Application Support Installer
The behavior is harmless and there is no workaround currently. Errors occur during installation of Event IBM Tivoli Monitoring Event Forwarding tool The product functions normally in spite of the error. Check the installation log for more details.
Page 101 4. Retry the installation. Missing agent managed system group in a hot standby environment In certain IBM Tivoli Monitoring environments, it is possible to get no predefined managed system group for a self-describing agent in a hot standby environment. Tivoli Monitoring environment: v Hub Tivoli Enterprise Monitoring Server and the mirror hub monitoring server are at V6.2.3 Fix Pack 1 (or higher)
Page 102: Windows Installation Problems And Resolutions
See “Adding application support to a monitoring server on z/OS” in the Configuring IBM Tivoli Enterprise Monitoring Server on z/OS guide. Windows installation problems and resolutions...
Page 103: Problems That Are Cleared By Rebooting The Windows System
Remote update of a Windows system fails because of a pending rename that requires a reboot Note: In this case, a 'RC_INFO: Pending rename operations found, must reboot before installation can continue' message is found in the Abort IBM Tivoli Monitoring for Databases.log file. When installing and configuring the Tivoli Enterprise...
Page 104: After An Upgrade, The Tivoli Enterprise Portal Server Is In The 'Stop Pending' State And Cannot Be Manually Started
2. Configure the monitoring server to work correctly with Windows User Account Control (UAC). v Using Windows Explorer, navigate to the IBM Tivoli Monitoring product installation directory (default is c:\IBM\ITM). v Navigate to the appropriate subdirectory, right-click one of the executable files listed below, and select Properties.
Page 105: Installshield Displays The Error "1607: Unable To Install Installshield Scripting Runtime" During Installation On Windows From A Network-Mounted Drive
Installation on a Windows 2003 server fails with Error Number: 0x80040707 The following error can occur while installing IBM Tivoli Monitoring V6.1 on a Windows 2003 Server: This error can occur for the following reasons: 1.
Page 106: Deploying An Agent Instance Gives A Kuicar020E Error
When installing IBM Tivoli Monitoring or IBM Tivoli Monitoring agents on Windows systems, IBM Tivoli Monitoring installation should present a pop-up requesting reboot if files are locked. However, there are times when the IBM Tivoli Monitoring installation does not inform you of locked files. This can cause the IBM Tivoli Monitoring installation to loop or hang.
Page 107: Self-Describing Capability Might Be Overwritten By Unix Monitoring Server Application Support
If your environment has a self-describing monitoring agent that is at a lower version of IBM Tivoli Monitoring than the Tivoli Enterprise Monitoring Server on Linux or UNIX that it connects to, it is possible that the installation of application support to the monitoring server overwrites the monitoring agent's self-describing capability.
Page 108 Manually install this product on the portal server and portal client if the expected self-describing agent product installation did not take place. See “Self-describing agent installation” in the IBM Tivoli Monitoring Installation and Setup Guide and “Self-describing monitoring agents” in the IBM Tivoli Monitoring Administrator's Guide.
Page 109: On A Rhel6 64-Bit System, The Tivoli Monitoring Installer Fails With Errors
/opt/IBM/ITM/li6243/gs/bin/private_verifyinstall runGSkit: error li6243 - GSK check error, verifyInstall test failed runGSkit: Backup failed GSKit installation into /opt/IBM/ITM/tmp/badGSKit_keep.tar Tivoli Monitoring requires both the 32-bit and 64-bit compat-libstdc++ libraries installed on the 64-bit system. The installation fails because of the missing 32-bit libstdc++.so.5.
Page 110: Message Is Received About The Korn Shell After Running The Install.sh File
Refer to the Flash note titled "Newer ksh shell may allow regression of ITM installation" for more information, including steps to take to avoid damage to your IBM Tivoli Monitoring installation. The Newer ksh shell may allow regression of ITM installation (http://www-01.ibm.com/support/docview.wss?uid=swg21408506) Flash note...
Page 111: Unix And Linux Install.sh Command Fails With
The error states that the Java Runtime Environment shared library could not be loaded. Java will execute using unsecured credentials. On some Solaris, Linux, and HP platforms, IBM Tivoli Monitoring has files with different bit sizes: executable files are 64 bit, while the provided JRE is 32 bit. This mismatch does not allow the JNI to work properly, so the current method cannot be used, and the previous method will be used.
Page 112: On Hp-Ux Systems, Where The Host Name Does Not Equal The Nodename, The Upgrade Installation Fails To Stop Running Processes
Running IBM Tivoli Monitoring processes were not shutdown by the installer during the upgrade of the Tivoli Enterprise Monitoring Server or agents when the nodename does not equal the host name on HP-UX systems. On HP-UX, if the system has a host name longer than 8 characters then the nodename should be set to 8 characters or less.
Page 113: Installation On Sles9 Terminates With Install.sh Failure:kci1008E Terminating
“KCI1235E terminating ... problem with starting Java Virtual Machine” If you try to install IBM Tivoli Monitoring on Red Hat 5 with SELinux set to "permissive" or "disabled" mode ("enforced" mode is not supported by IBM Tivoli Chapter 5. Installation and configuration troubleshooting...
Page 114: Installation On The Linux S390 R2.6 64-Bit Operating System Fails With The Message "Linux Monitoring Agent V610Rnnn Unable To Install Agent" Where Nnn Is The Release Number
“z/OS-based installations problems and resolutions” on page 104 Tivoli Monitoring z/OS initialization checklist Use the IBM Tivoli Monitoring z/OS initialization checklist to troubleshoot problems with your Tivoli Monitoring installation on z/OS. The z/OS initialization checklist includes the following sections: v “Tivoli Monitoring Services Engine initialization”...
Page 115 The Reliability, Availability and Servicability (RAS1) service refers to the RAS1 building block (Basic Services component) used for diagnostic tracing. Nearly all diagnostic information for IBM Tivoli Monitoring is delivered via the RAS1 (trace) component. This component is configured in member KBBENV of RKANPAR using the KBB_RAS1 environment variable.
Page 116 3. Ensure the first SEND ran without error. See “The First SEND” on page 99. The INITAPI call IBM's implementation of TCP/IP requires that an address space perform an INITAPI before issuing an TCP/IP service request. The INITAPI establishes a communication pipe between the TCP/IP and the OMEGAMON Platform address space.
Page 117 GLOBAL or DEFAULT configuration data. Consequently, native z/OS address spaces are not enabled for name resolution by default. By adding a DD statement for SYSTCPD to the started task JCL of the IBM Tivoli Monitoring task (pointing to a usable file in USER.PARMLIB(TCPDATA)), resolver support can be enabled.
Page 118 NULL", and it is followed by another RPC timeout message. The Server list IBM Tivoli Monitoring processes build and query a list of possible Tivoli Enterprise Monitoring Server hub addresses, called the Server list. This server list contains IBM Tivoli Monitoring: Troubleshooting Guide...
Page 119 local (LLB) and global (GLB) entries. The LLB entries of the Server list are derived. The GLB entries of the Server list are built from the content of the KDCSSITE member of RKANPAR. Shown below are two server lists. The first Server List is for a Tivoli Enterprise Monitoring Server hub, the second Server List is for a remote Tivoli Enterprise Monitoring Server.
Page 120 If the bind failure is due to EADDRINUSE but the Broker service is started, the error might not be fatal. Determine whether or not the bind of this IBM Tivoli Monitoring address space was to the LLB in that address space. In some instances, an address space can bind to the LLB of another address space.
Page 121 Global Location Broker service initialization The Global Location Broker (GLB) differs from the Local Location Brokers in one important respect other than the name: there is only one GLB for the domain or enterprise. By definition, there will be only one Local Location Broker which points to the Global Location Broker for the domain.
Page 122: Z/Os-Based Installations Problems And Resolutions
How do you change monitoring server storage parameters using the Configuration Tool? About this task You can increase the following storage-related parameters if IBM Software Support personnel instructs you to do so: v Web Services SOAP Server v startup console messages...
Page 123 If you must edit the field, regenerate the RTE Build job. For more information about configuring a z/OSTivoli Enterprise Monitoring Server and the RTE Build job. see the Configuring the Tivoli Enterprise Monitoring Server on z/OS (http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/ com.ibm.itm.doc_6.2.3fp1/itm623fp1_zconfigtems.htm). The error 'CMSLIST NOT ALLOWED' occurs on the 'Specify Advanced Configuration Values' panel when Tivoli Enterprise Monitoring Server type equals hub.
Page 124 If you attempt to copy the catalog and attribute files to a Tivoli Enterprise Monitoring Server on z/OS using the IBM Tivoli Monitoring “FTP Catalog and Attribute Files” option on Linux or UNIX and get an error that the transfer failed, take steps to resolve the error.
Page 125: Uninstallation Problems And Workarounds
Save the file and exit. c. Stop the portal server if it is running and restart it. Backing up the ICAT and CSI environment Manually merge existing datasets with IBM Tivoli Monitoring datasets if IBM Software Support instructs you to do so. Procedure 1.
Page 126: Unable To Uninstall Multi-Instance Agent From A Managed System On Windows 64Bit
About this task After uninstalling an IBM Tivoli Monitoring v6.1.1 agent and its application support files, the IBM Tivoli Monitoring Online (F1) Help produces an error when selected. The browser displays "The page cannot be displayed" with a URL of http://host:9999/help/index.jsp.
Page 127: Uninstallation Of An Agent Occurring More Than Once Stops The Os Agent
OS agent If uninstallation an agent is performed more than once, it stops the Monitoring Agent for Windows OS agent as well as other IBM Tivoli Monitoring components. Also, an error message does not appear in the console. After uninstallation, Tivoli Enterprise Monitoring Server folder is not deleted There is no negative impact from these files being left on the system.
Page 128 109. Your previous installation is too corrupt to use and must be completely removed. You must either completely reinstall the previous release and then upgrade to IBM Tivoli Monitoring or just install IBM Tivoli Monitoring without attempting to upgrade.
Page 129 Installation failed after files were copied: If your installation failed after the files were copied, your current installation has been corrupted by the partial installation of IBM Tivoli Monitoring. You must either completely reinstall the previous release and then upgrade to IBM Tivoli Monitoring or just install IBM Tivoli Monitoring without attempting to upgrade.
Page 130 OMEGAMON or IBM Tivoli Monitoring, attempt to uninstall. About this task Use the following steps if an entry for either Candle OMEGAMON or IBM Tivoli Monitoring exists in the Add and Remove Programs utility: 1. Attempt to uninstall both releases from the Add and Remove Programs entry.
Page 131: Incorrect Behavior After An Uninstallation And Reinstallation
Restart the system to resolve the problems. Tivoli Data Warehouse database does not uninstall When you uninstall IBM Tivoli Monitoring, the Tivoli Data Warehouse database is not removed and the ODBC data source exists. You must remove the Tivoli Data Warehouse database and the ODBC manually.
Page 132: Prompted To Uninstall A Database That Was Not Running During Uninstallation
\\ITMUpgradeManager\\setup. ITMUpgradeManager/uninstall.sh Contact IBM Software Support if you cannot uninstall the agent. See Chapter 2, “Logs and data collection for troubleshooting,” on page 5 for information on what types of data to collect before contacting Support. See the IBM Support Portal (http://www.ibm.com/support/entry/portal/software).
Page 133: Chapter 6. Connectivity Troubleshooting
If security validation is active on the hub monitoring server, make sure the user ID is defined to the security system. For more information on security validation see the IBM Tivoli Monitoring Installation and Setup Guide (http://publib.boulder.ibm.com/infocenter/ tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623FP1_install.htm) or IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Page 134 Edit the agent *.ini file and add KDEB_INTERFACELIST=IP_address, where IP_address is the correct address. For more information see “Controlling port number assignments” in the IBM Tivoli Monitoring Installation and Setup Guide. The portal server cannot initialize Start DB2 or wait for DB2 to finish initializing.
Page 135: Cannot Connect To The Portal Server
Table 12. Cannot log in to the Tivoli Enterprise Portal Server (continued) Problem Corrective action and solution If the Tivoli Enterprise Portal Server When the portal server is configured to authenticate against the LDAP connection to LDAP is lost. server (with optionally enabled Single Sign-On capability), if you lose the portal server to LDAP connection, this will cause any log in attempt to fail with error code KFWITM393E: "User ID or password is invalid".
Page 136 SQL1226N The maximum number of client connections are already started. SQLSTATE=57030 Both messages SQL1224N and SQL1226N occur when the portal server attempts to validate the user ID entered in the browser. 2. Restart the database. 3. Attempt the log in again. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 137: Cannot Connect To Tivoli Enterprise Portal Server
Note: Do not use localhost for 127.0.0.1 and simultaneously for ::1 (which is the IPv6 address). Tivoli Enterprise Portal client 1. Select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise cannot find the Tivoli Enterprise Monitoring Services.
Page 138: Cannot Launch The Portal Client On Windows Xp After Installation (Message Kfwitm215E)
4. Start Tivoli Enterprise Portal in browser mode using the IP address instead of the host name. 5. If you are still unable to connect, contact IBM Software Support. See Chapter 2, “Logs and data collection for troubleshooting,” on page 5 for information on what types of data to collect before contacting Support.
Page 139: Portal Server Is Initializing And Is Not Ready For Communications
Tivoli Enterprise Monitoring Server. You might need to include the IBM Java program in the programs section of your firewall software and include the IP addresses of other IBM Tivoli Monitoring components in the access control for the firewall.
Page 140: Db2 Errors When Opening A Tivoli Enterprise Portal Workspace
If you are able to log in but receive an error message that you cannot open a workspace in the Tivoli Enterprise Portal, verify that the database agent and manager are working correctly. The configuration settings might need updating. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 141: A Monitoring Process Fails To Start On Linux Or Unix After Changing A .Profile For Root
A monitoring process fails to start on Linux or UNIX after changing a .profile for root IBM Tivoli Monitoring processes such as the monitoring server, portal server, warehouse proxy agent, summarization and pruning agent, and other agents are all started while you are logged on as a user ID on Linux and UNIX systems.
Page 142: Heartbeat Issues When Running On A Linux Guest Using Vmware
Linux guest to run faster or slower than real world time. If any IBM Tivoli Monitoring products are installed on Linux guests whose clocks are not running correctly, the result can be erratic system behavior.
Page 143 Linux guest clock is running slow. This causes the IBM Tivoli Monitoring product to behave erratically if the clock is not fixed. Chapter 6. Connectivity troubleshooting...
Page 144 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 145: Chapter 7. Portal Client Troubleshooting
Data in the Tivoli Enterprise Portal is missing and you receive the following error: KFWITM217E - SQL1_CreateRequest failed, rc=209 No support exists for the 64-bit data type at levels before IBM Tivoli Monitoring v6.2.1for the remote monitoring server. In IBM Tivoli Monitoring v6.2.1 and later, only 16-bit, 32-bit, and 64-bit data types are supported.
Page 146: Client Allows You To Save A Situation With An Invalid Character
Tivoli Enterprise Portal parameter to a path that does not contain any non-latin1 characters by completing the following steps: 1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. 2. In the Manage Tivoli Monitoring Services window, right-click Tivoli Enterprise Portal >...
Page 147: The Tivoli Enterprise Portal Desktop Does Not Work When Exporting Display
Use a 1.6 JRE to run the Tivoli Enterprise Portal desktop by doing the following: 1. Locate the install_dir/architecture/cj/bin/cnp.sh file on the Linux system. 2. Export TEP_JAVA_HOME=/opt/ibm/java-i386-60/. 3. Export KCJ_HOME=..Some attribute groups showing a different name in the Tivoli...
Page 148 A sample setting looks like this: KFW_TOPOLOGY_CLUSTER_LIST=AFF_xxx AFF_yyy Where the setting lists the agent affinities to which this host name logic should apply. Here are some affinities for agents distributed with IBM Tivoli Monitoring version 6.1: AFF_NT_SYSTEM "Windows OS"...
Page 149: Tivoli Enterprise Portal Desktop Called Through Java Web Start Does Not Work Properly After Adding Agents Support For Tivoli Enterprise Portal Server
KUICCU097E: The path to the Java home directory was not found. The directory name returned by the CandleGetJavaHome script was not found. Call IBM Software Support. To resolve this problem launch the CandleGetJavaHome.bat script located in InstallITM subdirectory of ITM home directory. Ensure that valid Java Home directory is returned.
Page 150: Cannot Launch The Tivoli Enterprise Portal Help
About this task You receive the error message: invalid id/password. You must set the local security policy on an Active Directory server. If you installed IBM Tivoli Monitoring on a system where Microsoft Windows Active Directory is installed, you must update the local security policy on that system to include the sysadmin user so that you can log on to the Tivoli Enterprise Portal.
Page 151: Several Enterprise Workspaces Are Returning An
Enterprise Portal client exits. If you encounter this problem, use any recent Sun JRE (1.5.0_14 or above). This problem is limited to IBM's 1.5 java. Note: A Sun bug report bug_id=6578895 which describes the issue was fixed in Sun's 1.5.0_14.
Page 152: Password Problem Using The Ldap Security Option On Active Directory System
Internet Explorer 6.x, 7.x, or Mozilla Firefox 2.x, a memory leak might be observed that continues to grow as the number of workspace switches increases. This problem is due to a handle leak introduced by the IBM Java 1.5 plug-in component. The same problem is present in the Sun Java 1.5 plug-in component.
Page 153: On Linux, Ibm Tivoli Enterprise Monitoring Agent Topics Do Not Display In The Help Contents Or Index Tabs
About this task The Tivoli Enterprise Portal client uses the IBM Java Plug-in, which is automatically installed on your computer with the portal client. Adjust the IBM Java Plug-in properties if performance is slow or your workstation receives...
Page 154 Tivoli Enterprise Portal JAR files. Complete the following steps to adjust the Java Plug-in settings: Procedure 1. Open the Windows Control Panel. 2. Double-click IBM Control Panel for Java(TM) to display the Java(TM) Control Panel. 3. From the Java(TM) tab: a. Click View.
Page 155: Java Errors Occur With The Ibm V1.4.2 Jre
If you experience any problems using the IBM 1.4.2 JRE use the version shipped with the Tivoli Enterprise Portal v6.1. IBM Tivoli Monitoring v6.2 ships with IBM 1.5.0 JRE. Use this version if you have installed IBM Tivoli Monitoring v6.2.
Page 156: Tivoli Enterprise Portal Has High Memory Usage And Poor Response Time
Open). If you have multiple Java Plug-ins, check that you have the properties for the right plug-in opened: The About tab shows V1.4.2, and the Cache or Certificates tab shows IBM in the path or in the signed certificate. 3. In the Advanced tab, select the IBM JRE 1.4.2 from the Java Runtime Environment list.
Page 157: Data Is Not Returned To The Portal Client
Consider the following values: -Xminf0.15 –Xmaxf0.30 The IBM Java documentation warns that setting these values too low can cause poor Java performance. For more information on Java heap tuning parameters, see the IBM Developer Kit and Runtime Environment, Java 2 Technology Edition, Version 1.4.2 Diagnostics Guide (http://publib.boulder.ibm.com/infocenter/javasdk/...
Page 158: Workflow Editor Is Disabled And The Following Tools Do Not Display: Event Console, Graphic View, Edit Navigator View (Navigator View Toolbar)
Edit Navigator View (Navigator view toolbar) 1. On the computer where the Tivoli Enterprise Portal Server is installed, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. 2. Right-click the Tivoli Enterprise Portal Server service, point to Licensing and select Tivoli Enterprise Portal Server from the menu.
Page 159: At The Bottom Of Each View, You See A Historical Workspace Kfwitm217E Error
At the bottom of each view, you see a historical workspace KFWITM217E error At the bottom of each view, you see the following historical workspace KFWITM217E error: Request failed during execution, and a red icon. Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view.
Page 160: Kshsoap Client Fails Because Of Missing Libraries On Unix-Based Systems
Category and Message field of the universal message does not accept DBCS About this task To record a DBCS IBM Tivoli Monitoring universal message when a situation is true, following these steps on the Tivoli Enterprise Portal: 1. Open the Situation editor.
Page 161: Agents Display Offline In The Portal Client But Fire Situations And Agent Logs Report That They Are Running
Manually set the variable KFW_CMW_EVENT_SLEEP in cq.ini on Linux or kfwenv on Windows to less than 10 seconds: KFW_CMW_EVENT_SLEEP=5 Desktop client performs poorly after installing Language Packs for IBM Tivoli Monitoring About this task Some configuration settings for the Tivoli Data Warehouse database can cause performance degradation.
Page 162: Existing Omegamon Product Imagery Displays After Upgrading To Ibm Tivoli Monitoring V6.1
8. Start DB2: db2start 9. Recycle Tivoli Enterprise Portal Server service. Existing OMEGAMON product imagery displays after upgrading to IBM Tivoli Monitoring V6.1 About this task Existing OMEGAMON product imagery displays after upgrading because there it was cached on the client browser. Use the following steps to correct the problem: 1.
Page 163: Cannot Load A Ws_Pres.css File In Order To Select A Language Other Than English
Cannot load a ws_pres.css file in order to select a language other than English The user.language parameter allows you to specify the language code. The portal client uses cascading style sheets to render the application text. If no localized version of a style sheet, such as ws_press.css, is available, the English version will be used.
Page 164 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 165: Chapter 8. Portal Server Troubleshooting
KCIIN2724W User who runs IHS (IBM HTTP Server) does not have proper permissions to IHS content directory. This error occurs when the IBM HTTP Server is running under a user that does not match the user specified in the CANDLE_HOME/ARCH/iu/ihs/httpd.conf file. For the portal server to run correctly, the user who is running the IBM HTTP Server must have access to the IBM HTTP Server content directory.
Page 166: The Portal Server And Warehouse Proxy Agent Fail To Connect To The Database On A 64-Bit Windows System
For IBM Tivoli Monitoring v6.2.2 Fix Pack 2 or higher, you can set it in the command environment , using SET/export, or you can set it in the environment files (KUIENV on Windows systems, or the $CANDLEHOME/bin/tacmd shell script on UNIX and Linux systems).
Page 167: Portal Server Performance Is Slow
Restart the Tivoli Enterprise Portal Server using the following command: cd /opt/IBM/ITM/bin ./itmcmd agent start cq For information on how to modify kernel parameters, see “Modifying kernel parameters (Linux)” (http://publib.boulder.ibm.com/infocenter/db2luw/v9/ topic/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm) in the IBM DB2 Database for Linux, UNIX, and Windows Information Center. Chapter 8. Portal server troubleshooting...
Page 168: You Receive A Kfw Error When A Query Is Sent To
(#) in the following Tivoli Enterprise Portal Server environment files, and restart the portal server. v Windows systems: \ibm\itm\cnps\kfwenv v Linux or AIX systems: /opt/IBM/config/cq.ini After you change the KFW_REPORT_NODE_LIMIT variable, you might receive the following error: KFWITM217E Request error: SQL1_CreateAccessPlan failed, rc=1.
Page 169: Non-Hub Situations Are Not Associated At The Tivoli Enterprise Portal Server Level
The Tivoli Enterprise Portal Server depends on the Eclipse Help Server to display standalone help. The Eclipse Help Server is treated in the same way as Tivoli Enterprise Portal Server - as a server component (as opposed to IBM Tivoli Monitoring v6.1, where the Eclipse Help Server was treated as an agent).
Page 170: Corba User Exception Is Included In The Portal Server Log When Creating Situations
Using the eWAS start and stop commands results in an internal error, indicated by KFWITM392E Internal error occurred during login. If you have already used the eWAS commands, see "Starting and stopping eWAS" in the IBM Tivoli Monitoring Administrator's Guide for recovery instructions. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 171: Chapter 9. Monitoring Server Troubleshooting
Troubleshooting monitoring server problems on distributed systems The problems described in this section might occur on distributed systems. For information about configuring theTivoli Enterprise Monitoring Server, refer to the IBM Tivoli Monitoring Installation and Setup Guide . © Copyright IBM Corp. 2005, 2012...
Page 172: The Ct_Get Request Method Fails In Soap
Due to an issue in the monitoring server KRANDREG module, the remote monitoring server can go into a loop making continuous calls to the IBM Tivoli Monitoring Global Location Broker facility. This loop can happen whenever the hub monitoring server Global Location Broker contains EXACTLY 50 entries relating to the IBM Tivoli Monitoring Warehouse Proxy Agent.
Page 173: Upgrade Inconsistency Between The History And Object Windows
Upgrade inconsistency between the History and Object windows The historical collections created in previous versions of IBM Tivoli Monitoring are not eligible to be members of a group in a later version of the software. Attribute groups started for collection on the managed...
Page 174: To Decrypt A Password, Kds_Validate_Ext='Y' Is Required
Tivoli Enterprise Monitoring Server should be attempted only after verifying the CMS.EXE process is also terminated. A CMS.EXE left running in response to the earlier failure is likely to cause a subsequent start of Tivoli Enterprise Monitoring Server to fail. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 175: Thresholds.xml And Tivoli Enterprise Monitoring Server Table Not Cleaned When Managed System Override Is Removed
This crash has only been observed rarely during product testing. The IBM Tivoli Monitoring configuration tool checks the output produced by the seeding functions, and it reports that the monitoring server application support was added successfully.
Page 176: Tacmd Login Fails When Monitoring Server Is Configured With Ldap Authentication
1. export LDAP_DEBUG=65535 2. export LDAP_DEBUG_FILE=/opt/IBM/ITM/logs/ldaptrace.txt (or whatever path/file you want) 3. rm /opt/IBM/ITM/logs/ldaptrace.txt (to remove the file before restarting the Hub) Restart the hub monitoring server. Note that these LDAP-related trace settings remain active until the monitoring server is restarted from a shell session where the variables are not exported.
Page 177: Some Agents Are Displayed In The Service Console List That Are Not Accessible From That User Interface
Some agents are displayed in the Service Console list that are not accessible from that user interface For instance, if you click IBM Tivoli M5 Agent Service Interface, a popup is displayed for the User Name and Password. There is no valid user name and password combination that will work, and you must click Cancel to get out of this page.
Page 178: Tacmd And Soap Are Not Able To Connect
SOAP, the tacmd login command might fail. The tacmd logic attempts to use the base port connected with the "IBM Tivoli Monitoring Web Services" link. If that is unavailable, it uses the 1920 port. That will fail if the 1920 process is not the same as the monitoring server process.
Page 179: Remote Monitoring Server Lost Connection To The Hub And All Agents Display Offline
2. If you have a remote Tivoli Enterprise Monitoring Server, but the hub Tivoli Enterprise Monitoring Server is offline. In any other situation, call IBM Software Support. Providing the wrong path to configuration files during LDAP configuration causes the Tivoli Enterprise Portal login window...
Page 180: Crash On Linux Remote Monitoring Server During Hub Failover To Hot Standby
Tivoli Enterprise Monitoring Servers obtain their agent support from the hub Tivoli Enterprise Monitoring Server. In order to apply agent support to a remote Tivoli Enterprise Monitoring Server, the hub Tivoli Enterprise Monitoring Server must be running and reachable by the remote Tivoli Enterprise Monitoring Server. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 181: Using A Deploy Group With Addsystem Or Updateagent Commands
During installation of a remote Tivoli Enterprise Monitoring Server on a Windows system, the agent support is typically applied. This fails if the hub Tivoli Enterprise Monitoring Server is unreachable. During remote Tivoli Enterprise Monitoring Server installation on the Windows platform, ensure the hub Tivoli Enterprise Monitoring Server is running.
Page 182: The Platform View In The Manage Tivoli
An example of this is if the tacmd listSystems command is run specifying a remote monitoring server that contains universal agents that contain more than 200 subnodes, the query will OR together all of the subnodes. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 183: Tivoli Enterprise Monitoring Server Aborts Unexpectedly When Exiting The Telnet Session Used To Start It
Tivoli Enterprise Monitoring Server aborts unexpectedly when exiting the telnet session used to start it About this task A UNIX-based systems Tivoli Enterprise Monitoring Server aborts unexpectedly when exiting the telnet session used to start it, either from the client or the command line.
Page 184: A Deleted Object Is Redisplayed When Two Hot Standby (Fto) Hubs Reconnect
"Program KDFCINIT with task id 8 ended" and "Program FAXCMON with task id 7 ended" messages are generated in the IBM Tivoli Monitoring z/OS Tivoli Enterprise Monitoring Server RKLVLOG if either or both IBM Tivoli OMEGAMON XE on z/OS and OMEGAMON XE for Storage on z/OS are running in the monitoring server address space.
Page 185: Kppllist Klvst001 Candle Engine Initialization Error(S), Abend U0012' In The Rklvlog At Startup
The Tivoli Enterprise Monitoring Server start task (CANSDSST default) encountered error message 'KLVST044 LOADLIST MEMBER NOT FOUND IN RKANPAR DATASET (KDSLLIST) KppLLIST KLVST001 CANDLE ENGINE INITIALIZATION ERROR(S), ABEND U0012' in the RKLVLOG at startup About this task The Tivoli Enterprise Monitoring Server start task (CANSDSST default) encountered error message "KLVST044 LOADLIST MEMBER NOT FOUND IN RKANPAR DATASET (KDSLLIST) KppLLIST KLVST001 CANDLE ENGINE INITIALIZATION ERROR(S), ABEND U0012"...
Page 186: Cannot Encrypt Text. A Call To Csnbsye Failed. Cannot Encrypt Contents Of Keyfile
About this task You can increase the MINIMUM() storage settings in the &rhilev.&rte. RKANPAR(KDSSYNSIN) member if IBM Support personnel instructs you to do so. The default value for the MINIMUM() parameter is MINIMUM(150000,X). Use the following steps to increase this value or any other storage-related parameters: 1.
Page 187: Error Message 'Kdsma013 Open Vtam For
2. On the next panel, navigate to the F5=Advanced key. Do the following on the Specify Advanced Configuration Values: v Edit the Minimum extended storage field to 300000 K. v Edit the Maximum storage request size fields to 16 (Primary) and 23 (Extended).
Page 188 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 189: Chapter 10. Monitoring Agent Troubleshooting
Action Type: UNIX OS Description: Kux:KUX6065 Command : UX:AMS_Stop_Agent "&KCA_UX_Agent_Active_Runtime_Status.PAS_Agent_Name" "&KCA_UX_Agent_Active_Runtime_Status.Process_Name" &KCA_UX_Agent_Active_Runtime_Status.Process_IDKey : KUX_1212721981813 OS agents Review the OS agent entries for a description of configuration and usage problems and how to resolve them. © Copyright IBM Corp. 2005, 2012...
Page 190: Linux Os Agent Fails To Start
You might encounter a problem monitoring specific events with the Windows OS Agent. When running IBM Tivoli Monitoring V6.2.3 Fix Pack 1 (or later), you have the capability to display events and event data from any event log you are monitoring.
Page 191: Warehouse Agents
OMEGAMON XE agents on z/OS You might encounter a problem using reflex actions for your OMEGAMON XE agents on z/OS. Note that IBM Tivoli Monitoring V6.2.2 FP6 IZ98638 does not support reflex actions for OMEGAMON XE agents on z/OS.
Page 192: Unable To Configure The Warehouse Proxy Agent With Modified Parameters From The Tivoli Enterprise Portal Gui
A workspace view is showing an error It is possible that the workspace definition was saved incorrectly. An example workspace would be the IBM Tivoli Monitoring for Databases: Oracle Agent's SQL Text workspace. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 193: Local History Migration Tools Move The Agent Operation Logs To Multiple Agent History Locations
32-bit Agent Builder agent will not start on 64-bit Windows with System Monitor Agent-installed OS Agent A System Monitor Agent must not be installed into a system where existing IBM Tivoli Monitoring components (including other monitoring agents) are already installed, with this exception: Agents built with Agent Builder V6.2.2 or subsequent may be installed alongside a System Monitor Agent, provided they run in the same mode as the Windows System Monitor Agent.
Page 194: Unable To Locate The File Name Of An Exported Situation That Begins With Numerals
If you find that the Tivoli Data Warehouse database does not contain a WAREHOUSEPRUNE table, and if in the portal server database the KFWWHISTDATA table has been renamed KFWWHISTDATABAK, rename the KFWHISTDATABAK table to KFWWHISTDA in the portal server, and then IBM Tivoli Monitoring: Troubleshooting Guide...
Page 195: Agent Names And Icons Are Displayed Incorrectly
reconfigure the warehouse. The WAREHOUSEPRUNE table will then be in the Tivoli Data Warehouse database, and the issue will be resolved. Agent names and icons are displayed incorrectly When installing portal server support from images older than v6.2.2, the support installation might fail with no symptom, leading to names and icons related to the agent being displayed incorrectly in the Tivoli Enterprise Portal.
Page 196: Subnode Limitations For Autonomous Function
1 disk at a time. An enterprise situation would define the disk name as the display item so a separate situation alert would be displayed for each disk with less than 20% free space available. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 197: Binary Path Attribute Of The Windows Os Agent Does Not Show A Value
Unable to start tems service. Check the event log. Monitoring Agents for Windows OS that are v6.2.1 and higher can be installed onto a monitoring server with no adverse side effects. IBM Tivoli Monitoring Application Agents regardless of version can also be installed onto a monitoring server with no adverse side effects.
Page 198: Calendar Entries Overlap
Collection Configuration window If you have configured historical collection for the monitoring agents and upgraded to IBM Tivoli Monitoring v6.2.2, you might notice that the names listed for attribute groups are now unintelligible. In some cases, these names are not friendly and hovering over the item on the navigation tree shows the attribute group to which it belongs.
Page 199: Situations With Attributes From More Than 1 Group Not Supported With Autonomous Agent
There can be a variety of factors that lead to a failed history collection: v The size of the history data file affects the amount of time it takes the agent to read the file. v The amount of data the agent is trying to send to the monitoring server. v The bandwidth of the communications (for example, a slow data rate).
Page 200: Agent Goes Offline After Removing History Path
Due to packaging optimizations in v6.2.1, installing a backlevel Windows OS Agent into an existing 6.2.1 environment is not supported, and the Tivoli Enterprise Monitoring Server cannot start. If this is the desired deployment, the backlevel Windows OS Agent should be installed first. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 201: Snmp Trap Sendto Fails
Must end with an alphanumeric character BAROC file is missing for IBM Tivoli Monitoring 5.x Endpoint situations A BAROC file does not exist for the IBM Tivoli Monitoring 5.x Integration Agent that defines the class definitions for the following situations: v KTM_Health_Indication...
Page 202: The Target Host Name, Platform, And Version Information Is Not Displayed For The Deployment Status In The Cli Or The Workspace
@echo "Creating DEPLOY Group Window" tacmd creategroup -g Window -t DEPLOY -d "Windows Deploy Group" @echo "Adding ACHAN1 to Window DEPLOY group" tacmd addgroupmember -g Window -t DEPLOY -m achan1.raleigh.ibm.com -p KDYRXA.RXAusername=achan KDYRXA.RXApassword=xxxxx KDYRXA.installDir=C:\data @echo "Issuing group DEPLOY of Windows OS agent"...
Page 203 -g option has been previously run. See the "Securing your IBM Tivoli Monitoring installation on Linux or UNIX" appendix in the IBM Tivoli Monitoring Installation and Setup Guide for further details.
Page 204: After Installing And Configuring A Monitoring Agent, It Fails To Start
If the SecureMode file is in the registry directory, SecureMain was run in environment. This does not allow the monitoring agent to start if you try to start it without root privileges. See the IBM Tivoli Monitoring Installation and Setup Guide for instructions on how to have monitoring agents work properly with SecureMain in place.
Page 205: If A Managed System List Is Removed For A Situation, The Situation Stops
Tivoli Enterprise Portal Server Universal Message Console and the Tivoli Enterprise Monitoring Server RKLVLOG cannot display the situation display name, the ID string is displayed instead. To ensure that your situations are displayed using the display name instead of the display ID, make sure that your situation names do not exceed 31 characters in length, and that they do not contain any special characters.
Page 206: Unable To Receive Summarized Data For The Last Hour In The Tivoli Enterprise Portal
4. Open the tdw_schema_index.sql file and find the index that was deleted in step 5. Edit out all statements except the index you want to recreate. 6. Run the create index statement. 7. Start the Summarization and Pruning Agent. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 207: Summarization And Pruning Agent Schedule Not Affected By Daylight Saving Time
Summarization and Pruning agent schedule not affected by daylight saving time If after starting the Summarization and Pruning agent you allow daylight savings time to be reached, the agent start time is now 1 hour later than the time before the time change.
Page 208: Deploy Cannot Tell If The Installation Failed
Deploy cannot tell if the installation failed When installing an OS Agent on an endpoint that already has an OS Agent, the installation program does not write out a C:\IBM\ITM\InstallITM\Abort IBM Tivoli Monitoring 20070924 1319.log in the createNode specified directory. It writes messages to the existing C:\data\itm61_oqv_ga2_koy\InstallITM\IBM Tivoli Monitoring 20070924 1319.log log file and reports the error in that log file.
Page 209 be myhost1.acme.north.prod.com. Inclusion of the network domain name causes the agent name in the example above to expand to SERVER1:myhost1.acme.north.prod.com:KXX. This resulting name is 39 characters long. It is truncated to 32 characters resulting in the name SERVER1:myhost1.acme.north.prod. The agent name truncation is only a problem if there is more than one monitoring agent on the same system.
Page 210: One Monitoring Agent's Workspaces Are Listed Under Another Agent Node On The Portal Client
CTIRA_HOSTNAME environment variable to generate component names. Check the documentation for the monitoring agent that you are using for information on name generation. If necessary, contact IBM Software Support. Other symptoms that can be observed when multiple instances of a monitoring...
Page 211: Issues With Starting And Stopping An Agent As A Non-Administrator User
v On Windows: install_dir\tmaitm6\Kproduct_codeCMA.INI. For example, the product code for the Monitoring Agent for Windows OS is NT file name for is KNTCMA.INI. v On UNIX and Linux: install_dir/config/product_code.ini. For example, the file name for the Monitoring Agent for UNIX OS is ux.ini. 2.
Page 212: When Upgrading A System Service Monitors Agent From 3.2.1 To 4.0, Receive Kdy3008E Message
Tivoli Data Warehouse is copied over after a set period of time. You can set maintenance to roll off the data. For more information on rolling of this data so that it is backed up, see the IBM Tivoli Monitoring Configuring Tivoli Enterprise Monitoring Server on z/OS Guide.
Page 213: Error List Appears In Warehouse Logs
Error list appears in warehouse logs The following error list appears in the warehouse logs: == 25 t=Thread-1 com.ibm.db2.jcc.c.DisconnectException: A communication error has been detected. Communication protocol being used: T4Agent.sendRequest(). Communication API being used: OutputStream.flush(). Location where the error was detected: There is no process to read data written to a pipe.
Page 214: When Configuring The Monitoring Agent For Sybase And The Warehouse Proxy Agent, Receive Message To Use Candlemanage
Check the managed system status in the Tivoli Enterprise Portal. v Ensure that the agent process started. v Check the Tivoli Enterprise Monitoring Server kfwras1.log for errors. v Check the Tivoli Enterprise Monitoring Server kfwras1.log. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 215: Ctira_Hostname Has No Effect On Log File Names
DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null The solution is to increate the DB2 logging for the warehouse database. See the IBM Tivoli Monitoring for Databases: DB2 Agent User's Guide for more information. Receive a message saying that the statement parameter can only be a...
Page 216: Unresolved Variables In Custom Queries
Following are some of the commonly referenced symbols and example values: KFW_USER: Name of the summarized database schema owner. Default is ITMUSER but it can be any value assigned by the customer during installation. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 217: A Message Appears After Accepting The License
This message is harmless and is associated with verifying the versions of the gskit component installed by IBM Tivoli Monitoring. The message is displayed at a point where the UNIX installation normally pauses for a number of seconds, causing a tendency to think the installation has failed, although this is not the case.
Page 218: Adding Agent Help Files Requires A Restart Of The Eclipse Help Server And The Tivoli Enterprise Portal Server
This also requires a restart of the Tivoli Enterprise Portal Server. Unable to create historical collection directory for ud:db2inst1 If you receive the following message, check if the IBM Tivoli Monitoring environment is in SecureMode. db2inst1@amsnt148d:/opt/IBM/ITM/bin> ./itmcmd agent -o db2inst1 start ud Sourcing db2profile for user db2inst1 Starting Monitoring Agent for DB2 ...
Page 219: Chapter 11. Command Troubleshooting
-o EXECPREREQCHECK=Y command-line option, certain processes might not complete. If you supply a Windows-syntax installation directory (for example, C:\IBM\ITM) with either the -d | --directory flag or the group deployment property (KDY.INSTALLDIR=C:\IBM\ITM), the execution of the prerequisite check on the endpoint might hang some processes on UNIX or Linux operating systems.
Page 220: Tacmd Executecommand Command Run Against Subnode Fails
Server or in the directory where the monitoring agent is running, from the directory where the short-term history files are stored. For more information about the krarloff command, see the topic on converting files using the krarloff program in the IBM Tivoli Monitoring Administrator's Guide (http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/ com.ibm.itm.doc_6.2.3fp1/adminuse/itm_admin.htm).
Page 221: Missing Options For Login -Stdin Results In Unexpected Behavior
To solve this problem, convert your system to the equivalent Language_Locale convention. In the example above, use the tr_TR locale. Missing options for login -stdin results in unexpected behavior For both the tacmd login and the tacmd tepslogin commands, if the -stdin option is used, and an echo is used to pass the options, then all the mandatory options need to be passed in the echo.
Page 222: Commands With Embedded Single Quotation Marks Fail
-m UX Managed System gives no result The tacmd listsit command on AIX systems gives no results as shown below: ------------------------------------------------------- tacmd listsit -m UX Managed System gives no result. Return code = 255. ------------------------------------------------------- IBM Tivoli Monitoring: Troubleshooting Guide...
Page 223: Receive A Busy Monitoring Server Message When Using The Getfile, Putfile, Or Executecommand Commands
This behavior might be caused by an OUT OF MEMORY condition on the AIX system where the command is issued due to specific AIX memory management. This problem can be solved by setting the environment variable, LDR_CNTRL=MAXDATA=0x80000000, to be exported in the shell from which the tacmd command is issued: export LDR_CNTRL=MAXDATA=0x80000000 Receive a busy monitoring server message when using the getfile,...
Page 224: Receive An Outofmemory Exception When Using The Import Or Export Commands
KUIC02001E message on Japanese Systems Edit the kuilistsitVld.xml file to replace the following text: <Type arg1="-t" arg2="--type" Type ="String" ValidationRegExp="[-A-Za-z0-9 _/()\&%.]" Required="Y"/> with the following text: IBM Tivoli Monitoring: Troubleshooting Guide...
Page 225: Non-English Characters
The default timeout is 600 seconds (10 minutes). The following message is returned after successful execution: KUICAB022I: The following bundles were successfully added to the C:\IBM\ITM\CMS\depot\depot If the addBundlescommand times out, this message is not returned. Set the TIMEOUT environment variable to more than 600 before running the addBundles command.
Page 226: Tacmd Suggestbaseline Command Receives An Error
If the error information returned from the server is not sufficient to help you resolve the error, contact IBM Software Support. The command /opt/IBM/ITM/bin/CandleAgent -h /opt/IBM/ITM -c stop ul did not start or stop agent. The command returned a return code.
Page 227: Starting, Stopping Or Recycling Agents Fails On Windows 2000 Systems
You receive a message when trying to use the tacmd maintagent command The tacmd maintAgent command is disabled for the IBM Tivoli Monitoring v6.2.2 release. The command stops and starts situations on individual agents without notifying the Tivoli Enterprise Portal Server or Tivoli Enterprise Monitoring Server, therefore the Tivoli Enterprise Portal Server or the Tivoli Enterprise Monitoring Server can potentially lose track of the state of the situation on the agent.
Page 228: Take Action Commands Do Not Work If Unrequired Values Are Left Blank
Either update the systems host tables and correctly setup the DNS domain search so that the link between itmserver and itmserver.raleigh.ibm.com can be made, or supply the monitoring server fully-qualified host name during the createnode deployment using the SERVER=itmserver.raleigh.ibm.com property.
Page 229: The Listsystems Command Consumes High Cpu In Enterprise Environments
Procedure This problem has to do with your locale and system configuration, and can be fixed by performing the following procedure: 1. Open the command prompt. 2. Change the command prompt locale according to the following table: Country Code Page Default Setting New Code Page Value Latin 1 - Brazilian Portuguese, 1252...
Page 230: The Addsystem Command Fails With Error Message Kuiccr099E
This parameter is described in the “Timekeeping in VMWare Virtual Machines” paper on the VMWare website: IBM Service Management Connect (http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf). Measurement experience has shown that this setting can significantly improve the tacmd command response time on VMWare ESX systems.
Page 231: Tacmd Createsit Does Not Send Errors If You Mistype The Name Of An Attribute
When the wsadmin commands are run, the output indicates to restart server1, which is the default name for WAS server. However, the eWAS server for IBM Tivoli Monitoring is called ITMServer. C:\ibm\ITM\CNPSJ\profiles\ITMProfile\bin>wsadmin -connType NONE WASX7357I: By request, this scripting client is not connected to any server process.
Page 232: Installing An Exported Agent Bundle Using Install.sh Causes An Error
-o LOCAL command results in the following error message: [root@sdogoff ud_062000000_li6263]# ./install.sh INSTALL Enter the name of the IBM Tivoli Monitoring directory [ default = /opt/IBM/ITM ]: ITM home directory "/opt/IBM/ITM" already exists. OK to use it [ 1-yes, 2-no; "1" is default ]? Select one of the following: 1) Install products to the local host.
Page 233: Chapter 12. Performance Analyzer Troubleshooting
Linux or UNIX install_dir/logs directory. Procedure 1. Stop the Performance Analyzer agent. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services, then right-click on Performance Analyzer and select Stop. Enter the itmcmd agent stop pa command.
Page 234: Enabling Logging For The Monitoring Portal
Detailed logging has been enabled. What to do next If you want to send the log files to IBM Software Support, start the TEP desktop client and perform steps to reproduce the error, and then go to the user home directory, where java*.log.* files are created.
Page 235: Problems After Upgrading
100 MB of free space to store temporary files. See “Software and memory requirements for non-linear trending in Tivoli Performance Analyzer” in the IBM Tivoli Monitoring Installation and Setup Guide. “Enable SPSS Configuration” prompt while configuring from the command line During configuration of the Tivoli Performance Analyzer from the command line, you get a prompt for “Enable SPSS Configuration”.
Page 236: Interface For Tivoli Enterprise Portal Fails When Downloading Tasks List
SQL1224N: [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032b This message indicates that DB2 has exhausted all available shared memory segments.
Page 237: No Data Is Displayed In The Workspaces
After installing Tivoli Performance Analyzer, did you configure historical data collection? For more information, see the "Configuring historical data collection for the Performance Analyzer warehouse agent" section in the IBM Tivoli Monitoring: Installation and Setup Guide. If the agent is active and historical data collection is configured, your configuration may be wrong.
Page 238: Nonlinear Tasks Take Too Long To Complete
Net_Traffic_Out_NLT_Fcast_PA v CPU_Utilization_NLT_Status_PA v Mem_Utilization_NLT_Status_PA v Disk_Utilization_NLT_Status_PA v Net_Traffic_In_NLT_Status_PA v Net_Traffic_Out_NLT_Status_PA For example, for the KPA_GENERIC_D32_NLT_FCAST attribute group in DB2, use the following command: CREATE INDEX DB2INST1.ITMIXFCMEM ON DB2INST1.KPA_GENERIC_D32_NLT_FCAST_PA ("System_Name" ASC) ALLOW REVERSE SCANS IBM Tivoli Monitoring: Troubleshooting Guide...
Page 239: Agent Never Connects To The Monitoring Server
Agent never connects to the monitoring server In IBM Tivoli Monitoring V6.2.3.x, on 32- and 64-bit Red Hat Linux V5.x systems, the agent never connects to the Tivoli Enterprise Monitoring Server. The agent does not appear to attempt to connect, and there is no message in the error log.
Page 240 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 241: Utilities For Backing Up The Database
This ID is added when you install the database and is required by the product installer when you configure the Tivoli Enterprise Portal Server data source. TEPS This ID is added during installation for creating the portal server data source. © Copyright IBM Corp. 2005, 2012...
Page 242: Db2 Purescale Environment
1. On the computer where the portal server is installed, be sure you are logged on to Windows with an ID having administrator authority. 2. From your Windows desktop, select Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services.
Page 243: Installation
Administrative tools and double-click the Data Sources (ODBC) . 2. Verify that the IBM DB2 ODBC DRIVER datasource is defined. 3. If the IBM DB2 ODBC DRIVER data source is not present, run the install_dir\installITM\DB2DataSource.exe file. 4. Read the error messages after running the program.
Page 244: Oracle Problem With Jdbc Drivers Prior To 11.1.0.7
Universal Database installation. Use this utility only after migration problems and before customizing the monitoring server. The movefrom-m2i.bat is only used to migrate the contents of Microsoft SQL Server to Universal Database. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 245: After Upgrading To Db2 Udb Version 8.1 Fix Pack 10
An error occurs with the SQLTables if the database was created before applying IBM DB2 V8.1 Fix Pack 10 (also known as Version 8.2 Fix Pack 3), you encounter an SQL0443N error if you run a DB2 Call Level Interface (CLI) catalog function (such as SQLTables(), SQLColumns(), or SQLStatistics()).
Page 246: Historical Data Is Not Warehoused
Warehouse Proxy Agent log file (hostname_hd_java_nnnnnnnnnn.log) or the Summarization and Pruning Agent log file (hostname_sy_java_nnnnnnnnnn.log): com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null Increase the DB2 transaction log size. See the DB2 manuals for altering the LOGFILSIZ, LOGPRIMARY, and LOGSECOND parameters within DB2.
Page 247: Too Much Historical Data Is Collected
Tivoli Enterprise Portal" in the IBM Tivoli Monitoring Administrator's Guide for instructions. If you need to install the Summarization and Pruning agent, see the IBM Tivoli Monitoring Installation and Setup Guide. There you can find information for environment-wide capacity planning.
Page 248: To Perform Operation "Create Bufferpool Sqlstate=42502
(42ED71FA.0000-E4C:khdxbase.cpp,250,"setError") Error 20/3/-552(FFFFFDD8)/0 executing SQLExecute (42ED71FA.0001-E4C:khdxbase.cpp,266,"setError") Error "[IBM][CLI Driver][DB2/NT] SQL0552N "ITMUSER" does not have the privilege to perform operation "CREATE BUFFERPOOL" SQLSTATE=42502 When you configure a DB2 Warehouse Proxy connection from the Manage Tivoli Enterprise Monitoring Services utility using the Configure DB2 Datasource for Warehouse window, the user ID the Warehouse Proxy uses to connect to the warehouse database must have SYSADM permission.
Page 249: Chapter 14. Event Synchronization Troubleshooting
Errors occur during installation of IBM Tivoli Monitoring event synchronization When installation of the IBM Tivoli Monitoring Event Synchronization component is complete, the results are written to the itm_tec_event_sync_install.log file located in the following directories: v Windows: The itm_tec_event_sync_install.log file is created in the directory defined by...
Page 250: Netcool/Omnibus Integration Troubleshooting
BSM_Identity attribute. If you are not integrating IBM Tivoli Monitoring, Netcool/OMNIbus, and Tivoli Business Service Manager, comment out any rules files (like tbsm_eif_event.rules) that are intended for Tivoli Business...
Page 251: Resolving Problems Sending Events To
Default location: $OMNIHOME/log/NCO_PA.log where $OMNIHOME is the directory where Netcool/OMNIbus is installed. The Process Agent is used to run the IBM Tivoli Monitoring Situation Update Forwarder. To enable Process Agent tracing, run the Process Agent with the debug configuration parameter (for example, nco_pad –debug 1).
Page 252 Review the configuration of the OMNIbus EIF destination on destination is incorrect. the IBM Tivoli Monitoring side. Verify that the server and port information are correct. You can use the IBM Tivoli Monitoring CLI command listeventdest to list all the event destinations and use IBM Tivoli Monitoring CLI command vieweventdest to see detail of the event destination.
Page 253 If the process is not running, start the process using $OMNIHOME/probes/nco_p_tivoli_eif command. Check to see if the port number used to send events from the IBM Tivoli Monitoring side matches the port number used by the EIF Probe. To check the port number information on the IBM Tivoli...
Page 254: Event Status Updates In Netcool/Omnibus Are Not Forwarded To Tivoli Monitoring
If the triggers from itm_sync.sql are not defined in the ObjectServer, see the topic “Updating the OMNIbus database schema” in the IBM Tivoli Monitoring Installation and Setup Guide for the procedure to follow to add the triggers to the Object Server.
Page 255 If the monitoring server user name or password have changed recently, use the sitconfuser command to update the monitoring server’s information. See the IBM Tivoli Monitoring Command Reference for details on the syntax of the sitconfuser command. Chapter 14. Event synchronization troubleshooting...
Page 256 For more information on Agent log file for what user to specify, see the topic error messages. “Configuring the OMNIbus server for program execution from scripts” in the IBM See “Log files for Tivoli Monitoring Installation and Setup Netcool/OMNIbus Guide.
Page 257: Or Other Attributes Set By The Ibm Tivoli Monitoring Probe Rules
Summary attribute or other attributes set by the IBM Tivoli Monitoring probe rules “Default mapping of situation events to OMNIbus events” in the IBM Tivoli Monitoring Installation and Setup Guide describes how OMNIbus attributes should be set for monitoring events. If your events do not have the expected values described in that topic, consider the following possible causes and resolutions.
Page 258: Monitoring Events In Netcool/Omnibus Do Not Have Expected Values
For information on which EIF slots should not be customized, see the topic "Default mapping of situation events to OMNIbus events" in the IBM Tivoli Monitoring Installation and Setup Guide. The Netcool/OMNIbus Verify that the default duplication trigger has been...
Page 259: The Event's Severity Is Changed Back To Its Original Severity
IBM Tivoli Monitoring EIF slots and not any of the agent-specific data. In addition, the OMNIbus Summary attribute is set to the situation...
Page 260: Tivoli Enterprise Console Integration Troubleshooting
Windows and import event forwarding functionality into an existing rule base with an absolute path, you must copy setupwin32.exe to the local drive on which the rule base resides to import the IBM Tivoli Enterprise Console event synchronization functionality into that rule base. Launch the copied setupwin32.exe to start IBM Tivoli Enterprise Console event synchronization...
Page 261: Tacmd Refreshtecinfo -T All Shows No Results On Console
tacmd refreshTECinfo -t all shows no results on console The Tivoli Enterprise Monitoring Server facility used (DS START command) to trigger the refresh of the EIF info does not give a return code. So, it is not possible to give feedback as to the success or failure of the operation back to the command line interface.
Page 262 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 263: Chapter 15. Tivoli Common Reporting Troubleshooting
\profiles\TIPProfile\logs\serverName subdirectory of the Tivoli Common Reporting installation directory. Standard informational log messages are written to the SystemOut.log file; detailed trace messages are written to the trace.log file. See “Troubleshooting and support” (http://publib.boulder.ibm.com/ infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ ctcr_troubleshooting.dita.html) v If the connection to Tivoli Data Warehouse cannot be established, look in the WebSphere Application Server SystemOut.log file or SystemErr.log file for more...
Page 264: Reporting 2.1.1 On 64-Bit Aix 6.1 Results In Error Dpr-Err-2056
DPR-ERR-2056, as depicted in the following example: The Report Server is not responding. Handler trace back: [the_dispatcher] com.cognos.pogo.handlers. performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [reportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [ifElseBirthandler] com.ibm.cognos.birtservice.logic.IfElseBirtHandler IBM Tivoli Monitoring: Troubleshooting Guide...
Page 265: Displaying Data For Situations History Report Results In Error
MMM dd, yyyy and hh:mm 12h format, instead. Prompted to select report type when installing reports with CLI When you install IBM Tivoli Monitoring OS Agents reports within the CLI, you might be prompted to "Choose the report type" after you have already specified the reports you want to install.
Page 266: The Generated Report Does Not Display Report Legend
This problem is occurring because you are missing drivers required by Tivoli Common Reporting. You did not copy the required driver files or copied incorrect driver files. Refer to the “Configuring a JDBC data source” topic in the IBM Tivoli Common Reporting: User's Guide for additional information about this requirement.
Page 267: Documentation For The Base Agents
– HMC Base Agent User's Guide, SA23-2239 – VIOS Premium Agent User's Guide, SA23-2238 v Other base agents: – Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490 The report fails to generate because the SQL query was not valid If you have made changes to the reports or to the workspace against which the query is being run, you could see SQL query errors.
Page 268: Message "Sql Statement Does Not Return A Resultset Object" Displayed
1. Open the SystemOut.log file, found in this location: On Windows Systems: <tcr_install_dir>/tcr/eWas61/profiles/tcrProfile/logs/tcrServer/ 2. Confirm that this line can be found: An OutOfMemory error happened while running the report. If you find this line, do the following to correct this problem: 3. Stop Tivoli Common Reporting. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 269: The Generated Report Displays The Message "Sql Error
5. Locate this instruction about half way through the bat file: "%JAVA_HOME%\bin\java" -Xms128m -Xmx512m -Dcmd.properties .file=%TMPJAVAPROPFILE% %WAS_TRACE% %WAS_DEBUG% %CONSOLE_ENCODING% "%CLIENTSAS%" "%CLIENTSSL%" %USER_INSTALL_PROP% "-Dwas.install.root=%WAS_HOME%" com.ibm.ws .bootstrap.WSLauncher com.ibm.ws.management.tools.WsServerLauncher "%CONFIG_ROOT%" "%WAS_CELL%" "%WAS_NODE%" %* %WORKSPACE_ROOT_PROP% 6. Increase the JVM heap size by adding the -xms and -xmx options, as in the example shown below: "%JAVA_HOME%\bin\java"...
Page 270: No Data Is Plotted In Graph, Or Some Columns In The Table Are Blank
This change causes the calculations being performed for the report to process less data, reducing the chance of overflow. Note: All occurrences of this failure in the IBM-provided reports were eliminated by casting DB2 Integer values to DECIMAL(column_name 31,0). This problem should not occur with IBM-provided reports, but could be an issue in customer-generated reports.
Page 271: The Generated Report Displays The Message "The Requested Data Is Not Available
attribute that is not being displayed. Go to the Tivoli Enterprise Portal console and validate that this column contains data and, if the issue is with summarized data, that summarization is enabled for this attribute. Another reason might be that you have not configured historical collection when you installed and configured the monitoring agent or that not enough time has passed for Tivoli Data Warehouse to collect the data for your requested report time period before you tried to generate an historical report with Tivoli Common...
Page 272: You Receive The Message "Empty Data Set
The report parameters have excluded all the data. v You recently started using IBM Tivoli Monitoring for Energy Management and have not put data into the Tivoli Data Warehouse. v The computers you are monitoring do not have the correct level of firmware.
Page 273: Chapter 16. Tivoli Audit Facility Troubleshooting
These logs are located on the component in the <install_dir>/auditlogs directory. Refer to Appendix F. ITM Audit log in the IBM Tivoli Monitoring Version 6.2.3 Administrator's Guide.
Page 274 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 275: Ibm Tivoli Monitoring Processes By Operating System
Appendix. IBM Tivoli Monitoring processes Look up the IBM Tivoli Monitoring process names when you want to confirm that a process is indeed running and review the resources used. Table 22. IBM Tivoli Monitoring processes by operating system Component Windows...
Page 276 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 277: Documentation Library
Related publications See the IBM Tivoli Monitoring Documentation Guide for information about accessing and using the publications. You can find the Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON XE Information Center at http:// publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp. To open the Documentation Guide in the information center, select Using the publication in the Contents pane.
Page 278: Documentation For The Base Agents
Installation and Configuration Guide. Documentation for the base agents If you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents as part of the product. If you purchased a monitoring agent IBM Tivoli Monitoring: Troubleshooting Guide...
Page 279: Related Publications
– Systems Director base Agent User’s Guide, SC27-2872 – Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490 Related publications You can find useful information about related products in the IBM Tivoli Monitoring and OMEGAMON XE Information Center at http:// publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp. Other sources of documentation...
Page 280 Tivoli products. The wikis contain white papers contributed by IBM employees, and content created by customers and business partners. Two of these wikis are of particular relevance to IBM Tivoli Monitoring: – Tivoli Distributed Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/...
Page 281: Support Information
Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides ways for you to obtain the support you need. Online The following sites contain troubleshooting information: v Go to the IBM Software Support site at http://www.ibm.com/software/ support/probsub.html and follow the instructions.
Page 282 If there is no Download heading for your product, supply a search term, error code, or APAR number in the field provided under Search Support (this product), and click Search. For more information about the types of fixes that are available, see the IBM Software Support Handbook at http://www14.software.ibm.com/webapp/set2/sas/ f/handbook/home.html.
Page 283 Contacting IBM Software Support IBM Software Support provides assistance with product defects. The easiest way to obtain that assistance is to open a PMR or ETR directly from the IBM Support Assistant. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM.
Page 284 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 285: Notices
Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead.
Page 286 IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created...
Page 287 Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: © IBM 2012. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. previous releases to 2012.
Page 288 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 289: Glossary
An agentless monitor uses a standard API associate (such as SNMP or CIM) to identify and The process of linking a situation with a notify you of common problems with the Navigator item that enables a light to go © Copyright IBM Corp. 2005, 2012...
Page 290 A set of related attributes that can be processing. In IBM Tivoli Monitoring the combined in a data view or a situation. Tivoli Enterprise Portal is the client to the When you open the view or start the Tivoli Enterprise Portal Server.
Page 291 The name that is stored in the database Prior to IBM Tivoli Monitoring v6.2.3, the server and that enables you to retrieve Tivoli Enterprise Portal Server is a information from the database through CORBA implementation.
Page 292 A database used by the Tivoli Enterprise Standard Generalized Markup Language Monitoring Server that serves as a (SGML). A tool for encoding messages so repository of shared objects for all they describe their own fields, XML IBM Tivoli Monitoring: Troubleshooting Guide...
Page 293 (the krarloff A proprietary web server developed for utility on UNIX or Windows; jobname IBM Tivoli Monitoring that is installed KPDXTRA for the z/OS Persistent and configured automatically with the Datastore), and then delete entries in the Tivoli Enterprise Portal Server.
Page 294 JMX provides a Java-based alternative to the Simple Network If a managed system list is updated Management Protocol. (usually when a constituent managed system is added or deleted), then all the JDBC See Java Database Connectivity. IBM Tivoli Monitoring: Troubleshooting Guide...
Page 295 CORBA defines an object as a build a transactional unit of work. IBM's combination of state and a set of methods CICS and WebSphere MQ are examples of characterized by the behavior of relevant middleware.
Page 296 OMEGAMON Persistent Datastore A set of z/OS data sets where IBM Tivoli OMEGAMON Monitoring Agent Monitoring running on z/OS systems The software process that probes a stores historical monitoring data.
Page 297 TCP/IP environment. The collected data to the hub Tivoli Enterprise SNMP software protocol facilitates Monitoring Server to be made available to communications between different types one or more Tivoli Enterprise Portal of networks. IBM Tivoli Monitoring uses Glossary...
Page 298 SNMP messaging to discover the devices Enterprise Monitoring Server running on your network and their availability. under IBM Tivoli Monitoring version 6.1 and subsequent releases. Your site must Simple Object Access Protocol install this component on the Tivoli The Simple Object Access Protocol is an Enterprise Console server;...
Page 299 A MTTRAPD receiver. valid user ID and password for that remote system are required. No other IBM Tivoli Monitoring agents or other components should be installed on threshold the same node as a System Monitor A level set in the system at which a Agent.
Page 300 An * (asterisk) used to represent any external applications not a part of IBM characters that may follow or precede Tivoli Monitoring. those entered, such as Sys* to find System Tivoli Management Services and SysTray.
Page 301 Tivoli Enterprise Portal Server. See Extensible Markup Language. z/OS IBM's operating system for its line of mainframe, zSeries computers that can manage large amounts of memory, direct-access storage, and data. Glossary...
Page 302 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 303: Index
LONG value only for database 223 diagnostics 31 insert 197 backing up the 223 fixes, obtaining 264 Candle Management Workstation 272 recovering the 223 CandleManage 196, 206 restoring the 223 © Copyright IBM Corp. 2005, 2012...
Page 304 245 JDBC 248, 276 incorrect 228 dynamically modifying 53 JMX 276 krarloff 202 IBM Tivoli Enterprise Console 38 jobname KPDXTRAs 275 migration tools 175 IBM Tivoli Enterprise Console JRE 95, 137 missing or incorrect 20 Situation Update Forwarder 52...
Page 305 My support notifications 2 VMWare 139 missing managed system group 83 workspaces 174 service console 56 portal server See also IBM Tivoli Monitoring connectivity with hub 121 Technology Service Console NAT 277 database connection 225 See also Tivoli Monitoring Service...
Page 306 Unexpected Signal: 4 occurred at Backspace Check utility 60 PC=0xFEC3FDE4 95 Build TEPS Database 61 Unhandled Exception 87 BuildPresentation.bat 61 uninstallation IBM Tivoli Monitoring Operations Add and Remove Programs XML 283 Logging 61 utility 112 ITMSuper 63 problems 108 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 307 z/OS backing up ICAT and CSI environment 107 monitoring server 166 monitoring server support 84 runtime members job 105 z/OS agents reflex automation 173 Tivoli Enterprise Monitoring Server 168 Index...
Page 308 IBM Tivoli Monitoring: Troubleshooting Guide...
Page 310 Printed in USA GC32-9458-05...

This manual is also suitable for:

Tivoli monitoring 6.2.3 fp1

IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Tables

About this Information

Chapter 1. Introduction to Troubleshooting

Chapter 2. Logs and Data Collection for Troubleshooting

Chapter 3. Common Problem Solving

Chapter 4. Tools

Chapter 5. Installation and Configuration Troubleshooting

Chapter 6. Connectivity Troubleshooting

Chapter 7. Portal Client Troubleshooting

Chapter 8. Portal Server Troubleshooting

Chapter 9. Monitoring Server Troubleshooting

Quick Links

Troubleshooting Guide

Troubleshooting

Related Manuals for IBM E027SLL-H - Tivoli Monitoring - PC

Summary of Contents for IBM E027SLL-H - Tivoli Monitoring - PC