Installation Instructions for WebSphere Lombardi Edition V7.2.0 Fix Pack 4 (V7.2.0.4)

Product documentation


Abstract

This document provides the installation instructions for IBM WebSphere Lombardi Edition (WLE), Version 7.2.0 Fix Pack 4 (V7.2.0.4).

Content

It includes information that is specific to the Microsoft Windows and AIX, HP-UX, Red Hat Enterprise Linux (RHEL), Solaris, SUSE Linux operating systems.



The following tabs provide access to information you would need to know while installing, uninstalling, and reinstalling WebSphere Lombardi Edition, Version 7.2.0 Fix Pack 4 (V7.2.0.4) .

  • This fix pack requires a minimum of 5 GB disk space for complete installation.

  • Extract the contents of the compressed package for the fix pack to a temporary directory. In this document, we will refer to this directory as WLE_fixpack_installer_dir.

    For Windows operating systems, it would be C:\Temp\WLE-7.2.0.4-FixPack\.

    For UNIX-based operating systems, it would be /tmp/WLE-7.2.0.4-FixPack/.
    Note:
    The UNIX operating system zip library is needed while extracting the fix pack.

  • You can apply this fix pack to WebSphere Lombardi Edition Version 7.2.0 and later.
    CAUTION
    : This fix pack cannot be used for installing any other version of the WebSphere Lombardi Edition.

  • This fix pack requires WebSphere Application Server Version 7.0.0 Fix Pack 7 or later.
    Note:
    It is recommended that customers download and upgrade their WebSphere Application Server to the latest fix pack.

  • Ensure that JAVA_HOME is set to the location of the Java™ Development Kit used within the WebSphere product.

    For Windows operating systems, you need to set JAVA_HOME=WLE_install_dir\AppServer\java, where WLE_install_dir is the directory in which WebSphere Lombardi Edition is installed. Use set PATH=%JAVA_HOME%\bin;%JAVA_HOME%\lib;%PATH%

    For UNIX-based operating systems, you need to export JAVA_HOME=WLE_install_dir/AppServer/java
    Use export PATH=$JAVA_HOME/bin:$JAVA_HOME/lib:$PATH

  • Ensure that database users have the required authorization or privilege to drop, create, and run stored procedures while accessing the Process Center and Process Server databases. These users are listed in the ProcDB.properties file, which is located in the WLE_install_dir\twinit\resources directory for Windows operating systems and the WLE_install_dir/twinit/resources directory for UNIX-based operating systems.


Note: Before you apply WebSphere Lombardi Edition Version 7.2.0 Fix Pack 4, create backup copies of your existing WebSphere Lombardi Edition databases on your system.

Backups enable you to revert to the pre-upgrade state of the databases at any time, if necessary.
Note: You need to create backups of the Process Center databases and the databases in each runtime environment.

Most databases provide a backup wizard or other user assistance for creating database backups. Contact your database administrator for more information.

Process Center​


Note:
The following steps will update the IBM Process Center installation and also the embedded Authoring Environments.
  1. Stop the Process Center and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. If you are upgrading from V7.2.0 and are affected by an issue, where the password is not encrypted for proxy settings in the 99Local.xml file, then follow the steps provided below:
    1. Locate the file 99WLEFixPack7204.xml in the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\99WLEFixPack7204.xml.

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/99WLEFixPack7204.xml.

    2. Uncomment the section corresponding to this issue and edit the relevant properties based on your environment.

  3. Optional: Complete the following steps if you have changed the default password for the users tw_admin and tw_user using the process described in Changing the default user passwords on IBM WebSphere Lombardi Edition.
    1. Locate the file user.properties file inside the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\user.properties

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/user.properties
    2. Update the file with the modified password. The password should be in non-encrypted text.

  4. From the WLE_fixpack_installer_dir directory:

    Run the following command for Windows operating systems:
    install_fixpack.cmd WLE_install_dir

    For example: install_fixpack.cmd C:\IBM\Lombardi7.

    Note:
    After the installation is complete, you can find the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    Run the following commands for UNIX-based operating systems:
    1. chmod +x install_fixpack.sh

    2. ./install_fixpack.sh WLE_install_dir 

      For example: ./install_fixpack.sh/Lombardi7

      Note:
      After the installation is complete, you can find the backup files under WLE_install_dir/wlebackup/before7.2.0.4.
      Note: Review the Known Issues section for the list of issues fixed in the previous V7.2.0 fix packs. Wherever applicable for your installation, apply the required steps.

  5. Start both the Process Center and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run startLombardi.cmd.

      For UNIX-based operating systems, run ./startLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to start the relevant service.

