Because the columns are available to some users but not to the others,and
I can't modify the application.
It looks like you are running out of options, two questions to better picture your situation:
Is the application fully qualifying table names?
Is the application accessing tables directly or thru synonyms?
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
It looks like you are running out of options, two questions to better picture your situation:
Is the application fully qualifying table names?
Is the application accessing tables directly or thru synonyms?
yes the application is fully qualifying table names and accessing tables through synonyms.
As a newbie I should probably stay out of this discussion...but maybe I'll learn something.
Seems to me if app is fully qualifying table names (ie: table_owner.table_name) then it's not using synonyms. I suppose it could be fully qualifying synonyms (ie: synonym_owner.synonym_name) but that makes little sense.
If each user of app has own Oracle logon, and if app is NOT qualifying table names, then some users can have synonym pointing to the actual table and other users a synonym pointing to a view or views you have setup which eliminates certain columns. Have I overlooked something?
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Reply With Quote
Originally Posted by davey23uk
Bookmarks