Andreas' Adventures

I just learned the following, which I wanted to share with you. One reason for using the 10.1.3.3 HTTP Server rather than the companion cd - Apache 2.0 - version is that no generic patchsets are ever issued for the Apache 2.0 version. It means that the MOD_OC4J component which comes with the 2.0 version always stays the same and neve r receives any bug fixes. You can also more easily configure the base 10.1.3 HTTP Server as part of an OracleAS 10.1.3 cluster topology. I had the idea that a stand alone OHS in the web tier (e.g. in the DMZ) would be a better setup as there are less points to attack, especially as there is a direct exposion to the Internet. I'll try to switch to the AS 10.1.3.x version instead of the stand alone OHS to see if this solves my problem. However I do not understand why Oracle keep different patch regimes with their software when they should share the same code base?

Recently I was busy with the mod_oc4j clustering of two standalone OHS machines. As Oracle has integrated ONS into OC4J in 10.1.3.x you have to provide your own ons.conf file (just copy one from a 10.1.2.0.2 environment). But what happend to me was strange. I added a new node (machine_C.mydomain.local) while I removed another one (machine_A.mydomain.local). However getting the opmnctl status @farm still showed the machine_A in the list. Some investigation delivered the following: In the directory $ORACLE_HOME\opmn\logs\states two entries do exist: .opmndat p12345678 When you shutdown the OPMN the p* file will disappear. However the .opmndat file will remain there. Remove it, it will be rebuild with the next opmnctl startall. Now my machine_A.mydomain.local was gone and the machine_C showed up. cu Andreas