Hello, 

Do you mind sharing the full log.

Hi, Any update on the above?

Have you tried resuming the upgrade?

Could it be that you lost your DB connectivity? or to your ldap?

Regards

Anthony

Could you please add details on your infra:
From what kind of server you run the upgrade, jdbc used, oracle DB version.
The DB user used for upgrade is having full access to DB?
Can you please add the config file for the upgrade also?
Thanks
Anthony

for a 8.2.1 upgrade, from Websphere 8.5 but Oracle 11, I used ojdb7.jar.
Is it something you can try? I've not check detailled requirements for Ora12 and PEGA8.3.1

If you're at the first step of the upgrade, you need to put your RULES schema for both data & rules

Hi Anthony,

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.

Regards

Anthony

The first upgrade.sh will take care of upgrading the rules.
You'll have then to run upgrade.sh --DataOnly which will also handle the data schema

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

https://collaborate.pega.com/question/place-upgrade-82

dataOnly parameter is only needed when you perform out of place upgrade and then migrate rule schema separately for other environments, then to upgrade data schema you need this additional parameters.

but for now, it's your migration which fails :)
So it's worth a run with parameters as I mentioned or let's wait for someone else to give advice for your issue.
Regards
Anthony

We tried upgrading on another database and there it worked so now we are checking with our DB team if anything is wrong with the previous database.