Modify stmt leads dump (urgent)

PERFORM get_customer TABLES itab_futureorders.
FORM get_customer TABLES p_itab STRUCTURE itab_orders .
  DATA: wa_itab LIKE LINE OF itab_orders.
  SELECT avbeln aparvw
         b~name1
    INTO TABLE itab_customer
    FROM vbpa AS a
    INNER JOIN kna1 AS b ON akunnr = bkunnr
    FOR ALL ENTRIES IN p_itab
    WHERE vbeln EQ p_itab-soord
    AND parvw EQ 'ZE'.
  IF sy-subrc EQ 0.
    LOOP AT itab_customer INTO wa_customer.
      READ TABLE  p_itab INTO wa_itab
      WITH KEY soord = wa_customer-vbeln.
      IF sy-subrc EQ 0.
        CLEAR p_itab-name1.
        p_itab-name1 = wa_customer-name1.
      ELSE.
        CLEAR p_itab-name1.
      ENDIF.
      MODIFY p_itab.
      ENDLOOP.
  ENDIF.
ENDFORM.                    " get_customer
I am getting short dump while exec the modify statement. Please let me know the error in this.
Regards,
Cheritha

Hi,
Check out the errors.
PERFORM get_customer TABLES itab_futureorders.
FORM get_customer TABLES p_itab STRUCTURE itab_orders .
DATA: wa_itab LIKE LINE OF itab_orders.
SELECT avbeln aparvw
b~name1
INTO TABLE itab_customer
FROM vbpa AS a
INNER JOIN kna1 AS b ON akunnr = bkunnr
FOR ALL ENTRIES IN p_itab
WHERE vbeln EQ p_itab-soord
AND parvw EQ 'ZE'.
IF sy-subrc EQ 0.
LOOP AT itab_customer INTO wa_customer.
READ TABLE p_itab INTO wa_itab
WITH KEY soord = wa_customer-vbeln.
IF sy-subrc EQ 0.
CLEAR p_itab-name1.
" commentedp_itab-name1 = wa_customer-name1.
wa_itab-name1 = wa_customer-name1.
ELSE.
CLEAR wa_itab-name1.
ENDIF.
MODIFY p_itab from wa_itab..
ENDLOOP.
ENDIF.
ENDFORM. " get_customer
or u can use this logic.
data: lv_ind type i.
loop at p_itab into wa_itab.
lv_ind = sy-tabix.
read table itab_customer into wa_customer
  with key vbeln = wa_itab-soord.
if sy-subrc = 0.
  wa_itab-name1 = wa_customer-name1.
  modify p_itab from wa_itab index lv_ind
            transporting name1.
endif.
clear wa_itab.
ENDLOOP.
regards,
Santosh Thorat