Note:
After completing the installation, ensure that you complete the following steps for updating your process application.

Although the install_fixpack command updates the System Data toolkit to Version 7.2.0 Fix Pack 4, it does not automatically update the existing dependencies. Update the existing dependencies using the following steps for each process application and toolkit:
  1. Start the Authoring Environment.
  2. Open the existing application in the authoring environment.
  3. Under Toolkits, right-click System Data toolkit.
  4. Select Change Version of dependency.
  5. Select the 7.2.0.4 snapshot from the Change Dependency snapshot list.


Authoring Environments
  • For the embedded Authoring Environment in Process Center installation, the fix pack is applied when you install it on the Process Center.
  • For all the standalone Authoring Environments, delete the existing ones, download from the Process Center, and extract the updated Authoring Environment.

Note:
Ensure that you initiate the download after installing the fix pack on the Process Center and the Process Center server is started.


Process Server​
  1. Stop the Process Server and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.
    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. If you are upgrading from V7.2.0 and are affected by an issue, where the password is not encrypted for Proxy settings in the 99Local.xml file, then follow the steps provided below:
    1. Locate the file 99WLEFixPack7204.xml in the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\99WLEFixPack7204.xml

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/99WLEFixPack7204.xml.

    2. Uncomment the section corresponding to this issue and edit the relevant properties based on your environment.

  3. Optional: Complete the following steps if you have changed the default password for the users tw_admin and tw_user using the process described in Changing the default user passwords on IBM WebSphere Lombardi Edition.
    1. Locate the user.properties file inside the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\user.properties

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/user.properties

    2. Update the file with the modified password. The password should be in non-encrypted text.

  4. From the WLE_fixpack_installer_dir directory:

    Run the following command for Windows operating systems:
    install_fixpack.cmd WLE_install_dir

    For example: install_fixpack.cmd C:\IBM\Lombardi7.

    Note:
    After the installation is complete, you can find the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    Run the following commands for UNIX-based operating systems:
    1. chmod +x install_fixpack.sh

    2. ./install_fixpack.sh WLE_install_dir 

      For example: ./install_fixpack.sh/Lombardi7

      Note: After the installation is complete, you can find the backup files under WLE_install_dir/wlebackup/before7.2.0.4.
      Note: Review the Known Issues section for the list of issues fixed in the previous V7.2.0 fix packs. Wherever applicable for your installation, apply the required steps.

  5. Start both the Process Server and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

      For Windows operating systems, run startLombardi.cmd.

      For UNIX-based operating systems, run ./startLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to start the relevant service.

  6. Deactivate 7.2.0, 7.2.0 Fix Pack 1, 7.2.0 Fix Pack 2 and 7.2.0 Fix Pack 3 Process Portal Application, only. Process Portal(TWP) - 7.2.0 Fix Pack 4 needs to be active.
    1. Login to Process Admin and locate the application Process Portal(TWP) - 7.2.0, Process Portal (TWP) - 7.2.0.1, Process Portal (TWP) - 7.2.0.2 and Process Portal (TWP) - 7.2.0.3 under installed applications.

    2. Select the application and in the following screen select Deactivate Application.

Process Server Cluster Environment​

