Last updated on MAY 05, 2017
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
In release 22.214.171.124, the migration utility was improved to support bulk insert operations in the data load process to enhance performance (Reference "Bug 13036577 - migrate.bat utility has poor performance when migrating large databases")
As part of resolution to the bug, a JVM option was suppose to be included in the migrate.bat|.sh file -- -Dusebatchinserts=true -- to utilize the batch insert process, however this setting is missing from the files. As a result, the migration data load process is not utilizing the bulk inserting which will exhibit continued performance degradation when run against larger databases.
- Using Migrate.bat without adding the -Dusebatchinserts=true:
[USER] Complete Table Load ACTIVITYSPREAD loading 21173 rows in 46.021 seconds
[USER] Complete Table Load CALENDARX loading 199882 rows in 244.778 seconds
- Using Migrate.bat with adding the -Dusebatchinserts=true against the same database:
[USER] Complete Table Load ACTIVITYSPREAD loading 21173 rows in 5.047 seconds
[USER] Complete Table Load CALENDARX loading 199882 rows in 70.141 seconds
STEPS TO REPRODUCE:
- Browse to the P6_152_Media\p6suite\database
- Open the migrate.bat|.sh in a text editor
- On the "SET JVM_PROPERTIES" line, notice the -Dusebatchinserts=true is missing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms