Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. LDAP User Authentication
  16. Auditing
  17. Running Jobs from External Applications
  18. Upgrading Oracle History Data
  19. Upgrading PeopleSoft History Data
  20. Data Archive Maintenance
  21. Storage Classifications
  22. Appendix A: Datetime and Numeric Formatting
  23. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Upgrading PeopleSoft History Data Prerequisites

Upgrading PeopleSoft History Data Prerequisites

Before you upgrade PeopleSoft history data, verify the Data archive version, the accelerator version, the source connection, and the history database indexes. To increase performance of the database and the upgrade scripts, gather statistics for the history database.
Complete the following tasks:
  1. Verify that you have Data Archive version 5.3 or later. You cannot use these instructions to upgrade the history data if you have an older version of Data Archive.
  2. Verify that you have the most recent version of the accelerator. If you do not have the most recent version of the accelerator, contact Informatica Global Customer Support.
  3. Verify that the PSAESTEPDEFN, PSAESTMTDEFN, and PS_UPG_DATACONV tables in the upgraded environment have records. You can use these tables for troubleshooting if you encounter problems during the PeopleSoft upgrade.
  4. Verify the source connection. Do not change the source connection to reflect the updated version of the application. For example, if you upgrade from PeopleSoft 8.9 to 9.1, the application version for the source connection is PeopleSoft Applications 8.9.
  5. Verify that all indexes exist in the history database and that the indexes are valid. If indexes do not exist or are not valid, run the Create Indexes job.
  6. Gather database statistics for the history database. Gathering database statistics optimizes the database and increases performance of the upgrade scripts.

0 COMMENTS

We’d like to hear from you!