Note:
  • Repeat step 4 for each server in the cluster environment.

  • Review the Known Issues section for the list of issues fixed in the previous V7.2.0 fix packs. Wherever applicable for your installation, apply the required steps.
  1. Stop all the nodes, the Process Server, and the Performance Data Warehouse in your entire cluster environment.

  2. If you are upgrading from V7.2.0 and are affected by an issue, where the password is not encrypted for Proxy settings in the 99Local.xml file, then follow the steps provided below:

    1. Locate the 99WLEFixPack7204.xml file in the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\99WLEFixPack7204.xml

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/99WLEFixPack7204.xml.

    2. Uncomment the section corresponding to this issue and edit the relevant properties based on your environment.

  3. Optional: Complete the following steps if you have changed the default password for the users tw_admin and tw_user using the process described in Changing the default user passwords on IBM WebSphere Lombardi Edition.
    1. Locate the user.properties file inside the content directory.

      For Windows operating systems, it would be WLE_fixpack_installer_dir\content\user.properties

      For UNIX-based operating systems, it would be WLE_fixpack_installer_dir/content/user.properties
    2. Update the file with the modified password. The password should be in non-encrypted text.

  4. From the WLE_fixpack_installer_dir directory:

    Run the following command for Windows operating systems:
    install_fixpack.cmd WLE_install_dir

    For example: install_fixpack.cmd C:\IBM\Lombardi7.

    Note: After the installation is complete, you can find the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    Run the following commands for UNIX-based operating systems:
    1. chmod +x install_fixpack.sh

    2. ./install_fixpack.sh WLE_install_dir 

      For example: ./install_fixpack.sh/Lombardi7

      Note: After the installation is complete, you can find the backup files under WLE_install_dir/wlebackup/before7.2.0.4.

  5. Start the Deployment Manager by running the startManager command.

    For Windows operating systems, the command is C:\IBM\Lombardi7\AppServer\profiles\Dmgr01\bin>startManager.bat.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Dmgr01/bin>./startManager.sh.

    For more information about starting Deployment Manager, see startManager command.

    Note: If you have configured the WebSphere Lombardi Edition deployment manager to run as a Windows or Linux service, you need to start the relevant service.

  6. After the Deployment Manager starts, synchronize each node one at a time by using the syncNode command.

    For example:

    For Windows operating systems, the command is C:\IBM\Lombardi7\AppServer\profiles\Lombardi\bin>syncNode.bat ProdNode1.example.com -user tw_user -password tw_user.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Lombardi01/bin>./syncNode.sh ProdNode1.example.com -user tw_user -password tw_user

    Note:
    If you have modified the default Deployment Manager SOAP port, you must specify the port in the previous commands immediately after the host name for the primary node. For more information about synchronizing nodes, see syncNode command.

  7. Start all the nodes, Process Server, and Performance Data Warehouse in your entire cluster environment.

  8. Deactivate 7.2.0, 7.2.0 Fix Pack 1, 7.2.0 Fix Pack 2 and 7.2.0 Fix Pack 3 Process Portal Application, only Process Portal(TWP) - 7.2.0 Fix Pack 4 needs to be active.
    1. Login to Process Admin and Locate the application Process Portal(TWP) - 7.2.0, Process Portal (TWP) - 7.2.0.1, Process Portal (TWP) - 7.2.0.2 and Process Portal (TWP) - 7.2.0.3 under installed applications.

    2. Select the application and, in the following screen, select Deactivate Application.


Note: After uninstalling Version 7.2.0 Fix Pack 4, the databases are not reverted to the pre-upgrade state. You need to restore your database to revert to the pre-upgrade state after uninstallation, if necessary.

Note: Both the Process Center databases and the databases in each runtime environment need to be restored.

Most databases provide a restore wizard or other user assistance for restoring database backups. Contact your database administrator for more information.

Process Center
  1. Stop the Process Center and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. From the WLE_fixpack_installer_dir directory:

    For Windows operating systems, execute the following command:
    install_fixpack.cmd WLE_install_dir uninstall

    For example: install_fixpack.cmd C:\IBM\Lombardi7 uninstall

    For UNIX-based operating systems, execute the following command:
    ./install_fixpack.sh WLE_install_dir  uninstall

    For example: ./install_fixpack.sh /Lombardi7 uninstall

Process Server
  1. Stop the Process Server and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. From the WLE_fixpack_installer_dir directory:

    For Windows operating systems, run the following command:
    install_fixpack.cmd WLE_install_dir uninstall

    For example: install_fixpack.cmd C:\IBM\Lombardi7 uninstall

    For UNIX-based operating systems, run the following commands:
    ./install_fixpack.sh WLE_install_dir uninstall

    For example: ./install_fixpack.sh /Lombardi7 uninstall

Process Server Cluster Environment

Note: Repeat the step 2 below for each server in the cluster environment.
  1. Stop all the nodes, Process Server, and Performance Data Warehouse in your entire cluster environment.

  2. From the WLE_fixpack_installer_dir directory:

    For Windows operating systems, execute the following command:
    install_fixpack.cmd WLE_install_dir uninstall.

    For example: install_fixpack.cmd C:\IBM\Lombardi7 uninstall

    For UNIX-based operating systems, execute the following commands:
    ./install_fixpack.sh WLE_install_dir uninstall

    For example: ./install_fixpack.sh /Lombardi7 uninstall

  3. Start the Deployment Manager by running the startManager command.

    For Windows operating systems, the command is C:\IBM\Lombardi7\AppServer\profiles\Dmgr01\bin>startManager.bat.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Dmgr01/bin>./startManager.sh

    For more information about starting Deployment Manager, see the startManager command.

    Note: If you have configured WebSphere Lombardi Edition deployment manager to run as a Windows or Linux service, you need to start the relevant service.

  4. After the Deployment Manager starts, synchronize each node one at a time by using the syncNode command.

    For Windows operating systems, the command is C:\IBM\Lombardi7\AppServer\profiles\Lombardi\bin>syncNode.bat ProdNode1.example.com -user tw_user -password tw_user.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Lombardi01/bin>./syncNode.sh ProdNode1.example.com -user tw_user -password tw_user
    Note: If you have modified the default Deployment Manager SOAP port, you must specify the port in the previous commands immediately after the host name for the primary node. For more information about synchronizing nodes, see syncNode command.


