This is a discussion on force connections within the DB2 forums, part of the Database Server Software category; --> I am issuing the setof commands from my client ( udb 7.2 fixpack6) 1.db2 attach to webdem07 user db2admin ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am issuing the setof commands from my client ( udb 7.2 fixpack6) 1.db2 attach to webdem07 user db2admin using db2admin Instance Attachment Information Instance server = DB2/NT 7.2.4 Authorization ID = DB2ADMIN Local instance alias = WEBDEM07 2.db2 connect to pf1_psa user db2admin using db2admin Database Connection Information Database server = DB2/NT 7.2.4 SQL authorization ID = DB2ADMIN Local database alias = PF1_PSA 3.db2 list applications Auth Id Application Appl. Application Id DB # of Name Handle Name Agents -------- -------------- ---------- ------------------------------ -------- ----- DB2ADMIN db2bp.exe 13 0AA403B3.1B11.030818212723 PF1_PSA 1 Now I tried to force the connection from client side.. 4.db2 force applications all SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001 I am getting above message ?? any thoughts .. Thanks Uma |
| ||||
| You have pulled out a large gun and shot yourself. Your connection was killed by the "force applications all". Regards, V- > > > > 4.db2 force applications all > > > > SQL30081N A communication error has been detected. Communication protocol > > being used: "TCP/IP". Communication API being used: "SOCKETS". Location > > where the error was detected: "". Communication function detecting the error: > > "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001 > > > > > > I am getting above message ?? > > > > any thoughts .. > > > > Thanks > > Uma |