APP-ALR-04044 Against Sequence ALR_ACTION_SET_CHECKS_S

纵横四海

Periodic Alert completes with warning APP-ALR-04044 Against Sequence ALR_ACTION_SET_CHECKS_S in Applications 11i


fact: Oracle Alert
fact: Oracle Application Object Library
symptom: Periodic Alert completes with warning
symptom: 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 synonyms exist for this sequence.
symptom: APP-ALR-04102: Internal SQL error occurred.
symptom: 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.
symptom: ORACLE error 904 in AFPRSR
symptom: Cause:  AFPRSR failed due to ORA-00904: invalid column name
symptom: 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.
symptom: The SQL statement being executed at the time of the error was:  
and was
executed from the file .
symptom: APP-FND-01564: ORACLE error 942 in afpprq
symptom: Cause:  afpprq failed due to ORA-00942: table or view does not
exist.
symptom: 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.
symptom: APP-FND-01564: ORACLE error 6550 in afpevtg
symptom: Cause:  afpevtg failed due to ORA-06550: line 1, column 31
symptom: PLS-00201: identifier 'FND_EVENT.GET' must be  declared
symptom: ORA-06550: line 1, column 26
symptom: PL/SQL: Statement ignored
symptom: Verified that products used for the Alerts are fully installed and
registered.
cause: This issue is documented in Bug 1841831, which was closed as not a
bug. This could be a user input error.



fix:

Solution:
----------

There should be only one type of oracle id listed on the installations and it
should be APPS. When other oracle ids are listed the, presence of these rows
may trigger the errors above. The solution is to delete the rows which do not
have oracle id = APPS.
.
Steps:
-------

1. Navigate to Alert Manager Responsibility

2. Navigate to Alert - Define and query up the alert which errors.

3. Click on the Alert Details button

4. Click on the Installations tab

5. You should see a single row (if not using multi org) with Oracle id = APPS.
If you are using multi org the you may have multiple rows with operating unit
filled in but all rows will have Oracle id = APPS.

Oracle Id = APPS
Operating Unit = blank if select multi_org_flag from fnd_product_groups
returns 'N'
Enabled = Checked

6. If you have rows where the Oracle id not equal to APPS, delete those rows
by clicking on the rows -> Edit -> Delete.  Click on the Save Icon.

7. Rerun the alert. The errors should no longer occur.