Skip to main content

Hi,

 

We have a scheduled migration job that suddenly stopped working about 6 months ago. No changes to the system were made.

It works fine when you run it as an on-demand job.

 

Error message is: 

This background job was set to state Error because the executing Oracle process was killed. ( Detected by cleanup process at 2021-01-24-06.51.56 )

Any thoughts?

 

We are on Apps 9.

 

Thanks as always

Hi Matthew,

Based on the error it seems the cleanup process has set this to error state because there were no active session/background job running for this database process at that time. 

 

Regards,
Sahan

Hi,

 

How would that be / what would I check to enable?

 

Any help you can give would be vastly appreciated.

Hi Matthew,

 

If you start a new background job does it finishes without any errors or same thing happens. One reason I could think of is migration job has a performance issue and ran for longer time and backend session time out happen and got disconnected. 

 

Regards,

Sahan

Hi,

 

When we run-on demand - so not as background - it runs ok. When we set up a new scheduled job, even at a different time, it crashes.

So you are thinking that it is running for too long and a process is crashing. Any ideas how to stop this. 

 

Terms & ConditionsCookie settings