Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2005
    Posts
    6

    Unanswered: db2start doesn't start the database anymore

    I have a problem with DB2 8.2 on AIX 5.3, I am no longer able to start the database.

    db2 was running since 1 year without problems, but since it was recently run out of space I am no longer to start it.
    I even completly reinstalled db2 8.1 + FP13 but the problem still exist.

    The error message I receive seems to multi partitioned releated but I just have a single partition installation.

    When I run dbstart as the instance owner, I get the following error:

    0 0 SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.
    SQL1032N No start database manager command was issued. SQLSTATE=5701


    The db2diag.log looks like this:
    2006-10-16-15.12.54.257082+120 I1082C409 LEVEL: Event
    PID : 475250 TID : 1 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 52 bytes
    /home/db2inst1/sqllib/adm/db2rstar db2profile SN 0 0
    DATA #2 : Hexdump, 4 bytes
    0x2FF1DB38 : 0000 0010 ....

    2006-10-16-15.12.55.411917+120 I1492C338 LEVEL: Error
    PID : 475250 TID : 1 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloPdbExecuteRemoteCmd, probe:50
    DATA #1 : Hexdump, 8 bytes
    0xF0449EBB : 6C6F 6F70 6261 636B loopback

    2006-10-16-15.12.55.412174+120 I1831C482 LEVEL: Error
    PID : 475250 TID : 1 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloPdbExecuteRemoteCmd, probe:50
    DATA #1 : Hexdump, 37 bytes
    0x2FF1D520 : 7273 6864 3A20 3038 3236 2D38 3133 2050 rshd: 0826-813 P
    0x2FF1D530 : 6572 6D69 7373 696F 6E20 6973 2064 656E ermission is den
    0x2FF1D540 : 6965 642E 0A ied..

    2006-10-16-15.12.55.423824+120 I2314C291 LEVEL: Severe
    PID : 475250 TID : 1 PROC : db2start
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloPdbOpenConnection, probe:10


    I can run the db2 shell without problems, i can get and update the dbm configuration, loopback is resolved as commonly as 172.0.0.1 and pingable

    Any Ideas what's the cause is?
    Haven't found a solution yet.
    Thanks in adavnce

  2. #2
    Join Date
    Jun 2006
    Posts
    471

    db2start

    can you check db2nodes.cfg file
    this file is being used for detecting the nodes/hosts
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  3. #3
    Join Date
    Dec 2005
    Posts
    6
    The nodes.cfg was looking good.

    0 hostname 0

    But the loopback error was conncerning me, so I took a look to my /etc/hosts file and noticed that the 127.0.0.1 adress was before the main IP adress.

    After changing this I get the same error in db2diag.log, but this time I was receiving the real hostname in the error.

    So I just following stupd the instructions to allow remote exectuions:
    http://publib.boulder.ibm.com/infoce...6f%73%74%22%20

    Which was fixing the issue

    But I wonder why this had nnot to be done after the initial setup before a hlaf year???

  4. #4
    Join Date
    Jan 2004
    Posts
    2
    what about the DAS server is it running ? Did you do netstat -na | grep <port#>, is the port that db2 uses still LISTEN, TIME_WAIT or CLOSE_WAIT mode ? What is the timeout value of a TCP connection on AIX

Posting Permissions

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