Weblogic and Db2 UDB V8 64 bit

We are planning to migrate our db2 udb instance to V8.2 64 bit on SunOS. Currently we are on DB2 V81 32 bit using weblogic. We'd like to know what are the Weblogic Versions that are certified by BEA to support on db2 udb V8.2 32 and 64 bit instances on SunOS. And how to get weblogic to talk to Db2 UDB V8.2 64 bit instances?
Any feedback would be greatly appreciated.
Thanks a lot.
Li

LI Cui wrote:
We are planning to migrate our db2 udb instance to V8.2 64 bit on SunOS. Currently we are on DB2 V81 32 bit using weblogic. We'd like to know what are the Weblogic Versions that are certified by BEA to support on db2 udb V8.2 32 and 64 bit instances on SunOS. And how to get weblogic to talk to Db2 UDB V8.2 64 bit instances?
Any feedback would be greatly appreciated.
Thanks a lot.
LiThe BEA WebLogic Type 4 JDBC driver for DB2 (the "DB2 driver") supports:
DB2 Universal Database (UDB) 7.1, 7.2, and 8.1 on Windows NT, Windows 2000,
Windows 2003, Windows XP, UNIX, Linux, and Linux/s390 via DRDA
DB2 6.1 and DB2 UDB 7.1 running on OS/390 and z/OS via DRDA
DB2 UDB V4R5, V5R1, and V5R2 running on iSeries and AS/400
Note: This documentation uses the following terms to describe the different DB2 versions:
"DB2 UDB" refers to all versions of DB2 running on Windows, UNIX, and Linux/s390 platforms
"DB2 OS/390" refers to all versions of DB2 on OS/390 and z/OS platforms
"DB2 iSeries" refers to all versions of DB2 on iSeries and AS/400
Joe

