The “what’s new” document states that DS 4.0 finally supports Oracle (and DB2) synonyms (section 2.9 “Source and target support” on page 15). I can’t seem to find/figure out how to import the metadata using an Oracle Synonym. It won’t accept the @xyz dblink parameter and doesn’t find it just using the synonym name.
Anybody done that yet? Is it too obvious for me to see?
We don’t have rights to the linked objects, though indications are that they are tables. From an SQL window, we can read the data from the synonyms simply with a “select * from synonym_name”, but seem to have only select rights and can’t see the structure or anything else. In the DS Designer metadata browser, all of the synonyms show up in the list of objects with type “SYNONYM”, but when we right click and import, we get a “not found” error.
Is there something we need to do in the data store definition that enables importing metadata on a synonym?
synonym doesn’t have any metadata so for importing the metadata of the synonym DS will first find the underlying object for which this synonym is created and get the metadata from the actual object (using the ALL_* views)
have you tried importing the synonym using import by name ?
can you send me the output of the following Query (use the same username that you are using in datastore)
select synonym_name, owner, table_owner, table_name, db_link from all_synonyms where synonym_name =
Does anybody has any hint about this, I can see my development connection is using the synonyms as tables in it.
I have just created another connection for test database and cannot import the synonyms from this conneciton. Same connection works from TOAD for these tables.
The workaround that was used in prior versions will still work here. Create a view, import the metadata, then drop the view and recreate the synonym. DS works fine with views.
However, I just tested the import against a synonym and it worked as advertised. I’m running 14.0.2.376.