Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2003
    Location
    Melbourne, Australia
    Posts
    53

    Unanswered: DB2 Error SQL5043N

    Environment -- IBM RS/6000 with AIX 5.1 mainatainence patch 03 and DB2 UDB 7.1 with Fixpack 7

    Problem -- Whenever the command 'db2start' is given, am getting a error as below

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

    However, there's no error message in the db2diag.log file.

    Any help appreciated.

    Regards

  2. #2
    Join Date
    Apr 2003
    Location
    P.R.China
    Posts
    6

    Re: DB2 Error SQL5043N

    use "db2set -all" to check the "db2comm" setting, if it is not right, change it .

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: DB2 Error SQL5043N

    Assuming , you are using TCPIP, check the db2comm varaible is set to tcpip

    db2set DB2COMM

    will give you the output ...

    Check the SVCENAME dbm cfg ...

    db2 get dbm cfg

    and cross-check it against the port number in /etc/services

    cat /etc/services | grep `db2 get dbm cfg | grep SVCE | nawk '{print $NF}'`

    If there is no entry for serivices, add it ..

    If all these are OK, on starting DB2, do

    netstat -an | grep <port-number>

    You should see the status as LISTENING for the port ...

    With all these done, check whether your clients can connect ....

    HTH

    Cheers

    Sathyaram


    Originally posted by xiaochuan_li
    use "db2set -all" to check the "db2comm" setting, if it is not right, change it .

  4. #4
    Join Date
    Apr 2003
    Location
    Melbourne, Australia
    Posts
    53

    Re: DB2 Error SQL5043N

    Hi All,

    As per the suggestion given below, everything is in order. But, when i try to start the instance its gives the same error. On this machine there are 2 instances running, DB2 and DB2CTLSV. Surprisingly the below mentioned error is only coming for the DB2 instance.

    Any help appreciated.



    Originally posted by sathyaram_s
    Assuming , you are using TCPIP, check the db2comm varaible is set to tcpip

    db2set DB2COMM

    will give you the output ...

    Check the SVCENAME dbm cfg ...

    db2 get dbm cfg

    and cross-check it against the port number in /etc/services

    cat /etc/services | grep `db2 get dbm cfg | grep SVCE | nawk '{print $NF}'`

    If there is no entry for serivices, add it ..

    If all these are OK, on starting DB2, do

    netstat -an | grep <port-number>

    You should see the status as LISTENING for the port ...

    With all these done, check whether your clients can connect ....

    HTH

    Cheers

    Sathyaram

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: DB2 Error SQL5043N

    Well, the first fundamental question(which I missed), did you have a chance to check the db2diag.log file ... There should be an error logged for the protocol .... Many times, it is not TCP/IP, depending on what other protocol is configured on your server ....

    The next question, are you able to connect to the server from the client ...

    Cheers

    Sathyaram

    Originally posted by rupee2003
    Hi All,

    As per the suggestion given below, everything is in order. But, when i try to start the instance its gives the same error. On this machine there are 2 instances running, DB2 and DB2CTLSV. Surprisingly the below mentioned error is only coming for the DB2 instance.

    Any help appreciated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •