Troubleshooting installation problems

This information covers common problems that occur with installing or uninstalling IBM® Tivoli Application Dependency Discovery Manager (TADDM).

TADDM simple installation fails because the database cannot be created

Problem: The installation of the TADDM server with the local DB2® database fails, because the database cannot be created.

Solution: Starting with DB2 version 10, there is a limitation regarding the passwords of the DB2 users. The installer cannot connect to the newly created database if password of any of the users includes the exclamation point (!).
Ensure that none of the passwords for the DB2, which were provided during the installation, contain the exclamation point (!).

In a test environment, you can use the TADDM installer to create a remote TADDM DB2 database using DB2 client

Problem

If you do not have the DB2 client installed on the TADDM server when creating a remote TADDM DB2 database, you receive an error message that states that the db2cmd.exe file is not found.

You receive the following error message after the DB2 installation panel:

"db2cmd.exe" was not found.

Solution

In a production environment, do not install the TADDM server and the DB2 database on the same system. Install TADDM and the DB2 database on separate systems. On the system used for the DB2 database, manually run the scripts to create the database.

In a test environment, if you use the DB2 client to create the remote TADDM DB2 database, complete the following steps:

Install the DB2 client. See the DB2 documentation for instructions.
Install the appropriate DB2 fix pack. See the DB2 documentation for instructions.
Catalog the database node. See the DB2 documentation for instructions.
Create the local DB2 instance ID. The user ID must be the same as the user ID on the DB2 server. See the DB2 documentation for instructions.
Create the archuser user ID. The user ID must be the same as the user ID on the DB2 server. See the DB2 documentation for instructions.

Alternately, in test and production environments, you can create a remote TADDM DB2 database by using a script, make_db2_db, provided with the TADDM installation program. It is not required that you use the script that is provided with the TADDM installation program. This script is an example of a script that can be used. If used, the script creates a properly configured database for TADDM. You can use a different script that conforms to standards for your environment.

If you use the make_db2_db script, the existing database or users in your DB2 database are deleted when the make_db2_db script runs.

From the product DVD, copy the following file to the system where the DB2 database is installed:
- For Linux®, AIX®, and Linux on System z® operating systems, support/bin/make_db2_db.sh
- For Windows operating systems, support\bin\make_db2_db.bat2
Use one of the following procedures to run the make_db2_db script on the system where the DB2 database is installed:
- For Linux, AIX, and Linux on System z operating systems, complete these steps:
  1. Log in as the DB2 instance owner. For example, you can use the db2inst1 ID.
  2. Run the following command: make_db2_db.sh cmdb
- For Windows operating systems, complete these steps:
  1. Open the DB2CMD command prompt.
  2. Run the following command: make_db2_db.bat cmdb

The DB2 client is used only for database creation during installation. After installation, the TADDM server does not use the DB2 client.

SUSE Linux for System z operating system has memory problem

Problem

When uninstalling TADDM on a computer with SUSE Linux for the IBM System z operating system, SUSE Linux runs out of memory.

The computer where TADDM is installed with SUSE Linux for the System z operating system must have 4 - 8 GB of memory. This problem occurs if the computer has less than 4 GB of memory.

Solution

Before you uninstall the TADDM server, stop the server. If you do not stop the server, the system might run out of memory during the uninstall process, which means the uninstall process never completes in an orderly way. In this case, complete the following steps:

Stop the uninstall process.
Run the following command to stop all Java™ processes:
```
ps -ef | grep java
```
Run the following command, where pid is the process ID that is displayed as a result of running the preceding command:
```
kill pid
```
Uninstall the TADDM server.

TADDM installed on system with an Internet connection that is incorrectly configured

Problem: The TADDM installation process was successful, but the installation process was performed on a system where the Internet connection is incorrectly configured. The discovery process does not find any configuration items.
The Internet connection is fixed and a new IP address is assigned. During this process, all users of the system must redefine their user ID and password. TADDM fails with a DBInit Fails error.
Solution: The password for both database users (the primary and archive users) must be reset and manually tested before TADDM restarts successfully.

TADDM installation fails on a computer that is using a remote mounted CD/DVD on System z operating system

Problem

When you attempt to install TADDM on a computer that is using a remote mounted CD/DVD on System z operating system, the installer GUI does not appear and the installation does not start.

Solution

Copy the entire TADDM install image contents of the installer DVD on System z to the local drive of the computer on which you are trying to install TADDM.
From the local directory where you copied the files, run the following script:setupZLinux.bin

