SQL0723N An error occurred in a triggered SQL statement in trigger "DB2ADMIN.TRG_MQ_

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rooney10
    New Member
    • Dec 2013
    • 1

    SQL0723N An error occurred in a triggered SQL statement in trigger "DB2ADMIN.TRG_MQ_

    I am having db2 9.5 with no fix packs on AIX 6
    When i am firing the below procedure getting error ,basically we are trying to approve 305 files in this query if try to approve a single file it works.
    Request your help .

    db2 => call "DB2ADMIN"."PUT _FILE_STATUS" ( 49023, "DB2ADMIN".GET_ LKPID('FILE_APP ROVED'), 'shr6323', '')
    SQL0723N An error occurred in a triggered SQL statement in trigger
    "DB2ADMIN.TRG_M Q_PUT". Information returned for the error includes SQLCODE
    "-1131", SQLSTATE "38503" and message tokens "-2097151964|*|*| *|*||SEMAPHORE
    WAIT|". SQLSTATE=09000


    Also when i fire this query , a trap file is getting generated in diagpath and in the db2diag.log it shows only "marking fmp process as unstable " message

    $ head -50 9764984.2314.00 0.app_trap.txt

    <?xml version="1.0" encoding="ISO-8859-1"?>
    <?xml-stylesheet href="http://raspd.torolab.i bm.com/db2trapfile.xsl " type="text/xsl"?>
    <DB2TrapFile version="1.0">
    *************** *************** *************
    * *
    * DB2 USERS : *
    * ----------- *
    * A db2fmp thread terminated abnormally. *
    * This may have been caused by a prog- *
    * ramming error in the routine it was *
    * executing. A stack trace-back follows. *
    * The process remains active. *
    * *
    *************** *************** *************
    <Trap>
    <Header>
    DB2 build information: DB2 v9.5.0.0 s071001 SQL09050
    timestamp: 2013-12-10-10.46.46.469957
    instance name: db2inst1.000
    EDU name : db2fmp (Java) 0
    EDU ID : 2314
    Signal #11
    uname: S:AIX R:1 V:6 M:00F66EE74C00 N:DBServerDR
    process id: 9764984
    thread id : 2314 (0x90A)
    kthread id : 26148905
    </Header>
    <SignalDetail s>
    <Siginfo_t length="64">
    0000000B 00000000 00000033 00000000
    00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000
    </Siginfo_t>
    Signal #11 (SIGSEGV): si_addr is 0x0000000000000 000, si_code is 0x00000033 (SEGV_ACCERR:In valid permissions for mapped object.)
    </SignalDetails>
    <ResourceLimits >
    Data seg top [sbrk(0)] = 0x000000011239F 440
    Cur data size (bytes) = 0x7FFFFFFFFFFFF FFF
    Cur stack size (bytes) = 0x0000000100000 000
    Cur core size (bytes) = 0x00000000FFFFF FFF
    </ResourceLimits>
    <Registers>
    IAR: 0900000008925E3 0 MSR: A00000000000D03 2 LR: 000000011020E97 C
    CTR: 0900000008925E3 0 XER: E00FFFFF FPSCR: 82020000
    CR: 5342109B
    GPR[00]: 090000000890FEB 8 GPR[01]: 0000000111CBA3A 0 GPR[02]: 07000000000C997 0
    GPR[03]: 000000000000000 B GPR[04]: 000000000000000 0 GPR[05]: 090000000890FEB 8
    GPR[06]: 0000000111AB539 9 GPR[07]: 000000000000000 8 GPR[08]: 0000000111CBFF0 0
    GPR[09]: 000000001336000 0 GPR[10]: 0000000111520F9 8 GPR[11]: 0900000008925E3 0
    $
  • Anas Mosaad
    New Member
    • Jan 2013
    • 185

    #2
    Please try to open a PMR with this issue.

    Comment

    Working...