This content has been marked as final. Show 8 replies
Sorry, but the destination objects are always assumed to be in the schema owned by the destination connection.
Man, that's too bad. That's one of the final pieces that is keeping us using TOAD.
Yes thats a shame... I don't have CONNECT rights for specific schema to do DIFF..
and would prefer to do DIFF from my own schema
any plans on allowing from a different schema
Why would we assume something like that? As DBA's we compare difference schema's for differences all the time and rarely ever log in as the schema owner...Is that an identified enhancement request? If not...Where can we request that...
I am looking at this with Change Management to determine what we can do in this area. We are still in the investigation phase, so I do not have a concrete answer at this point.
This is what is keeping us on Toad as well. Developers need to be able to compare schemas without having to log in as the target schema, especially on production tiers.
Just wanted to add my voice to this...
It doesn't make any sense to assume the objects to be diffed belong to the owner the user is connected as. In an enterprise environment, we're not about to give developers the passwords to every schema. They can connect as themselves, that's it. So this "feature" is in no way ready for prime time.
I hope Oracle takes a hard look at this decision, because they are wrong in making this assumption, it makes this functionality in the tool pretty much worthless.
Edited by: cmcneil on Jul 20, 2012 3:27 PM
I also ran into a variation of this bizarre assumption and actually thought it was a bug while attempting to export a schema using a SYS connection. The target schema for export was not SYS, but tons of SYS and SYSTEM objects appeared in the export file, while not appearing in the summary of which objects would be exported.
If you want the gory details : Re: EA 3.1 - Database export - export file contains SYS objects - BUG ?
Both functions (export and diff) assume that the connected schema is relevant to the function, which I find a bizarre assumption.
Please add my vote to have the Diff and Export functionality changed to not assume the connected schema is the basis of comparison.