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

Report definition generates dynamic column alias



When running a report, DB2 Generated SQL has a dynamic column alias which causes performance hit. Environment remains responsive, but database responsiveness is excessively slow to respond to Pega engine.

Error Messages

Not applicable

Steps to Reproduce

Create a report definition against DB2 table with one of the column name 'large', for example 'CURRENT_STEP_SECONDARY_HOLDER_NM'
and run the report and check the generated sql in the tracer

Root Cause

A defect or configuration issue in the operating environment:

Pega generates a dynamic column alias for any column name that exceeds 30 characters. The 30 character limit represents the smallest maximum column name length of any of the databases we support (in this case Oracle).


An enhancement request, FDBK-17044, has been created for consideration by Pega Product Management. 



Published October 27, 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