Some issues that we might face during cluster installation:
Issue#1:
XML Parsing Error: no element found on esb console
Resolution#1:
The cause of the error was cluster_name collision for esb-dt and esb-rt.
vi $ORACLE_HOME/j2ee/oc4j_soa/applications/esb-rt/META-INF/orion-application.xml
vi $ORACLE_HOME/j2ee/oc4j_soa/application-deployments/esb-rt/orion-application.xml
Change “cluster_name” value to “ESBCluster” from "esb". Update your esb systems with this name on esb console i.e. update Cluster Name of each system with "ESBCluster".
Issue#2:
You see message “You have more than one instance of the Application Server Control application running in this cluster. This is not a recommended configuration and could lead to unexpected problems. Please stop the additional instances of Application Server Control or disable routing to these instances.” on the enterprise manager console.
Resolution#2:
Execute below command on all the non primary nodes.
opmnctl stopproc process-type=admin application=ascontrol
Issue#3:
When replacing the existing OPatch with a new patch then on running command opatch –version below error might come:
-bash: $ORACLE_HOME/OPatch/opatch: Permission denied
Resolution#3:
cd $ORACLE_HOME
chmod -R 755 OPatch
Issue#4:
java.net.SocketTimeoutException: Read timed out or java.net.SocketTimeoutException: connection reset when trying to initiate a bpel process on the bpel console.
Resolution#4:
Modify httpd.conf available at $ORACLE_HOME/Apache/Apache/conf on all the nodes.
Set KeepAlive as ‘Off’. Restart HTTP Server using command
opmnctl startproc process-type=HTTP_Server
I also recommend to cross check your load balancer setting. Sometime incorrect setting also causes this issue.
Issue#5:
An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found
Resolution#5:
Modified ant-orabpel.properties file available @ $ORACLE_HOME/bpel/utilities.
Cluster=true
oc4jinstancename = SOA_GROUP
local.oc4jinstancename = oc4j_soa
Please make sure there is no space after true,SOA_GROUP and oc4j_soa.
Issue#6:
During installation of Oracle Service Registry, the installation fails with “null
Installation failed. If accessible, see "/oracle/registry_10_1_3/log/install.log".
To correct installation parameters and resume installation click Recover.” error.
Resolution#6:
One cause of this error is incorrect java version.
[oracle@HOSTNAME ~]$ java -version
java version "1.4.2"
gij (GNU libgcj) version 4.1.2 20080704 (Red Hat 4.1.2-44)
update the JAVA_HOME to point to the soa suite java
export JAVA_HOME=$ORACLE_HOME/jdk
Issue#7:
During installation of DB, swap space requirements availability check the expected result ie swap memory is less than the actual result.
Resolution#7:
You can resolve this issue by creating a swap file. If installer is expecting 7832 the swap should have 7832*1024 = 8019968
1. Login as root
2. dd if=/dev/zero of=/swapfile bs=1024 count=8019968
8019968+0 records in
8019968+0 records out
8212447232 bytes (8.2 GB) copied, 82.5765 seconds, 99.5 MB/s
3. mkswap /swapfile
Setting up swapspace version 1, size = 8212443 kB
4. swapon /swapfile
5. Edit /etc/fstab
/swapfile swap swap defaults 0 0
6. Verify by cat /proc/swaps
7. Exit from root
No comments:
Post a Comment