Hi All,
Does anyone have experienced an issue by assigning a hard-coded value to the SOURCE_ACCESS_DB_LINK parameter of this LKM?
If I use a db link name without the ‘@’ in the middle of the name, it works fine. But if that db link name is a compound string with ‘@’ symbol, the mapping just ignores the value and it takes the name of the Data Server of the source table as DB Link.
For instance, the following db link name works fine:
HOST01
However, this one it doesn’t:
HOST01@SCHEMA01
I know that the quick solution is to avoid the ‘@’ symbol within the name of the db link but I would like to understand why this is happening and if there is any way to bypass the “bug”.
As part of a migration from OWB to ODI 12c we would like to minimise the number of database modifications within the production environment.
Thanks,
Jose