Confirmed by c.a.
There is a bug (or at least an error in the documentation) in the agent for oracle. The documentation of this agent at page 15 "installing the agent" (2-7) say :"log purge -The default value for this option is 1 (on)".
But the relative regkey by default is 0, not 1.
So, if you have oracle in archive log the log can't be deleted after a sucessful backup. As result -soon or later- the db will crash due to out of space problems.
I opened an issue, and the bug is confirmed.
You have to manually set to 1 the logpurge key.
There is a bug (or at least an error in the documentation) in the agent for oracle. The documentation of this agent at page 15 "installing the agent" (2-7) say :"log purge -The default value for this option is 1 (on)".
But the relative regkey by default is 0, not 1.
So, if you have oracle in archive log the log can't be deleted after a sucessful backup. As result -soon or later- the db will crash due to out of space problems.
I opened an issue, and the bug is confirmed.
You have to manually set to 1 the logpurge key.