Accelerated space reclamation on Exadata Cells
During my present Exadata course in Munich I learned that there is an (invisible) default threshold present on the Exadata Cells that triggers „Accelerated space reclamation“ when 80 % Filesystem Utilization is reached. This is what I observed on a Cell where I consumed 82 % of space:
CellCLI> list alerthistory detail name: 4_1 alertMessage: "File system "/" is 82% full, which is above the 80% threshold. Accelerated space reclamation has started. This alert will be cleared when file system "/" becomes less than 75% full." alertSequenceID: 4 alertShortName: Software alertType: Stateful beginTime: 2012-09-12T13:17:53-04:00 examinedBy: metricObjectName: / notificationState: 0 sequenceBeginTime: 2012-09-12T13:17:53-04:00 severity: critical alertAction: "MS includes a file deletion policy that is triggered when file system utilitization is high. Deletion of files is triggered when file utilization reaches 80%. In particular, the deletion policy is as follows: For the /opt/oracle and /var/log/oracle file systems, files in the ADR base directory, metric history directory, and LOG_HOME directory will be deleted using a policy based on the file modification time stamp. Files older than the number of days set by the metricHistoryDays attribute value will be deleted first, then successive deletions will occur for earlier files, down to files with modification time stamps older than or equal to 10 minutes, or until file system utilization is less than 75%. The renamed alert.log files and ms-odl generation files that are over 5 MB, and older than the successively-shorter age intervals are also deleted. Crash files that are over 5 MB and older than one day will be deleted. For the / file system, files in the home directories (cellmonitor and celladmin), /tmp and /var/spool directories that are over 5 MB and older than one day will be deleted. Try to delete more recent files, or files not being automatically purged, to free up space if needed."
I have not seen that documented, so I thought it might be of interest for the Exadata community. The threshold does not show, though:
CellCLI> list threshold
--Nothing here --
The mentioned metricHistoryDays attribute is documented and defaults to 7 days, which can be modified like this:
CellCLI> list cell attributes metricHistoryDays 7 CellCLI> alter cell metricHistoryDays=3 Cell qr01cel01 successfully altered
As always: Don’t believe it, test it! 🙂
EMEA Customer Support Services Excellence Award 2012
It makes me proud that I got this Award for the Fiscal Year 2012 granted – this is really the cream of the crop of an outstanding year and it is great to see it recognized by the corporation!
Needed to ask Joel what MVP means, though, he got the same award also and very well deserved 🙂
Retrieve Sessions with divergent Optimizer Settings using V$SES_OPTIMIZER_ENV
Just a little snippet from my present Performance Tuning course in Munich that you may find useful:
There are several Initialization Parameters that influence the Optimizer and that can be modified with ALTER SESSION. We can see whether certain sessions have settings different from the System-wide settings with a query like
SQL> set lines 200
col name for a40
col username for a10
col value for a40
select a.sid,c.username,a.name,a.value
from v$ses_optimizer_env a
join v$sys_optimizer_env b on a.id=b.id
join v$session c on a.sid=c.sid
where a.value<>b.value
and c.username is not null
and c.username not in ('SYS','SYSTEM','DBSNMP')
order by a.sid,a.name;
SID USERNAME NAME VALUE
---------- ---------- ---------------------------------------- ----------------------------------------
22 SCOTT workarea_size_policy manual
267 ADAM optimizer_mode first_rows
Probably of interest especially if one of these users complains about performance and we want to know what is different with their sessions 🙂

