Periodic Alerts Are Not Received And ALEPPE Errors APP-ALR-04102 & APP-ALR-04057 (Doc ID 1642058.1)

Last updated on JUNE 21, 2016

Applies to:

Oracle Alert - Version 12.0.3 to 12.2 [Release 12 to 12.2]
Information in this document applies to any platform.

Symptoms

When running Periodic Alerts, the concurrent program ALEPPE module: Periodic Alert Scheduler is completing in Error status with the following errors shown in the concurrent request log file:

APP-ALR-04102: Internal SQL error occurred.
APP-ALR-04057: Oracle Alert was unable to purge history in file &FILE in routine &ROUTINE on line &LINE. Check that all of the Oracle Alert history tables exist.


Checking the output file generated by the ALEPPE module: Periodic Alert Scheduler concurrent program it is showing the following Oracle Error:

CONCURRENT ALR ALEPPE 1 START="01-APR-14 00:00:00" REPEAT_INTERVAL="1" REPEAT_INTERVAL_UNIT="DAYS"
Submitted concurrent request ID 19847014
Purging history from ALR_ALERT_INPUTS
0 rows deleted
Purging history from ALR_ALERT_OUTPUTS
0 rows deleted
Purging history from ALR_ACTIONS
1 rows deleted
SQL error ORA-01841: (full) year must be between -4713 and +9999, and not be 0
occurred while performing the following: Selecting ID's to purge (STMT=SELECT A.APPLICATION_ID, SC.CHECK_ID FROM ALR_ALERT_CHECKS AC,ALR_ACTION_SET_CHECKS SC,ALR_ALERTS A WHERE A.APPLICATION_ID = AC.APPLICATION_ID AND A.APPLICATION_ID = SC.APPLICATION_ID AND A.ALERT_ID = AC.ALERT_ID AND A.ALERT_ID = SC.ALERT_ID AND AC.ALERT_CHECK_ID = SC.ALERT_CHECK_ID AND TO_DATE(:0,'YYYY/MM/DD HH24:MI:SS') - NVL(A.MAINTAIN_HISTORY_DAYS,0) > AC.LAST_UPDATE_DATE AND AC.HISTORY_PURGE_DATE IS NULL )



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms