Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

CPM Installation issue with Pega 7.1.8

SA-16001

Summary



A Customer Process Management (CPM) 7.13 has been installed on Pega 7.1.8 with DUAL-USERS and SPLIT SCHEMA options.

The CPM application appears to work and the UI displays as expected. However, in the log file there are many errors generated related to PR_INDEX_CIRCUMSTANCE_DEF table.


Error Messages



2015-09-17 18:02:00,202 [-threads-1730414987)] [ STANDARD] [ ] [ PegaRULES:07.10] ( internal.access.DatabaseImpl) ERROR [email protected] - Encountered problem when performing a Commit
com.pega.pegarules.pub.database.DatabaseException: Invalid column name 'CATabbedNavigation'.
From: (B49D8F4946FEBB04CA619C893E3BF0D3F)
SQL: INSERT INTO Rules.pr_index_circumstance_def (pzInsKey , pxCommitDateTime , CATabbedNavigation , CPMInInteraction , CPMInteractionType , CPMIsLinkForBU , CPMIsOwnerAccountLinks , CPMNewCustCaseOption , FromKPI , InteractionGoal , InteractionType , PartyType , SurveyDeliveryType , isChildInteraction , portalType , pxCreateDateTime , pxCreateOpName , pxCreateOperator , pxCreateSystemID , pxCurrentRuleBundle , pxIndexCount , pxIndexPurpose , pxIndexedClass , pxInsIndexedClass , pxInsIndexedKey , pxInsName , pxObjClass , pxSaveDateTime , pxUpdateDateTime , pxUpdateOpName , pxUpdateOperator , pxUpdateSystemID , pyCallType , pyChannel , pyCity , pyCompany , pyCountry , pyDefinitionName , pyDept , pyLabel , pyLevel , pyOrg , pyPostalCode , pyProductType , pyRegion , pyState , pyTemplateName) VALUES (? , CURRENT_TIMESTAMP , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)


Steps to Reproduce



Install CPM 7.13 on Pega 7.1.8 with DUAL-USERS and SPLIT SCHEMA options.


Root Cause



This is a database user privilege configuration issue. In a DUAL-USERS configuration option, the ALTER ANY TABLE is listed as required for the ADMIN USER.

Resolution



Grant ALTER ANY TABLE priviledge for the ADMIN USER.

 

Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us