|
Raj
I did this sometime back
but later on somehow this went on to the backburner.. (I also had half-developed
XL based interface to the central statspack data)
In the central repository
create the set of tables that statspack uses to store data under user "central".
Create individual schema's with different instance names (that you want
monitored). Under each of the schemas
1) create a db link with a
dba user to the database that this schema monitors
2) create private synonyms
for all of the v$, dba* views that statspack queries using db links created
above (create synonym v$session for sys.v$session@target_db)
3) create private synonyms
for all of the statspack tables to point to the "central" schema
Now when you schedule
statspack.snap it will read from the target db and insert data into the
"central" user...
Babu
|
Title: RE: Centralized StatsPack Repository
- Centralized StatsPack Repository dgoulet
- RE: Centralized StatsPack Repository Jamadagni, Rajendra
- Re: Centralized StatsPack Repository Mogens N�rgaard
- RE: Centralized StatsPack Repository Orr, Steve
- RE: Centralized StatsPack Repository Jamadagni, Rajendra
- RE: Centralized StatsPack Repository DENNIS WILLIAMS
- RE: Centralized StatsPack Repository Jared . Still
- Re:RE: Centralized StatsPack Repository dgoulet
- RE: Centralized StatsPack Repository Jamadagni, Rajendra
- RE: Centralized StatsPack Repository Jared . Still
- RE: RE: Centralized StatsPack Repository Babu Nagarajan
- RE: RE: Centralized StatsPack Repository Kirsh, Gary
