Problems on the installation and connection of Managing Server databases

IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Problems on the installation and connection of Managing Server databases

The following examples are some problems with the Managing Server databases you might encounter.

DB2 connection fails when installing Managing Server on Solaris

The problem: When using a DB2 type 2 JDBC driver while installing Managing Server on Solaris, the following error is returned:
CYNCR9705E Can not find DB2 type 2 jdbc driver library in the system library path.
The solution: Ensure that the database is running and accessible on the network. Confirm that the information you entered for the database is correct before you continue the installation. It may be caused by environment errors on the operation system or database. For example, when using a DB2 type 2 JDBC driver, the driver library path must be specified in the system library path.
Before running the Managing Server installation, you are required to source the DB2 environment by using the source db2profile command. You must also do this before starting WebSphere and Managing Server.
If the error still occurs, review the installation trace log file, trace-install.log, for more information. This log file is located in the common logging directory.

Error running db2install.sh script

The problem: After running the db2install.sh script, the following errors were returned:
./db2install.sh db2inst1 cyanea /tmp/wsam31/Installer-MS/scripts/db2
ksh: db2:  not found.
ksh: db2:  not found.
Does this mean the script failed?
The reason: The script may have completed successfully, but the error messages mean that the user did not have the correct information in the ".profile" file.
The solution: There needs to be a reference that sources the db2profile.

Fail to install DB2 with the Managing Server

The problem: During an installation of DB2 with the Managing Server, you may specify an invalid DB2 installation image (for example, DB2 Workgroup Server Edition). This may cause the installation of DB2 with the Managing Server to fail.
The solution: Ensure that you are using the DB2 installation images that were shipped with ITCAM for WebSphere. These images are provided in the CD-ROM packet or as a download as part of the ITCAM for WebSphere eAssembly.

Remote DB2 installation failed because of different DB2 instance owners on the client and the server

The problem: When installing ITCAM for WebSphere Managing Server, the installer cannot find the database with db2inst1 specified as the DB2 instance user. After db2inst3 is specified as the remote user, the installer shows that the user does not exist.
The cause: When installing ITCAM for WebSphere in an environment with a remote DB2 database there are issues when your DB2 instance user (db2inst1 by default) is different on the DB2 client and server. DB2 handles this fine. But when you connect to a database using the DB2 client you supply the remote instance user name and password. The problem is with the installer. It expects the remote user name and password AND it checks to see whether there is a local user of that same name. If your instance user name is not the same, at least create a dummy user on the Managing Server (DB2 client) with the same name as the instance user on the DB2 server.
The following section describes an example of this issue:

DB2 Server - Had multiple DB2 instances, and the customer created a new one called db2inst3 where the ITCAM databases were created using the provided scripts on the install CDs;
ITCAM Managing Server - Had the DB2 client installed with the defaults including creating the instance user db2inst1, and could connect to the remote databases with no problems using the db2 command shell.

The solution: To complete the installation, you are required to create a dummy user on the Managing Server (DB2 client) with the same name as the instance user on the DB2 server. In this specific example, create a local user db2inst3 to solve the problem.

Set up an alternate SID name on an Oracle Database

The question: How do I set up an alternate SID name on an Oracle Database?
The answer: Do the following steps:
Oracle Configuration
Install the Managing Server per standard procedures, skipping the creation of the Managing Server database. This procedure is standard when using a remote database instance.
Create the ITCAMx (i/q/p) database on the wanted Oracle server using the dbca utility or existing Oracle scripts.
Extract the contents of the oracle-remote-scripts.tar file copied from the Managing Server to a temporary directory on the Oracle server.
Generate the wanted schema user and assign it 100-200 MB table space. The configuration script will grant unlimited table space to the user.
Execute the following commands to grant roles to the schema user.
GRANT RESOURCE TO ITCAMIWAS;
GRANT CREATE PROCEDURE TO ITCAMIWAS;
ALTER USER ITCAMIWAS DEFAULT ROLE ALL;
Execute the following command from the oracle directory in the path of the extracted tar file. The following parameters are used in the following command:
itcamiwas - Oracle schema owner
CAM - Oracle tablespace name
admin - local Managing Server OS account, used as default administrator

