Error: F_JD5E12 Missing Input Encoding for Datatype during Localization of Column

Issue

The following error appears during Activate Replication, Capture, or Integrate:

F_JD5E12: Missing input encoding for datatype '<type number>' [<type name>] with CBuf string '<string>' during localization of column [<column>] of table [<table>]

Environment

HVR 6

Resolution

To resolve this issue, update the missing character encoding values in the HVR catalog.

You can do this in one of the following ways:

Manually enter the character encoding value in the HVR UI catalog view.
Run the hvrmigratemissingencoding script.

For more information about valid encoding values, see Supported character encodings.

Use hvrmigratemissingencoding script

The hvrmigratemissingencoding script is located in the HVR installation directory.

The script scans the HVR catalog for character columns with missing encoding values. It then updates those columns using either:

The database encoding stored in the location properties.
The encoding specified with the -e option.

Command syntax

hvr hvrmigratemissingencoding [-n] [-A] [-v] [-e <encoding>] [-c <channel>]...
                              [-t <table>]... [-R <url>] hub

Options

Option	Description
`-e <encoding>`	Encoding name to use. If omitted, the script reads the database encoding from the channel's capture location properties.
`-c <channel>`	Restricts the update to a specific channel. This option can be repeated.
`-t <table>`	Restricts the update to a specific table. This option can be repeated.
`-n`	Runs the script in dry-run mode. Reports what would be changed without applying updates.
`-A`	Skips the post-update Activate step. Use this option if you want to run Activate manually later.
`-v`	Runs the script in verbose mode and prints the list of tables and columns that will be updated.
`-R <url>`	Routes the update through a running HubServer at the specified URL instead of writing directly to the repository.

Important considerations

The hvrmigratemissingencoding script assumes that every character column with a missing encoding should use the same encoding.

Do not use the script for columns that contain data in different encodings. In that case, update the affected columns individually in the HVR UI.

Activation after catalog updates

After the catalog is updated, the script posts an Activate event for each affected channel with:

replace_enroll=true

This regenerates the enrollment files from the updated catalog.

Activation behavior depends on whether HubServer is running:

If HubServer is running, the Activate events run immediately.
If HubServer is not running, the Activate events remain queued and run the next time HubServer starts.

Use the -A option to skip this automatic Activate step and run Activate manually later.

Cause

This error occurs when a character column in the HVR catalog does not have a character encoding defined.

Recent versions of HVR require all character columns to have an encoding so that column data can be interpreted correctly. This issue typically occurs when a channel was created in an older version of HVR that did not require an explicit character encoding for character columns.

When the channel is later opened or processed in a newer version of HVR, the missing encoding causes the error.