Question
Accenture
IN
Last activity: 6 Apr 2018 19:26 EDT
Execution of scripts with no DBA access
We have a last minute update from client that DBA user will not be provided as well as Client DBA also will not be given access to both Rules and Data schema. In this scenario, what can be a possible workaround?
In case we generate DDL scripts, do we require DBA user which require access to both Rules and Data schema or only a schema user can execute those?
Are there any other risks involved?
Please suggest as we are working on the upgrade already.
Pegasystems Inc.
IN
You definitely need certain privileges for analyzing the schema and generating the DDL. otherwise you wont be able to generate the DDL.
Please refer to deployment user privileges section in the following upgrade guide.
https://docs-previous.pega.com/pega-722-platform-upgrade-guide
ING, Netherlands
NL
As we understand, data schema user need to have read or read-write access on certain rule schema tables/objects.
Here the Client scenario is - they cannot provide any user who can access both Rules and Data which means a particular schema user has no access to any other schema as per the organization's policy.
In that case whether cross schema granting will have issues and pega split schema approach is not likely to function as expected. Is there any Pega suggested method to address similar Client scenario.
ING, Netherlands
NL
Hi Dev,
If you could update us on the query we had, whether split schema configuration is feasible in a scenario where as per organization's policy one schema cannot have any access on the other schema, not even read only.
Regards,
Arpita
Pegasystems Inc.
IN
In the split schema mode the data schema user definitely requires basic read write access to rules schema. You can refer to General User Permissions and Purposes in the upgrade guide.
https://docs-previous.pega.com/pega-722-platform-upgrade-guide
Accenture
IN
Hello Dhevendra, as is mentioned in the platform guide - the user will need access to Create/Update/Drop tables, hence does that mean we require DDL+DML access across schema here? Only DML access across schema will not be sufficient. Please confirm.
Pegasystems Inc.
IN
Deployment user requires the DDL+DML access however the baseuser which is generally data schema user requires the DDL operations along with execution of stored procedures and functions. Refer to BaseUser privileges section.
Bank of America
IN
Hi Dhevendra,
After running the scanner utility we found few issues.
Below mentioned access groups are missing. Will it impact anything in upgrade? If there is impact what is the suggested steps we have to take care before starting upgrade.
| prpc:eventprocessing |
| pegadm:administrators |
| pegabc:administrators |
| prpc:processarchitects |
| prpc:portalusers |
Also there are custom views,procedures,synonyms available in the V6.1 DB. So I hope those needs to be deleted before running the upgrade scripts and need to recreate once upgrade is done. Please confirm.
Your quick help is really helpful. Thanks.
Pegasystems Inc.
IN
This access group will not have any impact on the upgrade.
You have to drop the synonyms before starting the upgrade otherwise upgrade will fail.
If you have views and procedures defined on data schema then you no need to drop it . But if the views and procedures defined on rules tables then you need to manually apply it.