After i have upgrade the database from 9.0.1.4 to 9.2.0.8, which is used for E-Business Suite 11.5.10, I choose to install the HTTP Server, actually it’s not required.
Problem comes…..
“iostat -xnp 5 100″ indicates that average service time for disk is 400MS, what is the cause? software raid? bug? hardware fault?
After one week, I have noticed that http process is running as the database owner, when i check the error log, the pizzle is solved.
[Wed Jul 11 15:29:33 2007] [notice] child pid 23876 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:33 2007] [notice] child pid 23879 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:35 2007] [notice] child pid 23880 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:36 2007] [notice] child pid 23883 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:36 2007] [notice] child pid 23882 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:37 2007] [notice] child pid 23885 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:37 2007] [notice] child pid 23886 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:37 2007] [notice] child pid 23887 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:37 2007] [notice] child pid 23884 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
[Wed Jul 11 15:29:40 2007] [notice] child pid 23889 exit signal Segmentation Fault (11), possible coredump in /11i/app/oracle/product/9.2.0/Apache/Apache
Every 2 seconds, coredump is generated by apachectl process. After stop the Apache JServer, problem solved.
2 things can be learned here:
a) Every issue gets reason/cause.
b) If the feature is not going to used in any case, do not install it.
I have searched this message in metalink also, a few bugs/mis-configuration caused that.
