By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,286 Members | 1,290 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,286 IT Pros & Developers. It's quick & easy.

DB2 error SQL30081N on AIX version 5.2 / 5.3

P: 4
Hi All,

I am working for the first time on DB2.

I have installed ver 7.2, and am using AIX version 5.2, and 5.3 for some DBs. I am getting this error "SQL30081N" for some of the databases. I have added the Databases as per the info I have got. Please guide me as to when this kind of an error may occur, and how I can resolve this? This issue has been haunting me for long. Hope someone can help me out of this.

Any kind of help will be appreciated.

I am new to IT and so pls explain like you would to a beginner. :) I will try to pick up as much as possible.

Thanks.
Aug 29 '07 #1
Share this Question
Share on Google+
5 Replies


docdiesel
Expert 100+
P: 297
Hi,

SQL30081N means "A communication error has been detected...", that is the client cannot connect to your (remote) database(s).

How did you catalog the databases?

Regards, Bernd
Aug 29 '07 #2

P: 4
Hi,

SQL30081N means "A communication error has been detected...", that is the client cannot connect to your (remote) database(s).

How did you catalog the databases?

Regards, Bernd

Hi Bernd,

Adding a profile didn't work. So I had to get the databases added manually. I tried to connect to 5 databases, but 3 of them are having the SAME problem. 2 are ok. Thats why I wonder why the client is not able to detect the other REMOTE DBs.

Hope this is what you's asked for.

Regards,
BM
Aug 30 '07 #3

docdiesel
Expert 100+
P: 297
Hi bonymuscle,

I guess the groups of 2 / 3 databases are cataloged to different nodes? Perhaps you could post the db and node directory:
  • Open a db2 command line windows, e.g. by "Start"/"Run command", then start db2cmd
  • execute db2 list node directory
  • execute db2 list database directory
  • post the output, and lets have a look.

Regards, Bernd
Aug 30 '07 #4

P: 4
Hi bonymuscle,

I guess the groups of 2 / 3 databases are cataloged to different nodes? Perhaps you could post the db and node directory:
  • Open a db2 command line windows, e.g. by "Start"/"Run command", then start db2cmd
  • execute db2 list node directory
  • execute db2 list database directory
  • post the output, and lets have a look.

Regards, Bernd
Hi Bernd,

I am sorry cos I think I can't provide you with those details. I have run your commands and found that

> The Port numbers are the same.
> The Node names vary, though I don't know what it is related to.
> The IP addresses correspond to the server names, of the databases.

I will give you a sample though :

Node 1 entry:

Node name = < ABC12345 (Some Alphanumeric name) >
Comment = <blank>
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = < Server's IP >
Service name = < the same IP for all DBs >

Database 3 entry:

Database alias = < the alias name I'd used when I added the DB >
Database name = < Self Detected I presume, I didn't add this alphanumeric String it displayed>
Node name = < The NODE NAME that I'd entered above > Database release level = a.00
Comment =
Directory entry type = Remote
Authentication = SERVER
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =


I hope this information must help you in some way or the other. I appreciate your taking time to help me out with this. I am grateful. :)

I had to add some more DBs today, and now its like 3 out of 8 is positive!!! :( which is less than 50%. Having a great time!!! ;)

Have a great weekend.

Regards,
BM.
Aug 31 '07 #5

docdiesel
Expert 100+
P: 297
Hi bonymuscle,

Expand|Select|Wrap|Line Numbers
  1. Service name = < the same IP for all DBs >
  2.  
just to talk about the same, this entry should be the tcp/ip port number you're server is listening on.

Which brings me to the next point. If port numbers and ip addresses are ok, then the question is: Are you sure you're db2 instance is listening on that port? On Unix'es, you'll sometimes have to tell db2:

Expand|Select|Wrap|Line Numbers
  1. db2set DB2COMM=tcpip
  2. db2stop
  3. db2start
  4.  
Maybe a "netstat -lntp" won't show that port before but afterwards. You may check if that db2 variable is set before executing the above commands.

Some other questions - could there be some firewall between your client and your server(s)? On how many servers are databases connectable, on how many the aren't?

Regards, Bernd
Aug 31 '07 #6

Post your reply

Sign in to post your reply or Sign up for a free account.