dbtool is giving errors: "ERROR - Failed to get char count of the field, errno -4" after upgrading to OpenEdge version 11.7 or higher

Jan 6, 2022
Knowledge

Title

URL Name

dbtool-is-giving-errors-ERROR-Failed-to-get-char-count-of-the-field-errno-4-after-upgrading-to-OpenEdge-version-11-7-or-higher

Article Number

000207686

Environment

Product: OpenEdge Version: 11.7 and higher OS: All supported platforms

Question/Problem Description

dbtool option 1:
1. SQL Width & Date Scan w/Report Option
is giving errors:
ERROR - Failed to get char count of the field, errno -4
after upgrading to OpenEdge version 11.7 or higher

Steps to Reproduce

Clarifying Information

The OpenEdge database was created in OpenEdge version 11.6 or an older version of OpenEdge.

The OpenEdge database is a UTF8 database.

The dbtool version shipped with OpenEdge version 11.6 or lower did not generate errors when executing dbtool option 1.

The dbtool utility only gave the errors: "ERROR - Failed to get char count of the field, errno -4" after upgrading to OpenEdge version 11.7 or higher.

using the OpenEdge sqlexp utility doing a:
SELECT * FROM PUB."tableName" where rowid = xxxxx ;
where xxxxx is a recid such as 229078021 as mentioned in the dbtool errors such as:
ERROR - Failed to get char count of the field, errno -4
processFieldSizes - ERROR - Failed to get char count in field 2, record 229078021/255/0.
gives an SQL error message:
=== SQL Exception 1 ===
SQLState=HY000
ErrorCode=0
[DataDirect][OpenEdge JDBC Driver]Transliteration failed, reason: invalid UTF8 data

Error Message

processFieldSizes - ERROR - Failed to get char count in field 24, record 1099565184/244/0. ERROR - Failed to get char count of the field, errno -4

Defect Number

Enhancement Number

Cause

The dbtool code generating the dbtool error:
ERROR - Failed to get char count of the field ...
was added in OpenEdge 11.7, therefore previous versions of OpenEdge do not generate those error messages.

Resolution

Using a prowin session started with:
prowin datababaseName -cpinternal UTF-8 -cpstream UTF-8
use 4GL code like this to export the corrupted data mentioned by dbtool:

OUTPUT TO corruptedRecords.d .

FOR EACH tableName NO-LOCK
WHERE RECID(tableName) = xxxxx
OR RECID(tableName) = xxxxx
OR RECID(tableName) = xxxxx
:
EXPORT tableName .
END.

OUTPUT CLOSE.

then use 4GL code like this to delete the data containing the corrupted data:

FOR EACH tableName NO-LOCK
WHERE RECID(tableName) = xxxxx
OR RECID(tableName) = xxxxx
OR RECID(tableName) = xxxxx
:
DELETE tableName .
END.

instead of xxxxx use the recids such as 229078021 mentioned in the dbtool errors such as:

ERROR - Failed to get char count of the field, errno -4
processFieldSizes - ERROR - Failed to get char count in field 2, record 229078021/255/0.

If the previously exported corrupted data in the text file corruptedRecords.d can be corrected then that data can be imported again in the database using an ASCII load.

Workaround

Notes

Progress Articles:

Error (42) due to record corruption
i18N: ABL code to find field data that does not match the database codepage
Attempt to retrieve data via JDBC fails with error Transliteration failed, reason: invalid UTF8 data

Keyword Phrase

Last Modified Date

1/6/2022 3:51 PM

dbtool is giving errors: "ERROR - Failed to get char count of the field, errno -4" after upgrading to OpenEdge version 11.7 or higher

Files(0)

Was this article helpful?

Was this article helpful?

dbtool is giving errors: "ERROR - Failed to get char count of the field, errno -4" after upgrading to OpenEdge version 11.7 or higher

Information

Related Articles