Restricted view access to other schemas 'showstopper' problem
524145Jul 20 2006 — edited Sep 6 2006I'm tasked with the potential roll-out of SQL Developer across a large number of users (doing away with equivalent software in the process).
The feedback has been very positive. However, the only real issue stopping the replacement from progressing is that we cannot view certain objects in other schemas (package bodies, triggers etc) ... i.e. we need to connect as the schema owner to view these. This is essential, otherwise everyone would need to know the application schemas password.
Our current software has the same issue unless the following option in the Options/Startup window is activated: 'Check for access to DBA views. Otherwise, SYS.ALL_xx views will be used when listing objects'. Thereafter the issue is resolved.
Is there any workaround (e.g. like the above) in SQL Developer?
Many Thanks.