Drop more tables

Hi,
Knows someone how can I drop more table, e.g. all tables that start with A and how can I add two columns to all tables that start with B?
Thank you

You need to write a script for that, using dynamic SQL.
small example:
create or replace procedure my_ddl_proc
(p_tab_name in VARCHAR2)
is
begin
for rec in
(select table_name from user_tables where table_name like UPPER(p_tab_name))
loop
execute immediate 'DROP TABLE '||rec.table_name;
end loop;
end;
Edited by: hoek on Mar 27, 2009 6:23 PM

Similar Messages

  • Ora-00604,ora-01422 error while dropping the table

    Hi gurus,
    I am using Oracle 10g R2 on windows 2000 platform,while dropping the table the following error occured.
    ORA-00604 : error occurred at recursive sql level 1.
    ORA-01422: exact fetch returns more than requested number of rows.
    Need urgent help.
    Thanks in advance

    Is there an AFTER EVENT trigger defined on this database? Can you check that?
    Secondly, was this database migrated from earlier version? I remember having seen this problem on 9i (it was 9.2.0.1 or 9.2.0.2; I can't recall exactly).

  • WHERE clause creating a join for two or more tables

    The CS3 Dreamweaver book says that the WHERE clause can
    create a join for two or more tables. The join was created, but the
    data is repeating. I have searched the web and this forum and have
    not found the answer.
    My Master page filters the recordset by Style No and when a
    customer clicks on a particular style, it sends him to the Detail
    page. All the records are showing from all tables on the detail
    page from the Dynamic List, except they are showing multiple times
    (ex. Size table has 4 sizes and Color table has 2 colors - my Size
    Drop Down list is showing 8 options and my Color Drop Down List is
    showing 8 options) I have a Master Page with a recordset pointing
    to a Detail Page using the same recordset.
    Master page works perfectly.
    Master Recordset SQL:
    SELECT products.itemID, products.category, products.styleno,
    products.name, products.description, products.ourprice,
    products.imageTH, products.image, coloroption.color,
    sizeoption.size
    FROM products, coloroption, sizeoption
    WHERE category = 'chefcoats' AND
    products.styleno=sizeoption.styleno AND
    products.styleno=coloroption.styleno
    GROUP BY products.styleno
    ORDER BY styleno ASC
    The Detail Recordset:
    SELECT products.itemID, products.category, products.styleno,
    products.name, products.description, products.ourprice,
    products.imageTH, products.image, sizeoption.size,
    coloroption.color
    FROM products, sizeoption, coloroption
    WHERE itemID=colname AND products.styleno=sizeoption.styleno
    AND products.styleno=coloroption.styleno
    I tried using the GROUP BY on the detail page, but then it
    only showed one size and color from the dynamic drop down list. I
    tried changing the field name "styleno" in the other tables to be
    unique, however, I was using the table identifer. I tried using the
    JOIN command instead of the WHERE clause and that didn't help
    either.
    On the detail page, the customer is supposed to click on the
    Size box and see sizes XSM - 6XL ONLY ONE TIME. and then be able to
    click on the Color option and see White, Black, Red ONE TIME.
    Is this possible?
    Thank you for giving your time to read this.!
    Evie

    Do you have a link we can look at to see what you are trying
    to do?
    Dave
    "EviePhillips" <[email protected]> wrote in
    message
    news:[email protected]...
    > The CS3 Dreamweaver book says that the WHERE clause can
    create a join for
    two
    > or more tables. The join was created, but the data is
    repeating. I have
    > searched the web and this forum and have not found the
    answer.
    >
    > My Master page filters the recordset by Style No and
    when a customer
    clicks on
    > a particular style, it sends him to the Detail page. All
    the records are
    > showing from all tables on the detail page from the
    Dynamic List, except
    they
    > are showing multiple times (ex. Size table has 4 sizes
    and Color table has
    2
    > colors - my Size Drop Down list is showing 8 options and
    my Color Drop
    Down
    > List is showing 8 options) I have a Master Page with a
    recordset pointing
    to a
    > Detail Page using the same recordset.
    >
    > Master page works perfectly.
    > Master Recordset SQL:
    > SELECT products.itemID, products.category,
    products.styleno,
    products.name,
    > products.description, products.ourprice,
    products.imageTH, products.image,
    > coloroption.color, sizeoption.size
    > FROM products, coloroption, sizeoption
    > WHERE category = 'chefcoats' AND
    products.styleno=sizeoption.styleno AND
    > products.styleno=coloroption.styleno
    > GROUP BY products.styleno
    > ORDER BY styleno ASC
    >
    > The Detail Recordset:
    > SELECT products.itemID, products.category,
    products.styleno,
    products.name,
    > products.description, products.ourprice,
    products.imageTH, products.image,
    > sizeoption.size, coloroption.color
    > FROM products, sizeoption, coloroption
    > WHERE itemID=colname AND
    products.styleno=sizeoption.styleno AND
    > products.styleno=coloroption.styleno
    >
    > I tried using the GROUP BY on the detail page, but then
    it only showed
    one
    > size and color from the dynamic drop down list. I tried
    changing the
    field
    > name "styleno" in the other tables to be unique,
    however, I was using the
    table
    > identifer. I tried using the JOIN command instead of the
    WHERE clause and
    that
    > didn't help either.
    >
    > On the detail page, the customer is supposed to click on
    the Size box and
    see
    > sizes XSM - 6XL ONLY ONE TIME. and then be able to click
    on the Color
    option
    > and see White, Black, Red ONE TIME.
    >
    > Is this possible?
    >
    > Thank you for giving your time to read this.!
    > Evie
    >
    >

  • Can I add more tables into existing Data Modeler

    My Data Modeler has been generated by SQL Developer, it contains 68 tables. Later I would like to add more tables into my current model. Is there any way I can add more tables into my current model without creating a new one from the scratch? Thanks for your help.
    Kevin

    Hi Kevin,
    you can add new tables using File>Import functionality - you can import from database or DDL scripts.
    Working in SQL Developer you can drag tables from SQL Dev browser and drop them on relational diagram. If Ctrl key is pressed while dropping then subordinate tables also will be added to the model.
    Here you can find tutorials http://apex.oracle.com/pls/apex/f?p=44785:2:0:FORCE_QUERY::2,RIR,CIR:P2_TAGS:Data%20Modeler
    Philip

  • Drop temp tables

    how to drop temp tables if i created with same name in different sessions 
    create table #temp(id int)
    (with same in different sessions)

    In addition to Olaf's, if you create temp table in two different sessions, you will find the 2 #test in the TempDB.sys.tables.
    CREATE TABLE #test (id int);
    Either the different object_ids or the "same" names indicate they are
    different temp tables. The same named local temp tables created in different sessions are traced with a 12 suffix in the tempdb.sys.tables. That's why when creating temp tables, maximum length can be of 116 characters only, while creating a
    table, the maximum is 128.
    The fragment referenced from the BOL
    You can create local and global temporary tables. Local temporary tables are visible only in the current session; global temporary tables are visible to all sessions.
    All local temporary tables are dropped automatically at the end of the current session.
    You can read more from the below link.
    https://technet.microsoft.com/en-us/library/aa258255(v=sql.80).aspx
    If you have any question, feel free to let me know.
    Eric Zhang
    TechNet Community Support

  • Import bug (fatal error): SQL Developer 4.1EA2 drops destination table upon rollback after error

    I created a table in the worksheet and then I tried to import data into is using SQL Developer EA2. After error is raised, I was presented with the error on the screenshot below. (Note: Rightmost button stands for "Cancel") By choosing cancel (i.e. Click cancel to cancel and rollback.) my destination table is dropped to recycle bin. Rollback should not undo any DDL even when the table was created using the import wizard. But purging a table that was not created by the import wizard is a fatal error.
    Steps to reproduce:
    create the destination table from worksheet and check if it was created:
    column table_name format a21
    create table test_imp_rollback_bug(dummy number(2));
    insert into test_imp_rollback_bug values (-1);
    commit;
    select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG';
    --Result:
    TABLE_NAME
    TEST_IMP_ROLLBACK_BUG
    import CSV using the import settings attached, To achieve this, utilize the new Restore state of the SQL Developer's import wizard. Note: you might need to adjust schema of the destination table.
    test_imp_rollback_bug_numbers.csv
    test_imp_rollback_bug-import_settings.sdimp
    Upon "Insert failed for rows  1  through  50 " message presented, click Cancel.
    The table does not exists any more:
    select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG';
    --Result:
    no rows selected
    Edit (jmarton, 2015-04-26):
    Software versions used:
    SQL Developer version: 4.1.0.18.37
    Oracle JDK: 1.8.0_31, 64bit, Linux
    Instant client: linux.x64-12.1.0.2.0
    Database: 12cR1 12.1.0.2.0 64bit, Linux, EE, CDB-install

    select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG'; 
    --Result: 
    no rows selected
    >>Note: you might need to adjust schema of the destination table.
    A rollback won't drop a table. Are you sure the tale isn't there? select from dba_tables or all_tables, assuming you had to change the destination schema as indicated in your test notes.

  • Dropping multiple tables in SQL Developer 1.1.25

    HI all
    I am trying to drop multiple tables simultaneously from tha schema but I am unable to find any such option. My host end database in Oracle 9.2.0 and client on Win XP.
    Thanks!
    Ankur

    Hi Ankur,
    Currently that's not possible. It is requested on the SQL Developer Exchange though. If you go vote there, you'll be adding more weight to the feature, so it will be implemented sooner.
    K.

  • How to drop the tables (articles) in subscription database MERGE replication.

    We have configured the merge replication from publication server to subscription server,
    Here I mistakenly selecting few tables (articles) in publication,
    Now I need to remove those mistakenly selected tables in subscription server database . 
    Note: I am trying to below way but unable to remove those tables in subscription server.
    1<sup>st</sup> I unselected those tables (articles) in publication, but not working.
    Could please tell me the how to remove those tables in subscription database.

    Ok that is normal, dont worry, if you mistakenly  chosen few tables, just add the new tables
    that you forgot it, just make click on the publication, you only have to Re-run the snapshot agent, i mean you must generate another snapshot and then synchronice with your suscriber, and then you will not need DROP the tables on the suscriber, if you have
    troubles yet, please post imagens to help you more !
    Thanks and regards.

  • Error while dropping a table

    Hi All,
    i got an error while dropping a table which is
    ORA-00600: internal error code, arguments: [kghstack_free1], [kntgmvm: collst], [], [], [], [], [], [], [], [], [], []
    i know learnt that -600 error is related to dba. now how to proceed.
    thanks and regards,
    sri ram.

    00600 errors should be raised as service request with Oracle as it implies some internal bug.
    You can search oracle support first to see if anyone has had the same class of 00600 error, and then if not (and therefore no patch) raise your issue with Oracle.
    http://support.oracle.com

  • Dropping a table gives an error

    When I try to drop a table it gives the following error?
    SQL> drop table FLOWS_010600.SYS_IOT_OVER_55056;
    drop table FLOWS_010600.SYS_IOT_OVER_55056
    ERROR at line 1:
    ORA-25191: cannot reference overflow table of an index-organized table
    what should i do, please help!

    Hi ,
    You cannot refer the overflow table ...
    You have to drop the parent index-organized table containing the specified overflow table...!!!!
    Regards,
    Simon

  • Ora-00600 error when dropping a table

    Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
    When I tried to drop a table, I got 600 error:
    SQL> desc DEV.ATTR_IDX$EX
    Name Null? Type
    NODE_ID NOT NULL NUMBER
    COL1 NUMBER
    SQL> show user;
    USER is "DEV"
    SQL> select count(*) from DEV.ATTR_IDX$EX;
    COUNT(*)
    0
    SQL> drop table DEV.ATTR_IDX$EX;
    drop table DEV.ATTR_IDX$EX
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [15265], [], [], [], [], [], [], [],
    SQL> drop table DEV.ATTR_IDX$EX purge;
    drop table DEV.ATTR_IDX$EX purge
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [15265], [], [], [], [], [], [], [],
    I guess this is because it had a parent table, which I dropped (I used "drop table <parent_table>", and it did not give me error, very strange).
    SQL> select dbms_metadata.get_ddl('TABLE','ATTR_IDX$EX') from dual;
    DBMS_METADATA.GET_DDL('TABLE','ATTR_IDX$EX')
    CREATE TABLE "DEV"."ATTR_IDX$EX"
    ( "NODE_ID" NUMBER NOT NULL ENABLE,
    "COL1" NUMBER,
    FOREIGN KEY ("NODE_ID")
    REFERENCES () ON DELETE CASCADE ENABLE
    ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "USERS"
    MONITORING
    Try to drop FK constraints yields the same error.
    So now how can I drop this table table, any work around?
    Thanks.

    This is a bug. There is no Patch avaialble for this yet. This error is seen where recyclebin is enabled. Possible workaround is to disable the recyclebin.
    This happens with the dictionary corruption due to inconsistency between obj$ and seg$.
    This is a correct answer but still i would suggest to contact Oracle support.

  • Problem while dropping a table

    Dear All,
    I am facing a problem while dropping a table in Oracle 10g.
    I am able to find the number of records in the table but unble to delete it.
    SQL> select count(*) from merchant_audit;
    COUNT(*)
    30028278
    SQL> drop table merchant_audit;
    drop table merchant_audit
    ERROR at line 1:
    ORA-00942: table or view does not exist
    I have to drop this table from the database. Please help.
    regards,
    Santhosh

    Hi,
    IS it a table ? Is it your table ?
    Read this example :
    sqlplus scott/*****
    SQL> create table merchant_audit(col1 number);
    Table created.
    SQL> create public synonym merchant_audit for merchant_audit;
    Synonym created.
    SQL> grant select on merchant_audit to merchant;
    Grant succeeded.
    SQL> conn merchant/merchant
    Connected.
    SQL> select count(*) from merchant_audit;
    COUNT(*)
    0
    SQL> drop table merchant_audit;
    drop table merchant_audit
    ERROR at line 1:
    ORA-00942: table or view does not exist
    SQL>
    See owner into the dba_tables, and if synonym into dba_synonyms.
    Nicolas.
    Message was edited by:
    Nicolas Gasparotto

  • Can't drop database table objects on a EJB Diagram.

    JDeveloper 10.1.3 EA.
    When I drop a database table object on a EJB Diagram the error below occurs. Also dropping components from the Component Palette doesn't work. A wizard opens, but after completing that, nothing is on the EJB Diagram.
    However, after dropping a table and a restart of JDeveloper, there is an empty 'tablename EJB' on the EJB Diagram, but a click with the mouse on it generates the same error as the drop did.
    Simular errors occur with JDeveloper 10.1.2, so writing this I realize that this might be a database version problem. I'm using 9i! I'll try 10g and see what happens.
    Message
    BME-99003: An error occurred, so processing could not continue.
    Cause
    The application has tried to de-reference an invalid pointer. This exception should have been dealt with programmatically. The current activity may fail and the system may have been left in an unstable state. The following is a stack trace.
    java.lang.NullPointerException
         at oracle.jdevimpl.xml.DescriptorNode.getWhitespaceHandler(DescriptorNode.java:349)
         at oracle.jdevimpl.xml.DescriptorNodeDomIO.load(DescriptorNodeDomIO.java:164)
         at oracle.jdeveloper.xml.BindingIO.load(BindingIO.java:43)
         at oracle.jdevimpl.xml.DescriptorNode.getNewDescriptorImpl(DescriptorNode.java:506)
         at oracle.jdevimpl.xml.DescriptorNode.getDescriptor(DescriptorNode.java:140)
         at oracle.jdeveloper.xml.oc4j.ejb.OrionEjbJarNode.getOrionEjbJar(OrionEjbJarNode.java:145)
         at oracle.jdeveloper.ejb.BaseEjbModuleContainer.getOrionEjbJar(BaseEjbModuleContainer.java:476)
         at oracle.jdeveloper.ejb.modeler.diagram.dropHandler.TableDropEJB21Handler.isAvailable(Unknown Source)
         at oracle.bm.diagrammer.ui.DropChooserPanel.populateOptions(Unknown Source)
         at oracle.bm.diagrammer.ui.DropChooserPanel.createComponents(Unknown Source)
         at oracle.bm.diagrammer.ui.DropChooserPanel.<init>(Unknown Source)
         at oracle.bm.diagrammer.dropHandler.AbstractChooserDropHandler.createPanel(Unknown Source)
         at oracle.bm.diagrammer.dropHandler.AbstractChooserDropHandler.processObjects(Unknown Source)
         at oracle.bm.addinUtil.IDEAppContext$4.performAction(Unknown Source)
         at oracle.bm.diagrammer.LockMonitor.performLockedAction(Unknown Source)
         at oracle.bm.diagrammer.BaseDiagram.performDiagramLockedAction(Unknown Source)
         at oracle.bm.addinUtil.IDEAppContext.dropNavigatorNodeLater(Unknown Source)
         at oracle.bm.addinUtil.IDEAppContext$5.run(Unknown Source)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
    Action
    If further errors occur, you should restart the application.
    Also, report the problem on the JDeveloper forum on otn.oracle.com, or contact Oracle support, giving the information from this message.
    ________________________________________________________________________________

    Hi lisa, you've said that the problem does not occur in the 10.1.3 build but I have almost the same problem with the BME-99003 error message.
    I used the same workaround "changing the regional settings from BE to US" and the BME-99003 problem disappears :-)
    Here is the error message that I receive while I add a table into the EJBDiagram. I'm using
    windows XP SP2
    ADF Business Components     10.1.3.34.12
    Java™ Platform     1.5.0_04
    Oracle IDE     10.1.3.34.12
    Struts Modeler Version     10.1.3.34.12
    UML Modelers Version     10.1.3.34.12
    Versioning Support     10.1.3.34.12
    Abdelkrim BOUJRAF
    Message
    BME-99003: An error occurred, so processing could not continue.
    Cause
    The application has tried to de-reference an invalid pointer. This exception should have been dealt with programmatically. The current activity may fail and the system may have been left in an unstable state. The following is a stack trace.
    java.lang.NullPointerException
    at oracle.jdevimpl.xml.DescriptorNode.getWhitespaceHandler(DescriptorNode.java:349)
    at oracle.jdevimpl.xml.DescriptorNodeDomIO.load(DescriptorNodeDomIO.java:164)
    at oracle.jdeveloper.xml.BindingIO.load(BindingIO.java:43)
    at oracle.jdevimpl.xml.DescriptorNode.getNewDescriptorImpl(DescriptorNode.java:506)
    at oracle.jdevimpl.xml.DescriptorNode.getDescriptor(DescriptorNode.java:140)
    at oracle.jdeveloper.xml.oc4j.ejb.OrionEjbJarNode.getOrionEjbJar(OrionEjbJarNode.java:145)
    at oracle.jdeveloper.xml.oc4j.ejb.OrionEjbJarHelper.findOrionEjbJar(OrionEjbJarHelper.java:82)
    at oracle.jdeveloper.xml.oc4j.ejb.OrionEjbJarHelper.findOrCreateOrionEjbJar(OrionEjbJarHelper.java:73)
    at oracle.jdeveloper.ejb.modeler.diagram.dropHandler.TableDropEJBCommonHandler.processTableNodes(Unknown Source)
    at oracle.jdeveloper.ejb.modeler.diagram.dropHandler.TableDropEJB21Handler.processTableNodes(Unknown Source)
    at oracle.bm.typemodel.dropHandler.TableDropSubHandler.processDBObjectNodes(Unknown Source)
    at oracle.bm.typemodel.dropHandler.DBObjectDropSubHandler.processObjects(Unknown Source)
    at oracle.bm.diagrammer.dropHandler.AbstractChooserDropHandler.processObjectsImpl(Unknown Source)
    at oracle.bm.diagrammer.dropHandler.AbstractChooserDropHandler.processObjects(Unknown Source)
    at oracle.bm.addinUtil.IDEAppContext$4.performAction(Unknown Source)
    at oracle.bm.diagrammer.LockMonitor.performLockedAction(Unknown Source)
    at oracle.bm.diagrammer.BaseDiagram.performDiagramLockedAction(Unknown Source)
    at oracle.bm.addinUtil.IDEAppContext.dropNavigatorNodeLater(Unknown Source)
    at oracle.bm.addinUtil.IDEAppContext$5.run(Unknown Source)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
    Action
    If further errors occur, you should restart the application.
    Also, report the problem on the JDeveloper forum on otn.oracle.com, or contact Oracle support, giving the information from this message.

  • 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
    ============================================================

  • How can I use TopLink for querys that have two and more tables?

    I use TopLink today, and I can use one table to query, but how can I use TopLink for querys that have two and more tables?
    Thank you for see and answer this question.

    You can write a custom SQL query and map it to an object as needed. You can also use the Toplink query language "anyOf" or "get" commands to map two tables as long as you map them as one to one (get command) or one to many (anyOf command) in the toplink mapping workbench.
    Zev.
    check out oracle.toplink.expressions.Expression in the 10.1.3 API

Maybe you are looking for