Thanks to WL team for DB2/AS400 driver

Thanks to WL team for DB2/AS400 driver.
With IBM driver we should wait 7 minutes to load 7000+ records.
We had big problem with our customers.
Now it - few seconds.
Thanks,
Oleg.

Hello,
I am not talking about the XI timeouts. But the timeouts which can be used to get the connection timeouts for DB2/AS400 databases.
So please provide that information.
THanks,
soorya

Similar Messages

  • Thanks to Nokia Team for WhatsApp.

    Hello,
    I would like to thank to Nokia Team for providing us the WhatsApp. It works perfectly.
    I request Nokia to do much more efforts to provide many more apps for the Asha 501 users.
    Kudo's to Nokia.

    Yeah.A big Thanks to Nokia Team.  

  • Thanks to Oracle team for great Christmas gift ! (pb on Webcenter link)

    Hi,
    You are very great to give us TP3 for our Christmas gift !
    I've noticed a link problem on this page :
    http://www.oracle.com/technology/software/products/jdev/htdocs/11techpreview.html
    => This link for WebCenter is broken :
    Oracle WebCenter 11g Technology Preview 3
    http://www.oracle.com/technology/products/webcenter/owcs_r11_tech_preview.html
    Thanks you very much for your great job !
    Have a merry Christmas !

    Thanks, it's fixed now.
    -- Brian

  • Thank you Safari Team for new "Reader" feature

    This is a great new feature. I wish I could set Safari up to switch to "Reader" automatically where ever possible. Thank you.

    HI,
    Good article here: http://www.webmonkey.com/2010/06/safari-5s-reader-simplifies-the-web/
    Carolyn

  • Error while installing NW7.3 ABAP for DB2 on z/OS Install DB CLI driver

    Dear Experts,
    i'm installing for the first time NW7.3 ABAP for DB2 on z/OS with AIX application server. Central Services was installed succesfull but next step Install Database on AIX stoped with error (establishConn.log):
    db2radm (release: "720", patch level: "000", version: "Jan 14 2012") begin:28.02.2012 10:54:39
    This is db2radm release: "720", patch level: "120", version: "Jan 14 2012".
    This is db2radm setting up DB2 Connect.
    Message file is /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log.
    db2radm called as: /usr/sap/DW8/SYS/exe/uc/rs6000_64/db2radm -m db2i -P 456 -L DW8DDF -S DW88 -H s10d1 -u SAPADM -p ******** -W primary_only -l /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log
    Adjusting environment
      dbs_db2_ssid=DW88
      SAPDBHOST=s10d1
      dbs_db2_user=SAPADM
      dbs_db2_schema=SAPADM
      dbs_db2_schema8=1
      dbs_db2_pw=********
    Checking environment
      DB host    = s10d1
      SSID       = DW88
      SAPSYSTEMNAME = DW8
    DB2Trc:    000000 CLI_ALLOC_ENV 1
    connect.ini file used: 'connect.ini.for.db2radm'
    Fail over connection list of this application server:
    NAME       = DW88_on_s10d1             
    USER       = SAPADM                    
    PASSWORD   = <***>                     
    SCHEMA     = SAPADM                    
    PS         = SAP0907U                  
    LOCATION   = DW8DDF                    
    SSID       = DW88                      
    HOST       = s10d1                     
    PORT       = 456                       
    RETRY_CNT  = 3                         
    SLEEP_TIME = 0                         
    DB2Trc: trace level of dbdb2cli set to 1
    COLLECTION ID used is "SAP0907U"
    DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W  There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD.  SQL
    use lib_dbsl for DB2 version V9.
    Callback functions for dynamic profile parameter registered
    DbSl library successfully loaded.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    SQL DRIVER VERSION is "09.07.0003"
    DB2Connect driver identified as THIN CLIENT
    Now I'm connected to DW88_on_s10d1
    DB2 DBMS version 09.01.0005
    DB2 LOCATION name DW8DDF
    (HYB): Info: Using OLD dbsl support.
    DB2 connect shared library loaded successfully.
    09.07.0003DB2Connect driver identified as THIN CLIENT
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    connection profile /usr/sap/DW8/SYS/global/connect.ini opened.
    >>>>>> dump of connection profile
    ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
      [DEFAULT_GROUP]
      CON1=DW88_on_s10d1
      [DW88_on_s10d1]
      SSID=DW88
      HOST=s10d1
      PORT=456
      LOCATION=DW8DDF
    <<<<<< end of dump of connection profile
    ssid DW88 found in connection profile, section DW88_on_s10d1.
    >>> analyse line:  * ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
    >>> analyse line:  [DEFAULT_GROUP]
    >>> analyse line:  CON1=DW88_on_s10d1
    >>> analyse line: 
    >>> analyse line:  [DW88_on_s10d1]
    section DW88_on_s10d1 found.
    >>> analyse line:  SSID=DW88
    >>> analyse line:  HOST=s10d1
    >>> analyse line:  PORT=456
    >>> analyse line:  LOCATION=DW8DDF
    >>> analyse line:  section DW88_on_s10d1 found and data matches.
    backup connection profile /usr/sap/DW8/SYS/global/connect.ini .
    switch connection profile /usr/sap/DW8/SYS/global/connect.ini .
    check for adapted connection profile.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    ssid DW88 found in connection profile, section DW88_on_s10d1.
    check for adapted connection profile passed.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    SQL DRIVER VERSION is "09.07.0003"
    DB2Connect driver identified as THIN CLIENT
    DB2Trc: 00 000000 cli_get_cli_driver_bld_level 1 s101006
    SQL DRIVER NAME is "libdb2.a"
    SQL DBMS NAME is "DB2"
    SQL DBMS VERSION is "09.01.0005"
    DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
    The bind is skipped since collection for ssid DW88 is already bound.
    To force the bind, use option "-B force".
    DB2TRC: 0000000000 00      000000   CLI_DISCONNECT
    DB2TRC: 0000000000 00      000000   CLI_FREE_DBC 1
    DB2TRC: 0000000000 00      000000   CLI_FREE_ENV 1
    DB VERSION is 09.01.0005.
    Starting Grants .
    DB2Trc:    000000 CLI_ALLOC_ENV 1
    COLLECTION ID used is "SAP0907U"
    DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W  There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD.  SQL
    Connecting to <DW88_on_s10d1> on connection 0 ...
    Now I'm connected to DB2 (09.01.5)
    SQL DRIVER NAME is "libdb2.a"
    SQL DBMS NAME is "DB2"
    SQL DBMS VERSION is "09.01.0005"
    DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
    New functions of DB2 V9 are switched on
    Profile parameter dbs/db2/cli_trace_dir is not set
    dbdb2dic.c 1709 INFO    Profile: SDB2_DEBUG=<UNSET>                                                                           
    dbdb2dic.c 1733 INFO    Envrmnt: sdb2_debug=<UNSET>                                                                           
    dbdb2dic.c 1733 INFO    Envrmnt: SDB2_DEBUG=<UNSET>                                                                           
    DB2 Call 'CLI_EXECUTE' Error: sqlcode = -204 : [IBM][CLI Driver][DB2] SQL0204N  "SAPADM.#LOBU" is an undefined name.  SQLSTATE=42704
    dbdb2dic.c 2251 INFO    rc=103,sqlcode=-204: ExeRead                                                                          
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/max_retry=<UNSET>                                                                    
    dbdb2dic.c 1733 INFO    Envrmnt: DB2_MAX_RETRY=<UNSET>                                                                        
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/retry_on_924=<UNSET>                                                                 
    dbdb2dic.c 1733 INFO    Envrmnt: DB2_RETRY_ON_924=<UNSET>                                                                     
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/no_retry_on_10=<UNSET>                                                               
    dbdb2dic.c 1733 INFO    Envrmnt: dbs_db2_no_retry_on_10=<UNSET>                                                               
    dbdb2dic.c 1733 INFO    Envrmnt: DBS_DB2_NO_RETRY_ON_10=<UNSET>                                                               
    DB2 Call 'SQLEndTran' Error: sqlstate = 08003 : [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
    [dbdb2dic.c  1873:rc=99: COMMIT WORK failed]
    dbdb2dic.c 1873 ERROR   rc=99: COMMIT WORK failed                                                                             
    [dbdb2dic.c  2019:rc=99,sqlcode=268435455: ExecDDL failed (DB error)]
    dbdb2dic.c 2019 ERROR   rc=99,sqlcode=268435455: ExecDDL failed (DB error)                                                    
    DB2 Call 'SQLEndTran' Error: SQLCODE = -99999 : [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
    ROLLBACK failed with SQL error '-99999'
    ERROR: couldn't connect to DB
    rc = 99
    error message returned by DbSl:
    rc=99,sqlcode=268435455: ExecDDL failed (DB error)
    DB2RADM EXITCODE: 12
    db2radm finished (0012)
    db2radm stop:28.02.2012 10:54:39
    i've patched db2radm and sapinst to the latest version.
    May be i should manually create "SAPADM.#LOBU"?
    Please help to solve these issue.
    Best regards,
    Alexander V

    Hi ,
    Please check if Note 1581637 - Installing a System with DB2CODEPAGE other than the default is useful.
    Award points if useful.
    Thanks,
    Ravi

  • Configuring weblogic6.1 for db2 driver

    Hi all,
    I want to access DB2 database from a servlet running on weblogic6.1.But i am unable
    to configure weblogic 6.1 for DB2 driver.Going through the documentation for configuring
    weblogic third party drivers was of no help.when i run the program i get the error
    "no suitable driver found".
    Please post suggestions on how to configure weblogic6.1 for DB2 driver.
    Thank u in advance.

    Ramesh,
    We use code like the following to successfully connect to a connection pool:
    // put the pool name into a properties,
    // in the same way that you would put "user" and "password" in the properties
    dbproperties.put("connectionPoolID", mypoolName);
    Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    myconnection = DriverManager.getConnection("jdbc:weblogic:pool", dbproperties);
    It shouldn't be much different than the code you have where you get the driver
    and then connect directly. But, I do know that what we use works. Maybe the
    pool name has to be specified in the info properties, rather than in the url string.
    (that would be a simple and easy change to your code; to see if it worked.)
    Also, we have found that the CaSe of the DB2 driver name matters:
    COM.ibm.db2.jdbc.app.DB2Driver
    We also put the db2java.zip as the first item in the classpath. (I don't remember
    if that matters or not).
    Craig
    "Ramesh" <[email protected]> wrote:
    >
    Sree,
    In the weblogic 6.1 connection pool configuration i have the following
    settings:
    Name:myPool
    URL:jdbc:db2:database (database is the name of sample database in db2)
    Driver Classname:Com.ibm.db2.jdbc.app.DB2Driver
    Properties:user=db2admin;password=asits9;DatabaseName=database
    ACL name:blank
    Password:blank
    but when i select Target-Server from Targets tab of JDBC Connection Pool
    i get
    the error "Error Occured while processing your request" which is something
    java.lang.reflect.InvocationTargetException.
    in my servlet i establish the connection with the db2 database through
    the following
    codes
    Connection conn=null;
    Driver d;
    d=(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    conn=d.connect("jdbc:weblogic:pool:myPool",null);
    ramesh.
    "Sree Bodapati" <[email protected]> wrote:
    Can you show me your standalone program (or just the url, driver name
    and
    properties you use to get connection). Sometimes the url doesnt match
    up
    properly. Do you see any exceptions when the connection pool is getting
    created?
    sree
    "ramesh" <[email protected]> wrote in message
    news:[email protected]...
    Sree,
    I can access db2 from a simple standalone java application.
    but when i create connection pool in weblogic6.1,i think it is not getting
    created,bcos
    when i run the servlet i get the error "Pool connect
    failed:java.SQLException:Connection
    pool myPool does not exist" where myPool is the name of the connection
    pool
    i
    created.i have db2java.zip in my classpath.
    do i have to set some other classpaths also.
    ramesh.
    "Sree Bodapati" <[email protected]> wrote:
    Ramesh,
    If you can write a simple standalone java program to get a DB2 connection
    using the DB2 driver (without WebLogic in the picture). You will findout
    what URL and Driver name to use and what properties to pass to the
    driver.
    Specify these properties in the connection pool properties and make
    sure
    the DB2 driver is in the CLASSPATH when you boot the WebLogic server.
    sree
    "ramesh chand" <[email protected]> wrote in message
    news:[email protected]...
    Hi all,
    I want to access DB2 database from a servlet running on weblogic6.1.But
    i am
    unable
    to configure weblogic 6.1 for DB2 driver.Going through the documentation
    for
    configuring
    weblogic third party drivers was of no help.when i run the programi
    get the
    error
    "no suitable driver found".
    Please post suggestions on how to configure weblogic6.1 for DB2 driver.
    Thank u in advance.

  • There is  a JDBC Driver that allow me to Connect db2/as400

    Hi!
    I have an Oracle application and now I need to access some data in DB2/400 from this application. My first Idea was to use Java with JDBC to make the connection and I have tried to load the classes of the JDBC driver that I use to connect DB4/400 from Windows but It didn't work, I used the loadjava command but almost all the classes can be compiled when are being load to oracle.
    Have you ever do something like that?, Is there any JDBC driver to connect DB2/400 from Oracle?
    I have Oracle 8.1.5 with jdk 1.1.6
    Thanks in advance

    What JDK are you using on the Windows machine? My first guess is that you need to get a version of the DB2 JDBC driver that is compatible with the 1.1.6 JDK-- the version you have at the moment probably requires a later version of the JDK.
    I don't recall off the top of my head what version of the JDK 8.1.7.4 used, but I know 9.2 is using at least the 1.2 JDK. Is it possible for you to upgrade your database, at least to a supported version (8.1.7.4) if not the current version (9.2)?
    Justin
    Distributed Database Consulting, Inc.
    www.ddbcinc.com/askDDBC

  • Thank adobe team for Cp 8.0.1

    Thank adobe team for Cp 8.0.1
    many thing get better.
    and i wish to see 8.0.2
    thank you

    I think you are referring to this bug for which the patch was released earlier.
    http://blogs.adobe.com/captivate/2014/07/update-on-captivate-html-5-content-playback-issue -in-google-chrome-browser.html
    Here is the release notes of this new update.
    http://helpx.adobe.com/captivate/kb/cp8-patch.html
    Sreekanth

  • Driver and connection string for DB2 7.1 IBM Z/OS Mainframe

    Hi ALL,
                Could someone please provide me the connection string and driver for DB2 7.1 IBM Z/OS Mainframe?
    Regards,
    XIer

    Hello,
    With SAP and DB2 V7 still ICLI which is part of the operating system is used for DB connectivity. For details on the setup see related docs for SAP releases up to 6.20 .
    As of Netweaver 2004 DB2 V8 and DB2 Connect is used.
    If you're talking about Java you need a license either from IBM or if you're OEM customer for DB2 on z/OS it is delivered automatically.
    Regards,
    Thomas

  • Error when connecting to DB2/AS400 as a Datasource

    Hi All,
    I have an issue when connecting to DB2/AS400 as w datasource with IR studio. I am able to create an OCE but when click on tables it throws an error saying ""INFORMATIC.DM3601PF" is an undefined name. SQLSTATEB704
    sqlstate = 42S02
    The drivers I used is the drivers provided by the IBM DB2 and also the Merant drivers provided for Hyperion by DB2. I used ODBC/DB2, ODBC/ODBC, ODBC/AS400 connection while creating an OCE but it did not help.
    The exact version of the database is DB V5R4--AS400--OS. It is a 64 bit client.
    Can anyone help!!!
    Thanks,
    Sree

    Hi,
    Connecting Hyperion with DB2 is simple. When we install DB2 client on the machine it adds a new entry in ODBC drivers, using that DB2 Driver create a system DSN by selecting the appropriate DB. Give the proper credentials.
    Now open Hyperion IR select new Database option...Select ODBC/DB2 and choose the DSN name given by you while creating the system DSN. give the correct credentials to connect to DB.
    After that it will ask for OCE creation...just create oce by giving app name and you are done with the connection.

  • Icorrect table creation statements being generated for DB2

    Hi,
    I am using JDeveloper 903 and I have a datsource of IBM DB2 ver 7.3 type. I am creating a CMP2.0 beans Person and Address. When I try running these beans from JDeveloper on the embedded OC4J, I get the following exception :
    AAuto-creating table: create table Person_current_workspace_app__vkk_AmsNTO_Project1_classes_ (id BIGINT not null primary key, firstName VARGRAPHIC(255) null, lastName VARGRAPHIC(255) null, middleName VARGRAPHIC(255) null)
    Auto-creating table: create table Address_current_workspace_app__vkk_AmsNTO_Project1_classes_ (id BIGINT not null primary key, address1 VARGRAPHIC(255) null, address2 VARGRAPHIC(255) null, city VARGRAPHIC(255) null, state VARGRAPHIC(255) null, zip VARGRAPHIC(255) null, type VARGRAPHIC(255) null, Address_addresses BIGINT null)
    Auto-creating table: create table Address_addresses_Address_Address_addresses_current_workspace_app__vkk_AmsNTO_Project1_classes_ (Address_id BIGINT not null)Error creating table: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "," was found following "VARGRAPHIC(255) null". Expected tokens may include: "<references_spec>". SQLSTATE=42601Error creating table: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "," was found following "VARGRAPHIC(255) nu[i]Long postings are being truncated to ~1 kB at this time.

    Thanks wildmight for the reply.
    You're right on with the tip you provided -- I figured that this had to be related to some DB object setting in the Physical Layer. As I've never been able to find any documentation from Oracle on the definition of the "Features" tab settings, I just began trial-and-error troubleshooting with the settings to see what I could find. I actually tested it by selecting every "Value" checkbox in the 'Features" tab to see what I'd get. :D
    Apparently, when I selected "DB2/AS400" as the database object's data source type in the "General" tab, the "Features" tab also got updated to default DB2 features that OBIEE thinks are appropriate. HOWEVER, there is one +slightly+ important feature is then automatically deselected (and also not listed as "default") in the list:
    *DERIVED_TABLES_SUPPORTED*
    Once I put a check in the "Value" column of the "Features" tab and re-ran my query, it actually submitted one unified query to the DB as I had hoped!
    I have a fact table with about 30 million rows and when I would ask for only a month's worth of data, it previously would return ALL 30M records and then filter down on my month. That query was taking about 15 minutes. After I got the view to work properly, the same query took 19 seconds. :)
    Cheers,
    Jeremy

  • How to use DB2 XA driver instead of default DB2 driver

    Hi,
    I've been using the default DB2 driver (com.ibm.db2.jcc.DB2Driver) for a datasource until now. I need to switch to using an XA approved driver to handle some two phase commits. It appears Oracle has an XA driver for DB2 (weblogic.jdbcx.db2.DB2DataSource) but whenever I use it I get the following error:
    [BEA][DB2 JDBC Driver][DB2]PROGRAM NAME NULLID.DDJU360B 0X4A44424334444232 NOT FOUND IN PLAN null
    What does this error mean? How can I switch to an XA DB2 driver?
    Thanks...

    DB2 running on AIX:
    select * from sysibm.sysversions;
    7010200     2001-04-11 17:01:21.478428     WBDID04
    8020000     2005-02-01 19:55:13.083939     SYSIBM
    8020800     2007-09-08 08:16:45.496058     WBDID04
    WebLogic Server 10.3 running on Windows XP.
    Using the XA driver works fine for WebLogic Server 8.1 and the existing DB2 database. So, I'm wondering what went wrong when I upgraded to 10.3.
    The error happens on server startup when it's trying to test the connection:
    <25-May-2010 3:28:44 o'clock PM GMT-06:00> <Error> <JDBC> <BEA-001112> <Test "SELECT COUNT(*) FROM SYSIBM.SYSDUMMY1" set up for pool "csp" failed with exception: "java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]PROGRAM NAME NULLID.DDJC360B 0X4A44424334444232 NOT FOUND IN PLAN null".>
    Any ideas?

  • Error creating connection pool for WLS6.1 for DB2 connect

    Hi,
    We have installed licensed copy of Weblogic 6.1 Applciation server on HPUX 11.0.
    Our backend system is DB2 on Mainframe (S/390). We have installed DB2Connect
    JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic console with
    following parameters:
    Name: DB2Pool
    URL:jdbc:db2:INFOSYSG
    Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
    Properties:
    user=jargon
    password=jargon
    Then appropriate Target was selected.
    When server was started following error was recevied on console:
    "CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
    Any pointers to the solution are welcome.
    Regards,
    Punam Chordia
    Infosys Technologies Ltd, Pune
    Phone: 91-20-2932000 Ext. 5650
    Fax: 91-20-2932832

    Hi,
    thank you for your answer, but i already fixed my problem.
    i simply put the profile-script of the db2-instance into the start script of the
    weblogic server.
    i didn´t really figure out so far which variable was missing, but now it works.
    unfortunately i found that this driver supports only 2 connections at the same
    time when using jdk 1.3.0 :-(.
    Regards,
    Andreas Koch
    Netfidelity Consulting GmbH
    tel +49 211 6012330
    fax +49 211 6012320
    mail [email protected]
    Joseph Weinstein <[email protected]> wrote:
    If you can connect to DB2 on your own, using their
    driver and their JDBC examples, then show me the code
    that works, and show me the classpath and OS environment
    you're running in, and I'll show you what should be
    done for the server.
    Andreas Koch wrote:
    Hi,
    unfortunately i have the same problem and found no solution so far.
    you may check my start-script, but in my eyes all db/2 stuff shouldbe
    found.
    thanks for urgent help
    Andreas Koch
    NetFidelity Consulting Gmbh
    [email protected]
    "Slava Imeshev" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]...
    Hi Punam,
    You need to make sure that all driver's native libraries are
    available to the Weblogic. Check if SQLLIB\bin is on the path
    and let us know if it helps.
    Regards,
    Slava Imeshev
    "Punam" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    We have installed licensed copy of Weblogic 6.1 Applciation server
    on
    HPUX
    11.0.
    Our backend system is DB2 on Mainframe (S/390). We have installedDB2Connect
    JDBC driver ver 7.1 on HPUX. While creating pool throught weblogic
    console
    with
    following parameters:
    Name: DB2Pool
    URL:jdbc:db2:INFOSYSG
    Driver Classname: COM.ibm.db2.jdbc.app.DB2Driver
    Properties:
    user=jargon
    password=jargon
    Then appropriate Target was selected.
    When server was started following error was recevied on console:
    "CLI0647E Error allocating DB2 environment handle, rc=db2jdbc"
    Any pointers to the solution are welcome.
    Regards,
    Punam Chordia
    Infosys Technologies Ltd, Pune
    Phone: 91-20-2932000 Ext. 5650
    Fax: 91-20-2932832
    Name: startWebLogic.sh
    startWebLogic.sh Type: Kornshell Script File (application/x-unknown-content-type-mks_shell)
    Encoding: x-uuencode

  • Best Db2 thin driver

    Hi All,
    Can some one recommend a reliable jdbc thin driver which supports distributed
    transactions for DB2 on windows and solaris.
    What is the reliability of the db2jcc driver (Universal driver) which comes with
    the DB2 (8.1) installation.
    Also want to know the same(driver) for the informix on windows.

    Hi,
    just wondering, what are anyones thoughts on the best
    example driver to be working from - hme, le, ae, etc ?
    I have started with psli, 'cause i didn't have the
    source to the others at the time, but would like to
    know anyones thoughts on which are 'best'.
    Thanks in advance,
    S.If you want an example to implement your own ethernet driver based on the GLD, then
    I recommend looking at my drivers (particularly afe) located at
    http://garrett.damore.org/software/ethernet/
    The other sample drivers are "monolithic" drivers, which can be good for understanding the
    DLPI and writing generic STREAMs devices, but I wouldn't write a monolithic NIC driver
    without some compelling reason. (There is a roughly 2:1 code size difference between
    monolithic drivers and GLD drivers.)
    -- Garrett

  • 2.1ea2  iSeries DB2 jdbc driver

    Has anybody installed it and got it to work? The latest for the iSeries is jt400.jar, but I can't get it to work. It says there is a java class error.

    I'm not really sure if the iSeries migration is already covered. The DB2 connection tab is in my opinion only for DB2 UDB V8 and V9.
    Those UDB releases on LUW (Linux,Unix and Windows) have the jdbc driver installed in the DB2 home and you simply need to copy the libraries db2jcc.jar and db2jcc_license_cisuz.jar to SQL Dev and link them.
    But those drivers don't work with my iSeries V6 - I'll get an error message.
    Not sure where you saw the connection using those 2 jar files worked against an AS400 .. but if you want to test, them, you need to download DB2 Connect or a trial UDB database for Windows or Linux.

Maybe you are looking for