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

Extracts are failing in production error message - ORA-12899



Business Intelligence Exchange (BIX) extracts are failing in production, when the data from BLOB (value of property for one of the instance of case) is more than the data defined in the database column.

Error Messages

Batch Update Exception: ORA-12899: value too large for column "dbname"."schemaname"."propertyname" (actual: 136, maximum: 128)

Steps to Reproduce

Following is the details of the BIX Schema

1. Create an extract rule.
2. Include the table and column mapping in the extract rule.
3. Execute the extract rule.

Root Cause

User has modified the DDL script which generates for the first time when doing extraction to database to create table.

The default DDL will create columns to take length in terms of char.

User modified the DDL which will create columns to take length in terms of Byte.

There is a mismatch between the number of characters that user is trying to truncate and the actual bytelength of the column that is, column length is exceeding the byte length and truncation is failing with ORA-12899.


Use default DDL generated to create the table and column length must be in terms of characters.

Published August 17, 2017 - 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?

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