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

Not able to log in with FCM user in Pega 7.1.8

SA-16368

Summary



PRPC Users belonging to Federated Case Management (FCM) Access Groups are unable to log into Pega 7.1.8.

Environment Details:
 
  • Single PRPC instance, Multiple Applications, Split Schema.
  • Websphere 8.0.
  • Oracle 11.2
  • Oracle JDBC driver 11.1.0.7.0-Production
  • IBM java 1.6.0

Error Messages



2015-09-23 11:27:28,908 [ WebContainer : 5] [ STANDARD] [ PegaRULES:07.10] ( internal.access.DatabaseImpl) ERROR xxxx|xxxx - Encountered problem when performing a Commit
com.pega.pegarules.pub.database.ConnectionException: Database-General Problem clearing out old indexes for instance DATA-ADMIN-OPERATOR-ID-FEDERATED xxxxxxxx!PEGA, purpose RuleReference 0 enlist: caught Exception
From: (H7110DC60807A6329590FE49AA733428F:xxxx)
SQL: delete from PEGA_RULES.pr_index_reference where pxInsIndexedKey = ? and pxIndexPurpose = ?

Caused by SQL Problems.
Problem #1, SQLState null, Error code 0: java.sql.SQLException: enlist: caught Exception
...
Caused by:
com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal attempt to enlist multiple 1PC XAResources


Steps to Reproduce



Login with a user which belongs to a ‘FCM’ access group.

Root Cause



A defect or configuration issue in the operating environment.
Due to specific Reporting Requirements: this system differs from a standard FCM configuration in the following ways:

 
  • The FCM tables (for instance: “PR_DATA_ADMIN_FED”) were created within the DATA schema instead of a dedicated FCM scheme.
  • Two JDBC separate datasources (“PegaData” and “FCMR”) were created; but both were pointed to the same (“PegaData”) database schema.


Resolution



Perform the following local-change: 

For each FCM table:

Change the ‘Database Table’ rule so that the ‘Database’ field matches the ‘PegaData’ schema instead of the ‘FCMR’ schema.


​Example Screenshot:
 

 

Published January 31, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

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