Any chance you ran a patch against the repository, but did not patch an ODI Studio install - then connected with the "unpatched" ODI Studio? See excerpt from here (https://t.co/37ToIPhaEf) below.
I M P O R T A N T :
If used once, you are demanded to consistently use ODI 220.127.116.11.1 exclusively.
After an ODI Studio 18.104.22.168.1 connected once to a Repositories, any connection to the same Repositories using ODI 22.214.171.124.0 will corrupt the Work Repository data.
More precisely, when connecting again with ODI Studio 126.96.36.199.0 to a Repository where ODI Studio 188.8.131.52.1 was previously used...
... Mapping components (such as Lookup, Pivot, Unpivot, Table Function and Sub-query Filter) will be deleted from the Repository as soon as ODI Studio starts-up, and connects to the respective Repository, with no way (other than a database backup) for recovering the data.
Thanks for the response. Unfortunately I just read your reaction today ;-(.
We work with ODI Studio 184.108.40.206.0 and repository 220.127.116.11.0, so that is not the problem.
Somehow we start to believe that the problem is somthing in the environment though.
When only one of us in logged in in ODI, there are no problems, but as soon as a second person logs in, the problems start ...
Are you getting error "An internal error occurred whilst opening the Diagram"
becaue this Signaled When Clicking On The Mapping.
Actually this issue will come when you migrate from ODI 11g to higher version of ODI 11g
excluding upgradation from ODI 18.104.22.168.0 to ODI 22.214.171.124.0
Thanks for the response.
No, we can still open the mapping, but it is evry time a surprise whether or not some joins are removed and/or if the mapping can be executed.
Besides the evironment problems, we suspect that ODI has some problems with datasets in combination with reusable mappings and/or when the same tabel appears more than once in a dataset aith a different alias.
Is this is giving any error "Table or view does not exist" at a time of mapping execution on ODi 12c (12.1.2 version), if Yes, it is a bug in 12.1.2 version.
Please go through the Doc ID 1644315.1 for the same.
If No, then please raise an SR in oracle support portal for futher solution.