- May 3, 2016 at 1:49 am #8882MarkKeymaster
Can I use HVR to replicate case sensitive table or column names?
Yes, the action to use if at least one of the tables in the replication setup (channel) has a case sensitive name or column name is LocationProperties /CaseSensitiveNames. This action is particularly important against Oracle Databases when by default Oracle will assume table and column names are case insensitive unless quoted. The action LocationProperties /CaseSensitiveNames will ensure that table and column names will be quoted.
Please note that the action LocationProperties /CaseSensitiveNames:
- Always applies to all tables in the channel.
- Is required before tables are added to the channel, since by default HVR will assume that table and column names are case insensitive. If tables were already added (through the Table Explore/Table Select function in the GUI) then tables will have to be removed and re-added to the channel.
You may not realize that a table uses a case sensitive name or column name until you see errors like:
September 28, 2017 at 1:30 am #11306registerParticipant
- F_JD0006: A table named [.] does not appear in the DBMS catalogs during Table Explore/Table Select.
- ORA-00942: table or view does not exist during a Refresh.
- ORA-00904 “”: invalid identifier, e.g. during a Refresh. This may be an indication that the column reported in uppercase may in fact be in mixed case in the database.
F_JD0006: A table named [.] does not appear in the DBMS catalogs during Table Explore/Table Select.
Can you please let us know how to resolve above issue F_JD0006: ??September 28, 2017 at 11:03 am #11308ggoodrichKeymaster
Hello, and thank you for the question in the HVR forum related to supporting case-sensitive objects (table names).
For your case, it might be best to open a support ticket so that we can give you the best and most timely support. Our support portal is located at: https://support.hvr-software.com/
Before creating a ticket, please be sure to collect all of the supporting case documentation. For example, for your incident, please include:
* HVR version(s) – source/target/hub/console
* Source/Target platform details (database/version)
* An example of the DDL to create source table which is displaying the issue
* the full HVR error message including the full HVR log file (These are located in $HVR_CONFIG/log/<hub name>/<channel>.out)
* export of your hub
- You must be logged in to reply to this topic.