This is something very peculiar that we have noticed only a few days back.We had a performance issue and had to increase the number of oacore processes to 2 and the maxsize for memory to 1024M.
After we did this each time we restart the instance we had a special character '>' appended to the file server.xml located in /db01/oracle/VIS/inst/apps/VIS_server070/ora/10.1.3/j2ee/oacore/config/ which will prevent the oacore process from starting.
The oacore will exit with the following status
adoacorectl.sh: exiting with status 204
You will recieve the error message as shown below in file oacorestd.err under /db01/oracle/VIS/inst/apps/VIS_server070/logs/ora/10.1.3/opmn/oacore_default_group_1
10/01/27 17:25:52 Error initializing server: /db01/oracle/VIS/inst/apps/VIS_server070/ora/10.1.3/j2ee/oacore/config/server.xml, Fatal error at line 70 offset 1 in file:/db01/oracle/VIS/inst/apps/VIS_server070/ora/10.1.3/j2ee/oacore/config/server.xml: .
To fix this perform the following
1. Set server.xml file access right to read only mode.
2. Start OC4J container.
(or)
Apply the patch 6702510 for suitable version of your IAS.
No comments:
Post a Comment