No question at this time
DBA Top 10
1 M. Cadot 6500
2 B. Vroman 2700
3 J. PĂ©ran 1600
4 P. Tsongayinwe 1500
5 P. Wisse 1200
6 A. Kavsek 1100
7 D. Walgude 400
7 J. Schnackenberg 400
9 J. Alcroft 200
10 A. Hudspith 100
10 D. Johnson 100
10 B. B 100
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48695
Total active users1323
Act. users last 24h3
Act. users last hour0
Registered user hits last week79
Registered user hits last month345
Comment details
Date 29-NOV-05
Type Comment
User Guy Lambregts
Message Hi,

Overall appreciation : very high

The plato.audit gives info which I do not find back in statspack & awr reports, like

1. Plato detects VPD policies, Dataguard set up, ...
2. Plato detects,highlights some more or less critical situations. (system tablespace default tablespace for a user, ...)
3. Plato gives very usefull summaries of dba_segments
(easy but absent in statspack & awr reports)
4. Plato gives allocation type and segment space management of tablespaces (easy but absent in statspack & awr reports)
5. Plato warns you about not analyzed tables ...
6. Lot' s of very interesting statistics like average undo per hour, ...

Things I missed ( or I must overlooked it )

1. "In the Key system statistics" part of the plato.audit I haven' t seen any info about hard parses/total parses.
2. In the plato.tuning I missed some info of the header page of statspack, I think here about an execute to parse ratio, parse cpu to parse elapsed, ... also no info about hard parses/total parses. I should give some v$sysstat info in the plato.tuning.
3. It should be great if a plato.tuning or a plato.sessiondetails should list the sql statements with a bad parse calls/execute ratio (something like a order by parse_calls with executions )
4. It should be great if plato.tuning should list the literals in v$sql