The Deployment User running the scripts has the previous RULES72 schema as the 'Default Tablespace'. And the new schema name is RULES721. Can this be a probable reason that the deployment user cannot access the newly created rules schema for migration?
Posted: 7 years ago
Posted: 15 Aug 2016 21:13 EDT
John Peterson (JohnPeterson)
Director, Cloud Engineering, Platform Deployments
Make sure your deployment user has the required privleges and roles to perform a deployment of PRPC. The Pega7 deployment guide has them itemized for reference. Also please check to make sure you are connecting to the same system that your Oracle Enterprise Manager is connected to. It is possible the user/schema you created is not on the same system you are trying to update.
Thanks for the response. yes, the deployment user indeed has all the requisite privileges and it is the same one which we used for the Installation of the 72 platform. We are connecting with the same system the Oracle Enterprise Manager is connected to.
The tablespaces list in OEM shows the three schemas- RULES72 and DATA72 (Pega72) and the newly created RULES721 (for rules migration in 721).