Software update issue

Pega-as-a-Service
, , , , , ,
1

We are trying to upgrade the rulebase from 8.8.3 to 24.1 for on-prem setup using in-place approach. So we configured the setupDatabase properties files with all required details and ran upgrade.bat but then its stuck after below point and not proceeding further. Please review and let me know of any solution to proceed on the same?

[java] 2024-06-21 07:22:12.675 [main] INFO com.pega.codeloader.MainKt - Driver Type…: Oracle JDBC driver
[java] 2024-06-21 07:22:12.675 [main] INFO com.pega.codeloader.MainKt - Driver Version..: 19.17.0.0.0
[java] 2024-06-21 07:22:13.038 [main] INFO com.pega.codeloader.engine.EngineCodeDeleter - Clearing existing contents of pega-enginecode:08-24-01
[java] 2024-06-21 07:23:40.499 [main] INFO com.pega.codeloader.AbstractFastCodeLoader - Starting code import of 891 jars from \tmp\PegaInstallTemp-20-June-2024-08.38.41\load\lib
[java] 2024-06-21 07:23:40.554 [main] INFO com.pega.codeloader.AbstractFastCodeLoader - Loading with 8 thread(s)
[java] 2024-06-21 07:23:40.570 [ForkJoinPool-1-worker-1] INFO com.pega.codeloader.AbstractFastCodeLoader - Loading base/activation-1.1.1.jar …
.
.
.
.
.
.
.
[java] 2024-06-21 08:17:36.638 [ForkJoinPool-1-worker-7] INFO com.pega.codeloader.AbstractFastCodeLoader - Loading zstd-jni-1.5.5-10.jar …
[java] 2024-06-21 08:17:46.622 [ForkJoinPool-1-worker-6] INFO com.pega.codeloader.AbstractFastCodeLoader - Loading zt-exec-1.7.jar …
[java] 2024-06-21 08:17:50.449 [ForkJoinPool-1-worker-6] INFO com.pega.codeloader.AbstractFastCodeLoader - Loading zt-process-killer-1.8.jar …

2

Problem identified as shown below. Running with ojdbc11 jar resolved the issue. Thanks!

Please see this article. There is a bug in older versions of the Oracle JDBC driver that causes this step to hang. You want to be using at least the 20.5 or higher version of the ojdbc jar file. You should also be using either the ojdbc8 or ojdbc11 jar which matches the Java version you are using.

Pega Platform ’23 Installation and Updates stall on Oracle with old JDBC driver [SDR-A161] | Support Center?

3

@Jey2705 we also faced similar issue , we used the latest ojdbc8.jar and upgrade scripts ran successfully.

4

@AnshumanM1959 , Our platform is on WAS 9.x and we are working on in-place upgrade from 8.8.3 to 24.1 and have few questions. Can I please get your contact number as I have few questions ? Thanks !!

5

@Jey2705 Our platform is on WAS 9.x and we are working on in-place upgrade from 8.8.3 to 24.1 and have few questions. Can I please get your contact number as I have few questions ? Thanks !!

6

@HariP17292143 Please ask your queries here, I will respond to best of my ability. we have completed upgrades from 8.8.x to 24.1.x version successfully.

7

@AnshumanM1959 1) For in-place upgrade, should we put TRUE or Leave Blank for

BYPASS SCHEMA GENERATION?

Schema generation will be skipped if this property is set to true

Note: Leave this property blank to generate the schema

bypass.pega.schema=

We have existing PEGADATA and PEGARULES schemas to upgrade.

  1. Should we run generateDDL manually prior to executing update.sh or just execute update.sh after modifying setupDatabase.properties ?

  2. please advise if below values are good.

UPDATE EXISTING APPLICATIONS

Runs only during upgrades. Default setting is false.

You can also run this utility from the IUA, prpcUtils, or in Dev Studio.

update.existing.applications=false

UPDATE APPLICATIONS SCHEMA

Runs only during upgrades. Default setting is false.

Set to true to run the Update Applications Schema utility to update the cloned Rule, Data, Work,

