Changing Polling Time For BAM Logging In Oracle B2B Crashes The Job (Doc ID 1465692.1)

Last updated on APRIL 23, 2019

Applies to:

Symptoms

 B2B adds a new row whenever "BAM Polling Interval" changes, instead of changing the existing one.
When the BAM logging is activated in Oracle B2B by setting "Enable BAM" property to "true" a new row is added to B2B_Parameter table. Also a new database job is added. Each time the "BAM Polling Interval" is changed (and saved) a new job and a new row is added to the B2B_Parameter table.
This causes several jobs to run at different times and also the B2B_Parameter table returns multiple hits which causes the jobs to break.
The result is that no logging to the BAM queue is made.

The work around for this is to manually remove all but one of the B2B_Parameter rows and all but one of the jobs. 

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.