Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2005
    Location
    Bangalore,India
    Posts
    39

    Question Unanswered: Urgent:SQL0444N error with Reason Code 9

    Environment: UDB V8.2(Fixpack 8) on AIX.Instance uses 32 bits.

    In one of our applications,we are getting the below error.

    Message:[IBM][CLI Driver][DB2/6000] SQL0444N Routine "*ROPTABLE" (specific name "SQL061101145822817") is implemented with code in library or path ".../sqllib/bin/routine/db2pvm", function "pvm_entry" which cannot be accessed. Reason code: "9".

    Above error stats that it doesn't have enough memory resources.

    RC: 9 :- There was insufficient memory to resolve the function name "<function-code-id>" in the library identified in "<library-or-path>". Contact the routine creator or your database administrator to make sure the library containing the function was correctly linked. The system configuration may need to be changed to make more memory available to DB2 Server.

    My doubt is Can we set any parameters from database end like PCKCACHESZ and CATALOGCACHE_SZ in resolving the above issue. Else what is the workaround for this issue.

    FYI..entry in the diag.log,

    2006-11-06-22.50.48.139745-420 E39693789C728 LEVEL: Error (OS)
    PID : 1409224 TID : 1 PROC : db2agent (PMMDB01I) 0
    INSTANCE: pdid432 NODE : 000 DB : PMMDB01I
    APPHDL : 0-68 APPID: P4AB1D14.E25A.0A6787055051
    FUNCTION: DB2 UDB, oper system services, sqloLoadModule, probe:130
    CALLED : OS, -, dlopen OSERR: ENOEXEC (8)
    RETCODE : ECF=0x90000044=-1879048124=ECF_LIB_ENOEXEC
    ENOEXEC
    MESSAGE : Attempt to load specified library failed.DATA #1 : Library name or path, 38 bytes
    /db2/pdid432/sqllib/bin/routine/db2pvm
    DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
    2
    DATA #3 : String, 16 bytes
    Not enough space

    Can you please advise on this issue.
    Thanks in advance,

  2. #2
    Join Date
    Jul 2002
    Posts
    48
    check whether you have sufficient virtual memory in your box. If not try to check the buffepool sizes if you have allocated more. That can be derived from bufferpool hit ratio.

    Whether this problem is happening everytime you execute the procedure or whenver you have problem in virtual memory?

    Thanks
    Nagesh

  3. #3
    Join Date
    Feb 2005
    Location
    Bangalore,India
    Posts
    39

    Question

    Thanks Nagesh,
    Please see the o/p of Virtual memeory.
    /db2/pdid432>vmstat
    System Configuration: lcpu=3 mem=12544MB
    kthr memory page faults cpu
    ----- ----------- ------------------------ ------------ -----------
    r b avm fre re pi po fr sr cy in sy cs us sy id wa
    3 1 596366 1505726 0 0 0 512 1746 0 2046 9787 6500 18 10 66 7

    We have enough space(1505726 4K pages) in the virtual memory.Also we have only one bufferpool(using default one) which using 1000 4K pages and it has less bufferpool hit ratio.

    I believe we have enough memory.We are not receiving this error continuously..
    As a temporary fix,we are restarting the DB and it is working fine.Can you please suggest for any permanent fix??

    Thanks in advance,
    Nagaraj

  4. #4
    Join Date
    Jul 2002
    Posts
    48
    When ever it fails execute the db2mtrk command. Then check for package cache hit ratio.

    How may stored procedures you have and what is average size of a stored procedure

    Thanks

  5. #5
    Join Date
    Feb 2005
    Location
    Bangalore,India
    Posts
    39

    Exclamation

    Thanks Nagesh,
    Your information will be greatly helpful in fixing this issue.

    We have total 950 procedures in this database.I am not sure how to find the size(and average size) of the SP's.Can you please advise?? Also how this info will influence my issue?

    Thanks,
    Nagaraj Buchi

  6. #6
    Join Date
    Jul 2002
    Posts
    48
    In that case increase the package cache to 4096 roughly. If this not solving try for more.

    Thanks
    Nagesh

  7. #7
    Join Date
    Apr 2003
    Posts
    2

    Possible solution...

    We had this same issue today. The resolution was to look at the ulimit for the instance id and make sure that the data + stack <= 256MB.

    On our instance, data + stack = 272MB and we were receiving these errors as DB2 requested more that the 256MB limit. This was on AIX 5.2 running db2 fp11 32-bit.

    Here's a link to a webpage that describes the ulimit settings that are required.

    http://www-1.ibm.com/support/docview...id=swg21175377

    If your ulimit is not set as such, make the ulimit changes, START A NEW TELNET SESSION (very important so that you get the new ulimit settings) and then recycle the db2 instance (stop the app, force all remaining connections, db2stop, iplean (very important), db2start)

    Greg Marino
    IBM

Posting Permissions

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