TL1 TSM agent 5.3.1 will not run due to JDBC error

Technote (troubleshooting)


Problem(Abstract)

After moving the TL1 TSM probe on the other server it will not start, producing ScheduleJDBCStorageExtension Extension error

Symptom

>> Error in the tsm.log
18:13:23 ERROR ScheduleJDBCStorageExtension Extension 'Schedule JDBC
Storage' activate error: null; nested exception is:
lumos.scontainer.scheduler.ScheduleException Removing extension


Resolving the problem

The tl1-tsm's database might to be not populated with all the database tables. This error comes when some tables are missing from the database. especially when "SCHEDULE" table is missing.

A total of 61 tables needs to be present in the tsm database. Please ask the customer to check the count of tables.
As a fix right now a new database needs to be created & populated with all the LEAP tables , use the following steps if you are not clear.

Note: tl1tsm_installdir refers to the install directory of the tl1-tsm ( by default tl1tsm is installed in /opt/netcool/tl1tsm )

Step1. Log into mysql server using following command
"console> tl1tsm_installdir\mysql\bin\mysql -u root "

Step2. The customer has 2 options either to create a new database with new name or drop the existing database and create a new database with the same name.

Option a) create a new database
Create a new database using
"mysqlshell> create database tsm2" ;
and logout of the mysql server using
"mysqlshell> quit;"

Option b) use the same database name
drop database tsm - "mysqlshell> drop database tsm;"
recreate the database tsm - "mysqlshell> create database tsm;"

db-name from now refers to the database which the user has selected

Step3. Populate the new database with tsm's tables using this command
"console>tl1tsm_installdir\mysql\bin\mysql -u root db-name < tl1tsm_installdir/config/sql/mysql/leap_schema.sql "

Step4. Do this only if u have run Step2's option (a)
Update tsm's config files
update tl1tsm_installdir/config/tsm.xml - change the db name from "tsm" to "tsml2"

Step 5. Run the tsm after purging the log files
tl1tsm_installdir/bin/nco_t_tl1

If the user faces any problem logging into mysql please use following command to login to mysql server - just replace this command in the above steps.
Note: use the following commands only if the user is not able to login to mysql server in the normal manner.
"console> tl1tsm_installdir\mysql\bin\mysql -u root -S /tmp/mysql.sock"

or

"console> tl1tsm_installdir\mysql\bin\mysql -u root -P <port-num>"
- the port num at which mysql db server is listening can be got from this file tl1tsm_installdir/bin/start_mysql.sh

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Network Manager Transmission Edition

Software version:

5.3

Operating system(s):

Solaris

Reference #:

1390945

Modified date:

2011-05-17

Translate my page

Machine Translation

Content navigation