Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding database grants

Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

The user associated with the ExternalMKTData schema must have grants to certain tables in the PegaDATA schema. From your database client, run the following statements:

Pega Customer Decision Hub Installation Guide

ExternalMKTData privileges

GRANT SELECT ON ${dataschema}.PR_DATA_PUSH_MESSAGE TO ${mktdatauser};GRANT SELECT ON ${dataschema}.PR_DATA_PUSH_REGISTRATION TO ${mktdatauser};
Note:

On IBM Db2 environments, use the following syntax instead:

GRANT SELECT ON ${dataschema}.PR_DATA_PUSH_MESSAGE TO USER ${mktdatauser};GRANT SELECT ON ${dataschema}.PR_DATA_PUSH_REGISTRATION TO USER ${mktdatauser};

Replace ${dataschema} with the name of the schema referenced by the PegaDATA database rule, and ${mktdatauser} with the name of the user associated with the ExternalMKTData database rule.

Interaction History Data privileges

If the Interaction History tables are installed in a schema associated with a DB rule other than PegaDATA, for example PegaIHData, you must grant SELECT privileges on all Interaction History tables to the users and schemas associated with both the PegaDATA and ExternalMKTData DB rules. 

GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_APPLICATION to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CHANNEL to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CONTEXT to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CUSTOMER to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_JOURNEY to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_LOCATION to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OPERATOR to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OUTCOME to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_FACT to ${pegadatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_APPLICATION to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CHANNEL to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CONTEXT to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CUSTOMER to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_JOURNEY to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_LOCATION to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OPERATOR to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OUTCOME to ${mktdatauser};GRANT SELECT on ${ihdataschema}.PR_DATA_IH_FACT to ${mktdatauser};
Note:

On IBM Db2 environments, use the following syntax instead:

GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CHANNEL to USER ${pegadatauser}; 
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CONTEXT to USER ${pegadatauser}; 
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CUSTOMER to USER ${pegadatauser};
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_JOURNEY to USER ${pegadatauser}; 
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_LOCATION to USER ${pegadatauser};
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OPERATOR to USER ${pegadatauser};
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OUTCOME to USER ${pegadatauser}; 
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_FACT to USER ${pegadatauser};

GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CHANNEL to USER ${mktdatauser};  
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CONTEXT to USER ${mktdatauser};   
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_CUSTOMER to USER ${mktdatauser};  
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_JOURNEY to USER ${mktdatauser};   
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_LOCATION to USER ${mktdatauser};  
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OPERATOR to USER ${mktdatauser};  
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_DIM_OUTCOME to USER ${mktdatauser};   
GRANT SELECT on ${ihdataschema}.PR_DATA_IH_FACT to USER ${mktdatauser};

Replace ${ihdataschema} with the name of your IH schema, ${pegadatauser} with the name of your PegaDATA user, and ${mktdatauser} with the name of your External Marketing user.

Tags

Pega Customer Decision Hub 8.5 Decision Management

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us