Results 1 to 10 of 10
  1. #1
    Join Date
    Jun 2003
    Posts
    127

    Unanswered: Unable to accept requests (DB2 Linux)

    I did a 9.7 fp8 root install. After the database was created, SVCENAME,DB2COMM were set and services file updated. The database connects normally on the server. A few commands worked but when I tried to do a get dbm cfg, it threw a SQL1224. ipclean and db2start didn't help. In the FODC_Panic directory, the stack file complained about libdb2osse.so.1 not existing in /usr/lib. After the library was copied from lib64 of the install directory, it worked fine. To make sure that the clients are not going to have problems, I created a loopback. It keeps throwing this message.

    SQL1224N The database manager is not able to accept new requests, has
    terminated all requests in progress, or has terminated the specified request
    because of an error or a forced interrupt. SQLSTATE=55032

    This is on Redhat 6.3. The server has enough memory.
    total used free shared buffers cached
    Mem: 16334816 14254888 2079928 0 345260 11189524
    -/+ buffers/cache: 2720104 13614712
    Swap: 4292600 1416 4291184
    ======
    ulimit is as below:
    core file size (blocks, -c) 0
    data seg size (kbytes, -d) unlimited
    scheduling priority (-e) 0
    file size (blocks, -f) unlimited
    pending signals (-i) 127463
    max locked memory (kbytes, -l) 64
    max memory size (kbytes, -m) unlimited
    open files (-n) 65536
    pipe size (512 bytes, -p) 8
    POSIX message queues (bytes, -q) 819200
    real-time priority (-r) 0
    stack size (kbytes, -s) 32768
    cpu time (seconds, -t) unlimited
    max user processes (-u) 1024
    virtual memory (kbytes, -v) unlimited
    file locks (-x) unlimited
    ======
    The loopback database name is different from the local db name
    ======
    netstat shows the port being used by db2
    ======
    When I tried to uncatalog the loopback database, it throws
    SQL1042C An unexpected system error occurred. SQLSTATE=58004
    ======
    db2 log shows
    ADM7519W DB2 could not allocate an agent. The SQLCODE is "-1225".


    Any ideas?

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    "SQL1225N. The request failed because an operating system process, thread, or swap space limit was reached."

    Check db2diag.log to find out what resource is exhausted.
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Does the entry for the real db exist in the system db directory or just the loopback entry?

  4. #4
    Join Date
    Jun 2003
    Posts
    127
    Both the local db directory listing and loop back exist.
    =====Regarding the db2diag.log

    2013-06-18-12.14.18.700328-240 I1E1617 LEVEL: Event
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
    START : New Diagnostic Log file
    DATA #1 : Build Level, 152 bytes
    Instance "lcwzrstg" uses "64" bits and DB2 code release "SQL09078"
    with level identifier "08090107".
    Informational tokens are "DB2 v9.7.0.8", "s130316", "IP23433", Fix Pack "8".
    DATA #2 : System Info, 440 bytes
    System: Linux bnlvwsrwdb.labcorp.com 6 2 x86_64
    CPU: total:2 online:2 Cores per socket:4294967295 Threading degree per core:1
    Physical Memory(MB): total:15952 free:5337
    Virtual Memory(MB): total:20144 free:9511
    Swap Memory(MB): total:4192 free:4174
    Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:31896
    msgNumberOfHeaders:65536 msgMaxQueueSize:65536
    msgMaxSegmentSize:16 shmMax:68719476736 shmMin:1 shmIDs:4096
    shmSegments:4096 semMap:256000 semIDs:4096 semNum:256000
    semUndo:256000 semNumPerID:250 semOps:32 semUndoSize:20
    semMaxVal:32767 semAdjustOnExit:32767
    Cur cpu time limit (seconds) = 0xFFFFFFFF
    Cur file size limit (bytes) = 0xFFFFFFFF
    Cur data size (bytes) = 0xFFFFFFFF
    Cur stack size (bytes) = 0x02000000
    Cur core size (bytes) = 0xFFFFFFFF
    Cur memory size (bytes) = 0xFFFFFFFF
    nofiles (descriptors) = 0x0000FFFE

    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)

    2013-06-18-12.14.18.700278-240 E1619E398 LEVEL: Error (OS)
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, oper system services, sqloSpawnEDU, probe:80
    MESSAGE : ZRC=0x8300000B=-2097151989
    CALLED : OS, -, pthread_create OSERR: EAGAIN (11)

    2013-06-18-12.14.18.701476-240 I2018E327 LEVEL: Severe
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, global services, sqzEDUObj:tartEDU, probe:10
    RETCODE : ZRC=0x8300000B=-2097151989

    2013-06-18-12.14.18.701532-240 I2346E329 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeBsuEdu:tartEDU, probe:96
    RETCODE : ZRC=0x8300000B=-2097151989

    2013-06-18-12.14.18.701583-240 I2676E368 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeAgent::startAgent, probe:2323
    RETCODE : ZRC=0x8300000B=-2097151989
    DATA #1 : signed integer, 4 bytes
    1

    2013-06-18-12.14.18.701642-240 I3045E343 LEVEL: Severe
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeAgentServices::RequestAgentForAppl, pr
    obe:130
    RETCODE : ZRC=0xFFFFFB37=-1225

    2013-06-18-12.14.18.701702-240 I3389E457 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeAgentServices::RequestAgentForAppl, pr
    obe:1620
    MESSAGE : Error getting an agent. Return code =
    DATA #1 : Hexdump, 4 bytes
    0x00007FFFEB3FB798 : 37FB FFFF 7...

    2013-06-18-12.14.18.701746-240 I3847E350 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeAgentServices::RequestAgent, probe:70
    MESSAGE : Agent not allocated, sqlcode = -1225

    2013-06-18-12.14.18.701787-240 E4198E384 LEVEL: Warning
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, base sys utilities, sqeAgentServices::RequestAgent, probe:100
    MESSAGE : ADM7519W DB2 could not allocate an agent. The SQLCODE is "-1225".

    2013-06-18-12.14.18.701990-240 E4583E471 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
    MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.
    A possible cause is that the maximum number of agents has been
    exceeded.

    2013-06-18-12.14.18.702143-240 I5055E436 LEVEL: Error
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
    MESSAGE : Return code from sqleGetAgent =
    DATA #1 : Hexdump, 4 bytes
    0x00007FFFEB3FDB7C : 37FB FFFF 7...
    =======
    Information log has:

    2013-06-18-12.14.18.701872 Instance:lcwzrstg Node:000
    PID:24163(db2tcpcm) TID:3946833664 Appid:none
    base sys utilities sqeAgentServices::RequestAgent Probe:100

    ADM7519W DB2 could not allocate an agent. The SQLCODE is "-1225".

    2013-06-18-12.14.18.702054 Instance:lcwzrstg Node:000
    PID:24163(db2tcpcm) TID:3946833664 Appid:none
    common communication sqlcctcpconnmgr_child Probe:125

    ADM7009E An error was encountered in the "TCPIP" protocol support. A possible
    cause is that the maximum number of agents has been exceeded.

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by Kota View Post
    2013-06-18-12.14.18.700278-240 E1619E398 LEVEL: Error (OS)
    PID : 24163 TID : 140737140221696PROC : db2sysc
    INSTANCE: lcwzrstg NODE : 000
    EDUID : 15 EDUNAME: db2tcpcm
    FUNCTION: DB2 UDB, oper system services, sqloSpawnEDU, probe:80
    MESSAGE : ZRC=0x8300000B=-2097151989
    CALLED : OS, -, pthread_create OSERR: EAGAIN (11)

    From http://linux.die.net/man/3/pthread_create:

    The pthread_create() function starts a new thread in the calling process.
    ....
    EAGAIN
    Insufficient resources to create another thread, or a system-imposed limit on the number of threads was encountered. The latter case may occur in two ways: the RLIMIT_NPROC soft resource limit (set via setrlimit(2)), which limits the number of process for a real user ID, was reached; or the kernel's system-wide limit on the number of threads, /proc/sys/kernel/threads-max, was reached.


    Also, IBM ANR9999D pkBeginNamedThread(xxxx) Thread<xx>: Thread creation failed; rc=11 - United States


    max user processes = 1024 on your server. How many processes does ps -ef | grep lcwzrstg | wc -l show?

  6. #6
    Join Date
    Jun 2003
    Posts
    127
    Thanks. I will check and let you know.
    Machine reboot didn't help either.

  7. #7
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    This could also happen if something else is listening on the same port as what you configured for DB2.
    ---
    "It does not work" is not a valid problem statement.

  8. #8
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    n_i, Shouldn't db2start give a warning/error if the port db2 is configured to listen on is in use by something else?

  9. #9
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by db2girl View Post
    n_i, Shouldn't db2start give a warning/error if the port db2 is configured to listen on is in use by something else?
    It would but the instance would start.
    ---
    "It does not work" is not a valid problem statement.

  10. #10
    Join Date
    Jun 2003
    Posts
    127
    I already checked that db2 was using the port. There was no message when starting db2. We resolved the problem after rebooting and recataloging. The same port is being used.

Posting Permissions

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