How to Improve Performance of P6 Database Migrations Using Migrate.bat/sh
(Doc ID 2068053.1)
Last updated on MAY 04, 2021
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 188.8.131.52 and later
Information in this document applies to any platform.
The migrate utility is java based data pump utility, which can be used pump data from one database(source) to another(target). However, in all releases prior to r184.108.40.206, 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.
**Starting with r220.127.116.11, bulk inserting has been built into the migration utility to prevent row-by-row inserts being completed as resolution to the following defect - Bug 13036577 - MIGRATE.BAT UTILITY HAS POOR PERFORMANCE WHEN MIGRATING LARGE DATABASES.
Therefore, utilizing the migration utility starting with r15.2 should exhibit dramatic performance improvement without a need to complete steps 1, 4 and 5 defined in the solution section below. In addition, the bulk commit threshold can be increased from the default of 1000 when running the migration utility directly within the UI on the "Migration Options" page, "Row Batch Size To Commit" field, which can further improve the speed of the migration process. However, due to another defect, the migration utility is missing a JVM Parameter to use the bulk insert operation, causing it to still complete row-by-row inserts. Further context, as well as a workaround can be found by reviewing the following knowledge base document: Migrate Utility Missing The -Dusebatchinserts=true JVM Parameter Preventing Bulk Inserting From Running During The Target Database Data Load (Doc ID 2069596.1)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document