Error: F_JD0006 Table Does Not Appear in DBMS Catalogs after Upgrade
Issue
The following error appears during Activate Replication after upgrading the hub from HVR 6.1.0 to HVR 6.2.0 or later:
F_JD0006: A table named [<schema>.<table>] does not appear in the DBMS catalogs of <location>.
Environment
- HVR 6
- Upgraded from HVR 6.1.0 to HVR 6.2.0 or later
- Channels with the
Case_Sensitive_Nameslocation property enabled
Resolution
To resolve this issue, run the hvrmigrateschemacase script and then activate the affected channels again.
Use hvrmigrateschemacase script
The hvrmigrateschemacase script is located in the HVR installation directory.
The script scans channels and locations that use Case_Sensitive_Names, compares the stored TableProperties parameter Schema values with the actual schema names returned by the database catalog, and updates any values that differ only by letter case.
Availability
The hvrmigrateschemacase script is available in HVR 6.2.0/39, 6.3.0/9, 6.3.5/3, and later patch releases.
If your hub is on an earlier 6.2.x or 6.3.x patch release, upgrade the hub to one of the above builds before running the script.
Command syntax
hvr hvrmigrateschemacase [-n] [-c <channel>]... [-l <location>]... [-R <url>] hub
Options
| Option | Description |
|---|---|
-c <channel> | Restricts the migration to a specific channel. This option can be repeated. |
-l <location> | Restricts the migration to a specific location. This option can be repeated. |
-n | Runs the script in dry-run mode. Reports what would be changed without applying updates. |
-R <url> | Routes the update through a running HubServer at the specified URL instead of writing directly to the repository. |
Important considerations
Run the script once after upgrading the hub, before activating the affected channels.
Start with the -n option to review the changes before applying them.
If a stored schema name does not exist in the database catalog, the script skips it.
If a stored schema name matches more than one database schema when compared case-insensitively, the script stops and you must update the TableProperties parameter Schema manually.
Cause
This issue occurs because HVR 6.1.0 stored schema names in the hub repository using normalized casing, typically lowercase, even when Case_Sensitive_Names was enabled.
HVR 6.2.0 and later treat schema names case-sensitively for affected locations. If the stored TableProperties parameter Schema value does not match the actual schema name in the database catalog, Activate Replication cannot resolve the table and raises this error.