Salesforce

Error 2736 and 11114 running PROUTIL conv910 or conv1011 to convert a UTF-8 database

« Go Back

Information

 
TitleError 2736 and 11114 running PROUTIL conv910 or conv1011 to convert a UTF-8 database
URL NameP150782
Article Number000145780
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: conv910, conv1011
Question/Problem Description
Database migration with PROUTIL conv utilities fails with errors 2736 or 2739 and 11114.
Error 11114 running PROUTIL conv910 or conv1011 to convert a UTF-8 database.
PROUTIL conv910 fails to convert a UTF-8 database from Progress 9 to OpenEdge 10.
PROUTIL conv1011 fails to convert a UTF-8 database from OpenEdge 10 to OpenEdge 11.
 
Steps to Reproduce
Clarifying Information
Running proutil conv910
The version 10 install requires the proword.n file needed by the conversion process
Converting  UTF-8 database
Error MessageUnable to open word-break table file <table-num>. (2736)
CRC error in word-break rules table <table-num>. (2739)
Conversion failed in drcon, ret = -1. (11114)
Defect Number
Enhancement Number
Cause
Missing the word-break file in the new version environment (OpenEdge 10, OpenEdge 11) created in the previous version environment (Progress 9, OpenEdge 10) that uniquely identifies the set of rules that were created with the WBREAK-COMPILER qualifier.
Resolution
1. Copy the word-break file proword.<n> from the previous version environment (Progress 9, OpenEdge 10) installation directory to the new version environment (OpenEdge 10, OpenEdge 11) install directory (DLC), specified in the 2736 error message: Unable to open word-break table file <table-num>, ensuring the appropriate permissions.  
    

Alternatively or for the 2739 error message: CRC error in word-break rules table <table-num>, against the offline the previous version database, confirm the value stored in the database, refer to Article P175105, How to see what word-break table is defined for a database?   

2. Unfortunately having failed the conversion the previous version database is going to have to be restored to re-run the conversion once the expected word-break file is in place.

<
new version installation directory DLC>\proword.<n>
$   proutil dbname -C [conv910 | conv1011] -cpinternal UTF-8 
 
Workaround
Notes
Keyword Phrase
Last Modified Date9/13/2015 3:35 AM

Powered by