If you use Oracle Grid Control to monitor your PeopleSoft system, here is a simple tip that will help you identify batch processes.
Oracle provides two columns on the session information (v$session) to hold context information. They provide a PL/SQL package DBMS_APPLICATION_INFO, which has procedures to read and update these values. The idea is that application developers will instrument their programs and will update these values. Oracle’s Applications (that it has developed itself), such as E-Business Suite do this. PeopleSoft was rather slow to make use of this. They do set the module and action, but not to very useful values.
However, you can create a trigger on the Process Scheduler request table that will update these values when a process starts.
(Updated 19.4.2009) I have created a PL/SQL package psftapi that contains a number of procedure that I have used from triggers and other PL/SQL programs. It contains a function that sets the ACTION for the session with the process instance and the description of the status.
This procedure can be called from a trigger thus:
What is the benefit? The MODULE and ACTION show up in Grid Control. So now you can immediately identify the name and Process Instance of those expensive processes.
Unfortunately, it is not possible to do anything similar for sessions created by the Application Server. So all you know is what session belongs to what kind of server process. The Client Information is set at the top of each service, so you know the PeopleSoft Operator ID, but that is all.
It would be nice if perhaps the Component name and PeopleCode context was written to MODULE and ACTION. But it isn’t.
Updated 9.9.11: PeopleTools 8.50 does exactly this, there is another posting on this subject.