Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Why does ILM job get killed ?

pgruetterApr 6 2017 — edited Apr 10 2017

Hi all

I successfully activated ILM policies with

alter table TABLE_A ILM ADD POLICY COLUMN STORE COMPRESS FOR QUERY HIGH SEGMENT AFTER 2 DAYS OF NO MODIFICATION;

(2 days for testing purposes).

The policies work fine for recent partitions. When checking overall compression after a bit over a week, I saw that many older partitions are not compressed yet.

Digging in DBA_ILMEVALUATIONDETAILS, I see that the objects are selected for execution:

242P134OWNER_NAMETABLE_ASYS_P3341TABLE PARTITIONSELECTED FOR EXECUTIONILMJOB21354

With the JOB_NAME, I check in DBA_ILMRESULTS and find the following entry:

TASK_IDJOB_NAMEJOB_STATESTART_TIMECOMPLETION_TIMECOMMENTSSTATISTICS
242ILMJOB21354STOPPEDJob creation stopped by ADO framework

So now I'm stuck. How can I find out, why the job was stopped?

If I run DBMS_ILM.EXECUTE_ILM manually for this partition, the job runs fine and the partition is compressed afterwards.

This post has been answered by Mudasir Hakak on Apr 8 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 8 2017
Added on Apr 6 2017
4 comments
604 views