Toplink support for DB2

I was wondering if anyone had any experiences with Toplink's support for DB2? If I have an existing application working with Oracle, is it easy to get the application working with a DB2 database or another DBMS such as SQL Server, etc.? Obviously, the different vendors have different conformities to the SQL syntax standard, and I was wondering if Toplink took these differences into account?
Thanks,
Ted

I don't know of any specific papers/docs on this.
The nature of TopLink is supporting any app server, any ide/toolset and any Database. For example, look in the source.zip file in your lib directory for TopLink... Notice there is a DB2Platform.java file in there. If there were any specific compatibility or idiosynchracies we hadn't accounted for (but we have), you could easily do so yourself just by modifying that class. We have cusotmers using dozens and dozens of different database variants just by using and modifying any of the Platform code provided...
- Don

Similar Messages

  • Toplink support for weblogic 9

    Hi ,
    Is toplink supported with weblogic 9?If yes,which version?
    There is a thread(on OTN) that speaks about toplink support for weblogic 9.
    Weblogic 9 -TopLink CMP
    Thanks,
    Rajbharat

    Rajbharat,
    We have completed our testing of POJO architectures and the WebLogic Support Matrix now reflects this:
    Doug

  • Toplink support for Java 5.0

    I tried to import java classes, compiled with jdk 5.0
    into Toplink workbench. The mapping fails.
    I tried to run the workbench with jre 5.0 but that didn't work either.
    Does anyone know how to do it and does Toplink even have a version that supports java 5.0?

    Anna,
    TopLink 10.1.3 will offer formal support for Java 5.0. Currently the runtime should work fine with Java 5.0. The only issue may be the workbench mapping process depending on the version of TopLink you are using.
    If you are using the 10.1.3 preview the workbench will still run with JDK 1.4 but should be compatible with importing and mapping classes compiled with JDK5. We will upgrade the JRE used by the workbench to JDK5 for the production release but this should not make any difference to your ability to map JDK 1.4 or 5 classes and use either at runtime.
    If you are using 9.0.4.X then the workbench will not be able to run or import JDK5 compiled classes. I believe the runtime is fine but not certified. For this environment you will need to compile the classes under JDK 1.4 and map this version of the classes. You can then use JDK5 compiled version in conjunction with the runtime.
    I hope this helps,
    Doug

  • TopLink support for JDO?

    Hi,
    I'm new to TopLink and am wondering what the status of JDO support is in 4.6. I can see that there is a JDO example, and that the RELNOTES indicate JDO support. But the level of spec compliance and JDO specific tools in TopLink are not documented AFAIK.

    I finally found the javadocs in the TopLink 4.6 distribution. From these, plus from the examples, it seems to me that the TopLink JDO 1.0 support is partial.
    They do provide partial implementations to most of the JDO interfaces in javax.jdo package. The one exception is javax.jdo.InstanceCallbacks. What I mean by partial is that some required methods are no-ops (no operation). No-ops do nothing and return null or zero depending on their return type.
    They don't support the JDO query language. You can use their implementation of javax.jdo.Query to create a query using SQL, TopLink query language, or EJBQL.
    They don't support the enhancer. The enhancer is controversial, therefore some people see this as a good thing.
    I ran a little program to display the results of PersistenceManagerFactory.supportedOptions() for TopLink.
    SUPPORTED OPTIONS
    javax.jdo.option.NontransactionalRead
    javax.jdo.option.ArrayList
    javax.jdo.option.HashMap
    javax.jdo.option.Hashtable
    javax.jdo.option.LinkedList
    javax.jdo.option.ArrayList
    javax.jdo.option.TreeMap
    javax.jdo.option.TreeSet
    javax.jdo.option.Vector
    javax.jdo.option.Map
    javax.jdo.option.List
    javax.jdo.option.Array
    UNSUPPORTED OPTIONS
    javax.jdo.query.JDOQL
    javax.jdo.option.RestoreValues
    javax.jdo.option.NullCollection
    javax.jdo.option.NontransactionalWrite
    javax.jdo.option.TransientTransactional
    javax.jdo.option.RetainValues
    javax.jdo.option.NonDatastoreIdentity
    javax.jdo.option.Optimistic
    javax.jdo.option.DatastoreIdentity
    javax.jdo.option.ApplicationIdentity
    I'm not sure why the javax.jdo.query.JDOQL option even exists. As I understand it support for the JDOQL is mandatory, not optional. But maybe this is a versioning thing. That is, maybe JDO 2.0 will allow implementations to provide JDOQL 1.0 and/or JDOQL 2.0. Just a guess.
    Hope this helps.

  • Toplink support for JPA vs. Toplink Essentials

    I think I read that Toplink has some support for EJB3/JPA as does Toplink Essentials.
    What is the difference in features?
    If one has a 10.1.3 app server license, should Toplink be used instead of Toplink Essentials for EJB3/JPA applications?
    Does the Mapping Workbench produce JPA object-relational mapping annotations or XML?
    Thank you.
    Richard Catlin

    Hi Robert,
    I'm not sure which comments you were directing specifically to Dali vs. JDeveloper but I'll try and address them from a Dali perspective. I do want to point out that Dali is at 0.5 and so it is still under development.
    yes you get a basic 1:1 entity from your databasetables...When generating Entities from tables, Dali will generate 1:1 and 1:many relationships based on database FK constraints.
    @temporary annotations are not inserted if you have a Date oder Calendar type.Also when generating Entities from tables Dali will generate an instance variable of java.sql.Date for a database date column. java.sql.Date does not require an @Temporal annotation.
    What's missing right now is a problem marker for missing @Temporal on java.util.Date and java.util.Calendar.
    If you want to rename attributes or methods it's a lot of manual work to do... because >@Column annoations are not inserted, if they do not exist because of >dbname=attributenameThere is a bugzilla bug opened for this refactoring support. https://bugs.eclipse.org/bugs/show_bug.cgi?id=136333 Fortunately in Dali if you rename a class or attribute (field/getter) and your explicit or default mappings are broken you will get a problem marking on the attribute and in the Problems view so you can fix it rather than finding out at runtime.
    generics are not inserted in the returnvalues of the methods...Generated Entities do use generics correctly e.g.:
    public class Publisher implements Serializable {
         @OneToMany(mappedBy="publisher")
         private Set<Title> titles;
         public Set<Title> getTitles() {
              return this.titles;
         public void setTitles(Set<Title> titles) {
              this.titles = titles;
    ...--Shaun                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • TopLink support for version 2.0/2.1 of ejbql

    Hello,
    TopLink support ejbql for pojo finders.
    What version of ejbql is supported in toplink 9.0.4.8 : 2.0 or 2.1 ?
    What version of ejbql is supported in future release (10.1.3) of toplink : 2.0 or 2.1 ?
    Regards

    I believe the answer to both is 2.1.
    Doug

  • TopLink support for Stored Functions

    I know that TopLink supports PL/SQL stored procedures. What I haven't been able to figure out is whether or not TopLink also supports functions as well. Is there any way to execute a PL/SQL function using the TopLink APIs? Thanks. -Michael-

    You can find additional information (including examples of usage) on using Stored Functions in the TL Dev Guide: http://download.oracle.com/otn_hosted_doc/toplink/1013/MAIN/_html/qrybas004.htm#BCFBBJBJ

  • Toplink support for SQL Server 2005 on Websphere 6.1

    Hi,
    We are using toplink in our application, it works fine when we use it with weblogic & SQL server or WAS 6.1 with Oracle or DB2. But when we use it with WAS 6.1 and SQL Server 2k5, it just does not work. It takes up all the connections in the pool and never returns it and starts giving connection time out errors.
    Internal Exception: com.ibm.websphere.ce.cm.ConnectionWaitTimeoutException: Connection not available, Timed out waiting for 100005Error Code: 0
    Thanks

    This sounds like a WebSphere connection pool issue, I'm not sure why WebSphere would not work with SQL Server.
    You could try using TopLink's internal connection pooling instead.
    EclipseLink : http://www.eclipselink.org

  • Toplink support for RAC Failover

    We need to enable Toplink to support RAC Fast Connection Failover. We need to support
    only read query retry functionality and not write query retry. We found one document
    (http://www.oracle.com/technology/events/develop2007/presentations/oracle_jdbc_high_availability_load_balancing_best_practices_and_road_map.pdf)
    that explains how to configure JDBC connection for RAC failover. However, since we
    are using Toplink, we don't explicitly write our own jdbc url and toplink's session/uow
    will automatically handle the actual sql query execution.
    Is there any way we can configure Toplink to support RAC Fast Connection Failover, such
    as possibly in the toplink's sessions.xml or in the oc4j container's connection pools setting?
    Just for information, the way we acquire Toplink session is through SessionFactory:
       SessionFactory sessionFactory = new SessionFactory("repository",
                                     "META-INF/repository-sessions.xml");
       Session toplinkSession = sessionFactory.acquireSession();Then we do queries, acquiring unit of work, etc, using that toplinkSession.
    Thanks.

    We have enhanced our RAC FCF support in 11gR1 leveraging the new Universal Connection Pool to make it more seamless to the application. Which version of TopLink and OC4J are you using?
    Doug

  • Toplink support for stored procedure with 2 OUT  REF CURSOR ?

    Can Toplink StoredProcedureCall be used with Oracle PLSql procedure with 2 OUT parameters. Parameter type is Ref Cursor (Oracle PLSQL resulset)
    Regards

    In a TopLink StoredProcedureCall using an OUT CURSOR the cursor is assumed to map to the result set for the TopLink query.
    For example if you had a stored procedure READ_ALL_EMP that returned a out cursor of EMP rows, you could use that procedure in a TopLink mapped Employee class mapped to the EMP table and use the stored procedure in a ReadAllQuery for the Employee class.
    If the procedure does not return data that maps to objects, you can use a DataReadQuery to access the data. The out cursor would be returned as a Vector of DatabaseRows that contain the data from the cursor rows.
    If the procedures data is complex and does not map to objects, it may be better to access the procedure directly through JDBC.

  • Sequence support for UDB

    In the documentation, sequences are supported for Oracle, informix, sybase, and mssql.
    I was wondering if there have been any advances in supporting UDB sequences.
    If so, which version of toplink supports it.
    If not, could you recommend a way to handle creating numeric keys for tables?
    Thanks,
    Michael

    Each time I try to insert a row where an id is an identity column using toplink, I get an error:
    EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
    EXCEPTION DESCRIPTION: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0407N Assignment of a NULL value to a NOT NULL column "ADDRESS_ID" is not allowed. SQLSTATE=23502
    INTERNAL EXCEPTION: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0407N Assignment of a NULL value to a NOT NULL column "ADDRESS_ID" is not allowed. SQLSTATE=23502
    Since this is an identity column, I don't pass any value in the identity field. Does toplink provide this support for DB2. And do I need to extend DB2Platform to get this support. If so, what needs to be implemented?

  • TopLink support DB2/OS390

    Does TopLink support connecting to DB2/OS390? If so, is it with the standard DB2 selection in Workbench, or will another method be required?
    Thanks

    Sorry, meant to say DB2 on AS/400. We do have a number of customers using TopLink on AS/400 with DB2. I do recall experiencing an issue with the JDBC driver IBM provided though. It would not properly report the meta-data information the Mapping Workbench uses to import schemas. To work around this, we manually entered the table information in one case, and in another case we exported the schema to another platform and imported it through a better JDBC driver. I'm sorry I can't confirm which specifric versions this was for. It is a documented limitation of the IBM JDBC driver however. Other than that, we had no problems at all.
    - Don

  • Does BC4J works as ORM (eg: Toplink) to support for MSQL Server / Oracle DB

    Hi,
    My current product is running on Struts 1.1, Apache Cocoon(for reports generation), JDBC & MS SQL Server environment.
    To provide the more flexibility & user friendliness to the application I have a proposal for the re-development of the application with ADF 11g.
    But the main concern here is, the current product is running on MS Sql Server DB, now the product team has a future plan to migrate it to Oracle Database. In view of this DB migration, the frame work/environment that I choose for the re-development must support for very less code changes (at least from the Application Business logic/Queries prospective)
    Here I have two options for the re-development
    1. ADF 11g + Top-link (ORM) + MS Sql Server / Oracle DB
    2. ADF 11g + BC4J + MS Sql Server / Oracle DB
    Plz suggest me, out of these two options which one suits for my requirement & better in performance too

    Check this out:
    http://www.oracle.com/technology/products/jdev/collateral/papers/11/certification/index.html#Databases
    Also
    http://www.oracle.com/technology/products/jdev/11/how-tos/multidatabaseapp.html
    Have a nice day

  • Pagination support for non-Oracle databases?

    Hi,
    I just read this thread (Pagination Support on pagination support. Is there any way to get pagination with non-Oracle databases? We are using an IBM iSeries / AS/400 DB2 database right now, and we're planning to use some local lightweight database in the near future as well (probably Cloudscape/Derby or "IBM Everyplace database".)
    We currently use code like this:
    String sql = "SELECT art FROM Artikel art" +
                /* dynamically generated where statement is added here */
                + "ORDER BY art.artikelNummer";
    Query q = em.createQuery(sql);
    q.setFirstResult(firstResult);
    q.setMaxResults(maxResults);If I look in the TopLink logs, I see queries like this:
    SELECT ARTNR, ARALT, ARAFJ, ARXII, ARAVJ, ARXIV, ARANJ, AHGCD, ARNVJ, ARCRJ, ARARK, ARFKJ, ARTNK, ARGP1, ASGCD, ARGP2, ARPR1, ARGP3, ARPR2, AREX1, ARPR3, AREX2, ARPR4, AREX3, ARASA, ARINA, ASSCD, ARIA1, ARBAN, ARIN1, ARBAV, ARIA2, ARBAK, ARIN2, ARCES, ARIA3, ARCDT, ARIN3, ARCRE, ARIA4, ARCWK, ARIN4, ARHBH, ARIA5, ARDFA, ARIN5, ARDFG, ARIA6, ARDOS, ARIN6, AREPW, ARINN, ARFOD, ARIAS, ARFOE, ARINS, ARFOF, ARNAB, ARFOI, ARNIB, ARFON, ARNIA, ARFOS, ARNN1, ARFTA, ARNA2, ARVIV, ARNO2, ARGAP, ARNN3, ARGPT, ARNA4, ARGPD, ARNO4, ARGPA, ARNN5, ARGPO, ARNA6, ARHIS, ARNN6, ARISP, ARNIO, ARKHM, ARNNS, MAGCD, AROVJ, MTGCD, ARPL1, ARMXM, ARPL2, MRKCD, ARPL3, ARMVR, ARVKJ, ARMIM, ARV12, ARMDT, ARVVJ, ARMTE, AR#VR, ARMTU, ARZLS, ARMTM, ARIAT, ARMWK, ARAVS, MPCCD, ARNVS, ARBTW, ARFJS, ARXI2, ARG2S, ARXI3, ARE1S, ARXI4, ARE3S, ARXI6, ARIB1, ARXI1, ARIB2, ARXI5, ARIB3, AROPI, ARIB4, ARPRV, ARIB5, SZGCD, ARIB6, ARSPC, ARINO, ARSMF, ARIOS, VEAAN, ARNIS, ARSYN, ARNO1, ARVR1, ARNA3, ARV1S, ARNN4, ARVR2, ARNO5, ARV2S, ARNIN, ARVR3, ARNOS, ARV3S, ARP1S, ARTFA, ARP3S, ARTFG, ARS12, ARUVC, ARZLD, ARUCW, ARAJS, ARBKV, ARCJS, ARVVI, ARG3S, ARVVP, ARINB, VPOCD, ARIO2, VPECD, ARIO4, ARVIH, ARIO6, ARVHG, ARNBS, ARVRW, ARNN2, ARVPR, ARNA5, ARVVR, ARNAS, ARVVS, ARP2S, ARVV1, ARSVV, ARZK1, ARNJS, ARNA1, ARNO3, ARIO1, ARNO6, ARIO5, AROJS, ARE2S, ARVJS, ARIBS, ARIAD, ARIO3, ARG1S FROM ART WHERE ((((ARUVC = 'N') AND (ARHIS = 'N')) AND (ASGCD = 7)) AND (AHGCD = 15)) ORDER BY ARTNR ASC
    (Yeah, I know we have too much columns in the table...)
    So, no pagination in the query. As you can see, we have a mechanism in place to dynamically generate a where clause. This is because the user can set filters. The problem is, if our user sets a filter that causes the result set to be significantly smaller, the performance is way better than when he sets no filter at all. We suppose this is because the whole result set is sent to TopLink, regardless of the values of firstResult and maxResults.
    We are using TopLink Essentials 2.1-10, by the way.
    Message was edited by:
    Bart Kummel

    Hi all,
    I'm trying to subclass <tt>DatabasePlatform</tt> to add pagination support for the AS/400 DB2 database of my customer. To be fair, it is not going very well so far.
    The first problem is, the query Chris found by googling (Re: Pagination support for non-Oracle databases?), does not work for AS/400s version of DB2. In fact, although it is called "DB2", the database on the AS/400 system is a whole other database than the "normal" DB2 database that runs on Windows and *nix. The AS/400 DB2 simply does not have a "ROW_NEXT" function.
    Another option would be to use the <b>row_number() over()</b> mehtod. But, as can be read here, this function is only available from version V5R4 of OS/400. And guess what? We're stuck on V5R3 at this client. (We cannot upgrade, because there's an application in use that's written in Delphi and IBM dropped the Delphi binding from V5R4...)
    So I pretty much ran out of options. On the mailing list I linked to above, someone mentions the option to make a sort of stored procedure that generates a row count number. An example of how to do this can be found here. I implemented it, and ended up with this code:
    package com.myclientsname.persistence;
    import java.sql.Connection;
    import java.sql.PreparedStatement;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import org.eclipse.persistence.expressions.ExpressionBuilder;
    import org.eclipse.persistence.internal.databaseaccess.DatabaseCall;
    import org.eclipse.persistence.internal.expressions.ExpressionSQLPrinter;
    import org.eclipse.persistence.internal.expressions.SQLSelectStatement;
    import org.eclipse.persistence.internal.sessions.AbstractSession;
    import org.eclipse.persistence.logging.SessionLog;
    import org.eclipse.persistence.platform.database.DatabasePlatform;
    import org.eclipse.persistence.sessions.SessionProfiler;
    public class AS400Platform extends DatabasePlatform {
        private static final long serialVersionUID = 0L;
        public AS400Platform(){
             super();
             super.setShouldBindAllParameters(false);
        public void printSQLSelectStatement(DatabaseCall call, ExpressionSQLPrinter printer, SQLSelectStatement statement) {
            int max = 0;
            int firstRow = 0;
            if (statement.getQuery()!=null){
                max = statement.getQuery().getMaxRows();
                firstRow = statement.getQuery().getFirstResult();
            if ( !(max>0) && !(firstRow>0) ){
                super.printSQLSelectStatement(call, printer,statement);
                return;
            } else {
                statement.setUseUniqueFieldAliases(true);
                ExpressionBuilder builder = new ExpressionBuilder();
                statement.addField(builder.getField("COUNTER() AS CNTR"));
                printer.printString("SELECT * FROM (");
                call.setFields(statement.printSQL(printer));
                printer.printString(") AS R WHERE R.CNTR >= ");
                printer.printParameter(DatabaseCall.FIRSTRESULT_FIELD);
                if ( max > 0 ){
                    // Use of binding parameters is not allowed here, so use
                    // String concatenation instead...
                    printer.printString(" FETCH FIRST " + max + " ROWS ONLY");
            call.setIgnoreFirstRowMaxResultsSettings(true);
        public boolean wasFailureCommunicationBased(SQLException exception, Connection connection, AbstractSession sessionForProfile){
            if (connection == null || this.pingSQL == null){
                //Without a connection we are  unable to determine what caused the error so return false.
                //The only case where connection will be null should be External Connection Pooling so
                //returning false is ok as there is no connection management requirement
                    //If there is no ping sql then we can not perform the ping.
                return false;
            PreparedStatement statement = null;
            try{
                sessionForProfile.startOperationProfile(SessionProfiler.ConnectionPing);
                if (sessionForProfile.shouldLog(SessionLog.FINE, SessionLog.SQL)) {// Avoid printing if no logging required.
                     sessionForProfile.log(SessionLog.FINE, SessionLog.SQL, getPingSQL(), (Object[])null, null, false);
                statement = connection.prepareStatement(getPingSQL());
                ResultSet result = statement.executeQuery();
                result.close();
                statement.close();
            }catch (SQLException ex){
                try{
                    // Had to add this check because of NullPointerExceptions
                    // (maybe a bug?)
                    if(statement != null){
                        //try to close statement again in case the query or result.close() caused an exception.
                        statement.close();
                } catch (SQLException exception2) {
                    //ignore;
                return true;
            }finally{
                sessionForProfile.endOperationProfile(SessionProfiler.ConnectionPing);
            return false;
    }(As you can see, I had to override the <tt>wasFailureCommunicationBased()</tt> method as well, due to some unexpected NPE's. (A bug, perhaps?))
    This code does work. However, the performance is not very well. The first page comes relatively fast, but as you browse further in the table, each page comes slower. I assume this is because the counter() method has to be evaluated for each row in the table.
    I have to get the performance better and constant. Does anyone have an idea how to optimize this further?
    Best regards,
    Bart Kummel

  • 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

Maybe you are looking for