This is the second post of my little project of building my own RAC on my Windows7-desktop (64-bits, 8GB RAM), using 3 VM’s (VM-workstation , 7.1.3 build-324285) : * 2 VM’s for two RAC-nodes, based on OEL 5.5, 18.104.22.168 for infra, and database. * 1 VM as my own SAN, based on Openfiler 2.3 (free), for ASM.
While building my own RAC on two VM's, using a third VM with Openfiler on it as my SAN, I had to dowload, install, configure and load ASMLIB. Loading didn't seem to go smoothly at my own project. First I analyzed what I did, steps I took
I was building my own Oracle RAC 11g cluster (22.214.171.124) with Openfiler as my shared storage. Two VM's as my rac-cluster, one VM with Openfiler as my own SAN. Followed the instructions of the article of Jeffrey Hunter how to build a RAC on OEL and iSCSI, however this article is not based on VM. My Openfiler-VM was ready, given access to my both nodes on iSCSI-level, and now I want my rac1-node to discover the iSCSI-drives on my Openfiler.
Installed an Apache on Suse Linux 10. Configured httpd.conf including a rewrite rule in a virtual host. No configuration errors, but it did not work at all! After a while I discovered that the mod-rewrite module had been installed, but not enabled with this version of Apache (2.2.x).
Simple question: is Oracle Application Server 10.1.2.0.2 with Forms and Reports certified on Suse Linux 10. The customer is forced to move to Suse 10, and is not quite happy to upgrade to 10.1.2.3, for that could have numerous consequences for Forms, Designer, Java etc.
What to do about the ever growing files on Oracle application server as: - default-web-access.log - server.log and more.. These files are not logrotated (OAS
Installed and configured application server 10.1.2.0.2 on VM-ware with guest-OS Suse Linux 9. All worked fine, until a (hard) reboot by system admin. OID can’t connect to the default port 13060.
Error in $ORACLE_HOME/ldap/log/oidldapd01.log :
“Bind Failed On Communication Endpoint” and “Dispatcher Process unable to bind to port”
Because it was a rough […]
Grid Control is calling >> “Difference between OMS system time and Agent system time is 121 mins and has exceeded the critical threshold 120 mins”
The system time runs too fast on a (Suse) Linux-based (kernel 2.6) virtual machine, while the ntp has been configured. There are a lot of documents […]
On my Grid Control management-server (Suse Linux, OMS version 10.2.0.4) a very large number of <defunct> processes arose what eventually caused the OMS not to respond anymore.
Looked like this:
oracle 16932 15961 0 Mar03 ? 00:00:00 <defunct>
oracle 16987 15961 0 Mar03 ? 00:00:00 <defunct>