ANR0162W Supplemental database diagnostic information: -30081

Technote (troubleshooting)


Problem(Abstract)

A Tivoli Storage Manager server fails to start with the following error :
ANR0162W Supplemental database diagnostic information: -30081:SQLSTATE 08001: The connection was unable to be established to the application server or other server.

Symptom

The Tivoli Storage Manager server does not start and the following information is displayed during startup in the foreground :


ANR0162W Supplemental database diagnostic information: -30081:SQLSTATE 08001: The connection was unable to be established to the application server or other server.
:-30081 (SQL30081N A communication error has been detected. Communication protocol being used:
"TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "127.0.0.1". Communication function detecting the error: "connect". Protocol specific error code(s): "79", "*", "*". SQLSTATE=08001).


Cause

DB2 Instance userid configuration


Resolving the problem

To resolve this issue, verify the following and make sure that they are configured correctly. You will need to run the following commands to validate if the configuration is correct.


db2set all
db2 list db directory
db2 list node directory
cat /etc/services | grep -i db2 ** Unix**
find /i "db2" c:\windows\system32\drivers\etc\services **Intel**
db2 get dbm cfg


Verify the following.

  1. Make sure that 'db2set all' displays the following environment variable as being set.
    For example :
    [g] DB2COMM=TCPIP
  2. Make sure that there is a DB2 port specified for the TSM Server/DB2 connection in the 'services' file. For example :
    DB2_TSMINST1 60000/tcp
    Note that the name could be any name and the port can be any port but we suggest in the 60000 range.
  3. Verify that the 'db2 get dbm cfg' is setup correctly for the SVCENAME value according to the value in the 'services' file.
    For example :
    TCP/IP Service name (SVCENAME) = DB2_TSMINST1
    Note that the SVCENAME may specify a tcpip port instead of a service name from the services file.
  4. You can also verify if this is setup correctly by the output from 'db2 list node directory'.
    For example :
    Service name = DB2_TSMINST1
  5. Make sure that you can ping the localhost which should resolve to 127.0.0.1.
    For example :
    ping localhost

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

6.2, 6.3

Operating system(s):

Platform Independent

Software edition:

All Editions

Reference #:

1590844

Modified date:

2014-07-15

Translate my page

Machine Translation

Content navigation