Using HP PRM with Oracle Databases

12
Figure 3 shows the PRM user configuration with the Oracle user having access to both the FSS PRM
group Mktg and the pSet PRM groups Sales and Support.
Figure 3. PRM user configuration
If users are not logging in to HP-UX directly, records for each individual user are not required.
If users are logging in to HP-UX and accessing interactive applications, the users’ shells and
applications should execute in PRM groups other than those used by the Oracle server processes
(OTHERS in this example).
PRM’s application records enable you to separate the instance processes into individual PRM groups.
The Oracle database executable is the same in every case, but the alternate name specifies a pattern
to match based on the instance name, $ORACLE_SID. The application manager recognizes the
appropriate processes based on the supplied pattern and assigns them to the specified PRM groups.
So the application is /u01/app/oracle/product/10.2.0/db_1/bin/oracle.
To place processes in the Sales PRM group, use an alternate name of ora*Sales. Processes starting
with “ora” and ending with “Sales” are put in the Sales PRM group. This pattern includes Oracle
database server processes and shadow processes.
Similarly, use an alternate name of ora*Support to place processes in the Support group and an
alternate name of ora*Mktg to place processes in the Mktg group.
Create a record to place all other child processes associated with starting an Oracle database
instance in the PRM group OTHERS.
The application manager checks all running processes against the PRM configuration application
records, moves the processes pertaining to each Oracle database instance to the appropriate PRM
groups, and writes a record to the /var/adm/syslog/syslog.log file.