Results 1 to 7 of 7

Thread: Das - Sql4401c

  1. #1
    Join Date
    Sep 2003
    Posts
    84

    Unanswered: Das - Sql4401c

    We are on UDB V8.1.0 for AIX. When we try to start the DAS it returns SQL4401C.

    The db2dasdiag.log contains the following :-

    2004-03-31-19.15.50.508097 pid:67364 tid:1 level:2
    DB2 tools - DB2 administration server - rrm_main() probe:70
    data #1 (4 bytes)
    -8050
    Anyone knows what the solution might be ?

  2. #2
    Join Date
    Jan 2004
    Location
    Canada
    Posts
    12

    Re: Das - Sql4401c

    Originally posted by Dipanjan
    We are on UDB V8.1.0 for AIX. When we try to start the DAS it returns SQL4401C.

    The db2dasdiag.log contains the following :-

    2004-03-31-19.15.50.508097 pid:67364 tid:1 level:2
    DB2 tools - DB2 administration server - rrm_main() probe:70
    data #1 (4 bytes)
    -8050
    Anyone knows what the solution might be ?
    Hm.. could be das port conflict. Maybe try specifying a das port using
    db2dasport command.

    To see the current das port setting, do db2dasport -q

    Hope that helps.

  3. #3
    Join Date
    Sep 2003
    Posts
    84
    Unfortunately I couldn't find the db2dasport file. Does it come with DB2 on AIX ?

    I believe the default port for the DAS to run is 523 - correct me if I am wrong. I checked the /etc/services and it does not show 523 being used.
    Is there any other way of checking whether anything is running on port 523 on AIX ?

  4. #4
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    Originally posted by Dipanjan
    Unfortunately I couldn't find the db2dasport file. Does it come with DB2 on AIX ?

    I believe the default port for the DAS to run is 523 - correct me if I am wrong. I checked the /etc/services and it does not show 523 being used.
    Is there any other way of checking whether anything is running on port 523 on AIX ?
    I had a very similar problem, I found that if I did an "UPDATE ADMIN CFG USING SCHED_ENABLE OFF" it starts successfully.

    I didn't pursue it with IBM, as we are at an unsuported Linux kernel right now. There were also some *.trp files generated in the das dump directory, indicating what looks like a jvm issue... Presumably the Scheduler must be Java-based?
    --
    Jonathan Petruk
    DB2 Database Consultant

  5. #5
    Join Date
    Sep 2003
    Posts
    84
    How did you find out that you needed to change the sched_enable variable ?

  6. #6
    Join Date
    Sep 2003
    Posts
    84
    Here's some more info from db2diag.log :-

    2004-04-02-09.28.04.287891 Instance:db2inst1 Node:000
    PID:46154(db2agent (idle) 0) TID:1 Appid:none
    DRDA Application Server sqljsInitAgent Probe:50

    sqljsVerifyAgent rc = 810f 001c ....


    2004-04-02-09.28.04.292501 Instance:db2inst1 Node:000
    PID:46154(db2agent (idle) 0) TID:1 Appid:none
    DRDA Application Server sqljsDrdaAsDriver Probe:10

    DIA8532C An internal processing error has occurred.
    ZRC=0x820A0001

    Can anyone interpret this ?

  7. #7
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    Originally posted by Dipanjan
    How did you find out that you needed to change the sched_enable variable ?
    Honestly it was a fluke... one of the first things they often recommend you do is to do a 'RESET' on your admin cfg, when I did that it started, but when I started putting my settings back it once again broke. That setting proved the one, and further examination suggested that the JVM was having trouble.

    Not sure at all this is what's going on in your case, but just something you might want to try, if you're not planning on using the Scheduler.
    --
    Jonathan Petruk
    DB2 Database Consultant

Posting Permissions

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