Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Boris Kouevi (KOUEB) PEGA Principal Client Success Manager
Pegasystems Inc.
US
KOUEB Member since 2007 2 posts
PEGA
Posted: Mar 13, 2017
Last activity: Mar 14, 2017
Posted: 13 Mar 2017 13:17 EDT
Last activity: 14 Mar 2017 12:54 EDT
Closed

sppr_aggregate_usage referencing PR_HOURLY_USAGE table in PegaRules vs Pegadata

We have just installed PRPC 7.2.2. with split-schema. We are getting an exception which looks like the sproc sppr_aggregate_usage is referencing the PR_HOURLY_USAGE table in the PegaRULES schema instead of the PegaDATA schema.

Is there a HFix for this? Is the only fix a local fix to update the sproc?

***Updated by moderator: Lochan to add Categories***

To see attachments, please log in.
Data Integration Installation and Deployment

Posted: 7 years ago
Posted: 14 Mar 2017 10:23 EDT
Celeste Dufresne (CelesteDufresne_GCS) PEGA Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

Did you install 7.2.2 or upgrade from another version?  The OOB stored procedure does not reference the rules schema.  If you look at the stored procedure body everything should be schema qualified with the data schema name.  What is the actual exception that you are seeing?

To see attachments, please log in.

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

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice