database down event is not caught in database exception

database down event is not caught in database exception

  

We have a scheduled task to connect to oracle database and grab data from a view which happens in the email preparation, 

We got error ORA-12516: TNS:listener could not find available handler with matching protocol stack

as per DBA, this is due to database down.

but in our logic, we have exception handling to send alert email, but in this case, no email was sent, does this means this error is not part of the database exception event?

Solution

Hi Linguo,

In OutSystems emails are send a separate email thread. It's a separate thread because the emails have a retry mechanism and are queued. This is useful when for instance the SMTP server is too busy or down.

As long as the Oracle database is an external database that is not running OutSystems, you should get an email when you move the exception flow to the preparation of the email itself.

When the Oracle database is the same as the OutSystems datbase, you won't get any mail when the database is unavailable, because OutSystems can't run without the database.

Kind regards,

Remco Dekkinga

Solution

Remco Dekkinga wrote:

Hi Linguo,

In OutSystems emails are send a separate email thread. It's a separate thread because the emails have a retry mechanism and are queued. This is useful when for instance the SMTP server is too busy or down.

As long as the Oracle database is an external database that is not running OutSystems, you should get an email when you move the exception flow to the preparation of the email itself.

When the Oracle database is the same as the OutSystems datbase, you won't get any mail when the database is unavailable, because OutSystems can't run without the database.

Kind regards,

Remco Dekkinga

Thanks Remco, the oracle database is a separate database, i will try to add exception handling in the preparation