yes, i have tried resuming the upgrade multiple times and it's giving the same error everytime at same stage. DB connection is successful everytime so I don't think there is any issue with DB connection.
Thanks for your reply. I have already tried previous upgrade on Pega 8.3 on oracel 12c and Ojdbc8 and it worked fine for me and the same is advised in pega platform support guide as well so I don't think they are incompatible.
Regarding your suggestion on changing the data schema name, i guess that sounds true for either Out-of-place upgrade or single schema environment but since we are performing in-place upgrade on split schema, i think we need to provide the schema name separately and the same is suggested as per platform upgrade guide.
Regarding resuming the upgrade process, yes i have tried that as well but unfortunately it didn't work for me. We have already upgraded pega successfully previously so it is interesting to see why it's failing this time. My first guess is to look at the DB level as the log provides some indication in the same area but not sure where should I look it. If you have any specific question for DB, you can let me know and I can convey the same to our DB team.
Lastly, thanks for the advising on changing the DB password so I have removed the configuration file, however I was less worried as it was a POC environment and can only be accessed within our organization's network..:-)
in-place or out-place, global process is the same.
for in-place, you just don't need to prepare a new rule schema.
then, for step 1 of upgrade, via command line, the property file should have rule schema name for both data & rule variable. If you let empty the data schema viariable, then rule schema name is considered.
I checked 8.2.1 upgrade guide and it's well mentioned p 42 :)
If you use the UI, then indeed, data schema viariable should have data schema name.
I was just wondering if we do not specify data schema name during in-palce upgrade then how pega scripts will identify the data schema to upgrade it because my impression was that upgrade scripts take care of both Rule & data schema upgrade if we specify their name separately in configuration file?
You may want to check the below community post where we discussed the same thing and it was advised that running upgrade.sh will take care of upgrading both rule & data schema if we provide them separately so need to run the upgrade.sh again with --dataOnly parameter
This was a data issue. In our database, a corrupt/invalid instance of Data-Admin-DB-Name was found with all records as null, however the same was not visible within Pega. Since during upgrade pega validates all DB instances, this instance was causing the NullPointerException.
After deleting the record from database, upgrade started working.