DBMS_SCHEDULER email notification not sent
(Doc ID 1645770.1)
Last updated on MAY 30, 2024
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
When creating a job and adding an Email notification to all its events, the job succeeds (or fails) but the Email is not sent, no error is reported during configuration of the job or during its run:
The following checks have been done:
1) Verified ping to the Database Server:
ping <NAME_OR_IP_ADDRESS>
Successful ping should retrun results similar to the following:
Reply from 10.82.150.186: bytes=32 time<1ms TTL=127
Reply from 10.82.150.186: bytes=32 time<1ms TTL=127
Reply from 10.82.150.186: bytes=32 time<1ms TTL=127
Reply from 10.82.150.186: bytes=32 time<1ms TTL=127
Ping statistics for 10.82.150.186:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
2) Verified that telnet to the Database Server on port 25 opens a blank window.
telnet <NAME_OR_IP_ADDRESS> 25
Successful telnet should retrun results similar to the following:
220 san.ci.la.ca.us ESMTP MDaemon 7.2.5; Fri, 09 May 2014 09:28:44 -0700
3) Checked if the SMTP server require any sort of credential or encryption to communicate with
4) Confirmed that email can be sent using using utl_mail.send
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 |