Hi ,

I am getting the following error during db2start

SQL5043N Support for one or more communications protocols failed
to start successfully. However, core database manager
functionality started successfully.


Instance is db2inst1


Following is there in the /etc/services file

DB2_db2inst1 60000/tcp
DB2_db2inst1_1 60001/tcp
DB2_db2inst1_2 60002/tcp
DB2_db2inst1_END 60003/tcp
db2c_db2inst1 50000/tcp


Following is there in the dbm cfg file

TCP/IP Service name (SVCENAME) = DB2_db2inst1


Following is the output of db2set -all command

[i] DB2COMM=tcpip
[g] DB2SYSTEM=aix2x4
[g] DB2ADMINSERVER=db2das


Also I am not able to catalog the databases through client configuration assistant

any help regarding this would be greatly appreciated

Thanks

Falcon

Check you db2diag.log and/or the nfy file in sqllib/db2dump path

Cheers
sathyaram

hI sathyaram ,

The Ddb2diag.log doesnot have any information about it it says TCPIP support sucessfully started


Regards

Falcon

Sorry for my english

Have you right access permission on file /etc/services ??
I remeber that this message represent a non valid access permission to
some file, but i don't remeber the file

Hi g.dipierto

I have read permission on /etc/services , I dont think you need to have write permission on /etc/services file Read permission only will do because my other instance are working fine with read permission on /etc/services file

Regards

Falcon

Firewall, IP filter on your AIX?

Best

What are you specifying for the port # in the CA (used to be CCA) and what version of the client and UDB server?
I'd think that you need to specify 50000
as per db2c_db2inst1 50000/tcp ?

Hi rubystep I have tried out with 50000/tcp as well but it didnt work

I am using V8 client and server

Regards

Falcon_down

Please, change the SVCENAME parameter to the Port Number, in this case 60000, with the command:

update dbm cfg using SVCENAME 60000

then:

db2stop
db2start

Sometimes this is the solution.

mrln.

Hi mrln
Thanks for ur help

But I tried that also , It didnot work

Regards

Falcon

I recently installed fixpack 5 and ran into the same problem. I realized I had not run the dasupdt utility after applying the fixpack as is noted in the readme.
I had run the db2iupdt, but not the dasupdt. Once I ran that, I was able to successfully start the server.
Don't know if this is your scenario but hopefully it will help.

I asume , U R using DB2 V8 fp x
add entry as below in /etc/services , then start the instance , that will work

DB2_db2inst1 60000/tcp
DB2_db2inst1_END 60003/tcp

Let me know , if any questions.


Thank You