Search This Blog

Friday, March 17, 2017

db2 not listening on port, connection refused on server boot.

 

 

If you are using community version , you might have configured tcp/ip for your dbcopy to listen on and you must have used db2admin as the master user for all accounts.

 

Once you start the server and it doesn’t connect, it could be because of the tcp/ip setting not configured for your instance.

if you want to connect or view table data use db2cmd  to initialize command line env

 

db2> connect to dbname user db2admin using password

 

// just to check if you are able to connect to your database.

if you are able to connect, that means your database is active and its not listening on the port.

 

Do a netstat –an from command line and see if your listening port is available, if not read below.

 

 

P.S when i had setup the db2 , i configured tcp/ip to listen to 5002 for ibm ioc, but this wasn’t reflected and i don’t know why.

 

Troubleshoot

view your db2set –all and see if db2comm is set.

if not read below.

 

db2set DB2COMM=tcpip

db2 update DBM CFG using SVCENAME 50002

db2stop force  -- from admin cmd window
db2start 
Retry the ear from eclipse 
 
 
 
 
/// Ref db2 connection refused connect. errorcode=-4499 sqlstate=08001
 

No comments:

Post a Comment