Skip to main content

I am hoping you can help.

We have a scheduled DB Task called ‘Update Override Values’ but we are now seeing errors in the BG Jobs for ORA-01476: divisor is equal to zero

I am not sure what the BG Job is for as I didn’t create it and there are no notes / descriptions I can find relating to it so I am unable to resolve the BG Job Error.

Is anyone able to point me in the right direction? I am using Apps 10

 

Thanks, 

Hi,

This could be related to a customization(or a config?) you have done. It can be used to update system defined or default values that would come in with standard IFS functionality to aid your customization.

Hope this helps.

Asanka


Hi ​@lisa.gilesAB,

The reason for “ORA-01476: divisor is equal to zero” is that the original logic did not handle situations where the date difference used as a divisor was zero, which caused a division-by-zero error.

Thanks,

Sarasi


Seems like the background job is updating a field value ( based on the name of the background job -Override). During the calculation, the denominator is getting the value of zero. Thus the error. You may want to look at the calculation and adjust it to handle this scenario as a number cannot be divided by zero. Reminds me of mathematics during my school days 🙂. You may need assistance to look at the code / custom field.


As Sarasi has mentioned above, it may be the schedule interval calculation it self, rather than a field is updated. A screen print of the whole section of the error message might be useful for someone in the forum to direct you a bit more targeted direction.


This is the error that I am seeing in the DB BGJ

 

Thanks :)


Hi,

This is not an override value error (which could be connected to a customization). Maybe it would help to update the case title and the description 🙂?

 

PM_ACTION_CALENDAR_PLAN_API. UPDATE_OVERDUE_VALUES


Hi ​@lisa.gilesAB,

Which UPD version are you using?

Thanks,

Sarasi


@sdhalk We are on update 28

 

@AsankaGaru - Sorry for the confusion - how can I update the Title of my question?


Hi ​@lisa.gilesAB,

This is a known issue in UPD 28, and it has already been resolved in App10 UPD 29.

Thanks,

Sarasi


Oh perfect! Thank you so much! I will request Update 29 and get it applied to our environment. Thanks so much! 


Reply