SQL30081N - Need solution for solving this problem - URGENT

WantedToBeDBA

Hi all,
We have db2 installed on AIX box (db2 version - 8.1). Its started
and i am able to view 50000(default port) in netstat(netstat -a -n).
But when i try to connect using telnet, i am getting this error. I
don't know how to correct it.

Till yesterday its working well. I don't know what is the problem
now..

Help me guys. Its very urgent

SQL30081N A communication error has been detected.
Communication protocol being used: "<protocol>".
Communication API being used: "<interface>". Location
where the error was detected: "<location>".
Communication function detecting the error:
"<function>". Protocol specific error code(s):
"<rc1>", "<rc2>", "<rc3>".

-WantedToBeDBA.

Nov 12 '05 #1

Mark Yudkin

It is VERY IMPORTANT that you actually post the values for the
meta-variables. It is there that the actual REASON for the failure is
specified. You also need to check the DB2 log for possibly related errors.

Otherwise it could be any of the following, and a lot more besides:
- wrong machine
- wrong address
- wrong port
- wrong or mismatched protocol
- DNS misconfiguration
- no DB2 started

Also what do you mean "try to connect with telnet"? What does telnet have to
do with DB2 client - server communication?

"WantedToBeDBA" <dba_oracle_db2@yahoo.com> wrote in message
news:9378c322.0412150356.4abdfd69@posting.google.c om...[color=blue]
> Hi all,
> We have db2 installed on AIX box (db2 version - 8.1). Its started
> and i am able to view 50000(default port) in netstat(netstat -a -n).
> But when i try to connect using telnet, i am getting this error. I
> don't know how to correct it.
>
> Till yesterday its working well. I don't know what is the problem
> now..
>
> Help me guys. Its very urgent
>
> SQL30081N A communication error has been detected.
> Communication protocol being used: "<protocol>".
> Communication API being used: "<interface>". Location
> where the error was detected: "<location>".
> Communication function detecting the error:
> "<function>". Protocol specific error code(s):
> "<rc1>", "<rc2>", "<rc3>".
>
> -WantedToBeDBA.[/color]

Nov 12 '05 #2

dotyet

maybe you need to run the following command on your db2 instance (the
server side)

check whether you have TCPIP listed as the communication protocol or
not? run the following command from the db2 instance owners shell
prompt:
db2set db2comm

if not, then type the following command to set it:
db2set db2comm=TCPIP

once done, then check your problem again. if not solved, then do a
db2stop followed by db2start and then try again.

if this does'nt help, then probably something else is causing this, you
need to post more information then.

regards,
dotyet

Nov 12 '05 #3