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

Data Table wizard fails - IMPLICIT SCHEMA privilege required



User is trying to create a data table / data class via the wizard and even after selecting "Create Dedicated Table" the class gets mapped to "pr_other" and errors are logged but wizard screen shows success.

Error Messages

2014-12-17 11:18:39,024 [HREAD1, eon_id=40774] [TABTHREAD1] [ ] [       MIGR:01.01.01] (ForClass.Rule_Obj_Class.Action) ERROR <IP Address> <user> - Unable to execute DDL statement(s) for work table 'pr_History_Data_V' (History-ABC-EFG): Database-General          Problem executing SQL to update database schema -552       42502    DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=<ATZ ID>;IMPLICIT CREATE SCHEMA, DRIVER=3.62.56

  from: (unknown) 


 Caused by SQL Problems.

Problem #1, SQLState 42502, Error code -552: DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=<ATZ ID>;IMPLICIT CREATE SCHEMA, DRIVER=3.62.56

Steps to Reproduce

Use Data table wizard with DB2 as PRPC backend database and the DB user should not have IMPLICIT_PRIVILEGE

1. Pega Button --> Data Model
2. Add new Data Table
3. Enter "Test", "Test" "Data-" , select dedicated table. Use ID as the identifier and click submit.
4. Success on the screen.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.
The problem is with the fact that the index WORKHISTORY_TE_677f is not schema qualified and hence the statement requires implicit_schema priv. 


This issue is scheduled to be resolved in Maintenance Level (ML) release 8

Published January 31, 2016 - Updated October 8, 2020

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?

Want to help us improve this content?

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