HP-UX HB v13.00 Ch-19 - PRM

HP-UX Handbook – Rev 13.00 Page 11 (of 31)

Chapter 19 Process Resource Manager (PRM)

October 29, 2013

ora_pmon_orm7q (server process)

ora_reco_orm7q (server process)

ora_smon_orm7q (server process)

oracleorm7q (shadow process)

...

NOTE: A shadow process is created for each user connecting to the database instance.

To put these two instances into different PRM groups you need to specify alternate names

using wildcards:

ora*orm* includes all processes (server & shadow) of the instance ORA_ORM

ora*bflt includes all processes (server & shadow) of the instance ORA_BFL

NOTE: Pattern matching rules

Pattern matching follows the rules for Basic Regular Expressions and, with PRM C.03.02

and later, Extended Regular Expressions, as outlined in the regexp(5) manpage. Because

pattern matching is intended to match a collection of alternate names to a fully qualified

executable, PRM was engineered to ensure that other applications and processes

matching the pattern were not inadvertently put in the wrong PRM group. PRM does this

by comparing file system inode numbers. For a process matching the alternate name

pattern to be placed in the configured PRM group, it must share the file system inode

number of the parent process.

The Oracle database administrator does not have to worry about inode numbers because

all processes launched from the same executable (for example, Oracle database instances)

share the same file system inode number.

NOTE: Managing listener processes

Although listener processes can be associated with a particular database instance, they are

actually started as part of the networking processes that run with Oracle. In ps output,

they appear as fully qualified executables:

oracle 1769 1 0 09:35:02 ? 0:00 /oracle/app/oracle/product/9.0.0/bin/tnslsnr LISTENER_Sales

oracle 1779 1 0 09:35:23 ? 0:00 /oracle/app/oracle/product/9.0.0/bin/tnslsnr LISTENER_Mktg

oracle 1774 1 0 09:35:12 ? 0:00 /oracle/app/oracle/product/9.0.0/bin/tnslsnr LISTENER_Support

The three listeners have exactly the same executable name, but with different parameters.

Starting with PRM C.03.02, PRM supports Extended Regular Expressions in alternate names.

This support enables you to create application records for listener processes. To put the listener

processes in the same PRM groups as their database instances, use the following application

records:

/u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr::::Sales,’tnslsnr.*Sales’