Differences

This shows you the differences between two versions of the page.

--- ilm [2016/02/08 16:45] – z0hpvk
+++ ilm [2025/03/08 22:24] (current) – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 It can be changed at the session and system level.
 <code> ALTER SYSTEM SET HEAT_MAP = ON;</code>
-V$HEAT_MAP_SEGMENT
-DBA_HEAT_MAP_SEGMENT
+Causes the database to track read and write access of all segments.\\
-DBA_HEAT_MAP_TOP_OBJECTS
+The activities are not tracked for objects in SYSTEM and SYSAUX tablespaces.\\
-DBA_HEAT_MAP_TOP_TABLESPACES
+=== Views ===
+V$HEAT_MAP_SEGMENT\\
+DBA_HEAT_MAP_SEGMENT\\
+DBA_HEAT_MAP_TOP_OBJECTS\\
+DBA_HEAT_MAP_TOP_TABLESPACES\\
 ==== Automatic Data Optimisation ====
+ADO policies can be set at row, segment or tablespace level.\\
+These policies will be evaluated automatically during the weekend maintenance window.
+The commands are used in conjunction with the CREATE and ALTER TABLE commands
+Compress Rows if they haven't been accessed for 60 days
+<code>ILM ADD POLICY
+ROW STORE COMPRESS ADVANCED
+SEGMENT AFTER 60 DAYS OF NO ACCESS;</code>
+Compress Rows 1 year after they have been created
+<code>ILM ADD POLICY
+ROW STORE COMPRESS ADVANCED
+SEGMENT AFTER 1 YEARS OF CREATION;</code>
+Compress Rows if they haven't been changed for 45 days
+<code>ILM ADD POLICY
+ROW STORE COMPRESS ADVANCED
+SEGMENT AFTER 45 DAYS OF NO MODIFICATION;</code>
+There can only be one row level policy for a segment.\\
+The view USER_ILMPOLICIES shows details of all existing ADO policies.\\
+Disable all ADO policies for the whole database
+<code>BEGIN
+DBMS_ILM_ADMIN.DISABLE_ILM;
+END;</code>
+Disable a single policy on a table
+<code>ALTER TABLE t1 ILM DISABLE_ALL;
+ALTER TABLE t1 ILM disable <policy_name>;</code>