IBM E027SLL-H Troubleshooting Guide - Page 37

2. If you have selected a workspace that is retrieving large amounts of data, wait for the data to be returned. If the workspace returns empty, see "Workspaces are missing or views are empty" on page 10. 3. On Windows, check theWindows Task Manager and in the %CANDLE_HOME\InstallITM directory, run the following kincinfo.exe commands: v kincinfo.exe -r to show running processes. v kincinfo.exe -i to show what is installed. 4. On Linux or UNIX, in the $CANDLEHOME/bin directory, run the following cinfo commands: v ./cinfo -r to show running processes. v ./cinfo -i to show what is installed. 5. If your portal client stops responding while in an Oracle Agent workspace, see "High CPU usage on a distributed system" on page 29. Your problem might be related to a high CPU usage problem. Similar problems might exist for other monitoring agents. 6. Running the following ITMSUPER tools might also provide more information: v Stressed Resources tool v Connectivity tool v Topology tool What to do next For more information on actions that relate to these diagnostics, see the problem resolution tasks. Resolving storage or memory problems Storage or memory problems are caused by a problem that leads to a lack of storage or memory. To resolve storage or memory problems, you perform diagnostic and corrective actions. These actions include reconfiguring the JavaControl Panel. Procedure Reconfigure the Java Control Panel. See "Tivoli Enterprise Portal has high memory usage" on page 138. Resolving client configuration problems To resolve Tivoli Enterprise Portal configuration problems, disable the DirectDraw to reduce high 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 19