Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega 8.3.1 out-of-place upgrade to Pega 8.4 fails



Out-of-Place upgrade of Pega 8.3.1 server to Pega 8.4 fails. Post creating a blank database to use during the upgrade, the 'migrate.bat' fails to perform the steps (listed in the Pega Deployment Guide) when executed. The upgrade completes instantly and a message of success displays.

For more information, refer to:

Error Messages

Generate Table Lists:
     [echo] Skipping generation of table list since we are not generating source xml or dumping the source database

Generate Source XML:

Create Clone DDL:

Apply Cloned DDL:

Create Migration Point:

Determine Action:

Move Database:

Generate Rules Schema Objects:

Apply Rules Schema Objects:

   [delete] Deleting directory C:\Temp\MigrateTemp


Total time: 0 seconds
Exiting with NO Error

Steps to Reproduce

Execute the migrate.bat script.

Root Cause

A software use or operation error.
The Migrate system properties  were set up incorrectly. All the Operation properties were set to false. Thus, the tasks that cloned the Rules tables in the new Rules schema were not performed.


The Deployment Guide provides details to set the properties for different steps of the Out-of-Place upgrade. Since Step 1 migrates the Rules tables from the existing Pega 8.3.1 Rules schema to the newly created and empty Pega 8.4 Rules schema, create directories and set them appropriately in a file. For this step, the first group of the 6 properties must all be true and the last two Operation properties must be set to false. 

After the Rules schema upgrade is completed, on the second pass of the Migrate script these properties have different values.

Migrate System Properties: The directory where the output from the bulk mover is stored. This directory is cleared when pega.bulkmover.unload.db is run.

This property must be set if either pega.bulkmover.unload.db or pega.bulkmover.load.db is set to true.\BulkMover

The location where a temporary directory is created for use by the migrate system utilities.\MigrateDump

The operations, to be run by the utility, will only be run if the property is set to true.
  1. Generate an XML document containing the definitions of tables in the source system. This is found in the schema directory of the Distribution image.

  2. Create a Data Definition Language (DDL) from the generated XML document. This DDL can be used to create copies of rule tables found on the source system.

  3. Apply the generated clone DDL to the target system.

  4. Unload the rows from the rules tables on the source system in to the

  5. Load the rows on to the target system from the

  6. Move all the tables present in the Rules schema specifically non-pega tables created by the user or the infrastructure directly on to the schema.
The following operations should only be run when migrating upgraded rules:
  1. Generate the Rules schema objects (such as, Views, Triggers, Procedures, Functions). The objects are created in the, but will contain references to the where appropriate.

  2. Apply the Rules schema objects (Views, Triggers, Procedures, Functions) to
Suggest Edit

Published June 19, 2020 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us