Troubleshooting
Problem
DB2 Database manager for the Tivoli Storage Manager 6.x Server fails to start with SQL6030N Reason Code 13.
Symptom
The following errors are reported on the console when starting the server in the foreground:
...
ANR7801I Subsystem process ID is 2540.
ANR0900I Processing options file /home/tsminst1/dsmserv.opt.
ANR7814I Using instance directory /home/tsminst1.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0151W Failure starting database manager.
ANR9999D_1438116997 RdbStartInstance(rdbinst.c:991) Thread<1>: Add codes to msg DB_DATABASE_START_FAILED sqlCode -6031.
ANR9999D Thread<1> issued message 9999 from:
ANR9999D Thread<1> 0x0000000000bee072 OutDiagToCons+0x0x142
ANR9999D Thread<1> 0x0000000000bf0bf4 outDiagfExt+0x0x194
ANR9999D Thread<1> 0x00000000007887eb RdbStartInstance+0x0x1db
ANR9999D Thread<1> 0x000000000070ba05 dbiInit+0x0x1045
ANR9999D Thread<1> 0x000000000051ffcd admStartServer+0x0x27d
ANR9999D Thread<1> 0x000000000046c072 main+0x0x1802
ANR9999D Thread<1> 0x0000003f6cc1d8b4 *UNKNOWN*
ANR9999D Thread<1> 0x000000000046a00a __strtoll_internal@@GLIBC_2.2.5 +0x0x52
ANR0172I rdbdb.c(969): Error encountered performing action InstanceStop.
ANR0162W Supplemental database diagnostic information: -6031:**No State
Information Available (-2)**:-6031 (**No Other Information Available (80)**).
-
The following error is reported when running the 'db2start' command to start the DB2 instance:
admtsmr2@cmaix192:/home/admtsmr2> db2start
SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13".
Cause
The Tivoli Storage Manager fails due to the DB2 Database manager failing to start.
Diagnosing The Problem
The problem can be verified by issuing the 'db2start' command.
Start the Database manager with the db2start command. In this example db2start failed with the following error:
> db2start
SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13".
RC =13 is a DB2 return code that means:
No port value is defined for your DB2 instance id (/etc/services file on UNIX-based systems).
Resolving The Problem
Verify the port range availability:
1. login as "root" and open the services file located in the /etc/services directory
2. add the following entries to /etc/services
DB2_<db2instance_name> <port_number>/tcp
DB2_<db2instance_name>_1 <port_number>/tcp
DB2_<db2instance_name>_2 <port_number>/tcp
DB2_<db2instance_name>_END <port_number>/tcp
Set the <port_number> to a unique value for each DB2 instance that is listed.
Once the /etc/services is setup with the correct port for the DB2 instance to listen on, 'db2start' should be able to start the DB2 instance normally and then start the Tivoli Storage Manager server.
Product Synonym
TSM
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21403062