Swift Upload to be configured as DBMS Scheduler instead of Job (Doc ID 2639698.1)

Last updated on JUNE 21, 2021

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
Swift_upload is currently running as DBMS Job
Users are facing performance issues as the Swift_ upload job is running every one hour and user has to wait for the incoming message to be processed and created as contracts .


EXPECTED BEHAVIOR
-----------------------
Bank wants to configure SWIFT_Upload as a Scheduler with frequency of 5 minutes, so that messages inserted into incoming browser will be automatically processed

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Submit SWIFT Upload Job
2. Monitor the performance of messages getting processed to create associated contracts

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users have to wait for long time for Incoming swift messages to be 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.