You can use this kludgey command (support actually gave it to me) to get all sorts of memory information:
# echo vmstat | kdb > vmstat_info.txt
grep for stuff like 4K to see if you have overtaxed your vio server memory.
You can use this kludgey command (support actually gave it to me) to get all sorts of memory information:
# echo vmstat | kdb > vmstat_info.txt
grep for stuff like 4K to see if you have overtaxed your vio server memory.
Is it possible for a reporting solution to both ‘look’ sufficiently effective to be purchased by the average IT department and ‘be’ sufficiently effective to accomplish anything of value? This is the real question and it seems sad that solutions may have to either pick one side or the other.
This shows queries that use signifantly greater cycles (and thus are a little suspicious):
select substr(sql_text,1,90),cpu_time from v$sql order by cpu_time;