Sure.  For every instance that you want to include in
the repository, create an account name that matches
the instance.

Setup FGAC so that each sees only it's own data.

Jared






"Jamadagni, Rajendra" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
 01/03/2003 07:08 AM
 Please respond to ORACLE-L

 
        To:     Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
        cc: 
        Subject:        RE: Centralized StatsPack Repository


Hmmm... FAGC ?? 
Jared, I am stumped ... I can't put these 2 & 2 together. I was planning 
on a new instance called "dbmon". One schema for each production database 
instance. Statspack will be installed for each schema and other monitoring 
scripts that we use internally.
I am thinking of best ways to propogate datasets from individual databases 
to this central db. 
Could you explain more about (your idea on) how FAGC would be useful?? 
Thanks in advance 
Raj 
______________________________________________________ 
Rajendra Jamadagni              MIS, ESPN Inc. 
Rajendra dot Jamadagni at ESPN dot com 
Any opinion expressed here is personal and doesn't reflect that of ESPN 
Inc. 
QOTD: Any clod can have facts, but having an opinion is an art! 

-----Original Message----- 
Sent: Thursday, January 02, 2003 8:03 PM 
To: [EMAIL PROTECTED] 
Cc: Jamadagni, Rajendra 
Importance: High 

Have you considered FGAC? ( fine grained access control ) 
I haven't tried it, but it seems like a good candidate for 
centralizing stats pack data with as little code as possible. 
Jared 

********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************2

Reply via email to