ORACLE DBA: November 2022

When I logged onto a server to clone an EBS instance from production, it gave a message

/app/PROD/inst/apps/PROD_xxxxxxxxxxx/ora/10.1.3/Apache/Apache/bin/apachectl start: execing httpd

httpd: bad group name applprod

-bash-5.1$ adopmnctl.sh startall

You are running adopmnctl.sh version 120.6.12010000.5

Starting Apache...

EXIT CODE is 204. Please check the log file for more details.

Starting OACORE oc4j...

OACORE oc4j started successfully.

Starting FORMS oc4j...

FORMS oc4j started successfully.

Starting OAFM oc4j...

OAFM oc4j started successfully.

The only error is in $LOG_HOME/ora/10.1.3/opmn/HTTP_Server~1.log :

apachectl startssl: execing httpd
httpd: bad group name applprod

Then I verified group inside

-bash-5.1$ grep -i group /app/PROD/inst/apps/xxxxxxxxxxxx/ora/10.1.3/Apache/Apache/conf/httpd.conf

# The configuration directives are grouped into three basic sections:

# If you wish httpd to run as a different user or group, you must run

# User/Group: The name (or #number) of the user/group to run httpd as.

# . On SCO (ODT 3) use "User nouser" and "Group nogroup".

# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)

# when the value of (unsigned)Group is above 60000;

# don't use Group nobody on these systems!

Group applprod

---> So changed group here to oinstall which fixed the issue

-bash-5.1$ adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.4

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: PROD_xxxxxxxxxx

---------------------------------+--------------------+---------+---------

ias-component | process-type | pid | status

---------------------------------+--------------------+---------+---------

OC4JGroup:default_group | OC4J:oafm | 13758 | Alive

OC4JGroup:default_group | OC4J:forms | 13713 | Alive

OC4JGroup:default_group | OC4J:oacore | 13608 | Alive

HTTP_Server | HTTP_Server | 22077 | Alive

ORACLE DBA