APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application to which the concurrent program executable &EXECUTABLE belongs.

APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM

Error:
=====
APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application to which the concurrent program executable &EXECUTABLE belongs.

Shut down the concurrent managers. Set the basepath environment variable for the application. Restart the concurrent managers. (VARIABLE=)

Routine AFPEOT cannot construct the name of an executable file for your concurrent request 5194371.

Check that the file name components are correct and valid on your system. Check that the environment for the person who started the concurrent manager

Scenario:
=======
There is a Custom Top registered and that top is not set in the ENV while starting the conc.

Request Name:  Project Balance Head Exp

Query to Check whether the Env is set for the Particular request: 

===============================================
select variable name, value from fnd_env_context e, fnd_concurrent_processes p ,fnd_concurrent_requests r where p.concurrent_process_id =p.concurrent_process_id and p.concurrent_process_id = r.controlling_manager and e.variable_name like '%CUSTOM_TOP%' and r.request_id = &request_id;

Solution:
=======

 Ø  Make the new custom environment file in $APPL_TOP.

    i.e. $APPL_TOP/customTEST_erptestappldb.env

   Doing below entry in above make custom environment file in $APPL_TOP

   export XXCUSTOM_TOP=/testappl/apps/apps_st/appl/XXCUSTOM/12.0.0

 Ø  Add the respective Top in env file.

   $APPL_TOP/admin/adovars.env

   so that while running autoconfig it won’t remove every time.

   export XXCUSTOM_TOP=/testappl/apps/apps_st/appl/XXCUSTOM/12.0.0

 

 

Warning: VKTM detected a time drift in 11gR2

ALERT LOG:

Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.

 

Cause:

This problem is due to the Bug 11837095 -"TIME DRIFT DETECTED" APPEARS INTERMITTENTLY IN ALERT LOG"

 

Solution:

Time drift" error is a " message which can be ignored, to remove the "Warning: VKTM detected set event 10795 or Apply patch 11837095

 

SQL> alter system set event="10795 trace name context forever, level 2" scope=spfile;

 

Then bounce the DB instances to implement the event/change.