RE: Changing USER_TAB_COLUMNS Synonym
- From: Dave Morgan <oracle@xxxxxxxxxxx>
- To: Oracle-L <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 19 Oct 2016 09:40:28 -0600
Wow, just wow. Comments inline. Please forgive me for my snarky ones and
take them as production DBA humor.
Thank you to Mark P, Jack A, Jeff S, Mathew P.
-----Original Message-----
From: Dave Morgan [mailto:oracle@xxxxxxxxxxx]
Hello All,
Does anyone know of bad consequences or side effects to altering a single
schema's USER_TAB_COLUMNS
synonym to point at ALL_TAB_COLUMNS?
Our sophisticated developers used a data owner schema in their ORM to code
against and since they
don't have access to those accounts in production ........
Instead of hacking the data dictionary, why not just fix your application?
Breaking the database for just
the app instead of fixing the app doesn't seem like a good idea.
Because there is a cost and a deadline. I would rather trust my rushed solution
than my sophisticated
developer's rushed solution.
how about changing the mindset of your developers?
If you could produce a 3-10 page document describing how to achieve that
objective it
would be extremely useful and greatly appreciated. In fact I suspect you could
raise
$25-$50,000 just from this list once the effectiveness of your method has been
proved.
Dave, I do not see a problem with modifying a specific username to give them
different
visibility to database objects if changing the application itself is not really
an option at this point.
They will fix it in the future. Apart from cost (mid 6 figure) it means a
database rollback which I hate.
I also like being a fscking hero, instead of Da Biggest A......
I ask for my schema's columns, and I get all the columns in the database
Maybe the database isn't broke, but it's lying to me.
Depends on your role. Why don't you just create private syns pointing to the
public ones.
If you don't have privs to do that, welcome to your environment, otherwise you
are lying to yourself.
I spent 3 days recently trying to help a user yelling that our app was
broke.and it was bc they create a local DUAL table.
Maybe I'm too gun-shy here. But still.
I feel your pain. Right NOW actually :) Mind you I am killing myself laughing
while I'm trying to help them
I don't yell, I just don't help. "It works for everyone but you, if you cannot
understand your own application I cannot help you"
There is no such thing as too gun-shy. Not to a production DBA.
There is a very valuable rule that DBAs [especially] always need to remember-
“Just because it seemed like a simple
change doesn’t mean it wasn’t impacting. Think globally, isolate locally.”
Amen Brother :)
I drove 400 miles to a plant in the North of England once to find they had
two rows in dual!.
I always thought the 2 rows in dual story was apocryphal Thank you,
Summary. The private synonym was implemented, All is good. Proper version
promised in 72 hours.
The hero is gone, the DBA is back, he questioned whether that was a reasonalble
timeline.
Thanks to all
Dave
--
Dave Morgan
Senior Consultant, 1001111 Alberta Limited
dave.morgan@xxxxxxxxxxx
403 399 2442
--
//www.freelists.org/webpage/oracle-l
Other related posts:
