Reference Architecture: Consolidating Oracle Databases with Secure Resource Partitions in a Serviceguard Cluster Whitepaper

2. (Optional) If your processor supports Hyper-Threading and you want to enable it for the SRP,

modify the PRM record for the SRP in the /etc/prmconf file and run prmconfig –i:

# grep ^MKTPRD /etc/prmconf

MKTPRD:PSET:::1::LCPU=ON

NOTE:

Hyper-Threading is only available with PSETs and must be enabled in the

kernel. (See lcpu_attr(5) for details.)

Step 2: Preparing the system

Task 1: Creating the Oracle user

Using the useradd command, create the user that the database instance uses. Set the user’s primary

group to the group specified in the SRP login group when creating the SRP in step 2. This setting

enables the user to log in to the SRP.

# useradd -u 200 -g mkt_dba -d /var/hpsrp/MKTPRD/home/ora_mkt -m ora_mkt

# passwd ora_mkt

Changing password for ora_mkt

New password:

Re-enter new password:

Passwd successfully changed

# id ora_mkt

uid=200(ora_mkt) gid=200(mkt_dba)

For Serviceguard integration, the Oracle user must exist on all cluster nodes on which the

package runs and must have the same uid and gid numbers. Use the cmexec command to

execute the same useradd and password commands on all remote nodes. You might

need to log in to the remote system to change the newly create users password.

Note: If you are using a central repository such as LDAP or NIS to store users and groups,

you might not need to use this command.

# cmexec atcuxvm8 useradd -u 200 -g mkt_dba -d

/var/hpsrp/MKTPRD/home/ora_mkt ora_mkt

# ssh atcuxvm8

Password: