DB2 9.1 support

Hi,
Can someone tell me when kodo support for DB2 9.1 will be added?
Thanks,
Jim
http://edocs.bea.com/kodo/docs41/supp_configs/supp_configs.html

Thank you for your response. ok ..So Note 116845 says that End of Support Date for DB2 8.1 will be 31-12-2015 ..So it is end of regular maintenance support or end of Extended Support from SAP ?
Thanks  in Advance.
Regards,
Saurabh

Similar Messages

  • Is HS Generic Connectivity(db2/400 odbc) supports Distributed Transaction?

    hi,
    Is HS Generic Connectivity(db2/400 odbc) supports Distributed Transaction?
    I am getting an error as follows
    "ORA-02047 cannot join the distributed transaction in progress" when i am trying a transaction, which is inserting in to db2/400 and updating in Oracle.
    if it does not support this, what is the best way
    to do such things using generic connectivity.
    (eg. by committing each sql statement ?)
    my db is oracle 9i 9.2.0.4.0
    remote db is db2/400 connected with client access ODBC.
    Thanks
    BA

    Hi,
    one of the restrictions of generic connectivity is, that distributed transactions are not allowed.
    See manual: 7-6 Oracle9 i Heterogeneous Connectivity Administrator's Guide
    - Generic Connectivity agents cannot participate in distributed transactions; they
    support single-site transactions only
    So you can only commit after each statement or you have to use the GATEWAY

  • DB2 on zOS support in SQL Developer?

    I managed to connect to DB2 on zOS by adding third party JDBC drivers from IBM (db2jcc4.jar and db2jcc_license_cisuz.jar) in SQL Developer preferences. During connecting I get an error:
    DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=SYSCAT.SCHEMATA, DRIVER=4.18.60
    The connection actually works and I can successfully execute SQL statements afterwards, however autocompletion and browsing the list of tables doesn't, which renders the tool pretty useless.
    So is this a faulty setup on my part, or does SQL Developer not support DB2 on zOS yet?
    If that is the case, are there any plans/roadmap for at least minimal support of DB2?

    The 3rd party database support in Oracle SQL Developer is provided for helping  you migrate said 3rd party databases to Oracle Database
    Our list of supported platforms

  • DB2 UDB9.1 support as CE10 CMS and Audit database

    Does any body know if DB2 UDB 9.1 is supported as CMS and Audit database for Crystal Enterprise (CE) version 10?
    I know CE 10 is not supported by BO any more, we are in the process of migrating to BOXI but mean while we have a need to upgrade DB2 UDB from 8.1 to 9.1 version.
    Also did any one encounter any issues using CE10 against DB2 UDB 9.1.
    Please advise.
    Thanks

    Hello Romain,
    Thank you very much for your clarifications.
    I guess there was a second question hidden behind my first question.
    Here is the whole story, we had a workshop yesterday with some Consultants specialized on BI.4 technologies. We were discussing the architecture, and more particularly which would be the most suitable Web Application Server :
    * It seems that most SAP Customers choose the bundled WAS : Tomcat 7
    * But as SAP Basis Administrators,we had pretty much no previous exposure to Tomcat/Apache Technologies
    * The Consultants told us that an increasing number of SAP Customers are choosing SAP NW AS for deployment of BOE.war and other BI webapps
    * But so are now considering installing dedicated Netweaver AS on Windows, that will be acting as BI 4.1 Application Servers. We do not plan to deploy BI 4.1 applications on any of our existing  NW AS ,as they have been installed on HP-UX ( not supported by BI.4 )
    The only problem with that is that you can not install a Netweaver AS, without its corresponding Database, so I was wondering if that New Oracle Database installed only when deploying"NW AS/BI 4 Web application Tier", could be used as the CMS/Audit Database.
    Your latest answer seems to suggest that it is definitely not a good idea.
    The thing is , that we do not want to end up with two databases per Landscape tier (DEV,QAS,PRD)
    I hope it is a bit more clear.
    Thank you

  • DB2 Migration from Windows - Linux supported with Backup/Restore ?

    Hi folks,
    we have to do a DB2 V9.1 migration from Windows -> Linux. Both servers are Intel based. Is it official supported by SAP to do this without SAP migration tools? E.g. with a backup/restore or redirected restore? I heard about it, but i'm not sure.
    Thanks a lot
    Jochen
    Edited by: Jochen Raab on Mar 1, 2010 5:40 PM

    Hi Jochen,
    Please have a look at the DB2 docu.
    http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0005960.html
    It clearly stats that Linux and Windows are not compatible.
    DB2® database systems support some backup and restore operations between different operating systems and hardware platforms.
    The supported platforms for DB2 backup and restore operations can be grouped into one of three families:
    Big-endian Linux® and UNIX®
    Little-endian Linux and UNIX
    Windows®
    A database backup from one platform family can only be restored on any system within the same platform family. For Windows operating systems, you can restore a database created on DB2 Universal Database (UDB) V8 on a DB2 Version 9 database system. For Linux and UNIX operating systems, as long as the endianness (big endian or little endian) of the backup and restore platforms is the same, you can restore backups that were produced on DB2 UDB V8 on DB2 Version 9.
    So you need to do an eport/import.
    Regards,
      Joachim

  • DB2 support for Crystal Reports for Enterprise And Unx errors

    Hi,
    I have a requirement to create a report in CrystalReports for Enterprise 4 sourcing data from Oracle 11 and IBM DB2 V9 databases. My first approach is to create relational connections for both the databases in the BO Repository (using Universe designer) and use them directley in the CR for Enterprise. Here I was able to create the two connections but unable to use the DB2 connnection in the report. I get the below error:
    "The Database DB2V9 is not supported".
    Is DB2 is a supported database for Crystal reports for Enterprise ??
    My second approach is to create a multisource universe using IDT. Here when I try to create the Datafoundation layer, I get to see the tables from the DB2 databasae but When I expand the Oracle connection, I get this error: "conversion from UTF8 to charset failed: encoding not loaded".
    Im unable to create a multisource universe at all no matter what connections I use.
    Here is some additional info:
    SAP BI4.1 SP1
    Windows 2008 R2 servers
    Oracle 11g
    IBM DB2 V9.7
    Any suggestions please!
    Thanks,
    Ravinder

    Hi,
    First of all I would strongly advice you to only use IDT for your universe development. The old Universe Designer is a legacy tool and should not be used unless you are using products that doesn't support IDT universes.
    The issue you are facing for your Oracle connection is likely caused by a missing path variable.
    Add "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64" to the PATH environment variables on the SAP Business Objects Enterprise server.
    Restart the SIA
    NOTE: Modify the path in case the SAP BusinessObjects Enterprise is installed in different folder.
    Hope this helps.
    Cheers,
    Josh

  • Central instance can not startup when i install the SAP /DB2 9 env

    Hi,
    could  anybody help me?   I just installed the SAP /db2 V9.1 on HACMP cluster envrioment . By now , the SCS, ASCS, DB instance installation have been  OK, Unfortunately , an
    error occurs when I installed the CI.
    the error message is that "ABAP Database db must be started on remote server "  i check the trans.log , the error message is "DbSlConnect to 'AE1' as 'sapae1' failed"  the detail informatioin ,please check the the following trans.log.  but i can startup and activate the database, i can connect to db with sapae1 and sapae1 user with password. 
    first i install the DB2 software and db2 instance with the virtual hostname dbae1. i found the hostname in the db2cfg.log is not virtual hostname but physical name. i don't know what happens.  In order to keep the hostname the same, i installed the CI on sapaix01, the error message is the same as before.  i have upgrade the sap kernel and reinstall the CI again, the error is the same as before too Could you give me some suggestion.
    First  let me describe our cluster enviroment
    For CI, and DI are not a Single point of failure  , so the DI and CI
    are out of cluster.     The cluster enviroment just includes the
    SCSASCS and DB instance. SCSASCS is installed on sapaix02, DB instance is installed on sapaix01
       1. Host name 
    sapaix01  : DB instance and DI  (visual hostname dbae1)
    sapaix02:   SCS,ASCS, CI        (visual hostname scsae1)
      2. file systems  (sapaix01 DB instance )
    Sapaix01
    Filesystem    512-blocks      Free %Used    Iused %Iused Mounted on
    /dev/hd4         6291456   4792544   24%     2808     1% /
    /dev/hd2        13107200   6175040   53%    73295    10% /usr
    /dev/hd9var     13107200  12816904    3%     1336     1% /var
    /dev/hd3        61603840  35610304   43%     3844     1% /tmp
    /dev/fwdump       786432    785656    1%        4     1%
    /var/adm/ras/platform
    /dev/hd1         1048576   1016152    4%      213     1% /home
    /proc                  -         -    -         -     -  /proc
    /dev/hd10opt     4194304   2512624   41%     6241     3% /opt
    /dev/lvusrsapae1d10   41943040  41935984    1%        4     1%
    /usr/sap/AE1/D10      (Local file system)
    /dev/lvdb2ae1   20971520  20927640    1%       38     1% /db2/AE1
    /dev/lvdb2logs   20971520  18346424   13%       25     1%
    /db2/AE1/log_dir
    /dev/lvdb2archive   41943040  41935984    1%        4     1%
    /db2/AE1/log_archive
    /dev/lvae1sapdata1  104857600  18817168   83%       47     1%
    /db2/AE1/sapdata1
    /dev/lvae1sapdata2  104857600  18817400   83%       48     1%
    /db2/AE1/sapdata2
    /dev/lvae1sapdata3  104857600  18817184   83%       48     1%
    /db2/AE1/sapdata3
    /dev/lvae1sapdata4  104857600  18817168   83%       48     1%
    /db2/AE1/sapdata4
    /dev/lvdb2db2ae1   20971520  19874760    6%     3931     1% /db2/db2ae1
    /dev/lvae1saptemp   20971520  20967584    1%       12     1%
    /db2/AE1/saptemp1
    /dev/lvdb2db2as   10485760  10483504    1%        4     1% /db2/db2as
    /dev/lvae1db2dump   10485760  10470600    1%        8     1%
    /db2/AE1/db2dump
    scsae1:/export/usr/sap/trans   20971520  20967592    1%       16     1%
    /usr/sap/trans
    scsae1:/export/sapmnt/AE1   12582912   9886168   22%     1529     1%
    /sapmnt/AE1
    10.241.13.54:/software2 1755152384 1154051696   35%    62702     1%
    /software2
    For the database version is 9.1 , so I installed the db2 software in
    /db2/db2ae1/v9 , and db2 client software in /opt/IBM/db2/V9.1  (for DI)
    on sapaix01,  db2 client software in /opt/IBM/db2/V9.1  (I installed the
    db software with virtual hostname dbae1 not sapaix01 )
    sapaix02
    Filesystem    512-blocks      Free %Used    Iused %Iused Mounted on
    /dev/hd4         6291456   4915592   22%     2790     1% /
    /dev/hd2        13107200   6177120   53%    73643    10% /usr
    /dev/hd9var     13107200  12857456    2%     1311     1% /var
    /dev/hd3        21495808  16955192   22%     3283     1% /tmp
    /dev/fwdump       786432    785656    1%        4     1%
    /var/adm/ras/platform
    /dev/hd1         1048576   1046848    1%      105     1% /home
    /proc                  -         -    -         -     -  /proc
    /dev/hd10opt     4194304   2197776   48%     9002     4% /opt
    /dev/lvusrsapae1   20971520  20966872    1%       47     1% /usr/sap/AE1
    /dev/lvae1ascs01   10485760  10243360    3%       86     1%
    /usr/sap/AE1/ASCS01
    /dev/lvae1scs00   20971520  20706584    2%       97     1%
    /usr/sap/AE1/SCS00
    /dev/lvsapmntae1   12582912   9886168   22%     1529     1%
    /export/sapmnt/AE1
    /dev/lvusrsaptrans   20971520  20967592    1%       16     1%
    /export/usr/sap/trans
    scsae1:/export/sapmnt/AE1   12582912   9886168   22%     1529     1%
    /sapmnt/AE1
    scsae1:/export/usr/sap/trans   20971520  20967592    1%       16     1%
    /usr/sap/trans
    10.241.13.54:/software2 1755152384 1154051696   35%    62702     1%
    /software2
    3. hosts file    the file is the same on sapaix01 and sapaix02
    10.241.13.121   dbae1
    10.241.13.125   scsae1
    10.10.11.1      sapaix01_boot1
    10.10.11.2      sapaix02_boot1
    10.10.10.1      sapaix01_boot2
    10.10.10.2      sapaix02_boot2
    10.241.13.71    sapaix01  sapaix01_per
    10.241.13.72     sapaix02 sapaix02_per
    4. the installation guide and error message  please check the attachment
    <<installation_and errorlog.zip>>
    5. I run  db2ilist command  nothing disppear
    I have another questions
    *      whether does DB2 9.1  support installation on the diffirence
    directory (default is /opt/IBM/db2/V9.1 my installation is
    /db2/db2ae1/V9)?
    *      Whether does DB2 9 installation has some relationship with
    hostname ?
    *       Why  db2ilist command result is nothing after I finished the
    DB instance installation ?
    trans.log 
    "trans.log" 143 lines, 14041 characters
    4 ETW000 R3trans version 6.14 (release 700 - 15.06.07 - 15:50:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 10.03.2008 - 20:25:40
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: R3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [dev trc     ,00000]  Mon Mar 10 20:25:40 2008                              70  0.000070
    4 ETW000  [dev trc     ,00000]  db_con_init called                                    25  0.000095
    4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                             42  0.000137
    4 ETW000  [dev trc     ,00000]  Loading DB library '/usr/sap/AE1/SYS/exe/run/dbdb6slib.o' ...
    4 ETW000                                                                              60  0.000197
    4 ETW000  [dev trc     ,00000]  load shared library (/usr/sap/AE1/SYS/exe/run/dbdb6slib.o), hdl 0
    4 ETW000                                                                            1018  0.001215
    4 ETW000  [dev trc     ,00000]  Library '/usr/sap/AE1/SYS/exe/run/dbdb6slib.o' loaded
    4 ETW000                                                                              39  0.001254
    4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library /usr/sap/AE1/SYS/exe/run/dbdb6slib.o
    4 ETW000                                                                              43  0.001297
    4 ETW000  [dev trc     ,00000]  Version of '/usr/sap/AE1/SYS/exe/run/dbdb6slib.o' is "700.08", patchlevel (0.133)
    4 ETW000                                                                             282  0.001579
    4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library /usr/sap/AE1/SYS/exe/run/dbdb6slib.o
    4 ETW000                                                                              42  0.001621
    4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library /usr/sap/AE1/SYS/exe/run/dbdb6slib.o
    4 ETW000                                                                              43  0.001664
    4 ETW000  [dev trc     ,00000]  New connection 0 created                              29  0.001693
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 00
    0, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              50  0.001743
    4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         41  0.001784
    4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
    4 ETW000                                                                              40  0.001824
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000
    , con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              47  0.001871
    4 ETW000  [dev trc     ,00000]  DB2 library successfully loaded DB2 library '/db2/db2ae1/sqllib/lib64/libdb2.a(shr_64.o)' suc
    cessfully loaded
    4 ETW000                                                                            9175  0.011046
    4 ETW000  [dev trc     ,00000]  DB6 (DB2 UDB) UNICODE database interface 700.08 [opt]
    4 ETW000                                                                              42  0.011088
    4 ETW000  [dev trc     ,00000]  DB6 shared library (dbdb6slib) patchlevels            24  0.011112
    4 ETW000  [dev trc     ,00000]    (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (note 150037)
    4 ETW000                                                                              42  0.011154
    4 ETW000  [dev trc     ,00000]    (0.8) Support of SDBUPDEXCL (note 847616)           25  0.011179
    4 ETW000  [dev trc     ,00000]    (0.9) DB6: use export file for dbdb6slib (note 835135)
    4 ETW000                                                                              40  0.011219
    4 ETW000  [dev trc     ,00000]    (0.9) DB6: Core in getAndBindSQLDA (note 833183)
    4 ETW000                                                                              39  0.011258
    4 ETW000  [dev trc     ,00000]    (0.10) DB6: link dbdb6slib.dll on windows with libdb6.obj (note 761159)
    4 ETW000                                                                              51  0.011309
    4 ETW000  [dev trc     ,00000]    (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (note 851474)
    4 ETW000                                                                              40  0.011349
    4 ETW000  [dev trc     ,00000]    (0.15) DB6: wrong CAST for short string ABAP type (note 861905)
    4 ETW000                                                                              40  0.011389
    4 ETW000  [dev trc     ,00000]    (0.17) DB6: special characters in sidadm passwd (note 865839)
    4 ETW000                                                                              40  0.011429
    4 ETW000  [dev trc     ,00000]    (0.21) DB6: no SAP_INFO comments (note 873889)
    4 ETW000                                                                              39  0.011468
    4 ETW000  [dev trc     ,00000]    (0.22) DB6: hints: get correlation names from view texts (note 868888)
    4 ETW000                                                                              41  0.011509
    4 ETW000  [dev trc     ,00000]    (0.23) DB6: hints: get correlation names from view texts (note 868888)
    4 ETW000                                                                              41  0.011550
    4 ETW000  [dev trc     ,00000]    (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_REF (note 883402)
    4 ETW000                                                                              40  0.011590
    4 ETW000  [dev trc     ,00000]    (0.27) DB6: activate value compression (note 886231)
    4 ETW000                                                                              40  0.011630
    4 ETW000  [dev trc     ,00000]    (0.28) DB6: optimization guidelines on views part 2 (note 868888)
    4 ETW000                                                                              40  0.011670
    4 ETW000  [dev trc     ,00000]    (0.30) DB6: no SQL trace for SQLCancel (note 892111)
    4 ETW000                                                                              40  0.011710
    4 ETW000  [dev trc     ,00000]    (0.33) DB6: append SAP_TA comment (note 873889)
    4 ETW000                                                                              39  0.011749
    4 ETW000  [dev trc     ,00000]    (0.34) DB6: activate value compression with quoted names (note 886231)
    4 ETW000                                                                              41  0.011790
    4 ETW000  [dev trc     ,00000]    (0.36) DB6: Repeat isolated DDL statements after SQL0911 (note 901338)
    4 ETW000                                                                              41  0.011831
    4 ETW000  [dev trc     ,00000]    (0.41) DB6: add V9 to list of supported DB2 releases (note 912386)
    4 ETW000                                                                              41  0.011872
    4 ETW000  [dev trc     ,00000]    (0.50) DB6: reread passwords for secondary connections (note 931742)
    4 ETW000                                                                              41  0.011913
    4 ETW000  [dev trc     ,00000]    (0.52) DB6: double quote table names in optguidelines (note 868888)
    4 ETW000                                                                              41  0.011954
    4 ETW000  [dev trc     ,00000]    (0.54) DB6: error handling in DBSL CLP (note 940260)
    4 ETW000                                                                              39  0.011993
    4 ETW000  [dev trc     ,00000]    (0.69) DB6: technical support of DB2 CLI driver (note 962892)
    4 ETW000                                                                              40  0.012033
    4 ETW000  [dev trc     ,00000]    (0.73) DB6: log table name on TRUNCATE failure (note 970743)
    4 ETW000                                                                              40  0.012073
    4 ETW000  [dev trc     ,00000]    (0.79) DB6: column type XML in index size calculation (note 982993)
    4 ETW000                                                                              41  0.012114
    4 ETW000  [dev trc     ,00000]    (0.82) DB6: CAST for SSTRING data types (note 989568)
    4 ETW000                                                                              47  0.012161
    4 ETW000  [dev trc     ,00000]    (0.86) DB6: long runtimes for R3szchk (note 1000847)
    4 ETW000                                                                              39  0.012200
    4 ETW000  [dev trc     ,00000]    (0.88) DB6: patch collection Dec 06 (note 1005574)
    4 ETW000                                                                              40  0.012240
    4 ETW000  [dev trc     ,00000]    (0.96) DB6: patch collection Jan 07 (note 1017852)
    4 ETW000                                                                              39  0.012279
    4 ETW000  [dev trc     ,00000]    (0.97) DB6: CLP commands with DB2 CLI Driver (note 1024102)
    4 ETW000                                                                              41  0.012320
    4 ETW000  [dev trc     ,00000]    (0.99) DB6: SUBSTITUTE VALUES with FAE statements (note 1028779)
    4 ETW000                                                                              41  0.012361
    4 ETW000  [dev trc     ,00000]    (0.107) DB6: patch collection Apr 07 (note 1047194)
    4 ETW000                                                                              39  0.012400
    4 ETW000  [dev trc     ,00000]    (0.110) DB6: SAP user names ending with non-ASCII char (note 1054555)
    4 ETW000                                                                              41  0.012441
    4 ETW000  [dev trc     ,00000]    (0.113) DB6: work process type in application snapshot (note 1059905)
    4 ETW000                                                                              41  0.012482
    4 ETW000  [dev trc     ,00000]    (0.114) DB6: connect using SAPDBHOST and DB2DB6_SVCENAME (note 1062049)
    4 ETW000                                                                              41  0.012523
    4 ETW000  [dev trc     ,00000]    (0.117) DB6: patch for execution of long DDL statements (note 1069658)
    4 ETW000                                                                              41  0.012564
    4 ETW000  [dev trc     ,00000]    (0.122) DB6: SNAPSHOT_TBS_CFG table function is deprecated (note 1077963)
    4 ETW000                                                                              41  0.012605
    4 ETW000  [dev trc     ,00000]    (0.123) DB6: CLP commands on Windows with V9.1 (note 1080149)
    4 ETW000                                                                              40  0.012645
    4 ETW000  [dev trc     ,00000]    (0.124) DB6: Set DB2CODEPAGE=819 for non-Unicode (note 1084400)
    4 ETW000                                                                              40  0.012685
    4 ETW000  [dev trc     ,00000]    (0.126) DB6: reuse optguidelines on FAE statements (note 1087375)
    4 ETW000                                                                              41  0.012726
    4 ETW000  [dev trc     ,00000]    (0.126) DB6: Enforce DB2CODEPAGE=819 for non-Unicode environments (note 1084400)
    4 ETW000                                                                              42  0.012768
    4 ETW000  [dev trc     ,00000]    (0.128) DB6: db6_free on invalid memory area (note 1092030)
    4 ETW000                                                                              40  0.012808
    4 ETW000  [dev trc     ,00000]    (0.133) DB6: statement cache enhancements (note 1101031)
    4 ETW000                                                                              40  0.012848
    4 ETW000  [dev trc     ,00000]  Supported features:                                   24  0.012872
    4 ETW000  [dev trc     ,00000]  ..retrieving configuration parameters                 24  0.012896
    4 ETW000  [dev trc     ,00000]  ..done                                               126  0.013022
    4 ETW000  [dev trc     ,00000]  Running with UTF-8 Unicode                            25  0.013047
    4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1640] CON = 0 (BEGIN)
    4 ETW000                                                                           67222  0.080269
    4 ETW000  [dev trc     ,00000]  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL30082N  Security processing failed
    with reason "24" ("USERNAME
    4 ETW000                                                                              48  0.080317
    4 ETW000  [dev trc     ,00000]  &+     AND/OR PASSWORD INVALID").  SQLSTATE=08001
    4 ETW000                                                                              45  0.080362
    4 ETW000  [dev trc     ,00000]  &+
    4 ETW000                                                                              45  0.080407
    4 ETW000  [dev trc     ,00000]  &+
    4 ETW000                                                                              46  0.080453
    4 ETW000  [dev trc     ,00000]  &+
    4 ETW000                                                                              45  0.080498
    4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1640] (END)          26  0.080524
    4 ETW000  [dbdb6.c     ,00000]  *** ERROR => DbSlConnect to 'AE1' as 'sapae1' failed
    4 ETW000                                                                              71  0.080595
    2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'AE1'"

    Hi,
    have you tried to connect on the command line (instead of using R3trans) ?
    db2 connect to AE1 user sapae1 using .....
    If this works and you have verified that the DB2DB6EKEY is set properly, use dscdb6up to update the password in the password file dscbd6.conf.
    Then try again to use R3trans to connect.
    Best regards,
      Jens

  • Migrate DB2 on an IBM OS390 VM/CMS mainframe to Oracle on NT

    The migration workbench documentation indicates that DB2 on an AS/400 can be converted to Oracle on NT. Has anyone attempted to convert DB2 on an IBM OS390 to Oracle on NT?
    Also, the workbench documentation indicates that stored procedures are not converted from DB2 to Oracle, but they are for Sybase and Informix. Is this true? If so, why doesn't the workbench convert DB2 stored procedures?

    Hi David,
    the latest version of the Migration Workbench (Version 2.0.2.0.0) supports the migration of DB2\400 V4R3 and V4R5 databases to
    Oracle. The Workbench does not currently support migrations from DB2 on the OS\390 and there are no plans to
    provide this through a migration workbench plugin in the short term. The next version of the Workbench, due out in July,
    will support the migration of DB2 UDB v6 and v7 (certified on the MS Windows platform).
    Currently, none of the DB2 Workbench plugins support the migration of parsable objects i.e. stored procedures, triggers,
    etc.. This capability may be added in future releases of the Workbench depending on the demand. Again, there are no
    immediate plans to include a parser with the DB2 plugins.
    If you would like to provide us with any input on what parser capabilities you would like to see in the DB2 plugins (i.e. a
    parser for a certain language?) then we would be delighted to recieve your information.
    I hope this information is of help,
    Tom - Team OMWB.

  • DB2 7.0.2 problem with jdbc type 2 app-driver (CLI0601E / CLI0616E)

    Hi folks,
    has anybody encounters an exception like this:
    javax.jdo.JDODataStoreException:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
    [SQL=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = 8]
    [PRE=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = ?]
    [IBM][JDBC-Treiber] CLI0601E Ung__ltige Anweisungskennung oder Anweisung
    ist beendet. SQLSTATE=S1000 [code=-99999;state=S1000]
    NestedThrowables:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
    [SQL=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = 8]
    [PRE=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = ?]
    [IBM][JDBC-Treiber] CLI0601E Ung__ltige Anweisungskennung oder Anweisung
    ist beendet. SQLSTATE=S1000
    at
    com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwDataStore(SQLExceptions.java:23)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java:381)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadField(StateManagerImpl.java:1987)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:721)
    at de.tolina.nachlass.data.Konto.jdoGetrevisions(Konto.java)
    at de.tolina.nachlass.data.Konto.jdoPreDelete(Konto.java:58)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:313)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:287)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.deletePersistent(StateManagerImpl.java:492)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistentFilter(PersistenceManagerImpl.java:1213)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistent(PersistenceManagerImpl.java:1193)
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:104)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    NestedThrowablesStackTrace:
    COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC-Treiber] CLI0601E Ung__ltige
    Anweisungskennung oder Anweisung ist beendet. SQLSTATE=S1000
    at
    COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwClosedError(SQLExceptionGenerator.java:593)
    at
    COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java:832)
    at
    COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:786)
    at
    com.solarmetric.datasource.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:93)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedQueryInternal(SQLExecutionManagerImpl.java:771)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQueryInternal(SQLExecutionManagerImpl.java:691)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:372)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:356)
    at
    com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1221)
    at
    com.solarmetric.kodo.impl.jdbc.ormapping.OneToManyMapping.load(OneToManyMapping.java:80)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java:375)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadField(StateManagerImpl.java:1987)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:721)
    at de.tolina.nachlass.data.Konto.jdoGetrevisions(Konto.java)
    at de.tolina.nachlass.data.Konto.jdoPreDelete(Konto.java:58)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:313)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:287)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.deletePersistent(StateManagerImpl.java:492)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistentFilter(PersistenceManagerImpl.java:1213)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistent(PersistenceManagerImpl.java:1193)
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:104)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    de.tolina.common.gui.binder.BinderException: Fehler beim L__schen des
    Objekts aufgetreten
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:112)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    kodo.properties:
    com.solarmetric.kodo.impl.jdbc.FlatInheritanceMapping=true
    javax.jdo.option.MsWait=50000
    javax.jdo.option.RestoreValues=true
    com.solarmetric.kodo.DefaultFetchThreshold=30
    com.solarmetric.kodo.EnableQueryExtensions=false
    javax.jdo.option.Multithreaded=true
    javax.jdo.option.IgnoreCache=false
    com.solarmetric.kodo.CacheReferenceSize=1000
    javax.jdo.option.NontransactionalWrite=false
    com.solarmetric.kodo.impl.jdbc.WarnOnPersistentTypeFailure=true
    javax.jdo.option.NontransactionalRead=true
    javax.jdo.option.RetainValues=true
    com.solarmetric.kodo.DefaultFetchBatchSize=10
    com.solarmetric.kodo.impl.jdbc.SequenceFactoryClass=com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory
    com.solarmetric.kodo.DataCacheClass=
    com.solarmetric.kodo.UseSoftTransactionCache=false
    com.solarmetric.kodo.ProxyManagerClass=com.solarmetric.kodo.util.SimpleProxyManager
    javax.jdo.option.Optimistic = true
    javax.jdo.option.MinPool=1
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    com.solarmetric.kodo.impl.jdbc.AutoReturnTimeout=10
    javax.jdo.option.MaxPool=10
    # kodo 2.4-license-key, in produktionsversion im java-code
    com.solarmetric.kodo.LicenseKey =
    # db2
    javax.jdo.option.ConnectionURL = jdbc:db2:myapp
    javax.jdo.option.ConnectionDriverName = COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionUserName = xxx
    javax.jdo.option.ConnectionPassword = xxx
    # oracle
    #javax.jdo.option.ConnectionURL = jdbc:oracle:thin:@SESCG:1521:myapp
    #javax.jdo.option.ConnectionDriverName = oracle.jdbc.driver.OracleDriver
    #javax.jdo.option.ConnectionUserName = xxx
    #javax.jdo.option.ConnectionPassword = xxx
    I think there is a connection between this error and bug #520 in kodos bug
    db.
    The message of the CLI means, that either the connection is closed before
    the prepared statement is completed or the statement itself is closed...
    Sometimes I get also CLI0116E-Error (invalid transaction state).
    Anyone an idea?
    PS: we bought a kodo license and would't like to be sorry about that - so
    please help!!
    Best regards Claudius

    Claudius-
    There are a couple possibilities. First, it might be some JDBC driver
    mismatch, as reported at:
    http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/document.d2w/report?&fn=1007004
    The other possibility is that cached PreparedStatements are being timed
    out on the server side and closed. You can investigate disabling the
    statement timeout on the server side (see the DB2 docs), or else you can
    disable prepared statement pooling (which will result in a small to
    medium performance hit). You can disable pooling by setting
    com.solarmetric.kodo.impl.jdbc.StatementCacheMaxSize to 0. See:
    http://docs.solarmetric.com/manual.html#com.solarmetric.kodo.impl.jdbc.StatementCacheMaxSize
    Please let us know if the problem persists, and, if so, some more
    details like when this happends, how reproducable it is, and a more complete
    log.
    In article <[email protected]>, Claudius Gr__ver wrote:
    Hi folks,
    has anybody encounters an exception like this:
    javax.jdo.JDODataStoreException:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
    [SQL=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = 8]
    [PRE=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = ?]
    [IBM][JDBC-Treiber] CLI0601E Ung__ltige Anweisungskennung oder Anweisung
    ist beendet. SQLSTATE=S1000 [code=-99999;state=S1000]
    NestedThrowables:
    com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
    [SQL=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = 8]
    [PRE=SELECT t0.JDOIDX, t0.JDOCLASSX, t0.JDOLOCKX, t0.COMMENTX, t0.GKX,
    t0.NRX, t0.REFERENZX, t0.SALDOX, t0.SALDOTYPX, t0.TIMEX, t0.TYPX,
    t0.USERX, t0.USERIDX, t0.ZINSENX FROM KontoRevision t0 WHERE t0.REFERENZX
    = ?]
    [IBM][JDBC-Treiber] CLI0601E Ung__ltige Anweisungskennung oder Anweisung
    ist beendet. SQLSTATE=S1000
    at
    com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwDataStore(SQLExceptions.java:23)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java:381)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadField(StateManagerImpl.java:1987)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:721)
    at de.tolina.nachlass.data.Konto.jdoGetrevisions(Konto.java)
    at de.tolina.nachlass.data.Konto.jdoPreDelete(Konto.java:58)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:313)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:287)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.deletePersistent(StateManagerImpl.java:492)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistentFilter(PersistenceManagerImpl.java:1213)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistent(PersistenceManagerImpl.java:1193)
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:104)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    NestedThrowablesStackTrace:
    COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC-Treiber] CLI0601E Ung__ltige
    Anweisungskennung oder Anweisung ist beendet. SQLSTATE=S1000
    at
    COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throwClosedError(SQLExceptionGenerator.java:593)
    at
    COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java:832)
    at
    COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:786)
    at
    com.solarmetric.datasource.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:93)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedQueryInternal(SQLExecutionManagerImpl.java:771)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQueryInternal(SQLExecutionManagerImpl.java:691)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:372)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeQuery(SQLExecutionManagerImpl.java:356)
    at
    com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1221)
    at
    com.solarmetric.kodo.impl.jdbc.ormapping.OneToManyMapping.load(OneToManyMapping.java:80)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java:375)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.loadField(StateManagerImpl.java:1987)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:721)
    at de.tolina.nachlass.data.Konto.jdoGetrevisions(Konto.java)
    at de.tolina.nachlass.data.Konto.jdoPreDelete(Konto.java:58)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:313)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.setJDOState(StateManagerImpl.java:287)
    at
    com.solarmetric.kodo.runtime.StateManagerImpl.deletePersistent(StateManagerImpl.java:492)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistentFilter(PersistenceManagerImpl.java:1213)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.deletePersistent(PersistenceManagerImpl.java:1193)
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:104)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    de.tolina.common.gui.binder.BinderException: Fehler beim L__schen des
    Objekts aufgetreten
    at de.tolina.common.gui.binder.Binder.deleteDataObject(Binder.java:112)
    at
    de.tolina.nachlass.gui.KontoPanel$2.actionPerformed(KontoPanel.java:88)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1445)
    at
    javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1499)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:373)
    at
    javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:245)
    at
    javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:211)
    at java.awt.Component.processMouseEvent(Component.java:3710)
    at java.awt.Component.processEvent(Component.java:3539)
    at java.awt.Container.processEvent(Container.java:1159)
    at java.awt.Component.dispatchEventImpl(Component.java:2588)
    at java.awt.Container.dispatchEventImpl(Container.java:1208)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at
    java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2446)
    at
    java.awt.LightweightDispatcher.processMouseEvent(Container.java:2211)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2120)
    at java.awt.Container.dispatchEventImpl(Container.java:1195)
    at java.awt.Window.dispatchEventImpl(Window.java:923)
    at java.awt.Component.dispatchEvent(Component.java:2492)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:334)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:126)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:80)
    kodo.properties:
    com.solarmetric.kodo.impl.jdbc.FlatInheritanceMapping=true
    javax.jdo.option.MsWait=50000
    javax.jdo.option.RestoreValues=true
    com.solarmetric.kodo.DefaultFetchThreshold=30
    com.solarmetric.kodo.EnableQueryExtensions=false
    javax.jdo.option.Multithreaded=true
    javax.jdo.option.IgnoreCache=false
    com.solarmetric.kodo.CacheReferenceSize=1000
    javax.jdo.option.NontransactionalWrite=false
    com.solarmetric.kodo.impl.jdbc.WarnOnPersistentTypeFailure=true
    javax.jdo.option.NontransactionalRead=true
    javax.jdo.option.RetainValues=true
    com.solarmetric.kodo.DefaultFetchBatchSize=10
    com.solarmetric.kodo.impl.jdbc.SequenceFactoryClass=com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory
    com.solarmetric.kodo.DataCacheClass=
    com.solarmetric.kodo.UseSoftTransactionCache=false
    com.solarmetric.kodo.ProxyManagerClass=com.solarmetric.kodo.util.SimpleProxyManager
    javax.jdo.option.Optimistic = true
    javax.jdo.option.MinPool=1
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    com.solarmetric.kodo.impl.jdbc.AutoReturnTimeout=10
    javax.jdo.option.MaxPool=10
    # kodo 2.4-license-key, in produktionsversion im java-code
    com.solarmetric.kodo.LicenseKey =
    # db2
    javax.jdo.option.ConnectionURL = jdbc:db2:myapp
    javax.jdo.option.ConnectionDriverName = COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionUserName = xxx
    javax.jdo.option.ConnectionPassword = xxx
    # oracle
    #javax.jdo.option.ConnectionURL = jdbc:oracle:thin:@SESCG:1521:myapp
    #javax.jdo.option.ConnectionDriverName = oracle.jdbc.driver.OracleDriver
    #javax.jdo.option.ConnectionUserName = xxx
    #javax.jdo.option.ConnectionPassword = xxx
    I think there is a connection between this error and bug #520 in kodos bug
    db.
    The message of the CLI means, that either the connection is closed before
    the prepared statement is completed or the statement itself is closed...
    Sometimes I get also CLI0116E-Error (invalid transaction state).
    Anyone an idea?
    PS: we bought a kodo license and would't like to be sorry about that - so
    please help!!
    Best regards Claudius
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • Native sequences in DB2

    Hi,
    I've just read in the docs that native sequences for DB2 are not supported.
    Blissfully unaware of this, we have been using native sequencing with db2 (and toplink 9.0.3) and it worked OK. After updating to 9.0.4, it stopped working (same id is used several times).
    What is the problem with db2 sequences? Is there a plan to support them some time in the future?
    Thank you,
    Ana Oleski

    Cache connect does not cache Oracle sequences; so if you need to share the same Oracle sequence in both TimesTen and Oracle, then you will need to go to Oracle and retrieve the nextval each time.
    Simon

  • How can I get conneced to DB2 Express with JDBC?

    Hi,
    I have DB2 Express 8.1 installed in my computer, can I get connected to it by using JDBC step by step?
    Or is there any tutorial to show how to do this?
    Thank you !

    There is lots of information on using DB2 UDB Express with Java, including JDBC at the IBM developerWorks site. A good first article is: www.ibm.com/developerworks/db2/zones/java/bigpicture.html
    It gives a good overview of Java support for DB2. DB2 Express supports everything the rest of the DB2 product does. You build for one edition and can support on all other editions and platforms. Express is just the least expensive option in the family.
    Another great resource is the DB2 Information Center. It includes all the information on DB2 including Java support and programming: publib.boulder.ibm.com/infocenter/db2help

  • Jdbc: get insert id / db2

    I'm using the JTOpen tool to connect to an iSeries DB2 with jdbc.
    I am looking for a way to retrieve the last insert id after an insert. My ID field aut-increments, so I just want to find out how to get the newly created ID.

    Do your DB2 JDBC driver supports JDBC 3.0 ? Try this:
    Reading the "JDBC� 3.0 Specification - Final Release":
    3.1 Overview of changes
    Retrieval of auto-generated keys
    Added a means of retrieving values from columns containing automatically
    generated values.
    13.6 Retrieving Auto Generated Keys
    Many database systems have a mechanism that automatically generates a unique
    key field when a row is inserted. The method Statement.getGeneratedKeys,
    which can be called to retrieve the value of such a key, returns a ResultSet object
    with a column for each automatically generated key. A flag indicating that any auto
    generated columns should be returned is passed to the methods execute,
    executeUpdate or prepareStatement when the statement is executed or
    prepared.
    Statement stmt = conn.createStatement();
    // indicate that the key generated is going to be returned
    int rows = stmt.executeUpdate("INSERT INTO ORDERS " +
    "(ISBN, CUSTOMERID) " +
    "VALUES (195123018, �BILLG�)",
    Statement.RETURN_GENERATED_KEYS);
    ResultSet rs = stmt.getGeneratedKeys();
    boolean b = rs.next();
    if (b == true) {
    // retrieve the new key value
    }CODE EXAMPLE 13-28 Retrieving auto generated keys
    Additional methods allow the ordinals or names of the columns that should be
    returned to be specified. In CODE EXAMPLE 13-29 the Statement method
    executeUpdate is called with two parameters, the first is the SQL statement to be
    executed, the second is an array of String containing the column name that should
    be returned when getGeneratedKeys is called:
    String keyColumn[] = {"ORDER_ID"};
    Statement stmt = conn.createStatement();
    int rows = stmt.executeUpdate("INSERT INTO ORDERS " +
    "(ISBN, CUSTOMERID) " +
    "VALUES (966431502, �BILLG�)",
    keyColumn);
    ResultSet rs = stmt.getGeneratedKeys();
    ....CODE EXAMPLE 13-29 Retrieving a named column using executeUpdate and
    getGeneratedKeys
    See the API Specification for more details.
    Calling ResultSet.getMetaData on the ResultSet object returned by
    getGeneratedKeys will produce a ResultSetMetaData object that can be used
    to determine the number, type and properties of the generated keys.
    In some cases, such as in an insert select statement, more than one key may be
    returned. The ResultSet object returned by getGeneratedKeys will contain a
    row for each key that a statement generated. If no keys are generated, an empty
    result set will be returned.
    The concurrency of the ResultSet object returned by getGeneratedKeys must be
    CONCUR_READ_ONLY. The type of the ResultSet object must be either
    TYPE_FORWARD_ONLY or TYPE_SCROLL_INSENSITIVE.
    The method DatabaseMetaData.supportsGetGeneratedKeys returns true if
    a JDBC driver and underlying data source support the retrieval of automatically
    generated keys.

  • Migrate DB2 Connection Question

    I'm trying to migrate an IBM DB2/390 db to Oracle, using SQL Developer Version 2.1.1.64. I was created a userid with read access to the schema owner. I notice there is nothing to migrate and generate says no objects to generate. Do I need some tiype of privileged account or schema owner on the DB2 database? -Thnx

    Currently only LUW DB2 migrations are supported - z/OS DB2 migration is scheduled for a later release. Please see:
    http://www.oracle.com/technology/products/database/sql_developer/files/supportedmigplatforms.html

  • DB2 - Oracle: problem with capturing source model

    After starting the capture process, the logging window shows a line
    "Capturing loaded table: <table-name>" for each table, and one line
    "Capturing Tables Loaded: 164, Tables NOT Loaded: 0", which sounds about right.
    It then prints messages about loading groups, and finally the two lines:
    "Capturing Loading Table Aliases"
    "Capturing Loaded table alias: CL"
    At that point, it stops. There are 3 buttons at the bottom,
    "Suspend Logging", "Abort", "Help".
    The OMWB Java client shows "Loading Source Model..." in the "UDB7 Source Model" tab, and "No objects have been mapped" in the "Oracle Model" tab.
    Clicking on the "Abort" button in the loggin window results in the message "unable to abort, please restart application".
    I have no experience at all with the omwb tool, greatly appreciate any feedback.
    Thanks !

    Thanks for your reply.
    Below is the error.log.
    I couldn't get the 7.2 Client to work, so I am using a IBM UDB 8.0 Client to
    connect to a 7.2 DB2 database, that's where the message regarding the JDBC driver comes from.
    ** Started : Wed Nov 02 09:37:45 PST 2005
    ** Workbench Repository : Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Repository Connection URL: jdbc:oracle:thin:@localhost:1521:orcl
    ** The following plugins are installed:
    ** IBM DB2 UDB Version 7 Plugin, Production Release 10.1.0.4.0
    ** Active Plugin : UDB7
    Informational: JDBC compatibility test is active.
    *** IBM DB2 UDB Information ***
    Product Name : DB2/LINUX
    Product Version : 07.02.0006
    JDBC Driver Name : IBM DB2 JDBC 2.0 Type 2
    JDBC Driver Version : 08.01.0002
    - (major version) : 8
    - (minor version) : 1
    Informational: IBM DB2 UDB JDBC driver is JDBC 2.0 compliant.
    Informational: You are using an IBM DB2 UDB Version 08.01.0002 JDBC driver against an IBM DB2 UDB Version 07.02.0006 database.
    Informational: IBM DB2 UDB Server supports identity columns.
    java.lang.NullPointerException
         at oracle.mtg.udb6.server.SourceModelLoad.createSourceModelAliasDefinitions(SourceModelLoad.java:537)
         at oracle.mtg.udb6.server.SourceModelLoad.createSourceModelDBDefinitions(SourceModelLoad.java:270)
         at oracle.mtg.udb6.server.SourceModelLoad.loadSourceModel(SourceModelLoad.java:176)
         at oracle.mtg.udb6.ui.CaptureWizard.doCapture(CaptureWizard.java:974)
         at oracle.mtg.udb6.ui.CaptureWizard._runDialog(CaptureWizard.java:832)
         at oracle.mtg.udb6.ui.CaptureWizard.capture(CaptureWizard.java:478)
         at oracle.mtg.migrationUI.ActionMenuHandler._capture(ActionMenuHandler.java:208)
         at oracle.mtg.migrationUI.ActionMenuHandler.run(ActionMenuHandler.java:85)
         at oracle.mtg.migration.WorkerThread.run(Worker.java:268)
    ** Shutdown : Wed Nov 02 11:32:57 PST 2005

  • Db2 database monitoring

    Hi,
       first time i am working db2 database on support project (linux with db2) what are the things i have to monitor on db2 database level daily.appreciate ur help.
    Thanku

    Query seems very generic, info could be found out by googling as well.
    However, if you can't, I would advise you to start with DBACOCKPIT transaction in SAP - most important and easiest way to monitor DB2 in SAP.
    For e.g. please refer the link
    https://websmp108.sap-ag.de/~sapidb/011000358700001298992010E.PDF
    More guides for database monitoring and administration, you can find on service.sap.com and http://www.sdn.sap.com/irj/sdn/db6
    service.sap.com/swdc --> installation n upgrades --> installation n upgrade guides --> NW version --> Operations --> DB guides
    Thanks

Maybe you are looking for