Steps for canceling the deadlock check code and canceling the deadlock session in the EBS background --- experience

Steps for canceling the deadlock check code and canceling the deadlock session in the EBS backend --- Experience 1. General process for handling request congestion: 1. Execute cc_post_hang. SQL in PL/SQL (to Tao ); [SQL] ----------------------------------------- -- lock -- cc_post_hang. SQL select t. INST_ID, gs. SID, gs. status, gs. MACHINE, gs. ACTION, gs. MODULE, gs. PROGRAM, gs. p3TEXT, gs. EVENT, t. TYPE, ID1, ID2, LMODE, REQUEST, CTIME, BLOCK, gs. LOGON_TIME, gs. SQL _EXEC_START from gv $ lock t, gv $ session gs where t. SID = gs. SID and t. INST_ID = g S. INST_ID and (ID1, ID2, t. TYPE) in (select ID1, ID2, TYPE from gv $ lock where request> 0) and lmode <> 0; 2. view the MODULE column. The value is AP *, for example, if APXINWKB is used as the invoice platform, it can be killed. If GLPPOSS is used, it cannot be killed. Check that the PROGRAMM column value is frmweb... kill, GLPPOSS... it cannot be killed. 3. Check the STATUS column. If the value is INACTIVE, it is not an active process and can be killed. actice should not be killed. 4. Check the value of INST_ID n and the value of SID m. log on to the PRODn server using PL/SQL to find the process whose SID value is m in Tools> Session, right-click> select kill. Think about the status before kill. 5. Repeat steps 1 to 4 until the system process is congested to a normal state.