Broadcaster Record Not Processing Automatically On Failure After V23 Migration (Doc ID 3020069.1)

Last updated on MAY 01, 2024

Applies to:

Symptoms

ACTUAL BEHAVIOR
-----------------------
Broadcaster record not processing automatically on failure after v23 migration. Customer recently moved from v19 to v23 for XOCS in stage environment. Upon v23 migration, broadcaster was provided with junk credentials and so all broadcaster records were error out.

As per the discussion with migration team it is expected that on updating the correct credentials to the broadcaster should pick up and retry the failed records and process the same.

Below is part of explanation given for this functionality from Migration team :
"As for the behavior you have seen is also expected. As soon as the registers start sending new transactions broadcaster records will be created. By design, the broadcaster system will keep retrying the same record (1 per broadcaster) until they are successful. The rest of the records are queued up behind that. So once customer updates the credential of this broadcaster, XOCS should start sending the records to the destination. The delay between retries will increase with every failure. That means depending on when customer re-enters the credential, the first retry wait can be longer. But once the first record is published successfully the operation should restore to normal."

Customer although are not observing this mentioned behavior and records are still lying in error state. Please check on this and help us understand the issue and why failed record is still present and whether it is even attempting to broadcaster once failed, by retry mechanism as explained above.

EXPECTED BEHAVIOR
-------------------------
Broadcaster record should process automatically after v23 migration.

Steps to Re-create :
-----------------------
1. Broadcasters has incorrect credentials after migration but broadcaster is enabled.
2. All transactions from Xstore starts to replicate from Xstore to XOC and create all broadcaster records as well.
3. when service is executed at Scheduled interval in application, broadcaster records are failed.
4. Customer updates/re-enter credentials for the Broadcaster.
5. Failed broadcaster records are not processed automatically which as per should process as there is a retry mechanism available for this as per our conversation with Migration Team.
6. Records are not processed.

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.