Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Make your application's Oracle database ready for internationalization

Updated on September 13, 2021

Preparing to localize your application might require additional configuration of your Oracle database to avoid problems with database size limits. The Pega 7 Platform checks string length in characters; however Oracle, by default, checks string length in bytes. Several languages do not have a 1:1 relationship between bytes and characters, for example:

  • Cyrillic uses additional bytes to identify characters.
  • Chinese and other languages use multibyte character sets.

This means that a text field that is acceptable in English and can be successfully saved to the BLOB might exceed the size limits for the relational database column.

Oracle supports two types of character semantics, BYTE (the default) and CHAR. To support Unicode and other international character sets, set the semantics to CHAR:

Related articles

Issue: “Error: Commit failed” when loading CPM 6.1 RuleSets into a UTF-8 encoded databaseIssue: “Error: Commit failed” when loading CPM 6.1 RuleSets into a UTF-8 encoded database


Pega Platform 7.1.1 - 8.3.1 System Architect Lead System Architect System/Cloud Ops Administrator Data Integration

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us