Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Step 3. Bind Packages on the Database Server

Step 3. Bind Packages on the Database Server

To ensure that the IBM DB2 client can connect to the database server to run DB2 commands, bind packages on the database server.
  1. Open an IBM DB2 command window, and change to the following directory:
    <
    IBM DB2 installation directory
    >/SQLLIB/bnd
  2. Connect to the database by running the following command:
    db2 connect to <
    database name
    > user <
    database user
    > using <
    database user password
    >
    The database user must have the bind permission.
  3. Run the following bind command:
    db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG 10
    The required packages are bound to the database server.

0 COMMENTS

We’d like to hear from you!