Support Article
Error occurs when importing a JAR file
SA-70253
Summary
Unable to import a JAR file.
Error Messages
Import of Database Configuration Archive failed.
Number of successfully imported Data-Admin-DB-Name instances: 0
String or binary data would be truncated.
DatabaseException caused by prior exception: java.sql.BatchUpdateException: String or binary data would be truncated.
| SQL Code: 8152 | SQL State: 22001
Steps to Reproduce
Import a JAR file to Pega 7.4.
Root Cause
The file name of the exported JAR file name is long. Therefore, the pyLabel column (JAR file name entry) value of pr_data_admin_restore table is truncated and the SQL server performed a rollback of the merge action.
Resolution
Perform the following local-change:
- Modify the file name of the imported JAR such that it is of shorter length (less than 128 characters).
- Use non-localized (Alphabet and numeric) characters.
Published January 12, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.