Table of Contents

Search

  1. Preface
  2. PowerExchange Installation and Upgrade Overview
  3. Installation Planning
  4. Upgrade Planning
  5. Installing and Upgrading PowerExchange on IBM i
  6. Installing and Upgrading PowerExchange on Linux and UNIX
  7. Installing and Upgrading PowerExchange on Windows
  8. Installing and Upgrading PowerExchange on z/OS
  9. Appendix A: Upgrade Considerations
  10. Appendix B: PowerExchange Environment
  11. Appendix C: Manual Installation on IBM i

Installation and Upgrade Guide

Installation and Upgrade Guide

Step 1. Stop Access to PowerExchange

Step 1. Stop Access to PowerExchange

Before you upgrade, you must stop some PowerExchange and PowerCenter tasks.
  1. If you use PowerExchange bulk data movement only, stop the following tasks:
    • All PowerCenter workflows that extract data from or write data to PowerExchange
    • All PowerExchange Listener address spaces
  2. If you use PowerExchange CDC, stop the following tasks:
    • All PowerCenter workflows that extract data from or write data to PowerExchange
    • All PowerExchange Listener address spaces
    • All ECCR address spaces
    • All PowerExchange Condense address spaces
    • All PowerExchange Logger for z/OS address spaces
    • All PowerExchange Agent address spaces
    To stop the Db2 for z/OS ECCR, use the ECCR QUIESCE command. This command stops the ECCR after it reaches a point in the Db2 log where no in-flight UOWs exist.
    Use the following syntax to issue the QUIESCE command:
    F
    job_name
    ,QUIESCE
    The
    job_name
    variable is the name of the ECCR job or the started task.
    The resulting output includes the PWXEDM177268I and PWXEDM177012I messages, as shown in the following example:
    PWXEDM177268I LAST READ DB2 LOG LOCATION=
    rba_or_lrsn
    .
    data_sharing_member_id
    .
    sequence_number
    PWXEDM177012I ECCR STATUS: LAST DB2 READ LOC
    rba_or_lrsn
    .
    data_sharing_member_id
    .
    sequence_number
    OLDEST OPEN UOW
    urid
    .
    data_sharing_member_id
    You will need the values in these messages if you have to perform a special start of the ECCR. For more information, see Considerations for Starting the DB2 ECCR.

0 COMMENTS

We’d like to hear from you!