Note: The steps in this section can be performed only if you have uninstalled the fix pack Version 7.2.0 Fix Pack 4 and have not restored your database to the pre-upgrade state.

Process Center
  1. Stop the Process Center and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. From the WLE_fixpack_installer_dir directory:

    For Windows operating systems, run the following command:
    install_fixpack.cmd WLE_install_dir reinstall

    For example: install_fixpack.cmd C:\IBM\Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    For UNIX-based operating systems, run the following command:
    ./install_fixpack.sh WLE_install_dir reinstall

    For example: ./install_fixpack.sh /Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir/wlebackup/before7.2.0.4.

Process Server
  1. Stop the Process Server and Performance Data Warehouse:
    1. From a command prompt, navigate to the WLE_install_dir\bin directory.

    2. For Windows operating systems, run stopLombardi.cmd.

      For UNIX-based operating systems, run ./stopLombardi.sh.

      Note: If you have configured WebSphere Lombardi Edition to run as a Windows or Linux service, you need to stop the relevant service.

  2. From the WLE_fixpack_installer_dir directory:

    For Windows operating systems, execute the following command:
    install_fixpack.cmd WLE_install_dir reinstall

    For example: install_fixpack.cmd C:\IBM\Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    For UNIX-based operating systems, execute the following command:
    ./install_fixpack.sh WLE_install_dir reinstall

    For example: ./install_fixpack.sh /Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir/wlebackup/before7.2.0.4.

Process Server Cluster Environment

Note: Repeat the step 2 below for each server in the cluster environment.
  1. Stop all the Nodes, Process Server, and Performance Data Warehouse in your entire cluster environment.

  2. From the WLE_fixpack_installer_dir directory,

    For Windows operating systems, execute the following command:
    install_fixpack.cmd WLE_install_dir reinstall

    For example: install_fixpack.cmd C:\IBM\Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir\wlebackup\before7.2.0.4.

    For UNIX-based operating systems, execute the following command:
    ./install_fixpack.sh WLE_install_dir reinstall

    For example: ./install_fixpack.sh /Lombardi7 reinstall

    Note:
    After installation is complete, you can find out the backup files under WLE_install_dir/wlebackup/before7.2.0.4.

  3. Start the Deployment Manager by running the startManager command.

    For Windows operating systems, the command is C:\IBM\Lombardi7\AppServer\profiles\Dmgr01\bin>startManager.bat.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Dmgr01/bin>./startManager.sh

    For more information about starting Deployment Manager, see startManager command.

    Note: If you have configured the WebSphere Lombardi Edition deployment manager to run as a Windows or Linux service, you need to start the relevant service.

  4. After the Deployment Manager starts, synchronize each node one at a time by using the syncNode command.

    For Windows operating systems, the command is C:/IBM/Lombardi7/AppServer/profiles/Lombardi/bin>syncNode.bat ProdNode1.example.com -user tw_user -password tw_user.

    For UNIX-based operating systems, the command is /Lombardi7/AppServer/profiles/Lombardi01/bin>./syncNode.sh ProdNode1.example.com -user tw_user -password tw_user.
    Note: If you have modified the default Deployment Manager SOAP port, you must specify the port in the previous commands immediately after the host name for the primary node.
    For more information about synchronizing nodes, see syncNode command.


This section lists the suggested fixes for issues identified in the previous V7.2.0 fix packs. For the complete list of fixes provided in the previous V7.2.0 fix packs, see Fix list for IBM WebSphere Lombardi Edition Versions 7.2 and 7.1.

Issues Common to Process Center, Process Server, and Process Server Cluster Environment