Similar Messages

  • HOW TO TRUNCATE LEADING ZEROS  [ URGENT ]

    A PROGRAM TO GET THE LENGTH OF THE SRVPOS [ SERVICE NUMBER]
    BUT IN OUTPUT IT IS GIVING 12 LEADING ZEROS WHAT SHALL I DO TO REMOVE LEADING ZEROS AND TO GET THE LENGTH OF  THE SRVPOS [ SERVICE NUMBER] AFTER REMOVING LEADING ZEROS
    TABLES: ESLL.
    DATA: BEGIN OF IT OCCURS 0,
          SRVPOS LIKE ESLL-SRVPOS,
          END OF IT.
    DATA:LEN TYPE I VALUE 0,
         IT1 TYPE I,
         IT2 TYPE C VALUE 0,
         N(15) VALUE'1000000000000'.
    SELECT SRVPOS INTO IT FROM ESLL .
           IT1 = IT MOD N.
           IT2 = IT1.
           LEN = STRLEN( IT2 ).
           WRITE: / LEN,IT2.
    ENDSELECT.

    Hi Shailendra
    We can use SHIFT LEFT command in this case.
    Eg: SHIFT LEFT <var> DELETING LEADING '0'.
    or FM: CONVERSION_EXIT_ALPHA_INPUT
    data: var(10) type c value '0000000123'.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
      EXPORTING
        INPUT         = var
    IMPORTING
       OUTPUT        = var.
    Kind Regards
    Eswar
    Message was edited by:
            Eswar Rao Boddeti
    Message was edited by:
            Eswar Rao Boddeti

  • Hai friends after read,how to write the modify stmt

    READ TABLE IT_makt into wa_makt  with key matnr = wa_ekpo-matnr.

    hi check this...
    types: begin of ttab ,
          vbeln(10) type c ,
          vkorg(4)  type c,
          dele(4)   type c,
          end of ttab ,
        begin of ttab1 ,
         vbeln(10) type c,
         dele(4)   type c,
         end of ttab1 .
    data: itab type table of ttab  with header line,
          itab1 type table of ttab1  with header line,
    wa like line of itab ,
    wa1 like line of itab1 .
    itab-vbeln = '0000000001'.
    itab-vkorg = '1000'.
    itab-dele  = 'DEL'.
    append itab .
    itab-vbeln = '0000000002'.
    itab-vkorg = '1000'.
    itab-dele  = 'DEL'.
    append itab .
    itab-vbeln = '0000000003'.
    itab-vkorg = '1000'.
    itab-dele  = 'DEL'.
    append itab .
    itab1-vbeln = '0000000001'.
    itab1-dele  = 'TST'.
    append itab1 .
    itab1-vbeln = '0000000002'.
    itab1-dele  = 'GRE'.
    append itab1 .
    sort itab by  vbeln.
    sort itab1 by vbeln.
    loop at itab into wa.
    data:v_index type sy-index .
    v_index = sy-tabix.
    read table itab1  into wa1 with key vbeln = wa+0(10).
    wa14(4) = wa110(4).
    modify  itab index v_index from wa   .
    endloop.
    loop at itab.
    write:/ itab-vbeln,itab-vkorg,itab-dele .
    endloop.

  • Restrict user not to modify the lead when status is CLOSED

    Hi,
    Is it possible to configure the system not to allow any modifications to the lead once the status is set to CLOSED (one of the user status)?
    Any input is appreciated.
    Regards,
    Venu.

    Hi,
    This is little interesting!
    Now I’m not able to set the REASON though we haven’t saved the lead
    Initially problem didn't get solved as suggested. i.e., Business Transaction Control -> No Change Allowed (Set Influence to Allowed)
    I don't know why?
    But i'm able to solve by setting LNCH (No Change Allowed) for status Closed in “User Status Profile” (last column in the table i.e., Trans).
    But now because of these settings as soon as i change the lead status to CLOSED before setting a reason it self system is internally making the lead 'transferred' and hence not saving the REASON.
    <b>How to configure the lead in such a way that: When i set the lead status CLOSED, i should be able to set the REASON for the corresponding status and should be able to save now. From next time onwards system should not allow user to edit the lead as the status is CLOSED</b>.
    Please suggest whether it’s possible with configuration. <b><i>If not then i want to know why SAP reverting back the changes we are doing for lead "after setting status to CLOSED and before clicking on SAVE"</i></b>.
    Regards,
    Venu.

  • Modified control loop.vi URGENT!!!!

    je souhaite utiliser le "modified PID control loop.vi" pour avoir deux entrées acquisition distinctes et une seule sortie output à gérer.dois je simplement dupliquer ce vi ? Dois je imbriquer les 2 boucles dans une seule ?
    merci si vous pouvez me fournir un vi adapté car je débute avec labview."

    Bonjour,
    De quel exemple parlez-vous? Pouvez-vous le poster ou me dire où le trouver?
    Merci.
    Matthieu Gourssies
    National Instruments France

  • Modified CRBO lead to serious errors

    Hi Guys,
    I am new to labview and I was playing around with labview file and accidently changed the CRBO for control relay output block to a pushbutton,now I cannot/ dont know how to revert it back.
    Now Labview is showing many errors,like "subVI" not executable,polymorphic sub VI is broken.I have no cluse what these means.
    I am using labview 2013.
    I am using labview 2013 as a dnp3 master to some sel relays.
    I made this dnp3 file by modifing the example dnp files form NI.
    Pls help me get this setting back.I have also attached an image regarding the same and also the labview file.
    Do I have to reinstall Laview completly to get the old settings back.I am quite sure the files I made are working fine because I had checked it before trying to modify the CRBO(trying  to make it look simple)
    Please Help mE
    Leon Koshy
    Attachments:
    crbo changed.jpg ‏136 KB
    Master_AI_vol_freq_trialLLOP.vi ‏45 KB
    plethora of errors,dnp3 master blocks not working.png ‏262 KB

    Hi Leon,
    You may have modified the typedef of the terminal CROB.
    Reinstalling DNP3 alone will cure the problem, I believe. You don't have to reinstall LabVIEW.
    The VI you attached opens with no error. It's executable.

  • Oc4j902 dump.Urgent!!

    I have encountered one problem.
    We use oc4j 902 on IBM AIX enviroment.use the command :
    java -Ddatasource.verbose=true -Dtransaction.log=true -DGCSIZE=10 -Xms400m -Xmx750m -jar oc4j.jar
    Running one day, the system will dump.
    The console output just like,
    SIGILL 4(*) illegal instruction(not reset when caught)
    Si_signo[4]:sigill*) illegal instruction(not reset
    si_errno [0]:Error 0
    si_code [30]LL_ILLOPC[addr:0*0]
    stackpointer=6414de98
    writing java dump to /oc4j/j2ee/home/javacore4226.1068446881
    jdbc:oracle:thin:@192.168.1.245:1521:cqec opened connection
    ./start_oc4j[2]:4226 Illegal instruction
    How to do it, please help me . Thansk.

    Hi Raghuram,
    STRLEN is a command to get a length of a string. So it might be a case that while passing the data to STRLEN the variable must be other than the character. Just check with the developer for the same.
    Thanks,
    Mandar

  • Dump urgent.

    Hi
    I get this error :-
    In statement
       "STRLEN( obj )..."
    the argument "obj" can only take a character-type data object.
    The termination occurred in the ABAP/4 program "SAPLKKBL " in
    "GEN_FIELD_OUT2".
    The main program was "ZRTUS001_V1 ".
    The termination occurred in line 3914
    of the source code of program "LKKBLF99 " (when calling the editor 39140).
    Please give some suggestions

    Hi Raghuram,
    STRLEN is a command to get a length of a string. So it might be a case that while passing the data to STRLEN the variable must be other than the character. Just check with the developer for the same.
    Thanks,
    Mandar

  • Short dump error report

    What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

    hi please look through this:
    Whenever any transaction or any process is executed it hits an ABAP code.
    If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
    Transaction ST22 is used to check any ABAP Dump within a given duration.
    U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
    you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    sap-basis   sap-basisAll Groups  Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
    SAP Groups > Technical-functional > sap-basis > Message
    About This Group | Invite peers to join this group 
    << Prev thread  < Prev msg  Next msg >  Next thread >> 
    short dump----urgent
    Reply from Keith Lewis on 5/2/2003 3:22:00 AM 
    Good explanation Joy, but it is not only limited to the current day and
    yesterday. If you click on the Selection button you can select previous
    days as well. In fact you can select back to the last 14 days if you are
    running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
    old ABAP dumps every day, possibly further if you run it weekly or
    monthly.
    Cheers
    Keith
    SAP R/3 Support Specialist
    Information Services International
    Tel +44 1664 41 6178 Mobile +44 7887 627818
    E-mail email@removed
    Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
    Dear sreenivas
    If you receive an error message in the R/3 System log (SM21), or if you
    see
    a terminated update in the update service analysis transaction (SM13), or
    DB
    realated error ,check for dumps using the dump analysis transaction
    (transaction ST22), or choose Tools -> Administration -> Monitoring ->
    Dump
    analysis.
    Transaction ST22 enables you to analyze short dumps from the current and
    previous day.
    The dump analysis function shows you:
    What happened
    What you can do
    How to correct the error
    The dump analysis function also provides an error ID and keywords that you
    can use to search in SAPNet, as well as information about:
    The system environment
    Users and transactions
    Transaction ST22 enables you to analyze the following data:
    Date, time, user, client
    Contents of system and data fields
    Contents of internal tables and application tables
    ST22 is a very nice feature in SAP. This is where all the system errors
    and users mistakes showed up. If there is a problem that you cannot
    solve and you contact SAP support, they look at this area to analyze it.
    This gives us lead where to handle the problems.
    Error analysis
    How to correct the error
    System environment
    User, transaction...
    Information on where termination occurred
    Contents of system fields
    Chosen variables
    Active calls / events
    Internal notes
    Active calls in SAP kernel
    List of ABAP programs affected
    List of internal tables
    Directory of application tables (contents)
    Directory of data areas (administration information)
    Directory of data areas (contents)
    ABAP control blocks CONT
    End of runtime analysis
    i think this would be helpful
    regards
    sravani

  • Format tab leader in table of contents

    I have a table of contents that uses tab leaders. There are two levels of header in the table of contents. One is bolded (major headers) and one is not (minor headers). The page numbers are not bold for any entry. For example:
    Major Header.................1
    Minor Header...........2
    Apparently if you make the header text bold, the tab leader is bold too. This means that the major headers have bolded tab leaders, and the minor headers have regular tab leaders. This makes them appear uneven. I would like to use regular, unbolded leaders for all entries, but I don't know how to modify the leader formatting without affecting the header text.

    You can override the heading style setting.
    In the major headers, type a space at the end of the text and before the tab leader begins.
    Select all of the leader and the text/nmber at the end of that line.
    Toggle Bold to Off.
    If your header levels use different type sizes, the leaders will still look different. You can also use the Size control in the format bar to match the size of the leader to that of the minor header.
    Not thoroughly checked. You may find this unstable in use, particularly if the content in this is edited.
    Regards,
    Barry

  • Performance Issue in modifying a ITAB

    Hi SDNs.,
    performance issue in modifying a internal table : code :
    *-Modify LT_DOC with Object list number(OBKNR) from SER03
      LOOP AT LT_SER03_HASH INTO LW_SER03.
        IF ( LW_SER03-OBKNR IS NOT INITIAL ).
          READ TABLE LT_DOC INTO LW_DOC WITH KEY  MBLNR = LW_SER03-MBLNR
                                                  MJAHR = LW_SER03-MJAHR
                                                  ZEILE = LW_SER03-ZEILE BINARY SEARCH.
          IF ( SY-SUBRC = 0 ). " AND ( LW_SER03-OBKNR IS NOT INITIAL ).
            LW_DOC-OBKNR = LW_SER03-OBKNR.
            LW_DOC-DATUM = LW_SER03-DATUM.
            LW_DOC-UZEIT = LW_SER03-UZEIT.
            MODIFY LT_DOC FROM LW_DOC INDEX SY-INDEX TRANSPORTING OBKNR DATUM UZEIT  WHERE MBLNR = LW_SER03-MBLNR AND
                                                                           MJAHR = LW_SER03-MJAHR AND
                                                                           ZEILE = LW_SER03-ZEILE .
          ENDIF.
        ENDIF.
        CLEAR: LW_DOC, LW_SER03.
      ENDLOOP.
    <b>could any one help me out in tuning this code...</b>
    Thank you
    RK S

    hi christain.,
    Thank you for reply.,
    field symbols not working for following case : could you pls check the following code and tel me how can i enhance the same...
    could you pls help me out..
    <b>Note : Without Modify stmt, the corresponding fields in following code are not updating. could any one pls help me out...</b>
      LOOP AT LT_FINAL_HASH1 INTO LW_FINAL_TEMP.
          IF LW_FINAL_TEMP-BWTAR IN R_BWTAR.
            READ TABLE LT_FINAL ASSIGNING <FS_FINAL> WITH KEY
              SERNR = LW_FINAL_TEMP-SERNR BINARY SEARCH.
            TAB_INDEX = SY-TABIX.
            WHILE SY-SUBRC = 0.
              IF <FS_FINAL>-SERNR <> LW_FINAL_TEMP-SERNR.
                SY-SUBRC = 9.
              ELSE.
                IF <FS_FINAL>-BWTAR IN R_BWTAR.
                  <FS_FINAL>-AG_DATE = <FS_FINAL>-BUDAT.
                  <FS_FINAL>-AG_MBLNR = <FS_FINAL>-MBLNR.
                 MODIFY LT_FINAL FROM LW_FINAL
                   TRANSPORTING AG_DATE AG_MBLNR WHERE SERNR EQ LW_FINAL_TEMP-SERNR.
                 CLEAR : LW_FINAL-AG_DATE,
                         LW_FINAL-BUDAT.
                  EXIT.
                ENDIF.
                TAB_INDEX = TAB_INDEX + 1.
                READ TABLE LT_FINAL ASSIGNING <FS_FINAL> INDEX TAB_INDEX.
              ENDIF.
            ENDWHILE.
    endloop.
    Thank you .,
    RK S

  • Workflow for Particular Role(Only) has to qualify the lead.

    Hi all,
    The lead(s) has to be qualified by only one role, and lead(s) should be converted with the other role. How this can be done.
    For example.
    Here "sales & Marketing Manager" has to qualify the lead and no permission to convert.
    Here "admin" has to convert the lead into account and opportunity.
    I tried with using lookup function, not suceeded. need help.
    Regards,
    Ratan

    You could try putting validation on the Lead Status field based on a user's role. E.g.
    IF(UserValue('<Role>') <> 'Sales Manager' AND PRE('<Status>') <>'Qualified' and [Status] = 'Qualified' THEN "ERROR", '')
    The syntax above is far from correct but hopefully enough for you to have a play. The PRE condition here is used to make sure someone is actually modifying a Lead which wasn't previously Qualified otherwise any amendments to existing qualified leads would throw errors. Let me know how you get on, personally I don't like the above as it's likely to cause issues.
    Thanks
    Oli @ Innoveer

  • Can't Drop a table in DB2 UDB on Windows 2003 server Ent EDT

    Previus step:
    Database DB2 ibm for a sap BW production got error in log - cause: no space on disk.
    system mark database as bad.
    system connection with db was restored with sap and ibm support
    I'm in disaster recovery situation,
    we have rebuilded index and table that got problem in db2dart report.
    Now Sap system go up, we have successfully  dumped 29 of 30 tables with db2dart /ddel command, now there is only a table that got problem:
    sapbw2.rsbatchdata
    we can't drop this table.
    We try with this step:
    1) db2dart bw2 /ddel
       (table id)1837     (tablespaceid)10 0 9000000
       we obtain a SQL file
    2) db2dart bw2 /mt
       (table id)1837     (tablespaceid)10 (password that you provide)
    3) db2 drop bw2 sapbw2.rsbatchdata after this command we got a crash database.
    2008-05-29-16.33.59.148000+120 I5094483F478       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : section stmt
    DATA #1 : Hexdump, 29 bytes
    0x000000003806E1F4 : 6472 6F70 2074 6162 6C65 2073 6170 6277    drop table sapbw
    0x000000003806E204 : 322E 5253 4241 5443 4844 4154 41           2.RSBATCHDATA
    2008-05-29-16.33.59.148000+120 I5094963F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section stmt
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095124F174       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: informational text for dump
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095300F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: Unrelocation Needed
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095468F204       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: Section relocated; reltables in global cache inaccessible
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095674F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5095834F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5095995F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096155F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096316F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: shared dynamic ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096483F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: shared dynamic size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096651F169       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic section header
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5096822F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: offset in section
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5096988F153       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: opcode
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097143F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: agg_mode
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097300F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section1
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097457F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: End of dumped section
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.241000+120 I5097627F438       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
    MESSAGE : Context info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for
              additional data.
    2008-05-29-16.33.59.273000+120 I5098067F452       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Private workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.33.59.288000+120 I5098521F451       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Shared workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.33.59.304000+120 I5098974F450       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
    MESSAGE : Package Cache info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000
              for additional data.
    2008-05-29-16.33.59.335000+120 I5099426F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA ASCB ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099594F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA CMNMGR CB ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099767F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** RECEIVE BUFFER ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099940F169       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** SEND BUFFERS ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5100111F174       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** CONNECTION HANDLE ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5100287F172       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA ATTRIBUTES ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.351000+120 I5100461F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** AS UCINTERFACE ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.351000+120 I5100634F468       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error detected"
              DIA8501C A buffer pool logic error has occurred.
    2008-05-29-16.33.59.351000+120 I5101104F331       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    2008-05-29-16.33.59.820000+120 I5101437F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.820000+120 I5101595F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5101753F400       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_AGENT_CB Pointer:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AB0 : 0001 E637 0000 0000                        ...7....
    2008-05-29-16.33.59.835000+120 I5102155F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5102317F398       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_TRAN_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AA0 : 8087 FD0F 0000 0000                        ........
    2008-05-29-16.33.59.835000+120 I5102717F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5102878F397       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_APP_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AA8 : 0083 FD0F 0000 0000                        ........
    2008-05-29-16.33.59.835000+120 I5103277F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5103437F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN PERM CURSORS: >>
    2008-05-29-16.33.59.851000+120 I5103787F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN PERM CURSORS: <<
    2008-05-29-16.33.59.851000+120 I5104134F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN TEMP CURSORS: >>
    2008-05-29-16.33.59.851000+120 I5104484F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN TEMP CURSORS: <<
    2008-05-29-16.33.59.851000+120 I5104831F346       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS:  >>
    2008-05-29-16.33.59.851000+120 I5105179F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
    2008-05-29-16.33.59.851000+120 I5105545F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.851000+120 I5105702F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
    2008-05-29-16.33.59.851000+120 I5106068F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106225F342       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS: <<
    2008-05-29-16.33.59.866000+120 I5106569F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLI_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106725F167       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106894F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5107054F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5107215F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.929000+120 I5107373F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.929000+120 I5107530F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.945000+120 I5107688F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.945000+120 I5107858F373       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : locklist
    DATA #1 : String, 59 bytes
    Check
    t1srv5bw\db2dumpBW2\l57042.000 for additional data.
    2008-05-29-16.33.59.960000+120 I5108233F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108394F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108548F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108708F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108872F412       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEA8 : 0800                                       ..
    2008-05-29-16.33.59.976000+120 I5109286F425       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABECA : 4E55 4C4C 4944 2020                        NULLID 
    2008-05-29-16.33.59.976000+120 I5109713F491       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbname =
    DATA #1 : Hexdump, 18 bytes
    0x00000000056ABEB8 : 4257 3220 2020 2020 2020 2020 2020 2020    BW2            
    0x00000000056ABEC8 : 2020                                        
    2008-05-29-16.33.59.976000+120 I5110206F491       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgname =
    DATA #1 : Hexdump, 18 bytes
    0x00000000056ABEDC : 5351 4C43 3245 3037 2020 2020 2020 2020    SQLC2E07       
    0x00000000056ABEEC : 2020                                        
    2008-05-29-16.33.59.976000+120 I5110699F416       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgcnstkn =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABEEE : 4141 4141 4163 4555                        AAAAAcEU
    2008-05-29-16.33.59.991000+120 I5111117F406       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgsn =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEF6 : CB00                                       ..
    2008-05-29-16.33.59.991000+120 I5111525F496       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pStatementText =
    DATA #1 : Hexdump, 29 bytes
    0x00000000062D0CC0 : 6472 6F70 2074 6162 6C65 2073 6170 6277    drop table sapbw
    0x00000000062D0CD0 : 322E 5253 4241 5443 4844 4154 41           2.RSBATCHDATA
    2008-05-29-16.33.59.991000+120 I5112023F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS APPL CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112183F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED APPL CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112350F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS SP REGISTERS CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112518F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS TRAN CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112678F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED TRAN CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5112845F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS COORD CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113006F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113168F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS INVOCATION CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113334F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS ACTIVE STMT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113501F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: NLSWA:DatabaseApp
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113667F153       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: nlsacb
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5113822F157       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dbNLSAppCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5113981F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: UnicodeNLSAppCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5114145F464       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    MESSAGE : Error -2045771763 when reading LSN 000006BDB601F7A1 from log file
              S0000000.LOG tellMe 0 dpsAcbFlags 0 setSkipOutputBuf 0
    2008-05-29-16.34.00.023000+120 I5114611F468       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    MESSAGE : NOTE: The log state was marked bad by another process, this message
              is not an indication of an error with the logger process
    2008-05-29-16.34.00.523000+120 I5115081F457       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.538000+120 I5115540F459       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptudo, probe:1010
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.538000+120 I5116001F455       LEVEL: Warning
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptudo, probe:4350
    MESSAGE : LSN being undone:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA87A8 : 0000 06BD B601 F7A1                        ........
    2008-05-29-16.34.00.538000+120 I5116458F157       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_TENTRY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116617F166       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116785F155       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116942F154       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5117098F390       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptud1, probe:1880
    MESSAGE : Due to error during UNDO, database will be brought down.
    2008-05-29-16.34.00.570000+120 I5117490F459       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpxrbk, probe:3040
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.570000+120 I5117951F155       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.570000+120 I5118108F154       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.570000+120 I5118264F384       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : cr_error:
    DATA #1 : Hexdump, 4 bytes
    0x00000000056AF4C8 : 0100 0000                                  ....
    2008-05-29-16.34.00.570000+120 I5118650F465       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrrbck_dps, probe:20
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.585000+120 I5119117F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : SQLRL281
    sqlerrd : (1) 0x87020002      (2) 0x00000002      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.00.585000+120 I5119811F418       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, global services, sqlzerdm, probe:40
    DATA #1 : Hexdump, 4 bytes
    0x0000000005AA8B08 : 0D00 1086                                  ....
    2008-05-29-16.34.01.070000+120 I5120231F461       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:40
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.01.070000+120 I5120694F474       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:88
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.01.070000+120 I5121170F435       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:190
    DATA #1 : Hexdump, 4 bytes
    0x0000000005AA8F6C : 0200 0287                                  ....
    2008-05-29-16.34.01.070000+120 I5121607F383       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : UCstate:
    DATA #1 : Hexdump, 4 bytes
    0x00000000056AFA70 : 4200 0004                                  B...
    2008-05-29-16.34.01.070000+120 I5121992F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -984   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : sqlrrbkd
    sqlerrd : (1) 0x8610000D      (2) 0xFFFFFC2C      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.070000+120 I5122686F508       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10
    MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected.  The
              diagnostic data returned is (SRVDGN): "SQLERRP:sqlrrbkd
              SQLCODE:-984".
    2008-05-29-16.34.01.085000+120 I5123196F691       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -984   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : sqlrrbkd
    sqlerrd : (1) 0x8610000D      (2) 0xFFFFFC2C      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.085000+120 I5123889F375       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
    2008-05-29-16.34.01.085000+120 I5124266F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1034   sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLRR09E
    sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0xFFFFFFE2      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.085000+120 I5124960F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.085000+120 I5125114F385       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : CREATOR
    DATA #1 : Hexdump, 8 bytes
    0x0000000037E6D1AE : 4E55 4C4C 4944 2020                        NULLID 
    2008-05-29-16.34.01.085000+120 I5125501F385       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : PACKAGE
    DATA #1 : Hexdump, 8 bytes
    0x0000000037E6D1CC : 5351 4C43 3245 3037                        SQLC2E07
    2008-05-29-16.34.01.101000+120 I5125888F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CREATOR
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126044F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: PACKAGE
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126200F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: REQUEST TYPE
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126361F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: APM COMMON INFO
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126525F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CONTEXT MCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5126685F161       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CONTEXT MEM CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5126848F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: PACKAGE ENTRY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5127010F438       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
    MESSAGE : Context info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for
              additional data.
    2008-05-29-16.34.01.116000+120 I5127450F452       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Private workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.34.01.116000+120 I5127904F451       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Shared workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.34.01.132000+120 I5128357F450       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
    MESSAGE : Package Cache info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000
              for additional data.
    2008-05-29-16.34.01.132000+120 I5128809F376       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
    2008-05-29-16.34.01.132000+120 I5129187F331       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    2008-05-29-16.34.01.601000+120 I5129520F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.601000+120 I5129678F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.601000+120 I5129836F400       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_AGENT_CB Pointer:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8970 : 0001 E637 0000 0000                        ...7....
    2008-05-29-16.34.01.601000+120 I5130238F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5130400F398       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_TRAN_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8960 : 8087 FD0F 0000 0000                        ........
    2008-05-29-16.34.01.616000+120 I5130800F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5130961F397       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_APP_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8968 : 0083 FD0F 0000 0000                        ........
    2008-05-29-16.34.01.616000+120 I5131360F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5131520F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN PERM CURSORS: >>
    2008-05-29-16.34.01.616000+120 I5131870F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN PERM CURSORS: <<
    2008-05-29-16.34.01.632000+120 I5132217F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN TEMP CURSORS: >>
    2008-05-29-16.34.01.632000+120 I5132567F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN TEMP CURSORS: <<
    2008-05-29-16.34.01.632000+120 I5132914F346       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS:  >>
    2008-05-29-16.34.01.632000+120 I5133262F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
    2008-05-29-16.34.01.632000+120 I5133628F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.632000+120 I5133785F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
    2008-05-29-16.34.01.632000+120 I5134151F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134308F342       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS: <<
    2008-05-29-16.34.01.648000+120 I5134652F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLI_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134808F167       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134977F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5135137F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5135298F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135456F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135613F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135771F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.726000+120 I5135941F373       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : locklist
    DATA #1 : String, 59 bytes
    Check
    t1srv5bw\db2dumpBW2\l79922.000 for additional data.
    2008-05-29-16.34.01.741000+120 I5136316F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.741000+120 I5136477F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136631F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136791F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136955F412       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEA8 : 0800                                       ..
    2008-05-29-16.34.01.757000+120 I5137369F425       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABECA : 4E55 4C4C 4944 2020                        NULLID 

    I can't use db2drop because this command crash my db with this table.
    So I must take another way.
    ============================================================
    About DB2 Administration Tools Environment
    ============================================================
    DB2 administration tools level:
    Product identifier           SQL08025
    Level identifier             03060106
    Level                        DB2 v8.1.12.99
    Build level                  s060429
    PTF                          WR21370
    ============================================================
    Java development kit (JDK):
    Level                        IBM Corporation 1.4.2
    ============================================================

  • What's the best way to do many NAT translations for WWW farm?

    Hello all, I hope this finds you in good spirits.
    I have recently upgraded my ASA 5510 to 8.3 code and honestly I am confused on the best and most efficient way to do many nat translations through it.  I have a group of about 100 IP's that need http/https/and sqlnet allowed through for our web farm.
    I have a text file with the real and translated IP addresses and in 8.2 I could simply modify it and dump the thing in and make the NAT rules and access-lists.  Now with the new object based model I am having a hard time wrapping my brain around how to do this using as few lines of code as possible.
    Do I have to create an network object for each and every IP i want to nat through? 
    Thank you for your consideration!

    Were your NATs not present in the pre-upgrade code? If they were, they should have been automatically rebuilt along with the recommended objects.
    If they weren't, you can relatively easily make a little script of spreadsheet with some transforms to go from your text listing to the necessary network objects and new syntax nat rules.
    It's also relatively easy to build them in ASDM and just copy, insert and modify down the list. You can even use the "Add Object" part of the GUI to also add the NAT rules at the same time:

  • BADI for MIGO update - Data not getting saved in table sometimes

    Hi,
    This is regarding automatic update of material document number to our Z Table for Gate entry in MM.
    Steps for Generating  GR throu2019 MIGO:-
    1) the user has to key in the gate entry number and plant,
    2) then after giving i/p values the user has to click the save button,
    3) MIGO number is generated by the system which is updated in gate entry header table.
    For updating the MIGO number BADI is used . But some time the system is not updating the GR number in gate entry header table.
    Can we use COMMIT WORK statement in BADI? Hope its not advisable to use it.
    What else can we do if data is not getting stored in table while updating throu2019 BADI?
    Inside the Method : IF_EX_MB_MIGO_BADI~POST_DOCUMENT the below code is written,
    Instead Of Updating The Gate Entry Item Table Now
    Update The Gate Entry Header Table. Update The
    Value Of The Field MBLNR With Current Document Number
    Generated Updating the header table ZMM_GATE_ENTRY
        SELECT SINGLE *
          FROM ZMM_GATE_ENTRY
          INTO WA_ZMM_GATE_ENTRY
         WHERE GATEENTRYNO EQ GS_EXDATA_HEADER-GATEENTRYNO
           AND WERKS       EQ GS_EXDATA_HEADER-WERKS
           AND GYEAR       EQ GS_EXDATA_HEADER-ENTRY_DATE+0(4).
    Check To Ensure That Once A Gate Entry Number
    Is Associated With A GR It Cannot Be Reused
        IF WA_ZMM_GATE_ENTRY-GR_NUMBER IS INITIAL.
          WA_ZMM_GATE_ENTRY-REFERENCE = GS_EXDATA_HEADER-REFERENCE.
          WA_ZMM_GATE_ENTRY-REFWERKS  = GS_EXDATA_HEADER-WERKS.
          WA_ZMM_GATE_ENTRY-GR_NUMBER = IS_MKPF-MBLNR.
          WA_ZMM_GATE_ENTRY-GR_YEAR   = IS_MKPF-MJAHR.
    MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the workarea
    u201CThe above modify stmt updates data sometimes and does not updates the data sometimes
        ELSE.
          MESSAGE E901(ZMM) WITH GS_EXDATA_HEADER-GATEENTRYNO WA_ZMM_GATE_ENTRY-GR_NUMBER.
        ENDIF.
    Plz suggest some soln?
    Regards,
    P.S.Chitra

    Hi,
    This is regarding automatic update of material document number to our Z Table for Gate entry in MM.
    Steps for Generating  GR throu2019 MIGO:-
    1) the user has to key in the gate entry number and plant,
    2) then after giving i/p values the user has to click the save button,
    3) MIGO number is generated by the system which is updated in gate entry header table.
    For updating the MIGO number BADI is used . But some time the system is not updating the GR number in gate entry header table.
    Can we use COMMIT WORK statement in BADI? Hope its not advisable to use it.
    What else can we do if data is not getting stored in table while updating throu2019 BADI?
    Inside the Method : IF_EX_MB_MIGO_BADI~POST_DOCUMENT the below code is written,
    MODIFY ZMM_GATE_ENTRY FROM WA_ZMM_GATE_ENTRY .u201Dupdating the workarea
    u201CThe above modify stmt in code updates data sometimes and does not updates the data sometimes
    Moderator message: duplicate post locked.
    Edited by: Thomas Zloch on Aug 10, 2010 11:33 AM

Maybe you are looking for

  • Vendor Invoices

    Could you please let me know where can I find the Vendor Invoice details in ECC ? I mean Tables and extractor name . Regards

  • How to render an image (byte array) in a JSP

    I don't know how to solve this: I have a bean 'Details' with a property 'photo' This bean is read in a servlet and put into session scope like this: PhotoDetails Details = getPhotoDetail(some_id); HttpSession session = request.getSession(); session.s

  • Key command for startup from Bootable CD

    I just got off the phone with AppleCare since I am having issues with booting from a CD (Techtool Deluxe). I know that upon restart, I should be able to start from the CD by holding the "C" button down until the Apple logo comes up, but it just goes

  • Album Menu on my iPhone 4

    I downloaded my photos from the phone. After editing them and choosing those I wanted them I put them in a folder to be uploaded to my iphone using the Sync function of iTunes. First I erased all photographs and then I asked the program to sync from

  • Content does not show in InDesign

    Working on a multipage document in InDesign, some pages don't show their content, allthough present. After restarting InDesign sometimes the problem is solved, the content is vissible again. Is this an InDesign problem or a local failure/setting on m