Similar Messages

  • Weblogic 5.1 and DB2 UDB 7.1 beta

    Does anyone know how I can use install the necessary drivers to make
    Weblogic and DB2 UDB on NT work together?
    Thanks,
    Amit.

    Check with the folks that make DB2.
    mbg
    In article <8ie3so$7js$[email protected]>, [email protected]
    says...
    Does anyone know how I can use install the necessary drivers to make
    Weblogic and DB2 UDB on NT work together?
    Thanks,
    Amit.
    ==================================================
    NewsGroup Rant
    ==================================================
    Rant 1.
    The less info you provide about your problem means
    the less we can help you. Try to look at the
    problem from an external perspective and provide
    all the data necessary to put your problem in
    perspective.

  • OWB and DB2 UDB

    Can OWB version 10.1.0.2.0 work with DB2 UDB on WIN NT as the source database / module? Is there any documentation available which has some details on this?

    Yes it can. You use hetergeneous services (HS) of the database to accomplish this. With HS, you two options: using an Oracle Gateway or using generic connectivity. Generic Connectivity uses ODBC to talk to DB2.
    Here's a link to the documentation:
    http://download-west.oracle.com/docs/html/B12146_01/defsource.htm#sthref717
    Can OWB version 10.1.0.2.0 work with DB2 UDB on WIN
    NT as the source database / module? Is there any
    documentation available which has some details on
    this?

  • Where to download Tuxedo 10gR3 and Weblogic 10.3.1 for 64-bit Win2K3 ?

    Folks,
    Hello. I am installing PeopleTools 8.50 in 64-bit Windows Server 2003 .
    PeopleTools 8.50 is certified on 64-bit OS and requires Tuxedo 10gR3 and Weblogic 10.3.1.
    In http://edelivery.oracle.com PeopleTools 8.50 package, there are only 3 files for Windows as follows:
    1) Tuxedo 10gR3 for MS Windows Server 2003 32-bit (V15053-01)
    2) Weblogic 10.3.1 for MS Windows 32-bit (V16992-01)
    3) Weblogic 10.3.1 Generic (V17003-01)
    As I know, Tuxedo 10gR3 and Weblogic 10.3.1 do support 64-bit Windows Server 2003. But I cannot find any website to download Tuxedo 10gR3 and Weblogic 10.3.1 for my 64-bit Windows Server 2003.
    Can any folks provide a link to download Tuxedo 10gR3 and Weblogic 10.3.1 for 64-bit Windows Server 2003 ?

    user8860348 wrote:
    ...> 1) Tuxedo 10gR3 for MS Windows Server 2003 32-bit (V15053-01)
    2) Weblogic 10.3.1 for MS Windows 32-bit (V16992-01)
    3) Weblogic 10.3.1 Generic (V17003-01)
    As I know, Tuxedo 10gR3 and Weblogic 10.3.1 do support 64-bit Windows Server 2003. But I cannot find any website to download Tuxedo 10gR3 and Weblogic 10.3.1 for my 64-bit Windows Server 2003.
    Can any folks provide a link to download Tuxedo 10gR3 and Weblogic 10.3.1 for 64-bit Windows Server 2003 ?Why looking for the 64-bit whereas the 32-bit are the only available on edelivery for Windows even though only 64-bit OS is supported ? Take the software under Peopletools 8.50 package for your plateform, they are certified with that one.
    Nicolas.

  • Migration from Zos and DB2 to Unix and UDB

    We will be migrating our CRM application from mainframe and DB2 to a Unix environment with UDB.
    Do you have any experience and/or guidelines ?
    Thanks
    Ronny

    Hi Ronny,
    I guess the right forum to post this question is SAP CRM: Webclient UI - Framework
    Thanks and Regards,
    santo.

  • WebLogic 6.1 and DB2 setup on Solaris 8

    Hi,
    I was wondering if anyone knows how? and if it is possible to setup WebLogic 6.1
    and DB2 to work on Solaris 8? and if they know any helpfull links for me to read
    up on how to set everything up.
    Thanks

    Ok.
    http://search.beasys.com/weblogic/gonews/
    S.
    "S Tomb" <[email protected]> wrote in message
    news:3b9d3f97$[email protected]..
    >
    The link you included does not work, is there another URL
    that does work? Thanks
    S Tomb
    "Slava Imeshev" <[email protected]> wrote:
    You could go to our newsgroup search engine,
    (http://search.beasys.com/weblogic/gonews/)
    select jdbc newsgroup, enter "DB2" keyword
    and press "Search" button.
    Regards,
    Slava Imeshev
    "S Tomb" <[email protected]> wrote in message
    news:3b996903$[email protected]..
    Hi,
    I was wondering if anyone knows how? and if it is possible to setupWebLogic 6.1
    and DB2 to work on Solaris 8? and if they know any helpfull links forme
    to read
    up on how to set everything up.
    Thanks

  • CRM Migration from Zos and DB2 to Unix and UDB

    We will be migrating our CRM application from mainframe and DB2 to a Unix environment with UDB.
    Do you have any experience and/or guidelines ?
    Thanks
    Ronny

    Hi Ronny,
    I guess the right forum to post this question is SAP CRM: Webclient UI - Framework
    Thanks and Regards,
    santo.

  • Configuration issue with DRDA Oracle 10g to DB2 UDB v8

    Oracle 10.2.0.4 linux RH 64 bit - DB2 UDB v8.2 linux 32 bit. I'm attempting to install transparent gateway to connect from my oracle instance to the db2 instance. I was successful until the step requiring the package rebind and this is the error I get:
    SQL> exec GTW$_BIND_PKG@MYDB2SERVER;
    BEGIN GTW$_BIND_PKG@MYDB2SERVER; END;
    ORA-04052: error occurred when looking up remote object
    DB2USER.GTW$[email protected]
    ORA-00604: error occurred at recursive SQL level 1
    ORA-28527: Heterogeneous Services datatype mapping error
    TG4DRDA v10.2.0.1.0 grc=0, drc=-332 (865B,0001), errp=GDJREACS
    errmc=1208,819
    ORA-02063: preceding 3 lines from MYDB2SERVERMy TNSNAME entry:
    MYDB2SERVER =
      (DESCRIPTION =
            (ADDRESS=
              (PROTOCOL=TCP)
              (PORT=1521)
              (HOST=172.xx.xx.xx))
            (CONNECT_DATA=(SID=MYDB2SERVER)
            (HS=)
    LISTENER entry:
       (SID_DESC=
            (SID_NAME=MYDB2SERVER)
            (ORACLE_HOME=/home/oracle/oraHomes/gateway)
            (PROGRAM=g4drsrv)
       )DBlink:
    SQL> create public database link MYDB2SERVER
      2  connect to db2user identified by mypass
      3  using 'MYDB2SERVER';initMYDB2SERVER.ora (lines I changed):
    DRDA_CONNECT_PARM=172.xx.xx.xx:50000
    DRDA_REMOTE_DB_NAME=db2
    DRDA_RECOVERY_PASSWORD=mypassI'm sure it's just a simple config issue, but I've been racking my rain for hours trying different things and cannot figure it out.
    Question - DRDA_REMOTE_DB_NAME - is the the O/S user? or the database instance name? For example, when accessing the DB2 instance, I login to the O/S as db2user but issue 'db2 connect to db2' when connecting to the instance - which value is DRDA_REMOTE_DB_NAME looking for?
    Any help is appreciated - thanks

    Hi,
    You are right, DRDA_REMOTE_DB_NAME should have the name of the Db2 instance.
    The error you are getting points to the fact that you are an multibyte character set in either Oracle and/or DB2. The gateway can connect, but first have to be able to map the character sets indicated by the error message:
    TG4DRDA v10.2.0.1.0 grc=0, drc=-332 (865B,0001), errp=GDJREACS errmc=1208,819 <<== 1208 and 819 are the CCSIDs
    Add the following entries to the gateway codepage.map file -
    S 367 > US7ASCII
    D 13488 > AL16UTF16
    D 1200 = AL16UTF16
    M 1208 = UTF8
    MBC 1208 = 1208 1200
    The default location of the file is $ORACLE_HOME/tg4drda/admin/codepage.map
    These values map code page 1208 to Oracle's UTF8 character sets so that the gateway can translate UTF8 data into code page 819 (WE8ISO8859P1).
    Regards,
    Ed

  • IAS 6.5 on DB2/UDB connection never released?

    We installed an application on DB2/UDB 7.1 (using JDBC type 2 driver) and found the connections never get released after use. Same code, if I switch to Oracle, MSSQL (using Merant), or Sybase. They all work fine - all connections are released properly. I believe it's not the driver problem since it works fine with WebLogic and WebSphere.
    So once connections run out, the whole system hung since there are connection request waiting in queue. We'll have to restart the server.
    Is this a known issue for iPlanet on DB2/UDB?

    No, it works fine. I have tested it in my test environment. In this test case thousand of time I am creating and closing a connection. It's working fine.
    Please send me your piece of code, which is causing error.
    Please clarify which j2ee component you are using for this purpose.

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

  • Error in "Checking Availabe Space for the DB2 UDB for Unix..." phase

    Hello,
    We are in the middle of an Upgrade proyect from R/3 4.6C (kernet 4.6D EXT) to ECC 6.0.
    As a first step we are doing an Heterogenous System Copy to migrate from servers with HP-UX B11.11/Informix 9.4 to servers with AIX 5.3/DB2 UDB 8.
    We already did the database import with no errors. When we are installing R3 4.6C in the target server we are getting u201CMemory Fault (coredump)u201D error in the u201CChecking Availabe Space for the DB2 UDB for Unix, Windows Tablespacesu201D phase.
    Any advice will be appreciated.
    Best Regards
    Francisco

    Hello Paul,
    There is no db2diag.log. We are in the first steps of the installation.
    Operating System logs just shows an ABNORMALY TERMINATION OF SOTWARE error.
    This is the CEDBMIG.log
    INFO 2010-08-04 10:12:00 CommandFileController SyFileCopy:150
        Copying source file CEDBMIG.R3S to target file CEDBMIG.R3S.30 ...
    INFO 2010-08-04 10:12:01 Main
        Preparation successfully completed.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:434
        checking host name lookup for 'sapqas'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:473
        offical host name for 'sapqas' is 'sapqas'.
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:541
        host 'sapqas' has ip address '172.26.26.64'
    INFO 2010-08-04 10:12:02 CENTRDBINSTANCE_IND_DB6 SyCheckHostnameLookup:581
        offical host name for '172.26.26.64' is 'sapqas'.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD KERNEL will not be copied.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD RDBMS will not be copied.
    INFO 2010-08-04 10:12:23 CDSERVERMIG_IND_DB6 InternalColdKeyCheck:0
        The CD EXPORT1 will not be copied.
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyCoprocessCreate:300
        Creating coprocess /usr/sbin/lsattr -El sys0 -a realmem  ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyRamSizeGet:100
        The process lsattr puts out:
         realmem 8388608 Amount of usable physical memory in Kbytes False
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyRamSizeGet:700
        Physical RAM size is 8192 MB.
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:100
        Retrieving swap space size ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SyCoprocessCreate:300
        Creating coprocess /usr/sbin/lsps -s  ...
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:150
        The process lsps puts out:
         Total Paging Space   Percent Used
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:150
        The process lsps puts out:
               8192MB               1%
    INFO 2010-08-04 10:12:23 CALCRAM_IND_DB6 SySwapGetSize:500
        Currently activated swap space is 8192 MB.
    INFO 2010-08-04 10:12:31 CENTRDBINSTANCE_IND_DB6 InternalWarmKeyCheck:0
        The installation phase is starting now. Please look in the log
        file for further information about current actions.
    INFO 2010-08-04 10:12:31
        Requesting Installation Details
    INFO 2010-08-04 10:12:31
        Reading and Checking DB2 UDB for UNIX, Windows Specific Keys
    INFO 2010-08-04 10:12:31
        Select the DB2 Storage Management.
    INFO 2010-08-04 10:12:31
        Choose the number of storage paths for DB2's Automatic Storage
        Management.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD KERNEL will not be copied.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD RDBMS will not be copied.
    INFO 2010-08-04 10:12:31 CDSERVERMIG_IND_DB6 InternalWarmKeyCheck:0
        The CD EXPORT1 will not be copied.
    INFO 2010-08-04 10:12:31
        Requesting Information on CD-ROMs
    INFO 2010-08-04 10:12:31
        Calculating RAM Distribution
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Dispatcher
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Gateway Service
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Secure Gateway Service
    INFO 2010-08-04 10:12:31
        Creating the Service Entry for the Message Server
    INFO 2010-08-04 10:12:31
        Creating the SAP Administration Group sapsys
    INFO 2010-08-04 10:12:32
        Creating the Database Administration Group db<dbsid>adm
    INFO 2010-08-04 10:12:32
        Creating the Group db<dbsid>ctl
    INFO 2010-08-04 10:12:32
        Creating the Group db<dbsid>mnt
    INFO 2010-08-04 10:12:32
        Creating the SAP connect user
    INFO 2010-08-04 10:12:32
        Setting Password of the SAP connect user
    INFO 2010-08-04 10:12:32
        Creating the db2<sapsid> User
    INFO 2010-08-04 10:12:32
        Setting the User Password
    INFO 2010-08-04 10:12:32
        Creating the SAP System Administrator
    INFO 2010-08-04 10:12:32
        Setting Password for for the SAP System Administrator
    INFO 2010-08-04 10:12:32
        Creating Directories
    INFO 2010-08-04 10:12:32
        Creating Symbolic Links
    INFO 2010-08-04 10:12:32
        Getting Minimal Size of the Database
    INFO 2010-08-04 10:12:32
        Changing DB2 UDB for UNIX, Windows Tablespace Data
    INFO 2010-08-04 10:12:32
        Checking if Required Directories Exist
    INFO 2010-08-04 10:12:32
        Checking Available Space for the SAP Instance
    INFO 2010-08-04 10:12:32
        Checking Available Space for the DB2 UDB for UNIX, Windows
        Tablespaces
    This is the CEDBMIG.R3S log
    120_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    130_SOURCE=@DB_HOME@/.cshrc
    130_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    200_SOURCE=@DB_HOME@/.profile
    200_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.SH
    210_SOURCE=@DB_HOME@/.profile
    210_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.SH
    [Z_OSUSERSIDADMENVIRONMENT_IND_DB6]
    100_GROUP=sapsys
    100_OWNER=@LOWER_SAPSYSTEMNAME@adm
    100_PERMISSION=0644
    100_SOURCE=@HOME@/.login
    100_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    110_SOURCE=@HOME@/.login
    110_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    120_GROUP=sapsys
    120_OWNER=@LOWER_SAPSYSTEMNAME@adm
    120_PERMISSION=0644
    120_SOURCE=@HOME@/.cshrc
    120_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.CSH
    130_SOURCE=@HOME@/.cshrc
    130_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.CSH
    200_SOURCE=@HOME@/.profile
    200_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/SAPSRC.SH
    210_SOURCE=@HOME@/.profile
    210_TEMPLATE=@CDMOUNTPATH@/@OS@/COMMON/INSTALL/DBSRC.SH
    [Z_R3DIRECTORIES_IND_IND]
    101_PATH=@SAPDIR@
    101_PERMISSION=0775
    101_SET_FILE_ATTRIBUTES=YES
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_PATH=@SAPDIR@/tmp
    103_PATH=@SAPDIR@/trans
    104_PATH=@SAPDIR@/trans/tmp
    104_SET_FILE_ATTRIBUTES=NO
    105_PATH=@SAPDIR@/trans/EPS
    106_PATH=@SAPDIR@/trans/EPS/in
    107_PATH=@SAPDIR@/trans/EPS/out
    108_PATH=@SAPDIR@/trans/EPS/log
    109_PATH=@SAPDIR@/trans/bin
    110_PATH=@SAPDIR@/trans/buffer
    111_PATH=@SAPDIR@/trans/cofiles
    112_PATH=@SAPDIR@/trans/data
    113_PATH=@SAPDIR@/trans/etc
    114_PATH=@SAPDIR@/trans/log
    115_PATH=@SAPDIR@/trans/sapnames
    120_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    120_PERMISSION=0751
    120_SET_FILE_ATTRIBUTES=YES
    121_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    121_PERMISSION=0755
    122_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe
    123_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/opt
    124_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen
    125_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen/opt
    126_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/gen/dbg
    127_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS/src
    128_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    129_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/data
    130_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/log
    131_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/work
    131_PERMISSION=0775
    132_PATH=@SAPMOUNT@
    140_PATH=@SAPMOUNTEXE@
    141_PATH=@SAPMOUNTPROFILE@
    141_PERMISSION=0755
    142_PATH=@SAPMOUNTGLOBAL@
    142_PERMISSION=0700
    150_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/sec
    160_PATH=@STARTDIRECTORY@
    160_PERMISSION=0777
    [Z_R3DIRPERMISSIONS_IND_IND]
    101_CHANGE_ON_NFS=NO
    101_PATH=@SAPMOUNT@
    101_PERMISSION=0755
    101_TRAVERSE=
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_CHANGE_ON_NFS=NO
    102_PATH=@SAPMOUNTEXE@
    102_PERMISSION=0755
    102_TRAVERSE=
    102_USERGROUP=sapsys
    102_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    103_CHANGE_ON_NFS=NO
    103_PATH=@SAPMOUNTGLOBAL@
    103_PERMISSION=0710
    103_TRAVERSE=
    103_USERGROUP=db@LOWER_DB_SID@adm
    103_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    104_CHANGE_ON_NFS=NO
    104_PATH=@SAPMOUNTPROFILE@
    104_PERMISSION=0755
    104_TRAVERSE=
    104_USERGROUP=sapsys
    104_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    105_CHANGE_ON_NFS=NO
    105_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    105_PERMISSION=0755
    105_TRAVERSE=
    105_USERGROUP=sapsys
    105_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    120_CHANGE_ON_NFS=NO
    120_PATH=@HOME@
    120_PERMISSION=0700
    120_TRAVERSE=
    120_USERGROUP=sapsys
    120_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    121_CHANGE_ON_NFS=NO
    121_PATH=@HOME@
    121_PERMISSION=0777
    121_TRAVERSE=FILES
    121_USERGROUP=sapsys
    121_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    130_CHANGE_ON_NFS=NO
    130_PATH=@STARTDIRECTORY@
    130_PERMISSION=0777
    130_TRAVERSE=
    130_USERGROUP=sapsys
    130_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    140_CHANGE_ON_NFS=YES
    140_PATH=@SAPDIR@/trans
    140_PERMISSION=0775
    140_TRAVERSE=
    140_USERGROUP=sapsys
    140_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    141_CHANGE_ON_NFS=YES
    141_PATH=@SAPDIR@/trans/bin
    141_PERMISSION=0775
    141_TRAVERSE=
    141_USERGROUP=sapsys
    141_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    [Z_R3FILEPERMISSIONS_IND_IND]
    101_CHANGE_ON_NFS=NO
    101_PATH=@SAPMOUNTEXE@
    101_PERMISSION=0755
    101_TRAVERSE=SUBDIRECTORIES
    101_USERGROUP=sapsys
    101_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    102_CHANGE_ON_NFS=NO
    102_PATH=@SAPMOUNTEXE@
    102_PERMISSION=0755
    102_TRAVERSE=FILES
    102_USERGROUP=sapsys
    102_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    103_CHANGE_ON_NFS=NO
    103_PATH=@SAPMOUNTGLOBAL@
    103_PERMISSION=0700
    103_USERGROUP=sapsys
    103_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    104_CHANGE_ON_NFS=NO
    104_PATH=@SAPMOUNTPROFILE@
    104_PERMISSION=0755
    104_TRAVERSE=SUBDIRECTORIES
    104_USERGROUP=sapsys
    104_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    105_CHANGE_ON_NFS=NO
    105_PATH=@SAPMOUNTPROFILE@
    105_PERMISSION=0755
    105_TRAVERSE=FILES
    105_USERGROUP=sapsys
    105_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    106_CHANGE_ON_NFS=NO
    106_PATH=@SAPMOUNTEXE@/saposcol
    106_PERMISSION=04755
    106_USERGROUP=sapsys
    106_USERNAME=root
    112_CHANGE_ON_NFS=NO
    112_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    112_PERMISSION=0751
    112_TRAVERSE=SUBDIRECTORIES
    112_USERGROUP=sapsys
    112_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    113_CHANGE_ON_NFS=NO
    113_PATH=@SAPDIR@/@SAPSYSTEMNAME@
    113_PERMISSION=0751
    113_TRAVERSE=FILES
    113_USERGROUP=sapsys
    113_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    114_CHANGE_ON_NFS=NO
    114_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    114_PERMISSION=0755
    114_TRAVERSE=SUBDIRECTORIES
    114_USERGROUP=sapsys
    114_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    115_CHANGE_ON_NFS=NO
    115_PATH=@SAPDIR@/@SAPSYSTEMNAME@/SYS
    115_PERMISSION=0755
    115_TRAVERSE=FILES
    115_USERGROUP=sapsys
    115_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    116_CHANGE_ON_NFS=NO
    116_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    116_PERMISSION=0755
    116_TRAVERSE=SUBDIRECTORIES
    116_USERGROUP=sapsys
    116_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    117_CHANGE_ON_NFS=NO
    117_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@
    117_PERMISSION=0755
    117_TRAVERSE=FILES
    117_USERGROUP=sapsys
    117_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    118_CHANGE_ON_NFS=NO
    118_PATH=@SAPDIR@/@SAPSYSTEMNAME@/@INSTANCENAME@/work
    118_PERMISSION=0775
    118_USERGROUP=sapsys
    118_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    120_CHANGE_ON_NFS=NO
    120_PATH=@HOME@
    120_PERMISSION=0700
    120_USERGROUP=sapsys
    120_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    121_CHANGE_ON_NFS=NO
    121_PATH=@HOME@
    121_PERMISSION=0700
    121_TRAVERSE=FILES
    121_USERGROUP=sapsys
    121_USERNAME=@LOWER_SAPSYSTEMNAME@adm
    [Z_R3LINKS_IND_IND]
    101_LINKCONTENT=@SAPMOUNTEXE@
    101_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/dbg
    102_LINKCONTENT=dbg
    102_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/exe/run
    103_LINKCONTENT=@SAPMOUNTGLOBAL@
    103_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/global
    104_LINKCONTENT=@SAPMOUNTPROFILE@
    104_LINKNAME=@SAPDIR@/@SAPSYSTEMNAME@/SYS/profile
    [Z_SAPDATAPATH]
    S1=/db2/@SAPSYSTEMNAME@/sapdata1
    S2=/db2/@SAPSYSTEMNAME@/sapdata2
    S3=/db2/@SAPSYSTEMNAME@/sapdata3
    S4=/db2/@SAPSYSTEMNAME@/sapdata4
    S5=/db2/@SAPSYSTEMNAME@/sapdata5
    S6=/db2/@SAPSYSTEMNAME@/sapdata6
    SAPDATAT=/db2/@SAPSYSTEMNAME@/sapdatat
    As you can see there is not an error message, the installation simply stops when the try to check the space available for tablespaces.
    Regards

  • Error while Installing NW701 EHP1 JAVA Only on AIX/DB2 UDB

    Hi All,
    While Installing NW701 EHP1 JAVA only on AIX/DB2 UDB platform I am getting below erron in Update Database Registry Step.
    Previously system was installed with DB29.1 patch level 7 whiach was wrong. Then I have uninstalled SAP and cleaned all the mounted directories related to SID. After that I stsrted again and getting below error.
    The step UpdateDB2Registry with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_DB6_DB|ind|ind|ind|ind|1|0|NW_DB6_UpdateDb2Registry|ind|ind|ind|ind|13|0|UpdateDB2Registry was executed with status ERROR .
    Imediate response would highly appreciated and rewarded.
    Best Regards
    Devendra

    Hi,
    Check file system characteristics, it should be created with read and write only. Please make sure that file system should not be created with cio option.
    Thanks
    Sunny

  • SAP ECC 6.0 SR3 Cluster failover not working in AIX with DB2 UDB V9.1 FP6

    Hi Gurus,
    We have installed the SAP ECC 6.0 SR3 High Availability  with DB2 UDB V9.1 FP6 in AIX cluster environment.
    After installation we are doing the cluster fail test.
    Node A
    Application Server
    Mount Points:
    /sapmnt/<SID>
    /usr/sap/<SID>
    /usr/sap/trans
    Node B
    Database Server
    Mount Points:
    /db2//<SID>
    The procedure followed to do the cluster failover:
    We have down the cluster on Node A and all the resources of the Node A has been moved to Node B.
    On Node B when we issued a command to start the SAP. It says u201Cno start profiles foundu201D
    WE have down the cluster on Node B and  moved the Resource from Node B to Node A .  There the db2 User IDu2019s are not available. We have crated the user Idu2019s manually on Node A. however it did not work.
    Please suggest the procedure to start the sap in cluster failover.
    Best Regards
    Sija

    Hi Sija,
    Can i have detailed scenario in your cluster configuration.
    Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
    Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
    Regards
    Nick Loy

  • SAP ECC 6.0 SR3 Cluster failover not working in windows with DB2 UDB V9.1 F

    Dear Expertise,
    We have installed the SAP ECC 6.0 SR3 High Availability with DB2 UDB V9.1 FP5 in windows cluster environment.
    We have installation following instances on nodes 1 and 2.
    Node 1                                                                               
    DB2 database software                                                                       
    Central service instance for ABAP Installation on Shared drive G:          
    First MCSC node to create a cluster group u201Cpdssapgrpu201D                            
    Database group u201Cpgsdbgrpu201D(Shared Drive)                                                  
    Enqueue replication service                                                                  
    CI (central instance)(local Drive)
    Node 2
    DB2 database software
    Additional cluster node
    Enqueue replication service
    DI(dialog instance)(local Drive)
    I can login into the system using both CI and DI.
    if my SAP Cluster group is moved from one node to another i can still login into the system
    But when my DB2 group is moved from node A to node B my SAP services are getting closed
    and i am getting the message database not found
    so please Guide me as soon as possible Friends.
    Thanks and Regards,
    Ravindra
    Edited by: Ravindra Bade on Mar 6, 2009 10:22 AM

    Hi Ravidra
    Have u solved the probelm I also have the same problem when i move the groups from node1 to node2 manually my 2 servrces 00 and 01 are failed not able to bring up again. If You solve the problem please guide me the solution to solve this.
    THanks in advance

  • I can't download IBM DB2 UDB V7.1 & V7.2 Beta Plug-in

    I want to download plugin for Oracel workbench migratipn . also I click Accept License Agreement and click download on plugin but I can't download IBM DB2 UDB V7.1 & V7.2 Beta Plug-in. Popup show 'Sorry, you must accept the License Agreement before downloading' . How I can download this plugin?? pls help me

    hi user645871
    After you accepted the license agreement :
    "You must accept the OTN License Agreement to download this software.
    Accept License Agreement "
    and click on the download
    do you get the window with
    Oracle Technology Network Developer License Terms
    Export Controls on the Programs ?
    Click on YES, I accept the License Terms and Export Restrictions and I acknowledge that I have reviewed and understood the agreement and agree to use the language I selected in entering into this agreement.
    and on I accept.
    Do you have created your account on the oracle OTN ?
    I could manage to download it without any issues.
    By the way herewith also the documentation http://www.oracle.com/technology/documentation/migration.html

Maybe you are looking for

  • Jdeveloper 11.1.2.0.0 Aduit rules problem.

    Hi All, I am using JDeveloper 11.1.2.0.0. I have created some custom audit rules and its working fine .But i cant override the warning or error messages. I have follwoed by the following steps. Tools -->Preferences -->Audit -->Profile -->Rule -- > Ja

  • On battery my Satellite A100-233 runs only 1 hour

    Hi I would like to know if it is normal that the battery lasts only 1 hour. All I do is either browse on internet or use word doc. or power point presentation. I can't watch a dvd without using power supply due to the battery. I would also like to kn

  • Hidden MP3 Files? Zen Mic

    Here's a problem. I have some songs that I transferred from computer to Zen Micro. For some reason, the names/artists did not transfer, but the audio is there. When I use a Media or File explorer to view the contents of my Micro so I can correct this

  • Dulicates, Thumbs and more...

    Sorry, this is going to be long, I hope someone patient doesn't mind reading through and helping me out! We recently bought a new iMac and I've been transferring our iPhoto libraries from where they were backed up on an external server. All the file

  • ICloud calendar has disappeared from Outlook 2007

    Hi folks, I've been searching the net and discussions for my particular problem and can't find it and I don't have a lot of time. Here goes. I moved from  MobileMe to iCloud a few weeks ago and have my calendar and contacts etc sync with my iPhone, i