This content has been marked as final. Show 7 replies
If you are all in the same database, there is no reason to use a dblink. In fact, you should not even need to use a LKM. Add a data server for your database with a user that has access to the source, work, and target schemas. Then, you will only need to select an IKM in your Interface.
If this is not possible, you will need to select a Loading Knowledge Module such as LKM SQL to Oracle. This LKM will stream the data through the agent, potentially causing performance issues.
Does your problem occur in development/test environment, or in pre-production / production environment ?
Actually, there may be 2 reasons for having 2 dataservers but only 1 DEV database host :
1) your topology is not set up correctly , as Jerome Fr said
2) or you have 2 database hosts in your production environment, but only 1 in your dev environment (for cost issues or other considerations).
In the second case, you need to have 2 dataservers, otherwise your scenario will fail in production (because the production flow will need LKM).
But, in development, with the same database host, you cannot use the LKM DB Link. If you use it, this error will occur because the LKM will create the "C$ synonym" object and the "C$ view object" in the same database, with the same name.
First, check in which case you are.
- If you're in the first case, modify your topology.
- If you're in the second case, don't use this LKM in dev (you may use the LKM sql to oracle during your test, then DB Link in other environment like production).