sh bin/oracleinstall.sh itcamiwas password CAM itcamiwas password admin
Verify that there are no unusual errors in the log files created in the ~/oracle/logs directory, oracle_createschema_installation.out and oracle_prepare_installation.out.
Verify the Oracle client connection from the Managing Server to database using an SQL plus connection using the schema owner credentials. The Managing Server owner account must have all the proper Oracle configurations in its profile file, as shown in the following example. The ORACLE_OWNER and ORACLE_SID variables can be changed to match the current environment.
Oracle 10g
ORACLE_BASE=/home/oracle/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_2; export ORACLE_HOME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=$ORACLE_HOME/bin:$PATH; export PATH
ORACLE_OWNER=oracle; export ORACLE_OWNER
ORACLE_SID=itcamx; export ORACLE_SID 
LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib; export CLASSPATH

TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
Managing Server Configuration
Managing Server configuration must be changed to accommodate the new database name. Changes are applied to the shell script that sets the Managing Server operating environment and the data source used by the WebSphere Enterprise Application that provides the Visualization Engine.
Log in as the Managing Server owner.
Back up the setenv.sh file in the ~/MS_home/bin directory.
Open the setenv.sh script and change the line listed to include the proper host name, Oracle SID, and listener port.
JDBC_DRIVER_URL=jdbc:oracle:thin:@rh4as20gb.test.org:1521:itcami
Test the database connectivity by using the command MS_home/bin/amctl.sh kl1 dbtest. This command checks the database credentials and client driver configuration then check for the presence of a table created by the Oracle configuration scripts. An example output from this command is shown.
[amuser@rh4as20gb bin]$ ./amctl.sh kl1 dbtest
/opt/IBM/itcam/WebSphere/MS/bin/klctl.sh dbtest kl1.properties
Testing DB Connection with kernel properties...
using the following properties to test database connection...
JDBC DRIVER NAME =oracle.jdbc.driver.OracleDriver
DB URL =jdbc:oracle:thin:@rh4as20gb.test.org:1521:itcami
DB USER =itcamiwas
DB PASSWORD =XXXX
Trying to establish connection to database
Succesfully established connection 
Testing by executiong two sql calls
.........................

Trying to get first prepared statement from connection Successfully got prepared statement from connection Trying to execute prepared statement on connection Successfully executed prepared statement on connection Trying to close prepared statement
Successfully closed prepared statement

Trying to get second prepared statement from connection Successfully got prepared statement from connection Trying to execute prepared statement on connection Successfully executed prepared statement on connection Trying to close prepared statement
Successfully closed prepared statement

Trying to close database connection Successfully closed connection 
Test complete
[amuser@rh4as20gb bin]$
Start the Managing Server processes using the command MS_home/bin/am-start.sh
WAS Configuration

Start the WAS configured for the Managing Server Visualization Engine and login to the Admin Console.
Open Resources > JDBC Providers > ITCAM-JDBCDriver > Data Sources > ITCAMDataSourceand change the URL at the bottom of the page to reflect the wanted host name, SID, and listener port.
Click Apply.
Select the "J2EE Connector Architecture (J2C) authentication data entries" link and then the Node...Cell/server1 entry.
Change the user ID and password values to match those changed in the setenv.sh file. Click Apply, then the Save link at the top of the Window. Click Save again.
Restart the Application Server, login to the Admin Console and test the data source connection to the new database. If this passes, login to the Visualization Engine using the default admin account.
Verifying that the database tables successfully populated the Octigate database

The problem: You need to verify that the database tables successfully populated the octigate database.
The solution:
In UNIX:
Switch to the user that logs into the Application Monitor.
su - admin_user
Issue the following DB2 commands:
db2 connect to octigate
db2 list tables
db2 terminate
In Windows:
From Windows Start menu, select Start > All Programs > IBM DB2 > Command Line Tools > Command Window.
Issue the following DB2 commands:
db2 connect to octigate user [username] using [password]
db2 list tables
db2 terminate
The DB2 list tables produces 65 tables. If there are no results, then the tables were not created.

Parent topic:
Installation and configuration

+
Search Tips | Advanced Search