Page 1 of 2 12 LastLast
Results 1 to 15 of 24
  1. #1
    Join Date
    Jul 2004
    Posts
    65

    Unanswered: SQL1032N No start database manager command was issued.

    We have DB2 V8.1 installed since March/2004 and we haven't got any problem since then. But since 3 days ago, our applications hang. The error we get is: "SQL1032N No start database manager command was issued. SQLSTATE=57019". We restart the service "manually" by opening Command Center. Doing this DB2 starts, but after a few moments, hangs again with the same error.
    Anybody knows why db2 stops delivering services this way?.
    I have checked db2diag.log and found no information about stopping db2 service or starting db2 service.
    Please help...!!!

  2. #2
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,

    Please specify the operating system type and version and also db2 version + fixpacks.
    Please also read Must Read thread.

    Do you have any fixpacks installed?

    Type "db2level" at DB2 Command Window, to see the fixpacks installed.

    Grofaty
    Last edited by grofaty; 07-19-04 at 07:33.

  3. #3
    Join Date
    Jul 2004
    Posts
    65
    Grofaty:
    Sorry about the little information I provided. Here is:
    DB2Level: DB2 v8.1.0.36", "s021023", "", FixPak "0".
    Platform : Windows 2000 Server.

    Here is part of db2diag.log for that hour.

    2004-07-17-14.02.15.468000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    database monitor sqm.evmgr::log_ev_err Probe:1 Database:BDGEST

    DiagData
    0c00 0d84 ...„

    2004-07-17-14.02.15.687000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:1 Database:BDGEST

    Error in agent servicing application with coor_node:0000 ..

    2004-07-17-14.02.15.890000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:2 Database:BDGEST

    Error in agent servicing application with coor_agent_index:7e01 ~.

    2004-07-17-14.02.16.078000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:3 Database:BDGEST

    Error in agent servicing application with CLIENT PID:3134 3936 1496

    2004-07-17-14.02.16.187000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:4 Database:BDGEST

    Error in agent servicing application with INBOUND APPLICATION ID:2a4c 4f43 414c 2e44 4232 2e30 3042 4234 *LOCAL.DB2.00BB4
    3731 3830 3231 35 7180215

    2004-07-17-14.02.16.281000 Instance:DB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:5 Database:BDGEST


    Hope this is useful
    Thanks
    Last edited by francis01; 07-19-04 at 11:47.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Looks like an instance crash... I guess you should install the latest fixpack (is it fp6 now?) and, if the problem continues, contact IBM support. You can try to contact IBM right away but they won't talk to you until you're at the latest fixpack level anyway :-)

  5. #5
    Join Date
    Sep 2003
    Location
    canada
    Posts
    230
    Quote Originally Posted by francis01
    Grofaty:
    Sorry about the little information I provided. Here is:
    DB2Level: DB2 v8.1.0.36", "s021023", "", FixPak "0".
    Platform : Windows 2000 Server.

    Here is part of db2diag.log for that hour.

    2004-07-17-14.02.15.468000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    database monitor sqm.evmgr::log_ev_err Probe:1 Database:BDGEST

    DiagData
    0c00 0d84 ...„

    2004-07-17-14.02.15.687000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:1 Database:BDGEST

    Error in agent servicing application with coor_node:0000 ..

    2004-07-17-14.02.15.890000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:2 Database:BDGEST

    Error in agent servicing application with coor_agent_index:7e01 ~.

    2004-07-17-14.02.16.078000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:3 Database:BDGEST

    Error in agent servicing application with CLIENT PID:3134 3936 1496

    2004-07-17-14.02.16.187000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:4 Database:BDGEST

    Error in agent servicing application with INBOUND APPLICATION ID:2a4c 4f43 414c 2e44 4232 2e30 3042 4234 *LOCAL.DB2.00BB4
    3731 3830 3231 35 7180215

    2004-07-17-14.02.16.281000 InstanceB2 Node:000
    PID:2616(db2syscs.exe) TID:1576 Appid:*LOCAL.DB2.00BB47180215
    base sys utilities sqleagnt_sigsegvh Probe:5 Database:BDGEST


    Hope this is useful
    Thanks
    Hanging instance is a bug in db2 v8 at early fixpacks (2 or 3 , I do not recall) please install the latest fixpack(6) hopefuly will be OK.

  6. #6
    Join Date
    Jul 2004
    Posts
    65
    Hi:
    I have a question about Fixes:
    ¿Are they cumulatives?, i.e. If I install Fixpack 6...do I need FP5 and FP4 and FP3...in order to have an "updated" db2 environment.?
    Thanks.

  7. #7
    Join Date
    Apr 2004
    Location
    Inside Intel
    Posts
    165

    Talking

    They are cumulative. No Need to install prior fixpaks to reach the latest level.

    Newbie

  8. #8
    Join Date
    Jul 2004
    Posts
    65
    OK Thanks Dsusendran:
    Please, one more queston:
    Are downloadable files language-specific?. I read the readme file from FP6. and found no information about language. So my question is: Do I need to download ESE FP6 and will be useful for Spanish too?.

    Thanks in advance...

  9. #9
    Join Date
    Apr 2004
    Location
    Inside Intel
    Posts
    165

    Talking

    Yes. Fixpaks are language and product(DB2 edition) specific. Please go to the following link to download the fixpak. Choose language / DB2 Edition etc..

    http://www-306.ibm.com/cgi-bin/db2ww...oad.d2w/report

    Newbie

  10. #10
    Join Date
    Jul 2004
    Posts
    65
    Thanks:

    Looking at the address, I have found two choices of FixPack:
    1.Windows 95, 98, NT4.0, ME, 2000, 2003 (Fix Pack 4 or later) and XP (32-bit)
    2.Windows 95, 98, NT4.0, ME, 2000, 2003 (Fix Pack 4 or later) and XP (64-bit)
    I found no Language specific for these two FP,
    and... 32-bit and 64-bit on what it depends ¿?.

    Thanks a lot.

  11. #11
    Join Date
    Jul 2004
    Posts
    65
    ... 32-bit and 64-bit on what it depends ¿?. Wich one should I choose.?

  12. #12
    Join Date
    Jan 2003
    Posts
    1,605
    Hi francis01,

    32 or 64 bit
    You use windows 2000 which is 32-bin. Only windows 2003 is 64 bit. There are also two versions of windows xp (32 and 64 bit), but this is not important to you. You use windows 2000 so use fixpack for 32-bin!!!


    Spanish

    Quote Originally Posted by francis01
    Do I need to download ESE FP6 and will be useful for Spanish too?
    On page for version 7 fixpacks there is a note:
    Code:
    "NLV (National Language Version) FixPaks are used for all non-English versions of DB2 on OS/2 and Windows platforms.
    If you are using an English version of DB2 on an OS/2 or Windows platform, please select an English FixPak.
    If you are using a non-English version of DB2 on an OS/2 or Windows platform, please select an NLV FixPak.
    All other platforms include English and non-English versions in the same FixPak."
    But there is no note on version 8 fixpacks page!!! Does anybody know if there is only one fixpack for version 8 available for all languages?

    Hope this helps,
    Grofaty

  13. #13
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Tips

    Hi,

    What I suggest is you apply fixpack 4a and proceed, don't apply fix pack 6 as of now wait for sometime till people report some issues maybe a week or two. I am sure you will run into problems if you apply it now.

    However once you apply fixpack please increase the following parametes AGENT_STACK_SZ and statement heap sizes coz if the parameters are bare minimal they cause the instance to crash whenever a long or heavy sql is run.
    HTH

    Nitin

    Ask the experienced rather than the learned

  14. #14
    Join Date
    Jan 2004
    Location
    Tallahassee, FL, USA
    Posts
    96
    what is your os


    before restarting the instance, clean all hangig threads.

    if it is unix

    ps -ef | grep instanceownerid

    kill -9 pid

    also check

    ipcs | grep instanceownerid

    clean all ques & semospgeres

    by using

    ipcrm -m pid
    ipcrm -q pid

    clean all , then

    issue db2start

    if it is NT , go to services db2 services, then restart

    Hope it may help, if any questions or info, let me know


    Thank you

    Lekharaju Ennam

  15. #15
    Join Date
    Jul 2004
    Posts
    65
    HI Nitingm:
    So you say FP4a is the last one known as best. ¿Am I Right?.

    Hi Lekharaju Ennam:
    My S.O. is Windows 2000 Server (32-bit). We already restart the service "manually" (as you suggest) but the problem is that we're doing that 6 or 7 times a day. We think that is anormal. If there is another thing you may suggest, please let me know. One solution I get from people of this forums is go to FP4a.Which is ok, but I like to know some other solutions too.
    Thanks...

Posting Permissions

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