Troubleshooting import of language packs

When you attempt to import data language packs, errors might occur. For example, the language pack might not import correctly, or the column size might be insufficient. You can view warnings and errors in the TranslationData.log and LabelManager.log files.

Import process is longer than expected

The import process for data normally takes less than 2 minutes. The import process for labels normally takes less than 7 minutes. However, the import process can take longer if the amount of data to be imported is large, if the system contains a large amount of data, or if you are using a customized environment. The increased length of import for data occurs because all path fields of all records in the target environment must be recalculated.

Insufficient column size error

In the Data Modeler, use the following steps:

  1. Fix the metadata of the field by increasing its size.
  2. Publish the business object.
  3. Reimport the language pack or the problematic XLIFF file in the language pack.

The following table shows the error codes for each database that signify an insufficient column size.

Table 1. Error codes for insufficient column size
Database Error
Oracle ORA-12899: value too large for column
Microsoft SQL Server Data truncation
IBM DB2 DB2® SQL Error: SQLCODE=-302, SQLSTATE=22001

Language packs are not imported

Verify that the record ID or name of the translation data matches the record ID or name of the target environment.

This problem can occur if you delete or add as-delivered records in the target environment, and the row numbers of the smart section records are not the same as the row numbers in the language pack.

This problem can also occur if multiple languages are found for the language code that is specified in the target language of the import file. Check the logs, including the rolled over logs, for the error 
There are multiple TRIRIGA languages available for the language: zh
If the error is in the logs, specify the correct language code by including the country code if needed in the language files and reimport. In the example error above, you need to add the country code that corresponds to your target language such as zh_CN or zh_TW.
This problem can also occur if the value in the target language in the import file is not in the Language Code table. Check the logs, including the rolled over logs, for the error 
There is no available TRIRIGA language equivalent for the language: th

If the error is in the logs, add the target language to the Language Code table and reimport the files. For information on adding the target language, see Creating language codes.