This chapter explains how you can mass-deploy Oracle Grid Infrastructure for standalone servers in an unattended, repeatable, and reliable manner. In particular, this chapter covers the following:
Provisioning Oracle Grid Infrastructure Using an Existing Installation
Provisioning Oracle Grid Infrastructure Using Certified Gold Image
Provisioning Oracle Grid Infrastructure Using Installation Binaries
Note:
Before you run the Deployment Procedure as outlined in this chapter to provision an Oracle Grid Infrastructure for a standalone server, Oracle strongly recommends you to check the prerequisites to ensure that you meet all the necessary requirements for provisioning an Oracle Grid Infrastructure. To do so, simulate the Deployment Procedure as described in Chapter 4, "Simulating Database Provisioning Deployment Procedures to Check Prerequisites", and resolve all operational conflicts and issues beforehand.This section helps you get started with this chapter by providing an overview of the steps involved in provisioning Oracle Grid Infrastructure. Consider this section to be a documentation map to understand the sequence of actions you must perform to successfully provision Oracle Grid Infrastructure. Click the reference links provided against the steps to reach the relevant sections that provide more information.
Table 6-1 Getting Started with Provisioning Oracle Grid Infrastructure
| Step | Description | Reference Links |
|---|---|---|
|
Step 1 |
Understanding the Deployment Procedure Understand the Deployment Procedure that is offered by Enterprise Manager Grid Control for provisioning Oracle Grid Infrastructure. Know how the Deployment Procedure functions, what use cases it covers, and so on. |
To learn about the Deployment Procedure, see Deployment Procedure. |
|
Step 2 |
Knowing About the Supported Releases Know what releases of Oracle Grid Infrastructure can be provisioned by the Deployment Procedure. |
To learn about the releases supported by the Deployment Procedure, see Supported Releases. |
|
Step 3 |
Selecting the Use Case This chapter covers a few use cases for provisioning Oracle Grid Infrastructure. Select the use case that best matches your requirement. |
|
|
Step 4 |
Meeting the Prerequisites Before you run any Deployment Procedure, you must meet the prerequisites, such as setting up of the provisioning environment, applying mandatory patches, setting up of Oracle Software Library. |
|
|
Step 5 |
Running the Deployment Procedure Run the Deployment Procedure to successfully provision Oracle Grid Infrastructure. |
|
Enterprise Manager Grid Control offers the following Deployment Procedure for provisioning Oracle Grid Infrastructure on standalone servers:
Oracle Grid Infrastructure Provisioning for Standalone Servers
Using this Deployment Procedure, you can perform the following operations:
Deploy Oracle Grid Infrastructure software using certified gold images, live reference installations, and installation media
Optionally configure Oracle Automatic Storage Management (Oracle ASM)
Use staging location for fast file transfer
Therefore, if you have a standalone server and want to use high availability features, then use this Deployment Procedure to provision Oracle Grid Infrastructure on the server before provisioing a standalone database using the Deployment Procedure as described in Chapter 5, "Provisioning Oracle Database".
The high available feature monitored in Enterprise Manager Grid Control appears as Oracle High Availability Service.
Using this Deployment Procedure, you can provision the following release of Oracle Grid Infrastructure across standalone servers:
Oracle Grid Infrastructure 11g Release 2 (11.2)
This section describes how you can provision Oracle Grid Infrastructure using an existing installation that is running on a host monitored by Enterprise Manager Grid Control.
This option is best suited when you have a running instance of Oracle Grid Infrastructure that is stable and has all the latest patches applied, and you want to make identical copies of that software on multiple standalone servers.
In particular, this section covers the following:
Before running the Deployment Procedure, meet the following prerequisites:
Ensure that you meet the prerequisites described in the following sections:
Compare the configuration of the source and target hosts and ensure that they have the same configuration. If the configurations are different, then contact your system administrator and fix the inconsistencies before running the Deployment Procedure.
To compare the configuration of the hosts, in Grid Control, click Targets and then Hosts. On the Hosts page, click the name of the source host to access its Home page, and then click the Configuration tab. On the Configuration page, click Compare Configuration and select the target host.
Meet the memory and disk space requirements for Oracle Grid Infrastructure installation on the target hosts. For information about the memory and disk space requirements for Oracle Grid Infrastructure installation, refer to the Oracle Database Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
Ensure that the following groups exist. If you do not belong to these groups, then the Deployment Procedure automatically adds you to the groups.
For information about creating these operating system groups, refer to the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
ASM Database Administrator (OSDBA) group
ASM Instance Operator (OSOPER) group
ASM Instance Administrator (OSASM) group
Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.
If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.
For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.
For information about customization, see Chapter 31, "Customizing Steps to Run as Another User".
Ensure that you use an operating system user that has write permission on the staging areas used for placing software binaries of Oracle Grid Infrastructure. Also ensure that the staging area is accessible from the Oracle Management Service (OMS) and the target host.
Deployment Procedures allow you to use staging locations for quick file-transfer of binaries and prevent high traffic over the network. While providing a staging location, ensure that the operating system user you use has write permission on those staging locations. For information about staging area, see Staging Area.
Ensure that the operating system groups you specify for OSDBA, OSOPER, and OSASM already exist on the hosts you select for provisioning. The operating system users of these groups automatically get the respective privileges.
To provision Oracle Grid Infrastructure using an existing installation, follow these steps:
In Grid Control, click Deployments.
On the Deployment page, from the Deployment Procedure Manager section, click Database Provisioning Procedures.
On the Deployment Procedure Manager page, from the procedures table, select Oracle Grid Infrastructure Provisioning for Standalone Servers and click Schedule Deployment.
On the Select Source and Destination page, in the Select Source section, select Existing Installation. Then, click the torch icon for Source Host and select the host that has the existing installation. When you select the source, in the Source Host Details subsection, Enterprise Manager Grid Control automatically populates the fields, such as Oracle home, Working Directory, and Files to exclude.
Note:
Enterprise Manager Grid Control creates a ZIP file of the Oracle home in the working directory of the source host, and then copies this ZIP file to the working directory of the destination host.In the Source Host Credentials subsection, specify the operating system credentials of the selected host where Oracle Grid Infrastructure is installed. You can choose to use the preferred credentials stored in the Management Repository or override them with a new set of credentials.
In the Specify Destination Host Settings section, do the following:
Click Add to search and select the destination hosts on which you want to provision Oracle Grid Infrastructure. Once you add a host, you will see default values for Oracle Base, Oracle Home, and other fields. You can either retain the default values or specify another custom value.
Note:
If you decide to specify an Oracle home location of your choice, then Oracle recommends you to maintain the Oracle home outside the installing user's home, and NOT inside. For example, if your home is/home/john, then you must not provision Oracle Grid Infrastructure in /home/john/gi11g.If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts. If you want to use different paths for each host, then select Different for each host.
Note:
If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.From the Credentials list, select one of the following to provide the operating system credentials of the destination host:
Preferred, if you want to use the preferred credentials stored in the Management Repository. For this, you must have already registered the preferred credentials.
Override Preferred Credentials, if you want to override the preferred credentials and use another set of credentials for this operation. If this environment is secure and has locked accounts, then make sure that the credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation. Also ensure that the Deployment Procedure has been customized to support locked environments.
For information about customizing Deployment Procedures for locked accounts, see Chapter 31, "Customizing Deployment Procedures".
Optionally, click Customize Host Settings if you want to provide additional, custom information about the destionation host and customize its settings.
For example, you may want to use an alternative host name instead of using the first host name identified on the system. Similarly, you may want to specify a custom name for the Oracle home. Also, if the Oracle Management Agent home credentials are different from the Oracle home credentials, then you may want to specify the agent home credentials. Under such circumstances, you can use this option to customize the host settings.
In the Advanced Installation Parameters subsection, specify any additional Oracle Universal Installer (OUI) parameters you want to run while provisioning Oracle Grid Infrastructure. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.
If you want to stage the software binaries to a shared location, then select Stage to Shared Location and specify a shared, NFS-mounted location that is accessible by Oracle Management Service and all the destination hosts. The software binaries will be staged only once to the staging location. Once they are staged, they will be copied to the working directory of each of the destination hosts.
Note:
The staged location can also act as a source for future deployments, that is, once the software binaries are available in the staged location, you can select Staging Location as the source when you run the Deployment Procedure next time.In the Group Details section, specify the ASM Database Administrator (OSDBA) group, ASM Instance Operator (OSOPER), and ASM Instance Administrator (OSASM) group you want to use for operating system authentication.
Ensure that these groups already exist on the hosts you select for provisioning. If they do not exist, then either specify alternative groups that exist on the host or create new groups as described in Oracle Database Quick Installation Guide available at
http://www.oracle.com/pls/db112/homepage
The new groups you create or the alternative groups you specify automatically get SYSDBA and SYSOPER privileges after the database is configured.
For more information, see Oracle Database 2 Day DBA Guide available at:
http://www.oracle.com/pls/db112/homepage
Note:
This section appears only if the source you selected is for a UNIX platform.In the Listener Port section, specify a custom listener port that can be used. Note that if you leave this field blank, then the port 1521 or any other available port is honored.
In the Configure ASM section, select Configure ASM if you want to configure ASM as part of this Deployment Procedure.
Note:
If you do not select Configure ASM, then the software binaries of Oracle Grid Infrastructure are copied to the destination host and a high-available listener is configured.If you want to configure Oracle ASM after provisioning, then you will have to manually configure it using Auomatic Storage Management Configuration Assistant (ASMCA). The high-available listener is configured in both cases, that is, when you select Configure ASM on this page and also when you manually configure Oracle ASM after provisioning.In the Schedule section, retain the default selection, that is, One Time (Immediately) if you want to run the procedure immediately. If you want to run the procedure later, then select One Time (Later) and provide time zone, start date, and start time details.
There may be occasions when the Management Agent on that target host is down and as a result, Oracle Management Service is unable to start the deployment job. To handle such eventualities, you can specify a grace period. You can specify until when Oracle Management Service should continue to attempt to restart the deployment job if at all it stops for some reason. The default grace period is indefinite. If you want to have a defninte period, then select End After and specify the end time, in hours and minutes, when it should terminate.
Note:
If the deployment job does not start within a specified time frame, then Oracle Management Service marks the job "skipped".Click Next.
Note:
If you have Oracle ASM or Oracle Grid Infrastructure already installed on the destination host, then you are prompted to either deconfigure them or specify another set of destination hosts that do not have them.If you chose to configure ASM, then on the Configure Oracle ASM page, add a new disk group and specify its credentials. Otherwise, go to Step (14).
In the ASM Storage section, click Add Disk Group to add disk groups.
On the Disk Group Configuration window that appears, by default, you will not see any disk groups detected. Specify a disk discovery string and search for disks on the destination hosts. For example, if the disks are /dev/raw/raw1, /dev/raw/raw2, and /dev/raw/raw3 on the destination hosts, then specify /dev/raw/* for Disk Discovery String and click Search. Ensure that the disk paths are the same across all destination hosts. Once the disks are detected, select the ones you are interested in.
Alternatively, if you know the exact path to the disks, then you can manually specify a comma-separated list.
After selecting or specifying the disks, specify a name for the disk group.
In the ASM Password section, specify the ASM password for SYS and ASMSNMP user accounts. Ensure that you meet the requirements described in ASM Password Requirements.
Click Next.
On the Review page, do the following:
In the Procedure Instance Name section, for Instance Name, specify a unique custom name for the Deployment Procedure instance so that you can track its progress/status on the Procedure Completion Status page. If you do not specify a custom name, then a default name is computed and assigned to the procedure.
Review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then click Finish to run the Deployment Procedure according to the schedule set. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
Note:
Click Analyze Prerequisites if you want to simulate the Deployment Procedure to check for prerequisites and to ensure that all the necessary requirements for provisioning are met. This helps you identify and resolve all operational conflicts and issues beforehand.Note:
if the Deployment Procedure fails, then review log files described in Appendix M, "Reviewing Log Files".Note:
If Deployment Procedure failed at the prerequisites stage, then ensure that the latest prerequisites are downloaded from My Oracle Support and uploaded to the Software Library.If your Enterprise Manager Grid Control has connectivity to My Oracle Support, then the latest prerequisites are automatically downloaded every night by a predefined job. However, if your Enterprise Manager Grid Control does not have any connectivity to My Oracle Support or has firewall settings that prevent it from connecting to My Oracle Support, then manually download the prerequisite-specific ZIP files from My Oracle Support and upload them to the Software Library. For more information, see Appendix J, "Manually Downloading Prerequisites from My Oracle Support".
While specifying the ASM password, follow these guidelines:
Password must not exceed 30 characters.
Password must not contain invalid characters: ! @ % ^ & * ( ) + = \ | ` ~ [ { ] } ; : ' " , < > ?
Password must not be change_on_install or asmsnmp.
A user name must not be a password.
An empty password cannot be accepted.
contains at least one lowercase letter.
contains at least one uppercase letter.
contains at least one digit.
is at least 8 characters in length.
uses the database character set which can include the underscore (_), dollar ($), and pound sign (#) characters.
if contains special characters, including beginning the password with a number or symbol, then enclose the password with double-quotation marks.
should not be an actual word.
This section describes how you can provision Oracle Grid Infrastructure using a certified gold image.
In particular, this section covers the following:
Before running the Deployment Procedure, meet the following prerequisites:
Ensure that you meet the prerequisites described in the following sections:
Compare the configuration of the source and target hosts and ensure that they have the same configuration. If the configurations are different, then contact your system administrator and fix the inconsistencies before running the Deployment Procedure.
To compare the configuration of the hosts, in Grid Control, click Targets and then Hosts. On the Hosts page, click the name of the source host to access its Home page, and then click the Configuration tab. On the Configuration page, click Compare Configuration and select the target host.
Ensure that the gold image is available either in the Software Library or in a staging location.
To stage a gold image to the Software Library or to a shared location, follow the instructions outlined in Appendix K, "Staging Gold Image to Software Library or Staging Location".
Meet the memory and disk space requirements for Oracle Grid Infrastructure installation on the target hosts. For information about the memory and disk space requirements for Oracle Grid Infrastructure installation, refer to the Oracle Database Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
Ensure that the following groups exist. If you do not belong to these groups, then the Deployment Procedure automatically adds you to the groups.
For information about creating these operating system groups, refer to the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
ASM Database Administrator (OSDBA) group
ASM Instance Operator (OSOPER) group
ASM Instance Administrator (OSASM) group
Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.
If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.
For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.
For information about customization, see Chapter 31, "Customizing Steps to Run as Another User".
Ensure that you use an operating system user that has write permission on the staging areas used for placing software binaries of Oracle Grid Infrastructure. Also ensure that the staging area is accessible from the Oracle Management Service (OMS) and the target host.
Deployment Procedures allow you to use staging locations for quick file-transfer of binaries and prevent high traffic over the network. While providing a staging location, ensure that the operating system user you use has write permission on those staging locations. For information about staging area, see Staging Area.
Ensure that the operating system groups you specify for OSDBA, OSOPER, and OSASM already exist on the hosts you select for provisioning. The operating system users of these groups automatically get the respective privileges.
To provision Oracle Grid Infrastructure using a certified gold image, follow these steps:
In Grid Control, click Deployments.
On the Deployment page, from the Deployment Procedure Manager section, click Database Provisioning Procedures.
On the Deployment Procedure Manager page, from the procedures table, select Oracle Grid Infrastructure Provisioning for Standalone Servers and click Schedule Deployment.
On the Select Source and Destination page, in the Select Source section, do one of the following:
If the gold image is stored as a component in Oracle Software Library (Software Library), then select Software Library. Then, click the torch icon for Component and select the component that has the gold image.
If the gold image was stored as an image in a staging location while provisioning a database in the past, then select Staging Location and then Gold Image. Click the torch icon for Select Host and select the host where the gold image is stored. Then click the torch icon for Stage Location and select the location on the host where the gold image is available.
Note:
This must be a gold image that was staged earlier by running the same Deployment Procedure either for provisioning the software or for staging the gold image. You must not select a gold image that was manually created and staged. For information about running the Deployment Procedure only to stage the gold image in a staging location, see Appendix K, "Staging Gold Image to Software Library or Staging Location".In the Specify Destination Host Settings section, do the following:
Click Add to search and select the destination hosts on which you want to provision Oracle Grid Infrastructure. Once you add a host, you will see default values for Oracle Base, Oracle Home, and other fields. You can either retain the default values or specify another custom value.
Note:
If you decide to specify an Oracle home location of your choice, then Oracle recommends you to maintain the Oracle home outside the installing user's home, and NOT inside.If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts. If you want to use different paths for each host, then select Different for each host.
Note:
If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.From the Credentials list, select one of the following to provide the operating system credentials of the destination host:
Preferred, if you want to use the preferred credentials stored in the Management Repository. For this, you must have already registered the preferred credentials.
Override Preferred Credentials, if you want to override the preferred credentials and use another set of credentials for this operation. If this environment is secure and has locked accounts, then make sure that the credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation. Also ensure that the Deployment Procedure has been customized to support locked environments.
For information about customizing Deployment Procedures for locked accounts, see Chapter 31, "Customizing Deployment Procedures".
Optionally, click Customize Host Settings if you want to provide additional, custom information about the destionation host and customize its settings.
For example, you may want to use an alternative host name instead of using the first host name identified on the system. Similarly, you may want to specify a custom name for the Oracle home. Also, if the Oracle Management Agent home credentials are different from the Oracle home credentials, then you may want to specify the agent home credentials. Under such circumstances, you can use this option to customize the host settings.
In the Advanced Installation Parameters subsection, specify any additional Oracle Universal Installer (OUI) parameters you want to run while provisioning Oracle Grid Infrastructure. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.
If you want to stage the software binaries to a shared location, then select Stage to Shared Location and specify a shared, NFS-mounted location that is accessible by Oracle Management Service and all the destination hosts. The software binaries will be staged only once to the staging location. Once they are staged, they will be copied to the working directory of each of the destination hosts.
Note:
The staged location can also act as a source for future deployments, that is, once the software binaries are available in the staged location, you can select Staging Location as the source when you run the Deployment Procedure next time.In the Group Details section, specify the ASM Database Administrator (OSDBA) group, ASM Instance Operator (OSOPER), and ASM Instance Administrator (OSASM) group you want to use for operating system authentication.
Ensure that these groups already exist on the hosts you select for provisioning. If they do not exist, then either specify alternative groups that exist on the host or create new groups as described in Oracle Database Quick Installation Guide available at
http://www.oracle.com/pls/db112/homepage
The new groups you create or the alternative groups you specify automatically get SYSDBA and SYSOPER privileges after the database is configured.
For more information, see Oracle Database 2 Day DBA Guide available at:
http://www.oracle.com/pls/db112/homepage
Note:
This section appears only if the source you selected is for a UNIX platform.In the Listener Port section, specify a custom listener port that can be used. Note that if you leave this field blank, then the port 1521 or any other available port is honored.
In the Configure ASM section, select Configure ASM if you want to configure ASM as part of this Deployment Procedure.
Note:
If you do not select Configure ASM, then the software binaries of Oracle Grid Infrastructure are copied to the destination host and a high-available listener is configured.If you want to configure Oracle ASM after provisioning, then you will have to manually configure it using Auomatic Storage Management Configuration Assistant (ASMCA). The high-available listener is configured in both cases, that is, when you select Configure ASM on this page and also when you manually configure Oracle ASM after provisioning.In the Schedule section, retain the default selection, that is, One Time (Immediately) if you want to run the procedure immediately. If you want to run the procedure later, then select One Time (Later) and provide time zone, start date, and start time details.
There may be occasions when the Management Agent on that target host is down and as a result, Oracle Management Service is unable to start the deployment job. To handle such eventualities, you can specify a grace period. You can specify until when Oracle Management Service should continue to attempt to restart the deployment job if at all it stops for some reason. The default grace period is indefinite. If you want to have a defninte period, then select End After and specify the end time, in hours and minutes, when it should terminate.
Note:
If the deployment job does not start within a specified time frame, then Oracle Management Service marks the job "skipped".Click Next.
Note:
If you have Oracle ASM or Oracle Grid Infrastructure already installed on the destination host, then you are prompted to either deconfigure them or specify another set of destination hosts that do not have them.If you chose to configure ASM, then on the Configure Oracle ASM page, add a new disk group and specify its credentials. Otherwise, go to Step (13).
In the ASM Storage section, click Add Disk Group to add disk groups. From the Disk Group Configuration window that appears, you can either select one of the disks discovered by Enterprise Manager Grid Control or manually specify the disk you want to use.
In the ASM Password section, specify the ASM password for SYS and ASMSNMP user accounts. Ensure that you meet the requirements described in ASM Password Requirements.
Click Next.
On the Review page, do the following:
In the Procedure Instance Name section, for Instance Name, specify a unique custom name for the Deployment Procedure instance so that you can track its progress/status on the Procedure Completion Status page. If you do not specify a custom name, then a default name is computed and assigned to the procedure.
Review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then click Finish to run the Deployment Procedure according to the schedule set. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
Note:
Click Analyze Prerequisites if you want to simulate the Deployment Procedure to check for prerequisites and to ensure that all the necessary requirements for provisioning are met. This helps you identify and resolve all operational conflicts and issues beforehand.Note:
if the Deployment Procedure fails, then review log files described in Appendix M, "Reviewing Log Files".Note:
If Deployment Procedure failed at the prerequisites stage, then ensure that the latest prerequisites are downloaded from My Oracle Support and uploaded to the Software Library.If your Enterprise Manager Grid Control has connectivity to My Oracle Support, then the latest prerequisites are automatically downloaded every night by a predefined job. However, if your Enterprise Manager Grid Control does not have any connectivity to My Oracle Support or has firewall settings that prevent it from connecting to My Oracle Support, then manually download the prerequisite-specific ZIP files from My Oracle Support and upload them to the Software Library. For more information, see Appendix J, "Manually Downloading Prerequisites from My Oracle Support".
This section describes how you can provision Oracle Grid Infrastructure using the archived installation binaries.
This option is best suited when you want a completely new installation to be provisioned across multiple standalone servers. Of course, understandably, this is a fresh installation and you will have to update it with all the latest patches that have been released so far.
In particular, this section covers the following:
Before running the Deployment Procedure, meet the following prerequisites:
Ensure that you meet the prerequisites described in the following sections:
Compare the configuration of the source and target hosts and ensure that they have the same configuration. If the configurations are different, then contact your system administrator and fix the inconsistencies before running the Deployment Procedure.
To compare the configuration of the hosts, in Grid Control, click Targets and then Hosts. On the Hosts page, click the name of the source host to access its Home page, and then click the Configuration tab. On the Configuration page, click Compare Configuration and select the target host.
Ensure that the installation binaries are downloaded, and archived and uploaded either as a component in the Software Library or as an archived file in a staging location.
To understand how you can download the installation binaries, and archive and uload them to the Software Library or to a shared location, see Appendix L, "Downloading Installation Binaries and Uploading to Software Library or Staging Location".
Meet the memory and disk space requirements for Oracle Grid Infrastructure installation on the target hosts. For information about the memory and disk space requirements for Oracle Grid Infrastructure installation, refer to the Oracle Database Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
Ensure that the following groups exist. If you do not belong to these groups, then the Deployment Procedure automatically adds you to the groups.
For information about creating these operating system groups, refer to the Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) available at:
http://www.oracle.com/technology/documentation/database.html
ASM Database Administrator (OSDBA) group
ASM Instance Operator (OSOPER) group
ASM Instance Administrator (OSASM) group
Ensure that you use an operating system user that has the privileges to run the Deployment Procedure, and that can switch to root user and run all commands on the target hosts. For example, commands such as mkdir, ls, and so on.
If you do not have the privileges to do so, that is, if you are using a locked account, then request your administrator (a designer) to either customize the Deployment Procedure to run it as another user or ignore the steps that require special privileges.
For example, user account A might have the root privileges, but you might use user account B to run the Deployment Procedure. In this case, you can switch from user account B to A by customizing the Deployment Procedure.
For information about customization, see Chapter 31, "Customizing Steps to Run as Another User".
Ensure that you use an operating system user that has write permission on the staging areas used for placing software binaries of Oracle Grid Infrastructure. Also ensure that the staging area is accessible from the Oracle Management Service (OMS) and the target host.
Deployment Procedures allow you to use staging locations for quick file-transfer of binaries and prevent high traffic over the network. While providing a staging location, ensure that the operating system user you use has write permission on those staging locations. For information about staging area, see Staging Area.
Ensure that the operating system groups you specify for OSDBA, OSOPER, and OSASM already exist on the hosts you select for provisioning. The operating system users of these groups automatically get the respective privileges.
To provision Oracle Grid Infrastructure using the archived software binaries, follow these steps:
In Grid Control, click Deployments.
On the Deployment page, from the Deployment Procedure Manager section, click Database Provisioning Procedures.
On the Deployment Procedure Manager page, from the procedures table, select Oracle Grid Infrastructure Provisioning for Standalone Servers and click Schedule Deployment.
On the Select Source and Destination page, in the Select Source section, do one of the following:
If the software binaries are stored as a component in Oracle Software Library (Software Library), then select Software Library. Then, click the torch icon for Component and select the component that has the archived software binaries. Ensure that you select only components that are in "Ready" status. When you select a component from the Software Library, Enterprise Manager Grid Control automatically populates the component location.
If the software binaries are stored as an archived file in a staging location, then select Staging Location and then Shiphome. Click the torch icon for Select Host and select the host where the archived file is stored. Then click the torch icon for Stage Location and select the location on the host where the archived file is available.
For information about archiving the software binaries from an installation medium and posting them to the Software Library or a staging location, see Appendix L, "Downloading Installation Binaries and Uploading to Software Library or Staging Location".
In the Specify Destination Host Settings section, do the following:
Click Add to search and select the destination hosts on which you want to provision Oracle Grid Infrastructure. Once you add a host, you will see default values for Oracle Base, Oracle Home, and other fields. You can either retain the default values or specify another custom value.
Note:
If you decide to specify an Oracle home location of your choice, then Oracle recommends you to maintain the Oracle home outside the installing user's home, and NOT inside.If you have selected multiple hosts, then from the Path list, select Same for all hosts if you want to use the same path across hosts. If you want to use different paths for each host, then select Different for each host.
Note:
If you select Same for all hosts, then ensure that the Oracle home and the user are present on all the hosts.From the Credentials list, select one of the following to provide the operating system credentials of the destination host:
Preferred, if you want to use the preferred credentials stored in the Management Repository. For this, you must have already registered the preferred credentials.
Override Preferred Credentials, if you want to override the preferred credentials and use another set of credentials for this operation. If this environment is secure and has locked accounts, then make sure that the credentials you specify here have the necessary privileges to switch to the locked account for performing the provisioning operation. Also ensure that the Deployment Procedure has been customized to support locked environments.
For information about customizing Deployment Procedures for locked accounts, see Chapter 31, "Customizing Deployment Procedures".
Optionally, click Customize Host Settings if you want to provide additional, custom information about the destionation host and customize its settings.
For example, you may want to use an alternative host name instead of using the first host name identified on the system. Similarly, you may want to specify a custom name for the Oracle home. Also, if the Oracle Management Agent home credentials are different from the Oracle home credentials, then you may want to specify the agent home credentials. Under such circumstances, you can use this option to customize the host settings.
In the Advanced Installation Parameters subsection, specify any additional Oracle Universal Installer (OUI) parameters you want to run while provisioning Oracle Grid Infrastructure. For example, -force (to override any warnings), -debug (to view more debug information), and -invPtrLoc <Location> (for UNIX only). Ensure that the parameters are separated by white space.
If you want to stage the software binaries to a shared location, then select Stage to Shared Location and specify a shared, NFS-mounted location that is accessible by Oracle Management Service and all the destination hosts. The software binaries will be staged only once to the staging location. Once they are staged, they will be copied to the working directory of each of the destination hosts.
Note:
The staged location can also act as a source for future deployments, that is, once the software binaries are available in the staged location, you can select Staging Location as the source when you run the Deployment Procedure next time.In the Group Details section, specify the ASM Database Administrator (OSDBA) group, ASM Instance Operator (OSOPER), and ASM Instance Administrator (OSASM) group you want to use for operating system authentication.
Ensure that these groups already exist on the hosts you select for provisioning. If they do not exist, then either specify alternative groups that exist on the host or create new groups as described in Oracle Database Quick Installation Guide available at
http://www.oracle.com/pls/db112/homepage
The new groups you create or the alternative groups you specify automatically get SYSDBA and SYSOPER privileges after the database is configured.
For more information, see Oracle Database 2 Day DBA Guide available at:
http://www.oracle.com/pls/db112/homepage
Note:
This section appears only if the source you selected is for a UNIX platform.In the Listener Port section, specify a custom listener port that can be used. Note that if you leave this field blank, then the port 1521 or any other available port is honored.
In the Configure ASM section, select Configure ASM if you want to configure ASM as part of this Deployment Procedure.
Note:
If you do not select Configure ASM, then the software binaries of Oracle Grid Infrastructure are copied to the destination host and a high-available listener is configured.If you want to configure Oracle ASM after provisioning, then you will have to manually configure it using Auomatic Storage Management Configuration Assistant (ASMCA). The high-available listener is configured in both cases, that is, when you select Configure ASM on this page and also when you manually configure Oracle ASM after provisioning.In the Schedule section, retain the default selection, that is, One Time (Immediately) if you want to run the procedure immediately. If you want to run the procedure later, then select One Time (Later) and provide time zone, start date, and start time details.
There may be occasions when the Management Agent on that target host is down and as a result, Oracle Management Service is unable to start the deployment job. To handle such eventualities, you can specify a grace period. You can specify until when Oracle Management Service should continue to attempt to restart the deployment job if at all it stops for some reason. The default grace period is indefinite. If you want to have a defninte period, then select End After and specify the end time, in hours and minutes, when it should terminate.
Note:
If the deployment job does not start within a specified time frame, then Oracle Management Service marks the job "skipped".Click Next.
Note:
If you have Oracle ASM or Oracle Grid Infrastructure already installed on the destination host, then you are prompted to either deconfigure them or specify another set of destination hosts that do not have them.If you chose to configure ASM, then on the Configure Oracle ASM page, add a new disk group and specify its credentials. Otherwise, go to Step (13).
In the ASM Storage section, click Add Disk Group to add disk groups. From the Disk Group Configuration window that appears, you can either select one of the disks discovered by Enterprise Manager Grid Control or manually specify the disk you want to use.
In the ASM Password section, specify the ASM password for SYS and ASMSNMP user accounts. Ensure that you meet the requirements described ASM Password Requirements.
Click Next.
On the Review page, do the following:
In the Procedure Instance Name section, for Instance Name, specify a unique custom name for the Deployment Procedure instance so that you can track its progress/status on the Procedure Completion Status page. If you do not specify a custom name, then a default name is computed and assigned to the procedure.
Review the details you have provided for the Deployment Procedure. If you are satisfied with the details, then click Finish to run the Deployment Procedure according to the schedule set. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.
Note:
Click Analyze Prerequisites if you want to simulate the Deployment Procedure to check for prerequisites and to ensure that all the necessary requirements for provisioning are met. This helps you identify and resolve all operational conflicts and issues beforehand.Note:
if the Deployment Procedure fails, then review log files described in Appendix M, "Reviewing Log Files".Note:
If Deployment Procedure failed at the prerequisites stage, then ensure that the latest prerequisites are downloaded from My Oracle Support and uploaded to the Software Library.If your Enterprise Manager Grid Control has connectivity to My Oracle Support, then the latest prerequisites are automatically downloaded every night by a predefined job. However, if your Enterprise Manager Grid Control does not have any connectivity to My Oracle Support or has firewall settings that prevent it from connecting to My Oracle Support, then manually download the prerequisite-specific ZIP files from My Oracle Support and upload them to the Software Library. For more information, see Appendix J, "Manually Downloading Prerequisites from My Oracle Support".