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

ORA-12899 value too large for column

SA-31565

Summary



Errors are generated in logs when adding data to the database.

The database column has a length of 64 and user is trying to add 64 characters.

Character set used in  database:
NLS_CHARACTERSET               AL32UTF8
NLS_LENGTH_SEMANTICS           BYTE



Error Messages



ORA-12899: value too large for column "PEGADATA"."PR_ASSIGN"."PYLABEL" (actual: 65, maximum: 64)


Steps to Reproduce



Unknown


Root Cause



A defect or configuration issue in the operating environment.  

The Oracle database was configured using a multi-byte character set and measured the length of the VARCHAR2 columns in bytes instead of characters. 

This worked when all the characters inserted are a single byte. 

Issue was encountered because one or more of the characters inserted were two or more bytes long and could not fit in the column.



Resolution



Make the following change to the operating environment:

In the Oracle database, change NLS_LENGTH_SEMANTICS from BYTES to CHAR.

With this change, the Oracle database calculates the column lengths in characters instead of bytes for any newly created tables and columns.

Any existing VARCHAR2 columns will continue to use the semantics from when they were created.

To modify the semantics for any existing column, alter the individual columns to use CHAR semantics.

For example,

alter column pyLabel varchar2(64 char)
Suggest Edit

Published February 16, 2019 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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