Upgrade script stuck upgrading from 8.6 to 23

General
, , , , ,
1

Hi All,

I’ve just kicked off an upgrade of a cloned DEV environment from 8.6 to 23 but its been running now for almost an hour and seems to be stuck at the below point and not moved.

generate_upgrade_ddl:

Check zOS Upgrade:
[echo] setting resume checkpoint
[propertyfile] Updating property file: /common/PegaUpgrade/pega23/117667_Pega_23.1.1/scripts/resume.properties

Schema Upgrade:

Schema Upgrade Inner:

RunSQLLoader:

Should I be concerned its not doing anything or do I simply need to wait some more?

I should point out that this Pega Platform ’23 Installation and Updates stall on Oracle with old JDBC driver [SDR-A161] | Support Center doesn’t apply as I’m using ojdbc11.jar on Oracle 19c.

Thanks
Craig

2

OK little updated, I cancelled the original run as I waited 2 hours and nothing happened.

I switched to ojdbc8.jar and then ran again removing the resume file.

I then monitored sql sessions on the database as it ran and could see it getting the metadata for the database, but then nothing as it got to the same point.

Think there is a problem with this version. Will need to raise an SR for this as I’m on a timeline and getting no where fast.

Cheers
Craig

3

@CraigA52 can you give us the INC id of the ticket you logged?

4

@CraigA52 I can see that you logged INC-B13037 (Upgrade from 8.6 to 23 command line gets stuck at RunSQLLoader)
·

Info from the ticket:

Original issue was because of length of classpath. You suggested that upgrade scripts have an issue with path length. - you moved the upgrade directory to a lower mount point

The originally reported issue was resolved by changing the directory path where the upgrade was run to different location.
In general, we have seen issues where NFS shares cause this. We recommend to run upgrades from not mounted NFS directory

On April 3rd you confirmed that upgrade finally completed.

I believe that this issue is therefore resolved. Any new issues can be logged directly via the MSP.