Friday, September 28, 2018

How to Clear Apache Cache (Oracle EBS General)


How to Clear Apache Cache (Oracle EBS General)

Steps to Clear Apache Cache


Step - 1 Navigate to Functional Administrator responsibility.

Description: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQTOH-iWu4IrDwu5KaEb8e_6emRAX6QaEIAaOQnjlzsjWpxSMyS-di6WWAKsXKbCUFrUGMiPDn3AhaJcgGEYcp2eq1gIhqO43O_lDa2a1k7lLg5dpJYiuHWmlC14Qge3WUbwM0ePljKCGo/s1600/FA.JPG





Step - 2 Go to: Home > Core Services > Caching Framework


Description: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgFvLQxK8_KNPdbEK24y-YtOce4n0HJ8oUkXgfH1g4hjL5Rq5ldfE4L0Dgvc77Bhr9isE0qJxdf1v1Hz1QsC_yHZWTMwZm87YVzHVELtT3Bm0RX0nqIY1JYRJLbFNUiqjYzvGzQKygSMYeV/s640/CS.JPG



Step - 3 Go to: Global Configuration > Clear All Cache.

Description: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiol7tPv5e_1a-zd8FHL6QQN9fT6_bwHosR11trjCSmKdC2AVOhtTdjloHFTvA03uMxjryKfT7BLtI9hTI6NkU7krXnrOMtoFoO3zUEqcNgddWhss7S39ECI0lcb4391zl5CL26yTVpJ1RL/s640/GC.JPG



Click Apply. Apache Cache is now clear.

 

How to clear Cache in EBS 11i and R12 environments and in similar environments?


* How to clear Cache in Apache/iAS, Cabo, browser, Java, Jinitiator, portal, webadi?


Apache / iAS
For 11i and earlier versions:
- shutdown iAS server
- go to $OA_HTML (for 11.5.9) or $COMMON_TOP (for 11.5.10.x) directory
- backup the directory _pages and delete its contents by running for instance:

