I'm using Version 3.2.20.09. When I use the AUTOTRACE option I'm getting "all" the stats from v$mystat. Older version only seemed to show stat that have a non zero (or non-null) value. But in 3.2 you get all the stats form the view of which most are showing a zero (which I suppose might be a null but is being shown as a zero). Also the output is not in any useful order, I assume they are in order based on statistic# which doesn't help when trying to find certain stats.
For example, looking for BUFFER IS PINNED COUNT is much harder then it should be, it's about a quarter of the way thru the stats:
...(151 stats before this)...
Workload Replay: think time 0
Workload Replay: time gain 0
Workload Replay: time loss 0
Workload Replay: user calls 0
active txn count during cleanout 0
application wait time 0
auto extends on undo tablespace 0
background checkpoints completed 0
background checkpoints started 0
background timeouts 0
blocks decrypted 0
blocks encrypted 0
branch node splits 0
buffer is not pinned count 0
buffer is pinned count 0 <------------------------------------Stat I wanted to find
bytes received via SQL*Net from client 346
...(442 stats after this)...
Is there any way to control this behavior?
First off it seems it would be better to just have the stat with non-zero values and second it would be great to have the stats sorted by name.
There is noting in the preferences that helps and I don't know if there might be a config file setting that would help. Thanks for your help.
A little research on this issue turned up the following: Possible bug on compare Autotrace results panel
The change to display even those statistics with zero values was intentional in order to avoid a bug in Autotrace comparisons.
As for the ordering of statistics, they are retrieved from the database in name order but then placed into an unordered HashMap, so the display order is unpredictable but usually acceptable in that large ranges of the statistic names tend to remain ordered.
I'll ping the developer so both of these issues can be taken under consideration.
Thanks for reporting them,
SQL Developer Team
Thank you very much for the replies!
I think I'm seeing the logic to this. It sure would be nice to have a control to turn on/off seeing values with 0. Is there a patch that I can apply to see the new ordering?
Ah ha! OK, I don't know why I didn't see this before, yes I now see the sort order. I just missed the fact that there are upper case and lower case. Doh. Well at least now I can see how to find the stats I'm looking for. I look forward to seeing the new sort order thought so they sort in a more human natural way at least.