|
Contents
|
Installing and Configuring the Oracle 10g R2 RAC Plug-In
This page explains how to install and configure the Oracle 10g R2 RAC plug-in on a Sun Cluster configuration. This page contains the following information:
Top
Acquiring the Oracle 10g R2 RAC Plug-In
The Oracle 10g R2 RAC solution is packaged as a plug-in to the N1 Service Provisioning System (N1 SPS) software. Plug-ins are packaged in Java™ Archive (JAR) files. The com.sun.oracle10g_RAC_1.0.jar file for the Oracle 10g R2 RAC solution is available from the Sun Download Center .
Top
Adding the Oracle 10g R2 RAC Plug-In to the N1 SPS Environment
To make a given plug-in known to the N1 SPS product, you need to import the plug-in. To import a plug-in, follow these steps as explained in detail in Chapter 5, Plug-In Administration, in Sun N1 Service Provisioning System 5.2 System Administration Guide.
- In the Administrative section of the N1 SPS browser interface main window, click Plug-ins.
- In the Action column of the Plug-ins page, click Import.
- Browse to the location where you downloaded the JAR file.
- Click the Continue to Import button.
When the import completes successfully, a plug-in details page appears that shows you the objects that the plug-in provides.
You can also import a plug-in archive file from the command line. Use the following command to import the plug-in:
% cr-cli -cmd plg.p.add -path com.sun.oracle10g_RAC_1.0.jar -u username -p password
Top
Customizing the Solution for Your Environment
This section contains the following information:
To use the plug-in, you must perform the following customization steps:
- Configure the cluster node ssh root passphrase.
- Ensure that the N1 SPS remote agent can run as root.
- Configure an N1 SPS session variable called debug_shell_code.
- (Optional) Increase the amount of output the N1 SPS master server captures.
How to Set Cluster Node ssh root Passphrase Requirements
The plug-in uses Secure Shell (SSH) and Secure Copy (SCP), as root, to run remote commands and copy files, respectively. Before you use the plug-in, you must configure every cluster node to use the same passphrase for SSH.
 | Note
The SSH passphrase must be set properly to ensure the correct operation of the plug-in. |
- On a cluster node, generate the SSH keys.
When prompted, enter and then confirm the passphrase that you want to use.
% ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (//.ssh/id_rsa):
Created directory '//.ssh'.
Enter passphrase (empty for no passphrase): passphrase
Enter same passphrase again: passphrase
Your identification has been saved in //.ssh/id_rsa.
Your public key has been saved in //.ssh/id_rsa.pub.
The key fingerprint is:
6f:53:8b:80:ef:2a:82:b5:0e:67:bb:3b:ff:8a:5d:47 root@nodename
- Verify that the public key was generated successfully.
% cat /.ssh/id_rsa.pub
ssh-rsa publickey= root@nodename
- Use an editor to add the contents of the /.ssh/id_rsa.pub file from each cluster node to a file called /.ssh/authorized_keys.
- Copy the /.ssh/authorized_keys file to each cluster node so that all nodes have an authorized_keys file with the same contents.
- Log in as root to another cluster node over an SSH connection.
% ssh root@nodename2
Enter passphrase for key '/.ssh/id_rsa': passphrase
Last login: Tue Nov 7 05:19:42 2006 from nodename1
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
- Repeat Step 5 for each additional cluster node.
Be sure to perform this task on the node that you logged in to for Step 1.
- After every node is set up, check that you can log into each node by using the passphrase configured.
The first attempt to log in by SSH connection to a new node will prompt you to confirm the authenticity of the remote machine. Confirm this and then supply the passphrase. You will not receive this prompt on subsequent connections.
Top
Remote Agent Requirements
When you install the provisioning software remote agent (RA), be sure to set the RA to run as root. Most of the Oracle installation runs as user oracle; however, some scripts that are generated during the installation process need to run as root.
How to Create the debug_shell_code Session Variable on the Master Server
Perform this task after you install the plug-in.
- Use the N1 SPS browser user interface to create a session variable called debug_shell_code.
For more information about how to set session variables, see the Sun N1 Service Provisioning System 5.2 Plan and Component Developer’s Guide.
- Set the debug_shell_code variable value to false.
Troubleshooting
If a plan fails while using the plug-in, set the debug_shell_code session variable to true, and run the plan again. This variable value enables the ksh -x flag, which permits you to see the code that has been executed and the values that are assigned to each shell script variable.
Top
Increasing Output Capture on the Master Server
Before you deploy Oracle RAC and its components from the Master Server, you can optionally modify the Master Server config.properties file to enable you to capture more output. By default, the Master Server only stores the last 10 Kbytes of output from the commands that the issued components used.
How to Customize the config.properties File
- On the Master Server, use a text editor to access the config.properties file.
By default, the configuration file for the Master Server resides in the following directory.
/opt/SUNWn1sps/N1_Grid_Service_Provisioning_System_6.0/server/config
- Add the following line to the end of the config.properties file.
pe.maxOutputSnapshotBytes=65536
The pe.maxOutputSnapshotBytes variable enables the plug-in to save up to 64 Kbytes of command output when a component is installed, uninstalled, or has a control step run.
- Restart the master server.
|
Sign up or Log in to add a comment or watch this page.