Password verification fails on the Windows system even when the user ID and password are correct

Problem

When you attempt to install TADDM on the Windows system, the installer is unable to successfully verify your password on the Runtime User Information page of the installation wizard, even if the user ID and password are correct.

Solution

This problem can occur on the Windows system if the name of the %temp% directory includes non-ASCII characters. Because the default %temp% directory is based on the user that is currently logged on, this can happen if your user ID includes non-ASCII characters (for example, Russian characters).

To avoid the problem, use either of the following workarounds:

Reset the temp environment variable so that it refers to a directory whose name includes only ASCII characters. For example, use this command to use the c:\temp directory:
```
set TEMP=c:\temp
```
Note: Make sure that the directory you specify exists.
Set the FORCE_OEM_CHARSET environment variable to specify the active code page. For example, if the active code page is 852, run the following command:
```
set FORCE_OEM_CHARSET=852
```
You can determine the active code page by running the chcp command.

After using either of these workarounds, run the TADDM installation wizard (setupWin.bat) from the same command-line session.

Restriction: When you run the TADDM installation wizard setupWin.bat on Windows operating systems, select the Run as administrator option. Otherwise, the installation will fail.

TADDM installation fails on the Windows system because of missing files

Problem: When you attempt to install TADDM on the Windows system, the installation fails, and error messages in the logs indicate that required installation files could not be found (for example, install.vbs).
Solution: This problem can occur on the Windows system if the name of the %temp% directory includes non-ASCII characters. For more information, see Password verification fails on the Windows system even when the user ID and password are correct.

You cannot see part of the installation wizard window

Problem

If you are using a low screen resolution such as 640x480 pixels, you might not see part of the installation wizard window, including some of the control buttons.

Solution

If possible, change the screen resolution to a minimum of 1024x768, and then run the installation wizard again.

If you cannot change the screen resolution, run the TADDM installation in console mode by using the -i console option. For more information, see Installing the TADDM server at a console.

The Tivoli Netcool Performance Flow Analyzer installer fails to start

Problem

If you run the wrong Tivoli® Netcool® Performance Flow Analyzer installer binary file for your operating system, you might see a misleading message that indicates success even though the installer does not start. For example, if you try to run the AIX binary file on a Linux system, the following message is displayed:

Launching installer...

./setupTNPFAAix.bin: line 2432: /tmp/install.dir.17107/Aix/resource/
jre/jre/bin/java: cannot execute binary file
./setupTNPFAAix.bin: line 2432: /tmp/install.dir.17107/Aix/resource/
jre/jre/bin/java: Success

Solution

Make sure that you are running the correct installer binary file for your operating system.

Installation fails on a Windows system because of incorrect .vbs file association

Problem

If you try to run the TADDM installer on a Windows system where the file type association for the extension .vbs has been changed from the default value, the installation fails, and the following message is displayed in the taddm_7.2.1_install_msg.log file:

Input Error: There is no script engine for file extension ".vbs"

Solution

Make sure the Windows file type association for the extension .vbs is set to Microsoft Console Based Script Host. For more information about how to set file associations, see the Microsoft Windows documentation.

Installation fails because of an error extracting from common.zip

Problem: Under some circumstances, the installation process on a Windows system fails, and a message in the logs indicates an error extracting files from the common.zip file. This message usually indicates that the file has been locked by another process.
Solution: Restart the Windows system and run the installation process again.

Error when running make_ora_cms_dis script

Problem

Under some circumstances, the make_ora_cms_dis script fails while attempting to configure the database for the Context Menu Service and Data Integration Service. The following error is displayed in the log file:

ERROR at line 1:
ORA-01119: error in creating database file 'DISTS00.dbf'
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists

Solution

Search the database server for the following files (typically found in the $ORACLE_HOME/database directory):

DISTS00.dbf
DISTS01.dbf

Rename these files (for example, DISTS00.dbf.old) and then run the make_ora_cms_dis script again.

Installation fails on AIX system with no "/usr/bin -> /bin" directory link

Problem

When running the installer on an AIX system, the installation fails with the following error message:

-bash: ./setupAix.bin: /bin/sh: bad interpreter: No such file or directory

Solution

This error occurs when the AIX system does not have a symbolic link established between files in the /bin directory and the /usr/bin directory that contains the AIX shell.

To correct the problem:

Navigate to the root directory.
Run the following command:
```
ln -s /usr/bin/ /bin
```
Verify the link by running the following command:
```
ls -ld /bin
```
If you see the files in the /usr/bin directory, the link is established correctly.
Run the installer again.

