Discussion
JP Morgan
IN
Last activity: 6 Apr 2018 19:26 EDT
Upgrade from Pega 5.5 to 7.2 : upgrade.sh/resume.sh logs does not update after certain point
Dear Team,
We ran upgrade.sh and observed that logs stops updating after certain point, we killed the command and ran resume.sh but still the issue is same. The logs stop updating at the same point.
Last logs at which the logs stop updating (CLI-Resume-log-May-03-2016-11-25-11.log)
ad 5020 class definitions
[java] 2016-05-03 11:28:05,678 [ main] [ ] [ ] ( internal.access.DatabaseImpl) INFO - Data-Rule-ClassAncestor class is not available, skipping table population
[java] 2016-05-03 11:28:05,704 [ main] [ ] [ ] ( internal.util.MoveLog) INFO - Loading pr4_base_07.10.01.zip
[java] 2016-05-03 11:28:05,728 [ main] [ ] [ ] ( internal.util.MoveLog) INFO - Operation Status: Bootstrapping Base Instances
[java] 2016-05-03 11:28:05,737 [ main] [ ] [ ] (pboard.StorageStreamCommonImpl) INFO - Storage stream version is 6
Contents of resume.properties
#Tue May 03 11:27:27 EDT 2016
completed.steps.RemoveInvalidSettings=true
resume.user.temp.dir=/apps/gcsa1/pega7.2/tmp
resume.action=upgrade
resume.current.version=05-05-16
upgrade.from.version=05-05-16
completed.steps.GenerateUpgradeDDL=true
resume.install.temp.dir=/apps/gcsa1/pega7.2/tmp/PegaInstallTemp-02-May-2016-23.12.45
completed.steps.UDFApplication=true
completed.steps.EngineLoad=true
resume.user.temp.dir.root=/apps/gcsa1/pega7.2/tmp
resume.rulesload.lastattemptedarchive.PegaRULES\ ProcessCommander\ V07=pr4_base_07.10.01.zip
No ORA errors found in logs
Please help me in troubleshooting this issue. Thanks
Venugopal Adep
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
AIG
US
how long does it executed and stopped?
has it completed package loading? like 1/84, 2/84....etc
are you running upgrade script from same data center machine/server?
do you find any exception to orignal upgrade script execution?
JP Morgan
IN
how long does it executed and stopped? -- upgrade.sh stopped after 12 hours of inactivity. resume.sh is still running since 22 hours
has it completed package loading? like 1/84, 2/84....etc -- In which file should I check this?
are you running upgrade script from same data center machine/server? -- Yes both Linux server and DB servers are in same database
do you find any exception to orignal upgrade script execution? -- what string/pattern should I search for exception?
Venugopal Adep
Updated: 12 May 2016 7:50 EDT
Cognizant
IN
The following steps for your rules-only single schema upgrade have been completed by the upgrade.sh
- Initialization
- Configuration
- Cleanup RuleSets
- Generate Upgrade DDL
- Schema Upgrade
- Apply UDFs
- Engine Load
- Reorganize Database Indexes Preupgrade
- Upgrade Java Syntax
- Remove Invalid Settings
I believe you are always getting stuck at "Rules Upgrade" step in the upgrade process. (also starts as _upgradeRuleBase in the CLI logs)
This became obvious after verifying the contents of the resume.properties and CLI-% logs.
Every single time the upgrade script stalls while "loading pr4_base_07.10.01.zip"; found at the very end of all the CLI-% logs
I hope these observations help; we are seeking suggestions ...
AIG
US
please
- check DB driver version
- is there active thread from deployment user id to DB, if yes then since how long it is active. DBA can answer for this
- do you see pega processes id
Cognizant
IN
In every attempt we made the upgrade process was getting stuck while performing a scan for list view rules.
Please verify the below error from the PRPC-RuleInstaller-YYYY-Mmm-DD.log
A similar error was also found in the corresponding CLI-Resume-log-Mmm-DD-YYYY-HH-MM-SS.log
2016-05-05 15:31:48,812 [.abc.net] [ STANDARD] [ ] (ternal.util.RuleScannerUtility) INFO - Scanning class Rule-Obj-JSP
2016-05-05 15:31:49,209 [.abc.net] [ STANDARD] [ ] (ternal.util.RuleScannerUtility) INFO - Processed 35 instances, skipped 0
Processing Phase CPU Time Elapsed Time
Overall 0.00 0.399000
Initialization 0.00 0.000000
Database Scan 0.00 0.383000
Rule Filter 0.00 0.000000
Process 0.00 0.007000
2016-05-05 15:31:49,215 [.abc.net] [ STANDARD] [ ] (ternal.util.RuleScannerUtility) INFO - ========================================
2016-05-05 15:31:49,215 [.abc.net] [ STANDARD] [ ] (ternal.util.RuleScannerUtility) INFO - Scanning class Rule-Obj-ListView
Cognizant
IN
This issue was referred to 'Pega Systems' as there was no solution in sight.
We were recommended to skip the Upgrade java Syntax while running the upgrade.sh (rules only upgrade).
To archive this we modified the setupDatabase.xml and removed Upgrade java Syntax step from the following tag
<target name="Upgrade Finalization" depends="Initialization,..........,Cleanup"> </target>
After this change another attempt was made on upgrade.sh and this time it ran successfully.