My Oracle Support Banner

EOD APPEARS TO BE STUCK IN SEAUTDLY BATCH (Doc ID 3023176.1)

Last updated on MAY 20, 2024

Applies to:

Oracle Banking Payments - Version 14.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

 Actual Behavior

EOD appears to be stuck in 'SEAUTDLY' batch and in sceduler job, the error "maximum open cursors exceeded" appears.


Expected Behavior

EOD should not stuck in 'SEAUTDLY' batch  


Steps

1. Run EOD for SEAUTDLY batch where RFR is configured.


Business Impact

EOD is stuck and system is not able to proceed further. SO user kills the session and rerun EOD again.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


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