Installation fails on remote system

Problem

If you start the installer on a remote system by using telnet or SSH, but do not specify the -i console option. The installer attempts to use console mode installation but fails.

Solution

When starting the installation that uses telnet or SSH, make sure that you explicitly specify console mode installation, as in the following example:

setupAix.bin -i console

Installation cannot proceed when using a custom temporary directory in a Linux environment

Problem

If you use a custom temporary directory to install TADDM for example, setupLinux.bin -t /path/to/custom/tmp, the installation might not proceed on a Linux system. An error stating that there is not insufficient space (0 bytes free) can be displayed. The installation log has additional information as shown in the following example:

4/8/11 3:16:58 PM : SEVERE : com.ibm.cdb.install.ia.utils.Utils 
(from runCommand(content, envs, filetype)) - null
Caused by: java.lang.NullPointerException
at: com.ibm.cdb.install.ia.utils.Utils.setFileExecutable(Utils.java:2472)

Solution

Check the option that was used to mount the temporary directory. You cannot use the noexec option. This option prevents direct execution of any binary files found in the custom temporary folder. Use the exec option to mount the temporary directory before carrying out the installation.

Installation cannot proceed when the default configuration cannot be applied

Problem

There is a port conflict when installing a domain server using the installation wizard. The following error message is displayed:

CTJT10057E The following port is being used by another application:
 port_number

Solution

For a simple installation, you can return and select the advanced installation option and specify port numbers that are free. Alternatively, you can change the system configuration to ensure that the defaults ports are free and start the simple installation again.

Installation fails because of the missing files

Problem

When you install TADDM on Windows operating systems, the following errors occur:

The following message is displayed on the first installation panel:

CTJTI0017E The following file is not found: \collation\common.zip.

A message about missing files in log files is displayed shortly after running the installation.

Solution

When you create administrator account manually on Windows operating systems, run the TADDM installation wizard setupWin.bat as administrator. Select the Run as administrator option.

DbInit fails to start after simple installation with DB2 database

Problem

The following error can occur usually on a system where the DB2 database was installed and then uninstalled, and later the TADDM server was installed together with the DB2 database. The error.log contains the following message:

[InitServletThread]  ERROR jdo.JdoDbInit - [JdoDbInit.E.8] An error occurred, could not 
connect to the jdbc:db2://100.101.102.103:50000/TADDM:deferPrepares=false; database.

Solution

Verify the DB2 server TCP/IP communications. For instructions, see the information about configuring DB2 server communications (TCP/IP) in the DB2 information center. You must also ensure that the JDBC connection URL in the collation.properties file is valid. Complete the following steps:

Find the port number in the JDBC connection URL. Go to the $COLLATION_HOME/etc directory, open the collation.properties file and locate the com.collation.db.url=jdbc:db2://host:port/database property.
Run the following commands to see whether the port is active. The port is usually not active. Run all commands on host.
- For the Linux or UNIX operating systems: netstat -an | grep port
- For the Windows operating system: netstat -an | find "port"
Depending on the operating system, complete the following step:
1. For the Linux or UNIX operating systems, log in as the DB2 database instance owner.
2. For the Windows operating system, open the DB2CMD command prompt.
Run db2 GET DATABASE MANAGER CONFIGURATION command.
The SVCENAME entry contains service name. The same entry is placed in the services file, but when this error occurs, there is no such entry. To fix the problem, complete either of the following steps:
- In the services file, update service name for the appropriate entry.
- Update DB2 configuration by following the instructions that are located in the DB2 information center.
You can find the services file in the following directories:
- For the Linux or UNIX operating systems: /etc/services
- For the Windows operating system: %SystemRoot%\system32\drivers\etc\services
Run the following commands:
```
db2set DB2COMM=tcpip
db2stop
db2start 
```
If the last command is successful, update com.collation.db.url with the service port number if necessary.
Restart the TADDM server.

See also the Connectivity problems section.

Simple installation fails on a Windows system

Problem

A TADDM installation fails when it is installed with a DB2 10 system. The following message is displayed in the cdb_cr_db2_stdout.log file:

ATTACH TO DB2 USER db2admin USING SQL1042C  
An unexpected system error occurred.  
SQLSTATE=58004

Solution

Exit the installer and start the installation procedure again. For more information about the problem, see the following technote: http://www.ibm.com/support/docview.wss?uid=swg21502619.