My Oracle Support Banner

Email notifications are not sent due to "452 4.3.1 Insufficient system resources" error which is noticed in the Workflow Mailer log. Cannot Resend such Emails as the MAIL_STATUS is set to NULL. (Doc ID 3026292.1)

Last updated on MAY 31, 2024

Applies to:

Oracle Workflow - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Workflow Mailer

Email notifications are not sent due to "452 4.3.1 Insufficient system resources" error which is captured in the workflow mailer log.

 
The issue can be reproduced at will with the following steps:

  1. Send email notification using test mail or through workflow approvals.
  2. Mail server hits "Insufficient resources" error and the workflow mailer fails to send the notification, which is captured in the workflow mailer log.
  3. Mail_Status is set to NULL.

Example Scenario: Customer is using Exchange mail server to send notifications. Due to "Insufficient system resources" at the Exchange server, some of the notifications are not delivered.
These could be some important mails like Purchase Orders, if they are missed out the material would not be delivered.
In such cases when the notifications are not sent, the mail_status should be set to FAILED, but in customer's case mail_status is NULL.
And hence customer cannot run the "Resend Failed/Error Workflow Notifications" concurrent program to send out these notifications.

 

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
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.