Unable to login after in place Upgrade to 8.2.1
We performed in place upgrade for our SIT environment from 7.3.1 to 8.2.1. We have followed the upgrade guide (https://community.pega.com/knowledgebase/documents/pega-platform-82-upgrade-guide-ibm-websphere-and-oracle) and after the upgrade none of our existing operators (including pega admin id) are able to login. Login screen shows fails status as shown in the attachment.
I am also attaching our config file along with setupdatabase.properties file which i used before running upgrade script.
PEG
GB
Can you please send the portion of the PegaRULES log when you attempt to log in with one of the OOTB users? (if available)
Also, please make a note of the time that you tried this so that it will indicate which portion of the logs to look at.
Swedbank AB
SE
Hi,
Thanks for your quick response. I have attached the portion of the log here which was generated during login.
PEG
GB
I don't believe I've seen this error before: -
Could not get CDK from systemKeyManagementCache
I'd suggest you check if there are customization in your ear/war file from the 7.3.1 environment, and see whether they've been moved across to the 8.2.1 ear/war
If this still isn't bringing anything to light, I'd suggest you raise an SR with the support team, so they can do some more in-depth investigation.
Swedbank AB
SE
We have not modified the EAR file. However I have raised SR-D5174 for further investigation.
Pegasystems Inc.
US
I see this in the log:
lx67249.sbcore.net|lt21410.fspa.myntet.se - Error in determining tenant visibility for the class Data-Decision-StreamService-Node
com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable CFO20_APP_DATA.pr_data_stream_nodes PegaDATA
Does the table exist? I would like to see your startup log to see if everything comes up fine.
Swedbank AB
SE
Hi,
Yes, I could see this table but the table is empty. Also it seems this table was introduced after upgrade as I don't see this table for other environments which are running on Pega version 7.x. Attaching the pega log during start up.
Accepted Solution
Swedbank AB
SE
Hi,
This issue is resolved now. The problem was at websphere level where the user id which was used to connect with data source did not have all the privileges and that's why it was unable to access these new tables introduced as part of Pega 8.2.1. Replacing the same with Admin user id has sorted out the issue.