Monday, January 24, 2011

Interview Questions: Oracle Alerts Part 3


21.   Can you use view as an event alert table?
Ans:  You cannot use a view as the event table for your alert.

22.   What are the four types of actions in alert can be specified?
Ans:  There are four types of actions you can create
a)      Message actions
b)      Concurrent program actions
c)       Operating script actions
d)      SQL statement script actions

23.   Are there any limitations in Response processing when getting inputs back from user?
Ans:  Yes, User must respond answer in a specific format and content.

24.   How does Alert work?
Ans:  Oracle Alert checks your database for the exceptions you want to know about using several concurrent programs
a)      Periodic Alert Scheduler
b)      Check Periodic Alert
c)       Check Event Alert
d)      Response Processor
The Periodic Alert Scheduler (ALEPPE) is a concurrent program that automatically checks your scheduled periodic alerts.

25.   How Check Event Alert Works?
Ans:  Once you define an event alert to monitor a table for any insert or update to the table will trigger the event alert. When an insert or update to an event table occurs, Oracle Alert submits To the concurrent manager, a request to run a concurrent program called Check Event Alert (ALECTC). The concurrent manager runs this request according to its priority in the concurrent queue. When the request is run, Check Event Alert executes the alert Select statement. The Response Processor (ALPPIM) is the Oracle Alert concurrent program that processes responses to an alert message.

26.   What is the purpose of: DATE_LAST_CHECKED ?
Ans:  An Oracle Alert implicit input that contains the date and time that an alert was last checked Oracle Alert automatically provides the value for: DATE_LAST_CHECKED. You must use DATE_LAST_CHECKED to create self–referencing alerts.

27.   What is meant by Action History?
Ans:  A record of the actual actions performed for each action set check that includes the value substituted for each output.

28.   Can you perform actions if a recipient doesn’t respond?
Ans:  Yes, Using No Response field to specify the actions you want Oracle Alert to perform if the recipient does not respond within the number of Response Days specified in the Action Details window of the Alerts form known as the response processor.

29.   Can one create event alerts on custom tables, triggered by custom applications?
Ans:  Yes, Oracle Alerts can be integrated with your custom application and detailed information is available in the below link

30.    How often should the Alert tables be purged?
Ans:  There is no recommended purge frequency.  It all depends on how many alerts have been enabled and their frequency.

2 Responses to “Interview Questions: Oracle Alerts Part 3”

Anonymous said...
March 1, 2011 at 7:50 AM

dear sir ,

i would like to ask about how i can make event alert when changes effect in specific field in specific table ?


Anonymous said...
November 18, 2011 at 9:46 AM

I don't think the event alert itself has the provision to trigger it for a specific field, but the sql in the alert can handle it by providing and required condition in the wheres clause.

For instance SO lines changed status from awaiting shipping to close. When SO line does change its status the alert would fire and in the sql code provide condition flow_status = 'CLOSED' so it will only raise an exception when condition is met.
Hope this helps.

Post a Comment


The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.