This document discusses several topics related to Oracle Applications administration:
1. It provides a solution for resolving Oracle Forms crashes in Internet Explorer due to JVM incompatibility by copying the correct jvm.dll file.
2. It describes the steps to clear the cache for a specific component in Oracle Applications Release 12, which involves querying and clearing the cache using the Caching Framework.
3. It explains Oracle's naming convention for custom schemas, which requires them to begin with "XX" to prevent them from being cleared during upgrades.
This document discusses several topics related to Oracle Applications administration:
1. It provides a solution for resolving Oracle Forms crashes in Internet Explorer due to JVM incompatibility by copying the correct jvm.dll file.
2. It describes the steps to clear the cache for a specific component in Oracle Applications Release 12, which involves querying and clearing the cache using the Caching Framework.
3. It explains Oracle's naming convention for custom schemas, which requires them to begin with "XX" to prevent them from being cleared during upgrades.
This document discusses several topics related to Oracle Applications administration:
1. It provides a solution for resolving Oracle Forms crashes in Internet Explorer due to JVM incompatibility by copying the correct jvm.dll file.
2. It describes the steps to clear the cache for a specific component in Oracle Applications Release 12, which involves querying and clearing the cache using the Caching Framework.
3. It explains Oracle's naming convention for custom schemas, which requires them to begin with "XX" to prevent them from being cleared during upgrades.
This document discusses several topics related to Oracle Applications administration:
1. It provides a solution for resolving Oracle Forms crashes in Internet Explorer due to JVM incompatibility by copying the correct jvm.dll file.
2. It describes the steps to clear the cache for a specific component in Oracle Applications Release 12, which involves querying and clearing the cache using the Caching Framework.
3. It explains Oracle's naming convention for custom schemas, which requires them to begin with "XX" to prevent them from being cleared during upgrades.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online from Scribd
Download as pdf or txt
You are on page 1/ 4
Author A.Kishore/Sachin http://appsdba.
info
Oracle Applications DBA Practical Notes
Oracle 11i forms crash in IE Unable to open forms due to IE Error in 11i or Forms crashes with IE Error or Jinitiator Issue.This is due to jvm incompatibility used by other Application or tools.
Solution : o Go to program files java ==> jre1.6.0_07 (Or recent jre we can download from java.sun.com). Path : C:\Program Files\Java\jre1.6.0_07\bin\client o Copy the jvm.dll file o Go to C:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot o Take the backup of current jvm.dll file o Copy the jvm.dll file, which you have copied from the above jre directory. o Close all the browsers and restart Now can access the forms now.
How to clear cache for a specific component in R12?
We know clearing cache in Oracle Apps is to delete the $COMMON_TOP/_pages directory. In 11i, after deleting we dont have to recompile the jsps whereas but in R12 we have to recompile the pages since s_jsp_main_mode is set to just run by default, which is in turn updated in orion-web.xml. We need to follow the below steps to clear cache for specific component in Oracle Apps R12. o o o o o Login as sysadmin Select Functional Administrator responsibility Go to Core Services -> Caching Framework -> Tuning Query the application (for example iStore) or by Name or code. Select the component and clear the cache.
Please Note: For some specific configuration changes, we need to bounce Apache also. If we need to clear Global Cache in R12, We will follow the below steps: o Go to Functional Administrator Responsibility o Go to Core Services -> Caching Framework o Go to Global configuration and clear all the cache from there. (Only If we want to clear all the cache)
Author A.Kishore/Sachin http://appsdba.info
Custom Schemas Naming Convention in Oracle Applications.
Have we ever questioned ourselves, why custom schema names always start with XX<some_name>? Before getting into the detail lets check what happens if the custom schema name doesnt start with XX. If you dont have a custom schema name starting with XX, be assured that this schema will be no longer available in our instance when we perform an UPGRADE. During upgrade Oracle apps will clear all unregistered schemas, which doesnt start with XX. Oracle had assured its customers that it would not touch any schemas that start with XX. This is the main reason why we find custom schema names starting with XX.
How to identify to which mid-tier you are/will be connected to on a multi -node R12 environment? If we have implemented multi-node Oracle Apps R12 setup with two node RAC. How will we identify to which server we are connected. Normally, when we have multi-node environment, we will access the login page using a virtual URL. Step 1. Open Internet Explorer or Firefox Step 2. Type in the url eg: https://ebsr12.com Step 3. This should bring the login page (AppsLogin) Step 4. Click on About this page bottom left Step 5. Click on Page Context (3rd tab) Here we will get the following details: o o o o Database Hostname DBC file being accessed JDBC Port SID being used to connect to the database The DBC file being accessed provides, the full path of the dbc file (ie., $FND_SECURE or $INST_TOP/appl/fnd/12.0.0/.dbc). The expanded path will have the hostname. That is the mid-tier we are connected to.
Author A.Kishore/Sachin http://appsdba.info
How to copy / migrate printer definitions to a new instance using FNDLOAD.
Lets Imagine below situation:
Target had been cloned from source. New printers have been configured on source after the clone. Now we need the same printer configurations on target instance similar to source.
We can achieve our goal in three ways as stated below: 1. Perform the steps manually on target instance 2. Clone target from source 3. Use FNDLOAD (Generic Loader Utility) We will use FNDLOAD option to copy printer configuration to target instance.For this we need to follow the below steps. o Download the printer definitions from source FNDLOAD apps/apps_pwd 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER o Connect to target instance o Get the source printer definition file (source_printer_def.ldt) from source (ftp, scp or any method that is suitable) o Create a backup of the target system printer information as shown below. Connect to sqlplus as apps user and issue the below: create table fnd_printer_bk as (select * from fnd_printer); select printer_name from fnd_printer_bk; o Now upload the printer definitions into the target system. FNDLOAD apps/apps_pwd 0 Y UPLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER SQL> select printer_name from fnd_printer; Above sql statement will list the new printers that are uploaded.
Author A.Kishore/Sachin http://appsdba.info
Please Note : To download a specific printer definition, we need to follow the below syntax FNDLOAD apps/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER PRINTER_NAME=[printer name] This is one of the functionality of FNDLOAD. Refer to this metalink note : 274667.1 for other features of FNDLOAD.
