How to Improve Performance of P6 Database Migrations with the Migrate.bat/sh Utility
(Doc ID 2068053.1)
Last updated on JANUARY 21, 2025
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 8.3.8.0 and laterInformation in this document applies to any platform.
Goal
The migrate.bat /.sh utility is a Java-based data pump utility, which can be used pump data from one database (source) to another (target). However, in all releases prior to r15.2.0.0, the process completes a regular insert operation into the target database which can result in performance degradation during the data loading process. This document will provide suggestions to improve the performance of the migration utility when run against larger databases.
For additional information about using the schema migration utility see How to Use Migrate.bat (Data Pump) to Move Data from a Source Database Instance to a Newly Created Target Database Instance (Doc ID 911740.1).
**Starting with r15.2.0.0, bulk inserting has been built into the migration utility to prevent row-by-row inserts being completed, as a solution for the defect in Bug 13036577 - MIGRATE.BAT UTILITY HAS POOR PERFORMANCE WHEN MIGRATING LARGE DATABASES. Therefore, the migration utility should exhibit dramatic performance improvement in P6 versions 15.2 and later, even without doing Steps 4, 5, and 6 below.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |