Deployment problems

A list of deployment problem descriptions and solutions.

Problem	Solution
The deployer window does not automatically become the focus window after launching from it from the Topology Editor.	Cause: In some cases (for example, when you export the display on a VNC session on Linux systems), the deployer window does not get the focus. User action: Click on the deployer window or move other windows to make the deployer window the focus window.
When the user tries to launch the Firefox browser an error is displayed regarding the Cairo 1.4.10 package. In the Topology Editor, the minimize and maximize buttons are red in color. Note: This is an in-built feature in Eclipse 4.2.2. See, http://stackoverflow.com/questions/12245102/eclipse-juno-red-minimize-and-maximize-buttons-on-linux	Cause: Cairo 1.4.10 may not support the requested image format. User action: Start VNC server using the following command: /usr/bin/X11/vncserver -depth 24 -geometry 1280x1024
In a fresh installation, the database installation step fails.	Cause: You did not perform the necessary preparatory steps. User action: This step verifies that the Oracle Listener is working properly before actually creating the Tivoli® Netcool® Performance Manager database. If the step fails: 1. Complete the necessary manual steps (see Configure the Oracle listener). 2. Change the status of the step to Ready. 3. Resume the installation. The step should complete successfully.
An installation step hangs.	Cause: There are many possible causes. User action: Make sure the installation step is really in a hung state. For example, the Tivoli Netcool Performance Manager database-related steps might take more than an hour to complete; other steps complete in far less time. Determine which child process is causing the hang. First, find the installer process by entering the following command: `ps -ef` The installer process has an entry similar to this one: `root 12899 7290 10 13:43:31 pts/7 0:10 /tmp/install.dir.12899/Solaris/resource/ jre/jre/bin/java -Djava.compiler=NONE -` Find the process that has that process number (for example, 12899) as its father. Continue until you find the last process. Kill the last process using the following command: `kill -9` At this point, the status of the hung step will change to Error. If you can determine the cause of the hang, fix the problem and resume the installation. Otherwise, collect the log files and contact IBM for support.
The deployer hangs when displaying the Preview page. (This step normally takes only a few seconds).	Cause: The NFS file system is not working properly. User action: Run the `df` `-k` command and make sure that all NFS mounted file systems are working properly. When the problem has been corrected, restart the deployer.
There is a problem with remote command execution.	Cause: The deployer uses either RSH or OpenSSH to perform remote command execution. You must configure OpenSSH to make this connection possible. User action: After configuring OpenSSH, run the test program provided in deployer_root`/proviso/data/Utils/testremote.sh` to test your configuration, where deployer_root is the root directory for the deployer. For example: `/export/home/pvuser/443/SOLARIS/Install/ SOL9/deployer`
Installation messages report success, but might include messages similar to the following: `Fatal Error]:4:1: An invalid XML character (Unicode: 0x1b) was found in the element content of the document.`	This is screen noise and can safely be ignored.
When you click the Done button to complete a fresh installation, the deployer displays database access error messages.	Cause: You stopped a fresh installation before the installing and configuring the Tivoli Netcool Performance Manager database. User action: If the Tivoli Netcool Performance Manager database has not been installed, complete the installation using the `-Daction=resume` option (see Resuming a partially successful first-time installation). If the database has been installed, there is another problem. Contact IBM Software Support.
Data does not appear in real-time reports, and right-clicking on a real-time report does not display the option menu. This problem can occur with a silent installation on a Solaris system.	Cause: When it starts, the channel manager (CMGR) places information in the database that is needed for real-time reports to start correctly. During installation, a `cron` job is created that starts CMGR. A silent installation might run fast enough that the `cron` job does not run before DataView is started. In this case, CMGR does not add the required information to the database, and real-time reports do not start up correctly. User action: Make sure that the CMGR process is running (see Management programs and watchdog scripts and Starting the DataChannel management programs). Restart DataView.