If you are upgrading from V7.2.0 Fix Pack 2 or V7.2.0 Fix Pack 3 to V7.2.0 Fix Pack 4, then you can skip the following steps needed for tuning the performance database.
  • If the user belongs to a large number of dynamic groups and has slow inbox query performance, the database administrator must complete the following steps:
    Check for an index named IDX8_LSW_TASK exists in the LSW_TASK table in the Process Center database and/or Process Server database. If it does not exist, run the following SQL statement:
    CREATE INDEX IDX8_LSW_TASK ON LSW_TASK("BPD_INSTANCE_ID","STATUS","PRIORITY_ID","GROUP_ID",
    "USER_ID")
     

  • If you have a deadlock for LSW_TIMING_INTERVAL_VALUE during volume database creation, a database administrator must complete the following steps:
    Check if an index named LSWC_TMNGIVLVAL_I exists in the LSW_TIMING_INTERVAL_VALUE table in the Performance Data Warehouse database. If it does not exist, the database administrator must run the following SQL statement:
    CREATE INDEX LSWC_TMNGIVLVAL_I ON LSW_TIMING_INTERVAL_VALUE("FUNCTIONAL_TASK_ID","TIMING_INTERVAL_ID") 

It is advisable to upgrade your WebSphere Application Server to the latest fix pack. The following issues have been addressed in the WebSphere Application Server fix packs:

For IC74641, update the wimconfig.xml file as follows:
  1. For Windows operating systems, locate the PROFILE_HOME\config\cells\<NODE_NAME>\wim\config\wimconfig.xml file.

    For UNIX-based operating systems, locate the PROFILE_HOME/config/cells/<NODE_NAME>/wim/config/wimconfig.xml file.

  2. Copy the wimconfig.xml file as wimconfig.xml.before7.2.0.4

  3. Change the following line in the wimconfig.xml file:
    <config:userDisplayNameMapping propertyForInput="principalName" propertyForOutput="principalName"/>

    to

    <config:userDisplayNameMapping propertyForInput="displayName" propertyForOutput="displayName"/>

    Note:
    This instruction was provided as part of WebSphere Lombardi Edition Version 7.2.0 Fix Pack 2. You can skip this step if you are upgrading from 7.2.0 Fix Pack 2 or 7.2.0 Fix Pack 3 to 7.2.0 Fix Pack 4


For Java Runtime Environment (JRE) error during WebSphere Lombardi Edition Version 7.2.0 Fix Pack 4 installation, the following error is caused if a JRE is used instead of Java Development Kit (JDK):

For Windows operating systems, the error message is
[native2ascii] Converting 1 file from WLE_fixpack_installer_dir\language-packs\temp\lp_1272289518\temp to WLE_fixpack_installer_dir\language-packs\temp\lp_1272289518\temp

For UNIX-based operating systems, the error message is
[native2ascii] Converting 1 file from WLE_fixpack_installer_dir/language-packs/temp/lp_1272289518/temp to WLE_fixpack_installer_dir/language-packs/temp/lp_1272289518/temp

Reason:
This error is due to WebSphere Lombardi Edition 7.2.0 Fix Pack 4 installer using a JRE, not a JDK.

Solution:
Ensure that the JAVA_HOME environment variable is configured to use a JDK, not JRE.


When you install the fix pack, you might encounter an error regarding the update of the stored procedure as shown below:

[exec] upgradeProcDbStructure:
     [exec]
     [exec] executeSQLFile:
     [exec] [execute 7204Structure.sql for process-server ] DBLoad starting
     [exec] [execute 7204Structure.sql for process-server ] DBLoad dbdriver : com.ibm.db2.jcc.DB2Driver
     [exec] [execute 7204Structure.sql for process-server ] DBLoad dburl : jdbc:db2://hostname:50010/xyz
     [exec] [execute 7204Structure.sql for process-server ] DBLoad dbuser : LOMUSER
     [exec] [execute 7204Structure.sql for process-server ] Error executing SQL statement
     [exec] [execute 7204Structure.sql for process-server ] DROP PROCEDURE LSW_HOUSE_KEEPING
     [exec] [execute 7204Structure.sql for process-server ]
     [exec] [execute 7204Structure.sql for process-server ] See error logs for more information.
     [exec] [execute 7204Structure.sql for process-server ] SQL error: com.ibm.db2.jcc.am.vo: DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=LOMUSER;DROP PROGRAM;LOMUSER.P7440570, DRIVER=4.8.87
     [exec] [execute 7204Structure.sql for process-server ] Error executing SQL statement

Reason: This error is due to lack of privileges to drop, create, and run stored procedures.

Solution: Ensure that database users have the required authorization or privilege to drop, create, and run stored procedures while accessing the Process Center and Process Server databases.

Original publication date

2012/7/14

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Lombardi Edition
Installation / Configuration

Software version:

7.2.0.4

Operating system(s):

AIX, Linux, Linux zSeries, Solaris, Windows

Reference #:

7027567

Modified date:

2012-07-05

Translate my page

Machine Translation

Content navigation