Mapping Warning as cause of changing database location

Question

hello group,
i am new in working with owb 10.2, so please forgive me trivial questions.
now to the problem:
i set up a location for my database, created some mappings and deployed them successfully.
yesterday i got new connection details for accessing the database, then i registered/unregistered the location in the control center manager (was that right?).
then i created some new mappings which use tables of the database.
when trying to deploy the new mappings (action:create) i get this error-message.
None
INFORMATIONAL
ORA-04052: error occurred when looking up remote object [email protected]@SRC_domain
ORA-00604: error occurred at recursive SQL level 1
ORA-02019: connection description for remote database not found
MY_FIRST_MAP_mytable
Create
Warning
ORA-06550: line 0, column 0:
ORA-04052: error occurred when looking up remote object [email protected]@SRC_domain
ORA-00604: error occurred at recursive SQL level 1
ORA-02019: connection description for remote database not found
what does this mean?
was the way to change the location settings for the database wrong? or can this be achieved?
can you give me some hints?
thanks in advance,
sven

Answer 1

When you deploy a Connector you are creating a Database Link in the schema you are deploying the connector.
With the replace option, you drop the database link and create it again, so all the objects referring the database link will be in "invalid" status, and you'll have to deploy them again (normally all the mappings, procedures and functions using the connector-databaselink).
If you change the location information, sometimes the name of the databaselink created when deploying the connector change, OWB creates the database link using not only the name of the connector, includes some information of the location properties, so the replace option partially fails, because the drop database link sentence fails, the create database link sentence works properly, though, and in the database you have two db-links: the old one and the new one, so if you aren't aware to deploy again the objects using the old db-link to refer to the new DB-Link, they will stay referring to the old one. For example:
The old information of LOCATION_SOURCE:
HOST: host1
PORT: port1
SID: sid1
When you deploy the connector MY_CONNECTOR in location LOCATION_TARGET referring the schema SCHEMA_TARGET, you create a DB-Link in SCHEMA_TARGET named SID1@MY_CONNECTOR
If you change the information of LOCATION_SOURCE:
HOST: host2
PORT: port2
SID: sid2
And then deploy MY_CONNECTOR again, you create a new DB-Link in SCHEMA_TARGET, named SID2@MY_CONNECTOR, and with the REPLACE option you don't drop the SID1@MY_CONNECTOR DB-Link so all the objects referring to this old DB-Link will be valid, but referring to an incorrect DB-Link.
Hope I've been able to make myself understand, I've read what I have written and seems a bit confusing. Regards.
ANA GH