BUG REPORT: Long names with non-ASCII characters may cause key-related issues on PGP Universal Server

Article:TECH202288  |  Created: 2013-01-31  |  Updated: 2013-01-31  |  Article URL http://www.symantec.com/docs/TECH202288
Article Type
Technical Solution


When using long key/user name which consist of non-ASCII characters, the key search or policy update is failing for respective key/user.


SQL command execution error: ERROR:  value too long for type character varying(255)


PGP Universal 3.x



This problem appears because PGP Universal stores non-ASCII characters in the database as textual representations of UTF-8 octets instead of UTF-8 characters. Depending on the character, a single character can be represented by up to 16 "character varying" values.

Here is an example how the 7-character Cyrillic word "Русский" (literal "Russian") is represented on the database level: "\320\240\321\203\321\201\321\201\320\272\320\270\320\271". In the example above each Cyrillic character is encoded as a 2 byte value which is stored as 8 symbols in the database.


Symantec Corporation is committed to product quality and satisfied customers. This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming version or Maintenance Pack of the product.  Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

The following is a known temporary workaround for the issue until the new version or maintenance pack is released:

Respective database table should be altered in order to extend the length of affected column.

Supplemental Materials


Non-ASCII characters in From field display can cause value too long error in database

Article URL http://www.symantec.com/docs/TECH202288

Terms of use for this information are found in Legal Notices