-----Original Message-----
From: Thomas Jeff [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 29, 2001 12:05 PM
To: Multiple recipients of list ORACLE-L
Subject: Location of PLAN_TABLERather a trivial question, but our DBA team is discussing how best
to implement the location of the plan table. My preference is
is simply create is as SYS, public synonym, and grant privs on
it to our developers. I'm being outvoted by the others, who
want to create it in each and every application schema, but still grant
access to all developers with no synonyms, the thinking being, that
it would help to minimize accidental deletions of execution plans
and so forth.My belief is that's simply over-thinking this issue. What do you
do at your sites?Thanks.
--------------------------------------------
Jeffery D Thomas
DBA
Thomson Information Services
Thomson multimedia Inc.Email: [EMAIL PROTECTED]
DBA Quickplace: http://gkmqp.tce.com/tis_dba
--------------------------------------------
Title: Location of PLAN_TABLE
individual schema is the way to go, IMO.
Deletions? if you want to save access paths, used stored outlines. (if an
option)
Otherwise, why not do a an export?
just a
thought
- Location of PLAN_TABLE Thomas Jeff
- RE: Location of PLAN_TABLE Mohan, Ross
- RE: Location of PLAN_TABLE Rao, Maheswara
- RE: Location of PLAN_TABLE Jacques Kilchoer
- RE: Location of PLAN_TABLE Thomas Jeff
- RE: Location of PLAN_TABLE Toepke, Kevin M
- RE: Location of PLAN_TABLE Deepak Thapliyal