rm -rf $COMMON_TOP/_pages/*

- for modplsql caches remove contents of $IAS_ORACLE_HOME/Apache/modplsql/cache directory
- restart iAS server


To clear middle tier cache in release 12:

- go to "Functional Administrator" responsibility
- select Core Services => Caching Framework => Global Configuration => Clear cache
(please review
Note 759038.1 for details).
In case you have login issue after accidentally cleared the _pages instead of using the method above for r12
please review
Note 433386.1 to recompile jsp files.

Cabo
Images and style sheets can be corrupted or out of sync in the cabo caches,
you may need to clear the related directories after backup:

$OA_HTML/cabo/images/cache
$OA_HTML/cabo/styles/cache


Web Browser


for Internet Explorer:
- go to menu Tools => Internet Options,
- select 'General' tab,
- click on button 'Delete Files' in 'Temporary Internet files' area
or
- click on button 'Delete...' then in 'Delete Browsing History' pop-up window click on 'Delete Files...'
- close all IE windows and restart new browser session.

for Mozilla Firefox:
- go to menu Tools
- select 'Clear Private Data...' or 'Clear Recent History...' then check 'Cache'
or
- go to menu Edit or Tools
- select Preferences or Options.
- expand the 'Advance' options and choose 'Cache' or Privacy
- click the button called 'Clear Cache'.

for Safari:
- go to Safari menu
- select Empty Cache => Click 'Empty' in the dialogue box
for Netscape:
- go to menu Edit => Preferences,
- choose 'Cache' in 'Advanced' category,
- click on buttons 'Clear Memory Cache' and 'Clear Disk Cache'.
- close all Netscape windows and restart new browser session.

Jinitiator

Two possibilities depending of the Jinitiator version:

for 1.1.8.x versions:
- delete all files in directory:

C:\Program Files\Oracle\Jinitiator \jcache\

for 1.3.1.x versions:
- go to Start => Parameters => Control Panel
- double-click on "Jinitiator " icon
- in the new pop-up window, click on "Cache" tab
- click on "Clear Jar Cache " button. On prompt, click Yes.

(you can also delete directly all files under directory:
C:\Documents and Settings\\Oracle Jar Cache)


Java
Java/JRE plug-in (Windows)
- go to Start => Parameters => Control Panel
- double-click on 'Java' icon
- in the new pop-up window, click on 'General' tab
- click on 'Setting...' button in 'Temporary Internet files' area then click on 'Delete Files...' button
(you can select Applets, Applications or other files)

JVM

- go to responsibility "Functional Administrator"
- click on "Core Services" tab then the "Caching Framework" sub-tab
- click on "Global Configuration" link then click on "Clear all cache" button to clear all of the Java Cache's


Portal
- go to the url: http://:/pls/admin_/gateway.htm or cache.htm
- click on "Cache Settings" option and note the "Cache Directory"
- go to this directory and delete all the cache files in the directory and sub directories

See also modplsql caches in Apache/iAS section above.


WebADI / BNE cache
For instance when enabling BNE log
- go to url: http://:/oa_servlets/oracle.apps.bne.framework.BneAdminServlet
- click on the "clear-cache" link
- at the bottom of the page you should see 'Cache Cleared'





Ref:
How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite? [ID 742107.1]

 

How to bounce Apache, clear HTML cache and have updated Java code class active in R12 Guidance or Training for Oracle Apps, OBIEE 11g, .NET and Java


 

To clear HTML cache and bounce Apache at R12 level, firstly go to the scripts directory of R12:

cd $INST_TOP/admin/scripts

 

To clear HTML cache :

The _pages directory under $COMMON_TOP should not be cleared for E-Biz R12, which we used to do in 11i applications. For clearing middle tier cache in R12,

 

Navigate to : -

Functional Administrator responsibility > Core Services > Caching Framework > Global Configuration > Clear cache

 

Instead of clearing the _pages in R12 creates blank login page issue, as in R12 the jsp files does not get compiled automatically.

cd $INST_TOP/admin/scripts

./adapcctl.sh stop

./adapcctl.sh start

 

At R12 level bouncing apache command is different of the one to bounce oacore oc4j engine and others.

An example of situation is: how to make a modification to a JSP and have that modification recognized by the OC4J - JSP engine.

 

In Oracle Apps 11i  the apache start and stop command, also bounce the JVM running on JSERV and clear caches by doings as below:-

 

To clear the jsp & modplsql caches run this command: -

rm -rf $OA_HTML/_pages/*

rm -rf $COMMON_TOP/_pages/*

rm -rf $IAS_ORACLE_HOME/Apache/modplsql/cache/*

 

But in Oracle EBS R12 the command to stop and start apache only takes action on Apache web server and not on the OC4J container that executes the JVM.

 

To bounce the OC4J container there is an specific script:

$INST_TOP/admin/scripts/

 

Therefore when making a modification to a JAVA class in R12 for the web application, in order to have that change recognized, it is needed to bounce

 

OC4J using adoacorectl.sh script.

cd $INST_TOP/admin/scripts

./ adoacorectl.sh stop

./ adoacorectl.sh start

Bouncing oacore OC4J engine may also be needed if you make modifications to system properties.

Example for JTT based applications:  jtt system properties.

 

 


Clear Cache bounce in R12

There are two ways to clear cache in R12.
1. Functional level (individual product/all product cache)
Functional Administrator -> Core Services -> Caching Framework -> Global Configuration -> "Go to specific cache or Clear All Cache"


2. Server level
In R12 apache bounce (which is actually opmn services here) takes a little more time then 11i, and we too have to take care of few things.
Basic steps for a clear cache bounce is as below:-
Set you application environment and go to $ADMIN_SCRIPTS_HOME

  1. ./adopmnctl.sh stopall
  2. wait for command to complete
  3. ./adopmnctl.sh status -l
  4. cd $COMMON_TOP/_pages
  5. ls -l|wc -l (note it down)
  6. rm -rf * (to remove all files)
    Note:- For step 4 to 6, better to take backup of _pages by renaming it, and create a new directory as _pages at the same place.
  7. ls -l|wc -l (it should be 0 now)
  8. cd $FND_TOP/patch/115/bin
  9. which perl (should come from $IAS_ORACLE_HOME/perl/bin)
  10. ojspCompile.pl --compile --flush -p 10 (to compile all JSPs,-p is for parallel and value (i.e. 10 here) can be varied accourding to your server)
  11. wait for successful completion
  12. cd $COMMON_TOP/_pages
  13. ls -l| wc -l (check whether count is same or more than before (pre-remove) - sometimes a little difference may be there)
  14. Go to $ADMIN_SCRIPTS_HOME again
  15. ./adopmnctl.sh startall
  16. wait for proper services startup
  17. ./adopmnctl.sh status -l
  18. check front-end and JSPs and FORMs should open up fine

 

You can avoid the step of regenrating the jsps like 11i but for that we need to make below changes in R12 context file (XML file):

parameter s_jsp_main_mode - you will find it justrun by default.

change it to - recompile

and run autoconfig to make the changes take place.

This will generate the jsps at run time saving bounce time, but obviously affect the performance.

cmclean.sql : Cleaning the Concurrent Manager tables


To cleanup running and pending requests we use cmclean.sql, If we stop concurrent managers using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.

CMCLEAN will update below tables:
1) FND_CONCURRENT_QUEUES
2) FND_CONCURRENT_PROCESSES
3) FND_CONCURRENT_REQUESTS
4) FND_CONFLICTS_DOMAIN
5) FND_CONCURRENT_CONFLICT_SETS


GET CMCLEAN SCRIPT FROM ORACLE NOTEID:
Concurrent Processing – cmclean.sql – Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]

—- SCRIPT —-
****************


REM
REM FILENAME
REM cmclean.sql
REM DESCRIPTION
REM Clean out the concurrent manager tables
REM NOTES
REM Usage: sqlplus @cmclean
REM
REM
REM $Id: cmclean.sql,v 1.4 2001/04/07 15:55:07 pferguso Exp $
REM
REM
REM +======================================================================+
set verify off;
set head off;
set timing off
set pagesize 1000
column manager format a20 heading ‘Manager short name’
column pid heading ‘Process id’
column pscode format a12 heading ‘Status code’
column ccode format a12 heading ‘Control code’
column request heading ‘Request ID’
column pcode format a6 heading ‘Phase’
column scode format a6 heading ‘Status’
WHENEVER SQLERROR EXIT ROLLBACK;
DOCUMENT
WARNING : Do not run this script without explicit instructions
from Oracle Support
*** Make sure that the managers are shut down ***
*** before running this script ***
*** If the concurrent managers are NOT shut down, ***
*** exit this script now !! ***
#
accept answer prompt ‘If you wish to continue type the word ”dual”: ‘
set feed off
select null from &answer;
set feed on
REM Update process status codes to TERMINATED
prompt
prompt ————————————————————————
prompt — Updating invalid process status codes in FND_CONCURRENT_PROCESSES
set feedback off
set head on
break on manager
SELECT concurrent_queue_name manager,
concurrent_process_id pid,
process_status_code pscode
FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp
WHERE process_status_code not in (‘K’, ‘S’)
AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND fcq.application_id = fcp.queue_application_id;
set head off
set feedback on
UPDATE fnd_concurrent_processes
SET process_status_code = ‘K’
WHERE process_status_code not in (‘K’, ‘S’);
REM Set all managers to 0 processes
prompt
prompt ————————————————————————
prompt — Updating running processes in FND_CONCURRENT_QUEUES
prompt — Setting running_processes = 0 and max_processes = 0 for all managers
UPDATE fnd_concurrent_queues
SET running_processes = 0, max_processes = 0;
REM Reset control codes
prompt
prompt ————————————————————————
prompt — Updating invalid control_codes in FND_CONCURRENT_QUEUES
set feedback off
set head on
SELECT concurrent_queue_name manager,
control_code ccode
FROM fnd_concurrent_queues
WHERE control_code not in (‘E’, ‘R’, ‘X’)
AND control_code IS NOT NULL;
set feedback on
set head off
UPDATE fnd_concurrent_queues
SET control_code = NULL
WHERE control_code not in (‘E’, ‘R’, ‘X’)
AND control_code IS NOT NULL;
REM Also null out target_node for all managers
UPDATE fnd_concurrent_queues
SET target_node = null;
REM Set all ‘Terminating’ requests to Completed/Error
REM Also set Running requests to completed, since the managers are down
prompt
prompt ————————————————————————
prompt — Updating any Running or Terminating requests to Completed/Error canceled by CMCLEAN
set feedback off
set head on
SELECT request_id request,
phase_code pcode,
status_code scode
FROM fnd_concurrent_requests
WHERE status_code = ‘T’ OR phase_code = ‘R’
ORDER BY request_id;
set feedback on
set head off
UPDATE fnd_concurrent_requests
SET phase_code = ‘C’, status_code = ‘E’
WHERE status_code =’T’ OR phase_code = ‘R’;
REM Set all Runalone flags to ‘N’
REM This has to be done differently for Release 10
prompt
prompt ————————————————————————
prompt — Updating any Runalone flags to ‘N’
prompt
set serveroutput on
set feedback off
declare
c pls_integer := dbms_sql.open_cursor;
upd_rows pls_integer;
vers varchar2(50);
tbl varchar2(50);
col varchar2(50);
statement varchar2(255);
begin
select substr(release_name, 1, 2)
into vers
from fnd_product_groups;
if vers >= 11 then
tbl := ‘fnd_conflicts_domain’;
col := ‘runalone_flag’;
else
tbl := ‘fnd_concurrent_conflict_sets’;
col := ‘run_alone_flag’;
end if;
statement := ‘update ‘ || tbl || ‘ set ‘ || col || ‘=”N” where ‘ || col || ‘ = ”Y”’;
dbms_sql.parse(c, statement, dbms_sql.native);
upd_rows := dbms_sql.execute(c);
dbms_sql.close_cursor(c);
dbms_output.put_line(‘Updated ‘ || upd_rows || ‘ rows of ‘ || col || ‘ in ‘ || tbl || ‘ to ”N”’);
end;
/
prompt
prompt ————————————————————————
prompt Updates complete.
prompt Type commit now to commit these updates, or rollback to cancel.
prompt ————————————————————————
prompt
set feedback on
REM <= Last REM statment —————————————————–
Disclaimer
EXCEPT WHERE EXPRESSLY PROVIDED OTHERWISE, THE INFORMATION, SOFTWARE,
PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS. ORACLE EXPRESSLY DISCLAIMS
ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NON-INFRINGEMENT. ORACLE MAKES NO WARRANTY THAT: (A) THE RESULTS
THAT MAY BE OBTAINED FROM THE USE OF THE SOFTWARE WILL BE ACCURATE OR
RELIABLE; OR (B) THE INFORMATION, OR OTHER MATERIAL OBTAINED WILL MEET YOUR
EXPECTATIONS. ANY CONTENT, MATERIALS, INFORMATION OR SOFTWARE DOWNLOADED OR
OTHERWISE OBTAINED IS DONE AT YOUR OWN DISCRETION AND RISK. ORACLE SHALL HAVE
NO RESPONSIBILITY FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR LOSS OF DATA THAT
RESULTS FROM THE DOWNLOAD OF ANY CONTENT, MATERIALS, INFORMATION OR SOFTWARE.
ORACLE RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES TO THE SOFTWARE AT ANY
TIME WITHOUT NOTICE.
Limitation of Liability
IN NO EVENT SHALL ORACLE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE,
DATA OR USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN
CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE OF, THE SOFTWARE.
SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY.
ACCORDINGLY, SOME OF THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.


 

1 comment:

  1. Core And Application Dba Blog: How To Clear Apache Cache (Oracle Ebs General) >>>>> Download Now

    >>>>> Download Full

    Core And Application Dba Blog: How To Clear Apache Cache (Oracle Ebs General) >>>>> Download LINK

    >>>>> Download Now

    Core And Application Dba Blog: How To Clear Apache Cache (Oracle Ebs General) >>>>> Download Full

    >>>>> Download LINK

    ReplyDelete

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files. I got the issue below wh...