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

Process Existing Jobs

Process Existing Jobs

Perform the following tasks to process existing jobs:
Upgrade Task
Details
Ensure no unmerged matches for relationship base objects
Ensure there are no unmerged matches for relationship base objects. Unmerged matches for relationship base objects are lost during the upgrade process.
Run load job on staging tables that contain records
In Microsoft SQL Server environments, run the load batch job on staging tables that contain records.
If you upgrade the Operational Reference Store when the staging tables contain records, the upgrade can fail because the log file size can exceed the available hard drive space.
Complete stage jobs and delete stage table contents
Before you upgrade the Operational Reference Store, complete any stage jobs that are in progress, and then delete the contents of the stage table.
If you do not delete the contents of the stage table, the Operational Reference Store upgrade takes longer than expected to complete in Microsoft SQL Server environments.

0 COMMENTS

We’d like to hear from you!