Question
Cognizant Technology Solution
IN
Last activity: 7 Aug 2023 10:33 EDT
Pega Upgrade Issue - Migrate Job Stuck
We are upgrading a Pega 8.5.6 Environment (Tomcat + Oracle). Running the 1st Job Migrate.bat. The job is stuck in the below area for over 8 hours.
[java] Fri May 13 09:04:09 UTC 2022 (INFO): Table PR4_RULE is still being moved... [java] Fri May 13 09:04:09 UTC 2022 (INFO): Table PR_ENGINECLASSES is still being moved... [java] Fri May 13 09:06:09 UTC 2022 (INFO): Table PR4_RULE is still being moved... [java] Fri May 13 09:06:09 UTC 2022 (INFO): Table PR_INDEX_REFERENCE is still being moved... [java] Fri May 13 09:06:09 UTC 2022 (INFO): Table PR4_RULE_VW is still being moved... [java] Fri May 13 09:06:09 UTC 2022 (INFO): Table PR_ENGINECLASSES is still being moved... [java] Fri May 13 09:08:09 UTC 2022 (INFO): Table PR4_RULE is still being moved... [java] Fri May 13 09:08:09 UTC 2022 (INFO): Table PR_ENGINECLASSES is still being moved...
==================================================================
All the tables mentioned here are already migrated in the new Rule schema.
But the next tables are not getting updated. Job is not failed.
But only the same verbiage is appearing in log that, these tables still bring moved.
PFA the Migrate Log.
Any idea on this?
***Edited by Moderator: Pooja Gadige to change category from Product to Update, add sub-capability tag***
***Edited by Moderator Marije to add Support Case Details; update capability tags***
Pegasystems Inc.
GB
@ANKITMITRA could you please clarify from which version you are updating to 8.5.6?
Are you following this documentation and additional steps?
What are the steps to reproduce the issue? Is it as per below?
1.Take RP for DB
2. shutdown the application servers.
3 take backup of xml files
4. update MigrateSystem.properties file as per Document upgrade
4. Run the Migrate.sh
We have seen errors like that in the past during an out-of-place upgrade if the plan.xml file is not updated with schema names.
Reference: Pega Platform 8.5 Upgrade Guide for Apache Tomcat and Oracle
IN the past suggestions have been to:
1. Perform the restore of the database or the schemas using restore point. 2. Create new rules schema or drop all objects from the new rules schema pegarules (Idea is to Cleanup the schema). 3. Run the migration process - Under target properties, You need to keep the new rules schema name only and target dataschema should be blank 4. Run the upgrade.sh by keeping the new rules schema in both rules schema and data schema
@ANKITMITRA could you please clarify from which version you are updating to 8.5.6?
Are you following this documentation and additional steps?
What are the steps to reproduce the issue? Is it as per below?
1.Take RP for DB
2. shutdown the application servers.
3 take backup of xml files
4. update MigrateSystem.properties file as per Document upgrade
4. Run the Migrate.sh
We have seen errors like that in the past during an out-of-place upgrade if the plan.xml file is not updated with schema names.
Reference: Pega Platform 8.5 Upgrade Guide for Apache Tomcat and Oracle
IN the past suggestions have been to:
1. Perform the restore of the database or the schemas using restore point. 2. Create new rules schema or drop all objects from the new rules schema pegarules (Idea is to Cleanup the schema). 3. Run the migration process - Under target properties, You need to keep the new rules schema name only and target dataschema should be blank 4. Run the upgrade.sh by keeping the new rules schema in both rules schema and data schema
(take a backup of DB or create another restore point once the Rules Schema upgrade is done).
Check the changes made to properties files as per upgrade script and populate the plan.xml with correct schema names
If there are no further suggestions provided on the forum and you run into issues, please log a support ticket for this and let us know the INCident number here so we can help track it.
Cognizant Technology Solution
IN
We are upgrading from 8.5.6 to 8.6.3 Server.
Facing the issue while running the migrate job (1st one)
Pegasystems Inc.
GB
Pega Platform 8.6 Upgrade Guide for Apache Tomcat and Oracle
If there are no further suggestions provided on the forum and you run into issues, please log a support ticket for this and let us know the INC incident number here so we can help track it.
Cognizant Technology Solution
IN