Monday, 19 November 2012

File system gets filled due to Report cache in Oracle apps R12




In Oracle Apps R12 the report server is started by the concurrent manager whenever there is a need to run a report and it is an in-process report server which is started as per the need.

During this process the oracle reports writes to a temporary cache directory. The path and cache size is defined in the rwbuilder.conf file.

For example:

<cache class="oracle.reports.cache.RWCache">
<property name="cacheSize" value="50"/>
<property name="cacheDir" value="full path for $INST_TOP/logs/ora/10.1.2/reports/cache"/>
<!--property name="maxCacheFileNumber" value="max number of cache files"/-->
<!--property name="ignoreParameters" value="parameter names to be ignored in constructing cache key, separated by comma ','"/-->
</cache>


This cache directory doesn’t have any control on its growth and purging, though its temporary in nature. The Purge Concurrent Request and/or Manager Data" (FNDCPPUR) program also doesn’t purge these files.

Hence as more oracle reports are run, more temporary files gets created and space gets filled up under:

 $INST_TOP/logs/ora/10.1.2/reports/cache.


Solution: 



  1. Manually delete the files under:
$INST_TOP/logs/ora/10.1.2/reports/cache



  1. Change the cache size parameter in rwbuilder.conf to zero:
<property name="cacheSize" value="50"/> to
<property name="cacheSize" value="0"/>





OACORE fails to start after increasing the JVM processes in Oracle R12




Issue: OACORE processes are not starting.


Recent changes: Increased the JVM processes in the context file.


Error:

adoacorectl.sh: exiting with status 206


Solution:

1)  Stop the middle tier processes:

adopmnctl.sh stop

2) Kill any runaway/zombie processes.

3) Remove the following jms lock files:

$ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/forms_default_group_1/jms.state.lock,

$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/jms.state.lock

$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/oafm_default_group_1jms.state.lock

4) Restart middle tier:
adopmnctl.sh start

Flow cycle of a web browser connection with Oracle Web server



Let’s consider Oracle Apps 11i/R12. 

 How does the web browser make connection with the http server?


 Below is the flow:

* An attempt is made to obtain an IP address using the IPname of the website/URL.

   * The Domain Name servers (DNS) provides this lookup (conversion of IP name to IP address).

   * Open an IP socket connection to that IP address.

   * Then the socket connection is used to write an HTTP data stream to the web server.
 
   * Receive an HTTP data stream back from the Web/HTTP server in response. This data stream contains status codes whose values are determined by the HTTP protocol.