RE: Synonyms
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: <JEREMY.SHEEHAN@xxxxxxxxxxxxxxxxx>, <Dominic.Brooks@xxxxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 1 Dec 2010 13:41:13 -0500
Humm, wonder what you management thinks of the public synonyms that
Oracle creates when it creates the database?? But really, it sounds
like someone really needs to go read the SOX requirements. We live
under SOX and a lot of other FDA rules including HIPPA and there is no
ban on public synonyms. Permissions, now that's another issue all
together.
Now we did go through a phase where everything was banned and audited
which only brought business to a halt. That caused some of the legal
folks to get involved in interpreting the rules for us. Now things are
much better because everyone has clear interpretation of the rules and
resources when that interpretation is not clear, vs. the knee jerk
reaction of misinformed damagers.
Dick Goulet
Senior Oracle DBA
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Sheehan, Jeremy
Sent: Wednesday, December 01, 2010 9:54 AM
To: Dominic.Brooks@xxxxxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Synonyms
--- Surely it's not really public synonyms but granting unnecessary
privileges on those objects to public.
Even then, public synonyms are frowned upon. We're pretty serious about
SOX here and that's what has been declared. So we follow the rules, you
know?
-- Is it SOX compliant to have a post release script to remove all
public synonyms and replace them with private synonyms for all users?
That's been done in the past, but for most things, we have the folks
just start modifying their code to it references the table in the
"owner.table" format. Makes it easier for deploying code, too. Not as
many passwords to remember (everything can be run by the DBA and not the
schema owner).
Jeremy
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Dominic.Brooks@xxxxxxxxxxxxxxxxxxx
Sent: Wednesday, December 01, 2010 9:36 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Synonyms
I love those declarations.
Surely it's not really public synonyms but granting unnecessary
privileges on those objects to public.
Is it SOX compliant to have a post release script to remove all public
synonyms and replace them with private synonyms for all users?
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Sheehan, Jeremy
Sent: 01 December 2010 14:30
To: Thomas.Mercadante@xxxxxxxxxxxx; jd@xxxxxxxxxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: RE: Synonyms
It's been declared that public synonyms are bad for any SOX databases
where I work. That means that the DBA's have to comb through any code
that needs to be promoted for the forbidden words 'create public
synonym'. It really sucks when a 3rd party application relies heavily
on them. We have to constantly push code back to them for revision.
Jeremy
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mercadante, Thomas F
(LABOR)
Sent: Wednesday, December 01, 2010 9:20 AM
To: jd@xxxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Synonyms
Josh,
I use them all the time. Standard practice here. I used to use public
synonyms but now use private syns. The schema who owns the objects
creates private syns for the users who need them.
Tom
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Joshua D. Drake
Sent: Tuesday, November 30, 2010 7:31 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Synonyms
Hello,
Kind of out of left field here but I was curious about how many people
here use Synonyms and the types of synonyms they are normally using,
i.e; table/view/column?
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
--
//www.freelists.org/webpage/oracle-l
i 0 zX + n { +i ^
i 0 zX + n { +i ^
_______________________________________________
This e-mail may contain information that is confidential, privileged or
otherwise protected from disclosure. If you are not an intended
recipient of this e-mail, do not duplicate or redistribute it by any
means. Please delete it and any attachments and notify the sender that
you have received it in error. Unless specifically indicated, this
e-mail is not an offer to buy or sell or a solicitation to buy or sell
any securities, investment products or other financial product or
service, an official confirmation of any transaction, or an official
statement of Barclays. Any views or opinions presented are solely those
of the author and do not necessarily represent those of Barclays. This
e-mail is subject to terms available at the following link:
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent
to the foregoing. Barclays Capital is the investment banking division
of Barclays Bank PLC, a company registered in England (number 1026167)
with its registered office at 1 Churchill Place, London, E14 5HP. This
email may relate to or be sent from other members of the Barclays Group.
_______________________________________________
!
0~ +-
rW
i0zX+ n{+i^
--
//www.freelists.org/webpage/oracle-l
Other related posts:
