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.7.1

Upgrading from Version 9.7.1

Step 7. Update Operational Reference Stores Schemas with the Source DDLs and Data

Step 7. Update Operational Reference Stores Schemas with the Source DDLs and Data

After you create Operational Reference Stores in IBM DB2 with Oracle-compatibility disabled and import seed into them, update the Operational Reference Stores with source DDL and data.
  1. To connect to the new database, run the following command:
    db2 CONNECT TO <
    new database name
    > USER db2admin USING <
    password
    >
  2. To grant privileges to the
    db2move
    command, run the following command:
    db2 GRANT EXECUTE ON PACKAGE NULLID.DB2MOVE TO USER <
    Operational Reference Store user
    >
  3. To grant privileges to the
    db2commo
    command, run the following command:
    db2 GRANT EXECUTE ON PACKAGE NULLID.DB2COMMO TO USER <
    Operational Reference Store user
    >
  4. To break the connection to the database, run the following command:
    db2 CONNECT RESET
  5. Change directory to the Operational Reference Store directory.
  6. To apply any applicable DDL changes to the Operational Reference Store schema, run the following command:
    db2 -tvf <
    Operational Reference Store
    >.ddl > <
    Operational Reference Store
    >.out
    The
    <
    Operational Reference Store
    >.out
    file is created.
  7. Check the
    <
    Operational Reference Store
    >.out
    file.
    Ignore any errors for existing tables or indexes.
  8. To generate the required permissions for the Operational Reference Store, run the following command:
    db2 -tvf <
    Operational Reference Store
    >2.ddl > <
    Operational Reference Store
    >2.out
  9. Check the
    <
    Operational Reference Store
    >2.out
    file for errors.
  10. To populate the Operational Reference Store schema, run the following command:
    db2move <
    new database name
    > load -lo REPLACE -u <
    Operational Reference Store user
    > -p <
    password
    >> db2move_load_<
    Operational Reference Store name
    >.out
    The
    db2move_load_<
    Operational Reference Store
    >.out
    file is created.
  11. To connect to the new database, run the following command:
    db2 connect to <
    new database name
    > user <
    Operational Reference Store user
    > using <
    password
    >
  12. To generate a script for SET INTEGRITY SQL commands, run the following command:
    On UNIX.
    db2 "select 'SET INTEGRITY FOR ' CONCAT trim(BOTH FROM tabschema) CONCAT '.' CONCAT trim(BOTH FROM tabname) CONCAT ' IMMEDIATE CHECKED@' from syscat.tables where tabschema='<
    OPERATIONAL REFERENCE STORE USER
    >' and status='C'" > <
    Operational Reference Store
    >_check.sql
    On Windows.
    db2 select 'SET INTEGRITY FOR ' CONCAT trim(BOTH FROM tabschema) CONCAT '.' CONCAT trim(BOTH FROM tabname) CONCAT ' IMMEDIATE CHECKED@' from syscat.tables where tabschema='<
    OPERATIONAL REFERENCE STORE USER
    >' and status='C' > <
    Operational Reference Store
    >_check.sql
    Specify the value for <
    OPERATIONAL REFERENCE STORE USER
    > in upper case.
    The
    <
    Operational Reference Store
    >_check.sql
    script is generated.
  13. Review
    <
    Operational Reference Store
    >_check.sql
    and ensure that it contains only SQL statements.
  14. To run the SET INTEGRITY script, run the following command:
    db2 -td@ -vf <
    Operational Reference Store
    >_check.sql
    Run the script five times so that interdependencies between the database tables get covered.

0 COMMENTS

We’d like to hear from you!