Why Does My HVR Table Name Differ from the Base Name?

Question

Why does the HVR Table Name differ from the table Base Name in my channel configuration? For example, why does the HVR Table Name have a t_ prefix or exclude special characters such as $?

Environment

• HVR 6
• Category: Table mapping and replication channel configuration

Answer

The naming mismatch is expected HVR behavior. HVR table names must be lowercase ASCII identifiers. They can't contain spaces, dollar signs ($), hashes (#), or other punctuation. When a source table name contains unsupported characters or patterns, we adapt the name so it complies with our naming rules.

During schema adaptation when running hvradapt, we:

• Remove unsupported special characters, such as $.
• Add a t_ if the original name contained prohibited characters.
• Store the original database table name as the Base Name.
• Store the adapted HVR-compatible name as the Table Name in the channel.

For example, a source table named tablename$ appears in the channel as:

• Base Name: tablename$
• Table Name: t_tablename

This difference is by design and doesn't affect data flow or consistency. Use the Base Name to identify the original source table, and use the adapted Table Name for HVR commands and configurations. To customize table names, such as adding prefixes or mapping tables to specific target names, configure TableProperties actions in the channel.

For help with complex channel configurations or bulk table renames, contact our support team.