dbafusion

This problem comes when we try to access any OC4J instances other than HOME, the Application Server will deny the access and gives following error on the screen: Unable to make a connection to OC4J instance instance_name on Application Server application_server_name. A common cause for this failure is an authentication error. The administrator password for each OC4J instance in the Cluster must be the same as the administrator password for the OC4J instance on which Application Server Control is running. This means that all the OC4J instances in the application server should have same oc4jadmin password. Perform below steps to debug the above error :- Before changing the oc4jadmin password for HOME instance, change the oc4jadmin password for all other instances using the following steps: 1. Click on OC4J instance 2. Click on Administration tab 3. Edit sub-task Security Providers under Security task 4. Edit any application name under Application Level Security 5.

Overview of applying Oracle Application Server 10g R3 patchset 4 (10.1.3.4) on existing 10g R3 (10.1.3) Key Points for 10.1.3.4 Upgrade 1. Patch Number for OAS 10g R3 patchset 4 (10.1.3.4) is 7272722 2. 10g R3 patchset 4 (10.1.3.4.0 - 7272722) is cumulative and includes all fixes from 10.1.3.0, 10.1.3.1, 10.1.3.2 and 10.1.3.3 3. 10g R3 patchset 4 (10.1.3.4.0) is NOT complete software, you need to install in on top of one of existing software i.e. 10.1.3.n (10.1.3.0, 10.1.3.1, 10.1.3.2 or 10.1.3.3) 4)10g Rel 3 patchset 1 (10.1.3.1.0) is starting point for Oracle SOA Suite (BPEL, ESB…) and 10g Rel 3 patchset 2 (10.1.3.2.0) is starting point for WebCenter Suite (ContentDB, WebCenter Services). If you are using Oracle SOA Suite or Oracle Web Center then you need to do additonal steps before upgrade like – upgrade_10131_10134_oracle.sql (10.1.3.1) or – upgrade_10133_10134_oracle.sql (10.1.3.3) (For BPEL from ORABPEL schema) – upgrade_10133_10134_oracle.sql (For ESB from O

1) Set ORACLE_HOME,OPATCH/bin under PATH. 2) Shut down the application server by $opmnctl shutdown command 3) Extract the MLR6 on the server & move inside the directory. 4) Execute below command :- bash-3.2$ ./opatch apply /u01/data/8279781/ Oracle Interim Patch Installer version 1.0.0.0.58 Copyright (c) 2007 Oracle Corporation. All Rights Reserved.. We recommend you refer to the OPatch documentation under OPatch/docs for usage reference. We also recommend using the latest OPatch version. For the latest OPatch version and other support related issues, please refer to document 293369.1 which is viewable from metalink.oracle.com Oracle Home : /u01/app/OAS/10.1.3.1/OH Oracle Home Inventory : /u01/app/OAS/10.1.3.1/OH/inventory Central Inventory : /home/appsoad/oraInventory from : /var/opt/oracle/oraInst.loc OUI location : /u01/app/OAS/10.1.3.1/OH/oui OUI shared library : /u01/app/OAS/10.1.3.1/OH/oui/lib/hpunix/liboraInstaller.so Java locatio

I have collected below brief information about some of the performance metrices used in OC4J monitoring in SOA Suite . This is a brief idea. Have a look :- CPU (%) Description: The percentage of the CPU currently being used by the OC4J instance, or--on the JVM Metrics page--the selected Java Virtual Machine (JVM). User Action: Use this metric to determine how much of the CPU is in use by the OC4J instance or JVM. If you encounter consistent high readings for this metric, try to isolate the problem by monitoring individual applications and services that are running on the OC4J instance. If no problems are found, consider obtaining additional hardware resources or load balancing solutions. Memory (MB) Description: Indicates how much of your total physical memory is in use by the current OC4J instance, or--on the JVM Metrics page--by the selected Java Virtual Machine (JVM). User Action: Use this metric to monitor memory use by the OC4J instance or JVM. Compare this with h

You may get an out of memory exception if the Oracle WSM is configured so that its runtime memory requirements exceed the JVM default configuration. One known situation where this can occur is if you patch Oracle WSM 10.1.3 to 10.1.3.1. To avoid this error, you need to increase the size of the Java heap. To change the values of the Java heap 1. Log in to Oracle Enterprise Manager 10g Application Server Control. 2. In the Cluster Topology page, locate the Members section, and click home. 3. Click Administration. 4. Find Server Properties in the Task Name list, and click the Go to Task icon. 5. Edit the values for Maximum heap size (1024 Mb) and Initial heap size (512 Mb). 6. Add a row for the -XX:MaxPermSize (256 Mb) and -XX:PermSize (128 Mb) parameters and provide a value. 7. Click Apply. 8. Restart the server. Note: The values in parentheses are provided as an example only. These values were derived assuming that all components in the Oracle Application Server

It is important to ensure that only authorized consumers can call the web services that are exposed. The below solution applies only to security internal web services. All the internal web services will be secured using OWSM Server Agents. This document consists of steps to be taken on order to deploy server agents. To configure a server agent component in Oracle Web Services Manager Point your browser to the Web Services Manager Control Console and log in using your user name and password. The Web Services Manager Control Console is accessed with a URL of the form: http:// :port_number/ccore For example: httphttp://dceapocxxxx:8888/ccore/index.jsp 2. Click Add New Component. 3. On the Add New Component page, define: ■Component name ■Component type ■Container type Click Register. Define Policy Set for Server Agent To define the policy set for the server agent: 1. At the Web Services Manager Control Console, click Policy Management, then click Mana