Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Data truncation occurs during Oracle database upgrade

Data truncation occurs during Oracle database upgrade

This article explains why data truncation occurs when migrating Optimal Trace 5.0 Oracle database.

Problem:

When migrating an Oracle database from the Optimal Trace 5.0 release, you may receive a message informing you that strings more than 1200 characters will be truncated.

Resolution:

This is due to a change in the character encoding for the 5.1 and above release. More specifically the use of Unicode characters in the database. There is no workaround for this issue.

Old KB# 14779

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:17
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.