APPLICATION ENGINE TROUBLESHOOTING GUIDE

APPLICATION ENGINE TROUBLESHOOTING GUIDE

Scenario1: If AE get into no success

Solution:In order to remove the process instance of the abended process from the temp tables.

 Delete the process instance from following tables:

            1. PS_AE_RUN_CONTROL /* Often has 0 rows */

2. PS_PRCSRUNCONTROL /* But if Application Engine then 1st table above */

Also rebuild temp table by running following SQL's

DELETE from PS_AERUNCONTROL

DELETE from PS_AETEMPTBLMGR

Run the following SQL statements:

SELECT * FROM PS_AELOCKMGR

If the table is not empty, run the following SQL statements:

DELETE FROM PS_AELOCKMGR

INSERT INTO PS_AELOCKMGR (AE_LOCK) VALUES ('N')

Then in App Designer, create a project containing all the temp tables to be re-built (be sure to select Temporary Table as Type).

Insert temp tables with the following prefixes:

SCH_

TL_

WRK_

There should be quite a few tables (over 200) to be re-built. Make sure that the settings specify to recreate table if it already exists. This step generally takes care of the Temp Table Allocation.

  

Scenario 2:  If AE process terminated with below error

All Processing Suspended: Restart OPRID=S390765, RUNID=31-01-03112240, PI=2988

Solution:A pending process was found for the current Operator id, Run Control id, and Application Engine Program. This process either is running now or has abended. Please restart the pending process if it has abended, and allow it to run to completion, before submitting a new process request."

You need to clean up the dead rows in sysadm.ps_aeruncontrol.

________________________________________________________________

Delete from ps_aeruncontrol where oprid = 'UserID';

Commit;

Scenario:  If AE process posted with Warning

WARNING: NO DEDICATED INSTANCES AVAILABLE FOR %s - USING BASE TABLE.) (108,-1)

Solution:

 Note:   This message is Not an error, it is only a Warning - but one that really should not be seen. The main cause of this warning message is more than 1 or 2 of this particular AE program is running concurrently or AE temp tables is locked out or any previous running application engine get into “no success” state.

  

Ø   To fix this warning issue the “instance count” of application engine "FS_BP" increase to 5 using application designer and cancel the process which is in no success status to release the locked temp table.

**FS_BP any temp table which getting locked out.

Ø  When there are rows in PS_AETEMPTBLMGR - there should be a corresponding row in PS_AERUNCONTROL as well.   If manual deletion is done from PS_AETEMPTBLMGR - the same PROCESS_INSTANCE row should be removed from PS_AERUNCONTROL as well.

By: Prasanth Bhaskaran (People Soft Application DBA)