ODS aborted, why?

[User21257322]

Hi There,

We have some clients that report the ENS ODS task was aborted.

Does anyone can share some possible reasons can lead ODS to aborted status, thanks.

ENS 10.6.1

Policy based ODS

I took a look at the ODS_activity.log:

2020/5/27 10:56:39 mfetp(7424.20496) <SYSTEM> odsbl.ODS.Activity: Last scan file: 

Some *.jar/zip/rpm files xxxxxxx

At 2020/4/18; 2020/4/19 and 2020/4/20, in the same log, have another 3 entries saying the ODS was stopped, but the last scan file was not a compressed file. 

Task ID = ODS_TASK_ID_FULL_SCAN
2020/5/27 10:56:39 mfetp(7424.20496) <SYSTEM> odsbl.ODS.Activity: Scan stopped 

[Former Member · Accepted solution]

Hi @User21257322 

An aborted ODS task can have many causes. The most common ones are:

- Task is run as a "Run client task now" and the default time out value of 20mins hasn't been changed

- Task has a "Stop after X minutes" definition

- System has been switched off

If you need assistance looking in to the logs, I would suggest raising a Technical Support SR with us so we can help you identify the cause. So we can help you, we would require a MER file from the system.