Periodic Alert Completes With Warning: APP-ALR-04044: ALR_ACTION_SET_CHECKS_S (Doc ID 169441.1)

Last updated on AUGUST 21, 2016

Applies to:

Oracle Engineering - Version: 10.7 to 10.7.16.1 - Release: 10.7 to 10.7
Oracle Product Intelligence - Version: 11.5.9 to 11.5.10.2   [Release: 11.5 to 11.5]
Information in this document applies to any platform.

Symptoms

Periodic Alert completes with warning

APP-ALR-04044: Oracle Alert failed to retrieve the next value for the sequence ALR_ACTION_SET_CHECKS_S. Check that either the sequence exists or the proper grants and exist for this sequence.
APP-ALR-04102: Internal SQL error occurred.
APP-ALR-04070: Oracle Alert was unable to update the success flag in ALR_ALERT_CHECKS or ALR_ACTION_SET_CHECKS in file &FILE in routine & ROUTINE on line &LINE. Check that both tables exist.
ORACLE error 904 in AFPRSR
Cause: AFPRSR failed due to ORA-00904: invalid column name
The SQL statement being executed at the time of the error was: and was executed from the file .
APP-FND-01564: ORACLE error 942 in afpprq
Cause: afpprq failed due to ORA-00942: table or view does not exist.
The SQL statement being executed at the time of the error was: SELECT MEANING FROM FND_LOOKUPS WHERE LOOKUP_TYPE = 'CP_STATUS_CODE' AND LOOKUP_CODE = :code and was executed from the file &ERRFILE.
APP-FND-01564: ORACLE error 6550 in afpevtg
Cause: afpevtg failed due to ORA-06550: line 1, column 31
PLS-00201: identifier 'FND_EVENT.GET' must be declared
ORA-06550: line 1, column 26
PL/SQL: Statement ignored
The SQL statement being executed at the time of the error was: declare b boolean; begin b := fnd_event.get(:sid, :styp, TRUE, :estr,:r); if (b) then :eget := 1; else :eget := 0; end if; end; and was executed from the file &ERRFILE.

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