Reply posted on September 23, 2019 by DmitryP1
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Gouri Shankar for achieving the title of Participant of the Week! Gouri Shankar believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
Problem solved. The problem was: BIX is using the user name name configured on the DB data source as schema name. Thus i had to update the data source configuration (JBoss) to connect using the data schema (OWNPEGDATA). Regards, Herve
We took the risky approach and went ahead and upgraded directly to the 8.2 version. We verified that the schema changes introduced in each of the version were in the 8.2 upgrade package as well. There was no need to make a sequential upgrade since 7.31...
The Hotfix referenced here HFix-47303, and the additional fixes for the specified SR, are actually for the 7.4 release. It appears to address a form of the component stack mismatch error relating to switching access groups.
That is normal to ensure backward compatibility, i.e., existing rules are still working. You will notice that even fresh installation of Pega 8.2 (even 8.3), you can still see the warning for some service packages.
Please wait while we search for PDN content that suits your question.