Oracle DB users permissions for DSM and Marketing schemas
We have the following Oracle schemas in our environment:
- Pega DATA schema
- Pega RULES schema
- Interaction History schema
- Pega Marketing schema mapped to ExternalMKTData database
- Predictive Analytics Director schema
- Adaptive Decision Manager schema
- Visual Business Director schema
We are quite clear regarding Pega DATA and Pega RULES schemas/users, but we cannot find any details in the documentation regarding Decisioning/Marketing schemas. What would be the minimum set of permissions required for Oracle users for Pega Decisioning/Marketing schemas.
***Updated by moderator: Lochan to add SR Created group tag; add documentation BUG ID***
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved by providing explanation and creating a documentation feedback.
Thank you,
Pegasystems Inc.
IN
Hi Przemyslaw,
1. With the PAD, ADM, VBD and IH in dedicated schemas, I do not think that they require any privileges on PegaRULES and PegaDATA schema considering the data read and write on each schema will happen using the corresponding DataSource created on the server.
2. For installation purposes, a deployment user is required which needs privileges to create objects in all of the schemas.
3. The marketing user will require privileges to create views and to select from tables in the PegaDATA schema.
Uniqa
AT
Hello Akash,
Thank you for your response.
Would you be able to provide a list of grants for each Oracle schema/user? E.g. according to Pega 7.1.9 Platform Installation Guide for Pega DATA Admin user it is: CREATE SESSION, CREATE ANY TABLE, ALTER ANY TABLE, INSERT ANY TABLE WITH ADMIN OPTION, SELECT ANY TABLE, UPDATE ANY TABLE, DELETE ANY TABLE, CREATE ANY INDEX, etc.
I am looking for a similar list for each Pega DSM/Marketing user/schema.
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved by providing explanation and creating a documentation feedback.
Thank you,