LC ES2 Upgrade to DB2 v9.7?

I have an existing and Operating LC ES2 installation running on WebSphere v6.1 and DB2 v9.5.  I am trying to upgrade our DB2 server to DB2 v9.7 but the LiveCycle Database is not being upgraded.  All my other database converted as expected but with the LiveCycle wont. Has anyone successfully migrated?

Does your OS release/patch and DP release/patch support backup of DB29.7?
Have a look here -> [http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01631170/c01631170.pdf]
Seems you will need at least HP-Ux 11.31 and DP A.06.1.x
Also check logs in '/usr/omni/log' (or the equivalent for HP-UX), you might find more details and some DP return codes.
Daniel

Similar Messages

  • Connect Livecycle ES2 directly to DB2

    Hi ,
    I am trying to connect livecycle ES2 forms directly to mainframe DB2.
    Is there any way I can do so? If yes, How?
    Thanks in advance.

    I believe you are trying to connect LiveCycle with IBM DB2 database server, if yes :
    Please go through the install instructions @ http://help.adobe.com/en_US/livecycle/9.0/documentation.html#task=0,1,2,3,4,5,6&module=-1
    It has all the details to configure/connect LiveCycle ES2 with IBM DB2 database.
    --Santosh

  • Updating Stalled Process Post ES2 Upgrade

    I just upgraded our server from 8.2 to ES2 SP2.  I had several active process instances before the upgrade that I'm testing post upgrade.
    The process I'm testing uses a Query Single Row Operation which is stalling.  It's stalling because I don't have a required parameter(Data Mapping) defined.  This parameter was not required in 8.2 so it worked fine.
    So I fixed that issue with the process(after creating an application and importing the process), and attempted a retry on the process, but that is not working.  Livecycle continues to use the invalid version of the process that does not specify the required parameter when I attempt a retry.
    So, my question is how can I update the "active" version of the upgraded process and retry the stalled process instances?

    The "deploy" option in the application version menu is apparently what I was looking for.

  • ES2 Upgrade on Windows XP

    I'm trying to use the LiveCycle ES2 Installer to upgrade from ES1 to ES2.  I'm having no problems with the installation (or so it appears) until I get to the end of the wizard step labelled "Installing..."  The progress bar goes all the way to the end and then a message appears in the wizard that says, "Please wait while the Adobe LiveCycle ES2 installer is processing.  The installer may take a moment to respond."  The installer appears to get stuck at this point.  I've let it go for close to an hour with nothing happening.  It appears my processor may still be doing some work, but it's tough to tell if it's the installer that's making the light blink.
    I have ES1 installed in Windows XP (yes, I know that's not ideal or supported...it's a development machine) and after adjusting some Java memory settings, it had been working just fine.  I checked the ES2 installation log.  The most recent thing printed there is...
    "Install Uninstaller:  Adobe LiveCycle ES2 (Install All Uninstaller Components) Status:  SUCCESSFUL"
    It does not appear looking through that log that anything went wrong.
    Does anyone have any suggestions or has anyone seen this before?  I appreciate any help you can provide!

    PORT ALREADY IN USE 9000Looks like the new helpdesk system is using port 9000. Ask your support people to change the port number of the helpdesk system. In case they cannot, change it directly in the application Context File, run AutoConfig, and bounce the application services. You should be able to access the application then.

  • Is DB2 version 10.5 supported by LiveCycle ES2?

    We have several LC ES2 environments with DB2 9.5 and we would like to upgrade the database engine. Wich is the highest DB2 version supported by it?
    Kind regards

    Stefan-
    Just to be clear, there are no known incompatibilities with DB2 7.2, and
    we know that there are people who are using Kodo with it without
    problems. However, it is not an officially verified version of the
    database against which we certify Kodo.
    If you have any problems with your testing against DB2, be sure to let
    us know, and we can help work through them.
    In article <c2hi2r$llo$[email protected]>, Stefan wrote:
    Abe White wrote:
    Only version 8.1 is officially supported. Other versions might work, but
    we don't test against them.Is this a real good decision ?
    We have to support many customers having a wide range of databases (mainly
    oracle 8 or 9 or DB2 7.2 or 8.1 respectively).
    We thought that in using kodo we could provide the support needed, because
    database abstraction is handled by kodo.
    Actually we run on kodo 2.5.8 just because we didn't have time to jump to
    3.0 yet. At the time it works quite well with the databases we support, so
    existing applications we will leave at 2.5.8.
    New applications we want to write with kodo 3 because all the new features
    of course are quite nice.
    As far as I understand you now, we could run into deep problems when just
    switching to 3.
    Of course we test our programs against our supported databases, but lets
    say somewhen we would find a case, where the application runs smooth on
    DB2 8 but not DB2 7 any more.
    We could'nt hope for a fix then, could we ?--
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • SIDADM do not have enough previlages to startsap after DB2 upgrade to 9.5

    Hello Anyone,
    I recently upgrade our DB2 version from 8.X to 9.5.2, We run SAP netweaver ECC 5  with DB2.  I can startsap if I do db2start and and then issue a startsap after su to sidadm. Please can anyone advice
    I had followed all instruction of the upgrade guide and OSS notes.
    Many Thanks
    Jacob

    Hi there,
    I have tried to start sap using startsap as user sidadm, it just fails.
    Here is the diag log
    2009-08-17-00.08.37.417658+000 I1A1159            LEVEL: Event
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
    START   : New Diagnostic Log file
    DATA #1 : Build Level, 152 bytes
    Instance "db2met" uses "64" bits and DB2 code release "SQL09052"
    with level identifier "03030107".
    Informational tokens are "DB2 v9.5.0.2", "s080911", "U820796", Fix Pack "2a".
    DATA #2 : System Info, 224 bytes
    System: AIX met01 3 5 00C99E9B4C00
    CPU: total:8 online:4 Threading degree per core:2
    Physical Memory(MB): total:9216 free:3312
    Virtual  Memory(MB): total:16256 free:10323
    Swap     Memory(MB): total:7040 free:7011
    Kernel   Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
                     shmMax:68719476736 shmMin:1 shmIDs:131072
                     shmSegments:68719476736 semIDs:131072 semNumPerID:65535
                     semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)
    2009-08-17-00.08.37.416595+000 I1161A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198683.LOG.
    2009-08-17-00.08.40.766956+000 I1524A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198683.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-02.13.33.102389+000 I1948A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198684.LOG.
    2009-08-17-02.13.36.482971+000 I2311A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198684.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-04.18.30.684538+000 I2735A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198685.LOG.
    2009-08-17-04.18.33.790534+000 I3098A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198685.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-06.23.26.267522+000 I3522A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198686.LOG.
    2009-08-17-06.23.29.483758+000 I3885A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198686.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-08.28.20.019219+000 I4309A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198687.LOG.
    2009-08-17-08.28.23.436688+000 I4672A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198687.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-10.24.00.636902+000 I5096A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198688.LOG.
    2009-08-17-10.24.05.195763+000 I5459A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198688.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-10.34.04.480384+000 I5883A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198689.LOG.
    2009-08-17-10.34.08.011061+000 I6246A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198689.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-12.39.10.127139+000 I6670A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198690.LOG.
    2009-08-17-12.39.12.681469+000 I7033A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198690.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-14.44.14.029881+000 I7457A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198691.LOG.
    2009-08-17-14.44.17.094413+000 I7820A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198691.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-16.49.06.646666+000 I8244A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198692.LOG.
    2009-08-17-16.49.10.213526+000 I8607A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198692.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    2009-08-17-18.53.50.528211+000 I9031A362          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0198693.LOG.
    2009-08-17-18.53.54.264228+000 I9394A423          LEVEL: Warning
    PID     : 139326               TID  : 2881        PROC : db2sysc 0
    INSTANCE: db2met               NODE : 000
    EDUID   : 2881                 EDUNAME: db2logmgr (MET) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0198693.LOG to TSM chain 97 from
              /db2/MET/log_dir/NODE0000/.
    Many Thanks
    Jacob

  • Upgrading db2 connect thin client from v9.1 to v9.5

    I'm looking for instructions on how to upgrade the db2 connect thin client CLI and JDBC drivers from v9.1 to v9.5 (latest fixpack). I found note 867976 describing how to update the JDBC portion. I'm wondering if there is an official way of upgrading the CLI client, now that this is normally automatically installed as part of the SAPINST process.  We want to upgrade our system from v9.1 thin client ot v9.5 thin client to use the new functionality.
    (We have instructions for upgrading from v9 Fat client to v9.5 thin client.)

    1.Copied new driver version into db2_clidriver and jdbc folders.
    2. Ran db2radm to bind new collection
    3. Used sappad to change connect.ini file back to Unix format.
    4. Restarted Cluster.
    New version working now.

  • DB2 upgrade to 10.5

    Hi,
    We have planned for the db2 upgrade from V9.7 FP5 to V10.1 FP3 and we have about 10 application servers to our ERP system.
    Apart from the execution of db6_update_client.sh , is there any particular steps needs to be done for application servers during upgrade ? or is it just the db2 upgrade on DB server and the execution of db6_update_client.sh script ?
    Best Regards,
    DVRK

    Hi,
    1. Prerequisites for a successful upgrade to DB2 LUW Version 10.5
      - Ref. SAP Note:1837312 - DB6: Upgrade to Version 10.5 of DB2 for LUW
    2. Make sure you are using the latest db6_update_client script.sh script
      - Ref. SAP Note: 1365982 - DB6: Current db6_update_db/db6_update_client script (V41)
    3. Check the required minimum SAP Basis Release Levels before you start.
      - Ref. SAP Note: 1851853 - DB6: Using DB2 10.5 with SAP Applications
    4. Install SAP Note 1835822 on top of your current minimum SAP Basis release
      - So as to avoid having to troubleshoot the DBACockpit thereafter.
    5. Following the above listed steps should preclude your anticipated appilcation server utilization  
        hitches.
        B/Rgds., SAM.

  • DB2 9.5: SAP Work Process Restart Issue

    We just upgraded to DB2 9.5 from DB 8.x. Currently we are having problems with the work process on SAP R/3 4.7 Ext 200. We are seeing the following entry in the work process log:
    M  ThWpRestart: restart wp (pid=1988) automatically
    B
    B Mon Mar 30 00:14:09 2009
    B  Disconnecting from ALL connections:
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost
    B  025 000 R/3              000000000 INACTIVE     NO  YES NO  000 255 255 20090329 190208
    After this entry the work process hangs and it does not get reconnect to the database. Looking at the database snapshots we are not seeing any PID of the work process. We are currently running non-unicode kernel 247. Any come across a problem like this?

    Sounds strange - any special activities running at that time ? E.g. a backup ? Do you see that on all application servers ?
    How to you resolve this situation ?
    What does the db2diag.log show for that time frame ?
    Malte

  • SAP ERP 6.0 EHP4 upgrade from SAP R/3 4.7 1.10

    Dear Experts,
    Our client is going to upgrade current landscape SAP R/3 4.7 1.10 to ERP 6.0 EHP4. The Source system O/s is AIX 5.3 and database is db2 8.1. Client procuring new hardware for the target release ERP 6.0 landscape and the O/s is going to be AIX 7.1 and databse would be db2 9.7 FP3.
    As part of the upgrade we are going to do initial upgrade in the mock server and vendor is going to provide mock server with AIX 7.1 O/S.  Current database size is 100GB, hence we are going to copy the production server data into the mock server using export and import method,
    Here my doubt is can i install db9.7 directly and do the import (using compitable kernel)?, insteady of installing source database version 8.1 and later upgrading to db2 9.7 . Please clarify me whether can i go head and install the db2 9.7 and do the system copy using R3load.
    Thanks and Regards,
    Seshu

    Seshu Mannepalli wrote:
    > As part of the upgrade we are going to do initial upgrade in the mock server and vendor is going to provide mock server with AIX 7.1 O/S.  Current database size is 100GB, hence we are going to copy the production server data into the mock server using export and import method,
    >
    > Here my doubt is can i install db9.7 directly and do the import (using compitable kernel)?, insteady of installing source database version 8.1 and later upgrading to db2 9.7 . Please clarify me whether can i go head and install the db2 9.7 and do the system copy using R3load.
    Hello,
    You can go ahead for IMPORT with DB 9.7.
    We completed an OS/DB Migration Project (which involves system copy using EXPORT/IMPORT) and we utilized direct newer version of DB2 on the target during IMPORT.
    But please confirm whether the kernel of your release would work fine with DB 9.7 or not. Otherwise, there is no problem in going for higher version of DB2 here.
    Small question -  Why you want to test the Mock Upgrade on DB2 version which is different than the current version on production server ? Or are you planning to upgrade your current DB2 8 to DB2 9.7 BEFORE the SAP Upgrade on all the servers - then the testing is OK I think (however OS is still the different - Or may be you will go for system copies for this too !)
    Thanks

  • Cannot connect to DB2 on XP

    I have a weird problem. I'm using a Type-2 JDBC driver for DB2. My development environment is on XP using VisualAge. On that platform, I cannot connect to the DB2 database. The environment this program runs on is an NT 4.0 machine. On there, the same code works fine.
    The DB2 libs are in c:\sqllib\java and are contained in the zip files db2java.zip and runtime.zip. In both environments, (both DOS cmd line and VAJ) these zip files are in the classpath.
    On XP, the line
    Class.forName("COM.ibm..db2.jdbc.app.DB2Driver");
    does load the class. However, when I go to register the driver I get the error:
    "No suitable driver"
    The alias I am trying to connect to is cataloged on my machine. I can access it through RapidSQL and the command line db2 client. Is it possible that the driver is not compatible with WinXP? Can anyone think of another reason why this would not work on XP but work on NT 4.0.
    Thanks,
    Curt

    Hello,
    I ran into a very similar problem when I upgraded to DB2 V7.2 in that my application could not find a Type 2 driver. I would recommend trying the same application using a Type1 driver just to see if you are running into the same bug I ran into.
    To make the switch to a Type 1 driver go to c:\sqllib\java12 and issue the usejdbc1 command from the command line. You may have to back out of everything to avoid sharing violations. After I did this I was able to execute my application successfully. I am not sure if there is a fixpack available for this problem yet.
    Please report your results.
    Regards,
    Bill

  • Does Toplink 9.0.3.5 version support DB2 Version 8

    Hi
    In our enterprise, we use Toplink 9.0.3.5. This is an old version of toplink.
    DB2 is the database used in our enterprise.
    Now, our enterprise is planning to upgrade to DB2 Version 8.
    I would need to know whether Toplink 9.0.3.5 version will support DB2 Version 8.

    We have certified 9.0.4 against DB2 v8. The details are available here.
    I have no reason to believe 9.0.3.X would not function with standard functionality offered by this version of DB2. If you encounter specific issues please let us know and we'll do our best to provide some solution options.
    Doug

  • DB2 V9.1.5 compatiblilty to Business Object V5.1.2

    We are currently using Business Object v5.1.2 and DB2 v8.2. As support of DB2 v8.2 is ending by March2009, we need to upgrade to DB2 v9.1.5. Can DB2 v9.1.5 compatible with Business Object v5.1.2?

    Hi Antonio,
    DB2 v9.1 is not supported with Business Objects v5.1.2.
    DB2 v9.1 is supported with Business Objects XIR2 SP2.
    Hope the above information helps you.
    Regards,
    Anisa

  • DB2 UDB Compression vs performance improvements benchmarks

    Hi
    Are there any bench mark results on the effect of DB2 UDB data compression. Though by theory, this is supposed to improve the performance, even after considering the trade off in the data compression, I am not seeing any real life results on this.
    If there are any, particularly for the BI 7.0, please let me know.
    Thanks
    Raj

    Hello,
    >> http://www-306.ibm.com/software/success/cssdb.nsf/CS/STRD-6Z2KE3?OpenDocument&Site=corp&cty=en_us
    at first i wanna say, that i have no experience and knowledge in DB2, but if i read some statements likes this - i do not wonder about some management discussions/decisions:
    The move from our existing version of DB2 to DB2 9 was very simple, so we didn’t need any external help. Because DB2 9 is backwards-compatible, there was no need to upgrade our SAP software
    With the STMM, we can tune the buffer pool automatically, which saves considerable time for our database administrators – reducing their workload by around 10 per cent.”
    Our database is now 43 per cent smaller than before, and some of the largest tables have been reduced by up to 70 per cent
    With DB2 9, our two-person IT team can handle database administration on top of all their other work, even without much specialist knowledge
    Please correct me, if i am wrong and DB2 can really handle this:
    1) Is the upgrade to DB2 9 really a big step or anything really hard to handle? I don't think so...
    2) Are memory settings really so time-consuming in DB2, that a SAP administrator is spending 4 hours per week on that (if he works 40 hours per week)? I don't think so..
    3) I have read some documents about the compression feature and it really seems to be great, but maybe an reorg would also make a benefit from round about 10-20%? All these aspects are not mentioned anywhere.
    4) DB administration without special know-how in DB2? I could not believe that.... if you want a fast and stable environment
    I am also very interested in some performance facts / data with compression and performance issues in DB2, but i am searching for real-data and not only some "manager" statements.
    What i am searching for is a benchmark with defined load simulations and analysis like this one from oracle:
    http://regmedia.co.uk/2007/05/20/ibmpower6.pdf
    Does anyone have some links to that kind of benchmarks?
    Regards
    Stefan

  • J2EE failover HA OSS note  1085521 - startup with primary db2 unavailable

    We have implemented J2EE HA failover solution according to OSS note 1085521.
    We have an SAP system called SXD with primary db2 SXD1 and standy db2 SXDA.  If JAVA is running against SXD1 and this Db2 subsystem is stopped/abends, then JAVA switches over to continue running on SXDA. However, if we then cycle the JAVA instance, it does not startup any more until we restart the primary SXD1 Db2 subsystem. Is this the way the design for the JAVA failover works, or do you think we must have an incorrect setting somewhere ?
    The ABAP stack of the same SAP system works fine and can be restarted without problems even when the primary Db2 is stopped.

    This problem is resolved after implementing latest 1085521 recommendations and upgrading to Db2 connect v9.5

Maybe you are looking for