Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2013
    Posts
    8

    Unanswered: db2admin start error

    hi guys,

    iam new in DB2 world, n i found the following error

    [dasusr1@TNMSERVER bin]$ db2admin start
    DB2ADMIN processing complete, SQLCODE = 4404

    as far as know dasusr1 was the DAS account that automatically created after DB2 installation right ??

    any idea ??

    i also have perform the following steps but nothing good comes up

    [root@TNMSERVER instance]# ./dasdrop dasusr1
    DB2ADMIN processing complete, SQLCODE = 4404
    DBI1070I Program dasdrop completed successfully.


    [root@TNMSERVER instance]# ./daslist
    [root@TNMSERVER instance]# ./dascrt dasusr1
    DB2ADMIN processing complete, SQLCODE = 4404
    DBI1070I Program dascrt completed successfully.


    [root@TNMSERVER instance]# ./dasupdt
    DB2ADMIN processing complete, SQLCODE = 4404
    cp: cannot create regular file `/home/dasusr1/das/adm/db2dasrrm': Text file busy
    DB2ADMIN processing complete, SQLCODE = 4404
    DBI1070I Program dasupdt completed successfully.


    [root@TNMSERVER instance]# ./daslist
    dasusr1

    [dasusr1@TNMSERVER bin]$ db2admin start
    DB2ADMIN processing complete, SQLCODE = 4404


    any idea ??

  2. #2
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Which linux distro and version?
    What db2 version and fixpack ?
    What is in ~dasusr1/das/dump/db2dasdiag.log ?

  3. #3
    Join Date
    Sep 2013
    Posts
    8
    thanks for the replay
    Quote Originally Posted by db2mor View Post
    Which linux distro and version?
    What db2 version and fixpack ?
    What is in ~dasusr1/das/dump/db2dasdiag.log ?
    1. Linux TNMSERVER 2.6.18-238.el5 #1 SMP Sun Dec 19 14:22:44 EST 2010 x86_64 x86_64 x86_64 GNU/Linux

    2. Version 9.7.0.4 and FP 4.0

    3.

    2013-09-30-04.52.47.932616-420 I1E454 LEVEL: Error
    PID : 27697 TID : 47119142620528
    FUNCTION: DB2 Common, Fault Monitor Facility, fmEmailNotify, probe:50
    MESSAGE : ECF=0x90000371 The fault monitor daemon failed to send an e-mail notification
    DATA #1 : Sint32, 4 bytes
    -22295
    DATA #2 : String, 119 bytes
    db2fmd
    The state of instance 'dasusr1' gcf module '/opt/ibm/db2/V9.7/das/lib/libdb2dasgcf.so.1' is OPERABLE (OFFLINE).


    2013-09-30-04.52.47.932695-420 I456E420 LEVEL: Error
    PID : 27697 TID : 47119142620528
    FUNCTION: DB2 Common, Fault Monitor Facility, fmMainLogic, probe:130
    MESSAGE : ECF=0x90000371 The fault monitor daemon failed to send an e-mail notification
    CALLED : DB2 Common, Fault Monitor Facility, fmEmailNotify
    RETCODE : ECF=0x90000371 The fault monitor daemon failed to send an e-mail notification

  4. #4
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Which distro is that? Ubuntu ? RHEL ? Fedora ? Suse ? etc...

    When you run the db2admin start, are these the *only* messages that get appended to the das log file ?

  5. #5
    Join Date
    Sep 2013
    Posts
    8
    im using RHEL 5.6, and the below are the others contain of das log file

    Code:
    2013-09-30-04.52.47.933985-420 I877E214           LEVEL: Error
    PID     : 27697                TID : 47119142620528
    FUNCTION: DB2 Common, Generic Control Facility, gcf_start, probe:10
    DATA #1 : Sint64, 8 bytes
    4407
    
    2013-09-30-04.52.47.934022-420 I1092E421          LEVEL: Error
    PID     : 27697                TID : 47119142620528
    FUNCTION: DB2 Common, Fault Monitor Facility, fmMainLogic, probe:150
    MESSAGE : ECF=0x9000034E Failed to start the GCF service module
    CALLED  : DB2 Common, Generic Control Facility, GcfCaller::start
    RETCODE : ECF=0x0 OK
    DATA #1 : Sint64, 8 bytes
    1
    DATA #2 : Uint64, 8 bytes
    1
    DATA #3 : Sint64, 8 bytes
    4407
    hopefully it could help...

  6. #6
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Did you configure your kernel parameters ?
    Kernel parameter requirements ( Linux ) - IBM DB2 9.7 for Linux, UNIX, and Windows

    If your kernel parameters are already configured, and you cannot find any more clues in either the DAS log or /var/log/messages, then open a PMR with IBM.

  7. #7
    Join Date
    Sep 2013
    Posts
    8
    thanksfully the DB2 running under ESX that i already create an snapshot when everything goes well. so i decided to go back to state when DB2 working smooth and well and leave the problem behind

    btw thank to all replies

Posting Permissions

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