and Work History tables with the schema changes in the latest base tables.

You can also run this utility later in prpcUtils or in Dev Studio.

update.applications.schema=false

RUN RULESET CLEANUP?

Generate and execute an SQL script to clean old rulesets and their rules from the system.

To generate the script and not execute it use the cleanup.bat/sh script.

run.ruleset.cleanup=true

8

@HariP17292143

Below details are correct :

bypass.pega.schema= ( This should be blank).

update.existing.applications=false

update.applications.schema=false

run.ruleset.cleanup=true

Just fill up the setupDatabase.properties with correct details and then run the command “nohup ./upgrade.sh &”

Ensure the permissions and ownership to be correct.

pega.jdbc.driver.jar=

pega.jdbc.driver.class=

pega.database.type=

pega.jdbc.url=

pega.jdbc.username=

pega.jdbc.password=

rules.schema.name=

data.schema.name=

user.temp.dir=

automatic.resume=true

9

@AnshumanM1959 Thank you!! Do we need to update prpcutils.properties as well for 24.1 ? I don’t see PRPCSetup.jar downloaded with Pega platform 118243_Pega24.1.3.zip ? Do we need PRPCSetup.jar file ?

I have updated setupDatabase.properties file as suggested but without updating the prpcUtils.properties file and got the error though we set up export Java.

tail -10f nohup.out
The JAVA_HOME environment variable must be defined.
The JAVA_HOME environment variable must be defined.

we have setup echo $JAVA_HOME
/mw/IBM/WAS/AppServer/java/8.0

or should I use system Java ? /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.452.b09-1.el7_9.x86_64/jre/bin/java ?

10

@HariP17292143

prpcUtils.properties file ( Not needed for upgrade), THis is only for deployment .

Try the below.

export JAVA_HOME=/mw/IBM/WAS/AppServer/java/8.0

export PATH=$JAVA_HOME/bin:$PATH

Note: you can see the JAVA path on Designer studio : cick on PEGA on bottom right corner and scroll down to see the details.

11

@AnshumanM1959It worked with above command. Created the logs folder and a file CLI-Upgrade-log-Aug-13-2025-15-43-55.log

Thank you !! Will keep you posted and really appreciate your help till now.

12

@AnshumanM1959

Upgrade ran for an hour and got stopped here and logs are not rolling. Does it mean upgrade successful ?

[echo] Cleaning up temp directory…
[delete] Deleting directory /app/tmp/PegaInstallTemp-13-August-2025-15.43.57
[delete] Deleting: /app/PEGA_TEMP/pega2413/118243_Pega24.1.3/scripts/resume.properties

Upgrade Finalization:
[echo] PegaRULES Process Commander database upgrade complete.

BUILD SUCCESSFUL
Total time: 64 minutes 48 seconds
2025-08-13 15:44:13,163 ( UpgradeDataModelImpl) INFO - Installed Product Versions:
2025-08-13 15:44:13,164 ( UpgradeDataModelImpl) INFO - {Instance: PEGARULES PROCESS COMMANDER!8.8.3, Upgraded from version: 08-04-06, Build name: PRPC-8.8.3-478} (current version)
2025-08-13 15:44:13,166 ( UpgradeDataModelImpl) INFO - {Instance: PEGARULES PROCESS COMMANDER!8.4.4, Upgraded from version: null, Build name: PRPC-8.4.4-833}

How do I validate if its completed prior to deploying new prweb.war if upgrade is completed or not ?

13

@HariP17292143 Yes its done and you can start the JVM and check , then stop the JVM and update the new prweb.war in all JVM’s with rolling restart.

14

@AnshumanM1959 Prior to running the update.sh we have stopped all the JVMs and uninstalled the applications so though we start the JVMs we won’t able to launch the application. Is there any other way ?I am also going thru the log files. Thanks !!

15

@HariP17292143 I looked at the PEGARULES schema in pr_engineclasses the ruleset version shows as 8.24.04 so I think upgrade went fine. Also, I reviiewed all the logs and no errors are seen. Thanks !!