test

Sun N1 Service Provisioning System User's Guide for Oracle Database Plug-In 3.0

ProcedureHow to Install Oracle Single-Instance Software for Oracle Database 10g

Before You Begin

You might need to perform the following tasks before you provision the Oracle Database 10g software.

Steps

  1. In the Common Tasks section of the N1 SPS browser interface, select Oracle Database 10g.

  2. On the Oracle Database 10g Common Tasks page, click Install.

  3. On the Plans Details page, click Run.

  4. Choose variables to use for the Oracle support scripts.

    Note –

    The first time you install the Oracle 10g Database Plug-In you must create a variables set other than default.

    • To use an existing variables set, select a name from the drop-down menu in the OraSpt component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the OraSpt component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set in the Set Name field.

      3. In the field for installPath, provide the full path to the location into which you want the support scripts installed.

        For example, /var/tmp/Ora_Spt.

        Note –

        The value for the installPath variable is treated as a relative path to the default Remote Agent directory, unless you specify an absolute path, such as /opt. For example, for a Solaris Remote Agent, if you set the installPath variable to opt and deploy the file to an Agent with a default home directory of /opt/SUNWn1sps/agent, the file is deployed to /opt/SUNWn1sps/agent/opt/.

      4. In the field for installerHome, provide the full path to the location of the Oracle software files.

        For example, /mnt/Ora10gR1.

        This path can point to a CD or to some other location in which you have placed the appropriate files. For Oracle 10g, the installerHome variable points to the top directory of the software CD, which is the parent directory above the Disk1 directory.

      5. For single-instance support files, verify that the racInstall field is set to FALSE.

      6. Save the variables set.

      7. Select the variables set that you just saved from the drop-down menu in the OraSpt component row of the Plan Parameters table.

  5. Choose variables to use for the single-instance software.

    • To use an existing variables set, select a name from the drop-down menu in the SingleInst component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the SingleInst component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. In the field for installPath, provide the full path to the location where you want to place the Oracle silent response file.

        For example, /var/tmp/Oracle10g.

        Note –

        The value for the installPath variable is treated as a relative path to the default Remote Agent directory, unless you specify an absolute path, such as /opt. For example, for a Solaris Remote Agent, if you set the installPath variable to opt and deploy the file to an Agent with a default home directory of /opt/SUNWn1sps/agent, the file is deployed to /opt/SUNWn1sps/agent/opt/.

      4. If a component already exists on this host for which the default value for ORACLE_HOME_NAME is used, define a value for the variable ORACLE_HOME_NAME.

        Note –

        Two components installed in the same physical host cannot have the same ORACLE_HOME_NAME.

      5. In the field for installerHome, provide the full path to the location of the Oracle software files.

        For example, /mnt/Ora10gR1.

        This path can point to a CD or to some other location in which you have placed the appropriate files. The installerHome variable points to the top directory of the software, which is the parent directory above the Disk1 directory.

      6. In the field for ORACLE_BASE, provide the path to the root directory into which you want the Oracle software to be installed.

        For example, /opt/app/oracle.

      7. To run the Oracle listener on this host, set the value for crListener to TRUE.

        Note –

        You should run only one Oracle listener per physical host.

      8. Verify that the softGroup and dbaGroup variables are correct.

        1. On the target host, type the following command: id -a oracle.

        2. Note the group names that were created for the oracle user.

        3. If the group names are different from the default names in the softGroup or dbaGroup fields, change those values as appropriate.

      9. Verify that the oraPrflFile is set correctly.

        • If you are installing the Oracle 10g database on a Solaris system, set the oraPrflFile variable to profile.

        • If you are installing the Oracle 10g database on a Linux system, set the oraPrflFile variable to bash_profile.

        Note –

        For the oraPrflFile variable, the environment file must be either a Bourne shell, Korn shell, or bash profile. C shell is not supported.

      10. Verify that the TOPLEVEL_COMPONENT variable exactly matches the version of Oracle to install.

        For example, if you intend to install 10.1.0.3.0, you must change the value of the TOPLEVEL_COMPONENT variable from its default of 10.1.0.2.0 to 10.1.0.3.0.

      11. Change other variables as appropriate.

      12. Save the variables set.

      13. Select the variables set that you just saved from the drop-down menu in the SingleInst component row of the Plan Parameters table.

  6. To select the target host, click Select from List next to the Target Host field on the Plans Details Run page.

    Note –

    Although the plug-in enables you to install this component into a host set, host sets are more likely to make sense for a RAC install rather than a single-instance install.

  7. If necessary, modify the values for the Limit Overall Running Time of Plan and Limit Running Time of Native Calls fields.

    By default, the timeout value for plans is set to 30 minutes. In some instances, such as when executing a plan on older hardware, the amount of time that is needed for a plan to complete exceeds 30 minutes. To increase the plan timeout value, increase the values of Limit Overall Running Time of Plan and Limit Running Time of Native Calls fields.

  8. To install the software, click Run Plan (includes preflight).