Advanced Installation Oracle Grid Infrastructure for a Cluster Preinstallation Tasks. This chapter describes the system configuration tasks that you must complete before you start Oracle Universal Installer (OUI) to install Oracle Grid Infrastructure for a cluster, and that you may need to complete if you intend to install Oracle Real Application Clusters (Oracle RAC) on the cluster. This chapter contains the following topics: 2. Reviewing Upgrade Best Practices. The new enterprise IT help desk features bots, cloud monitoring, and consolidated views into problems, and it can be implemented today. Table 14. FAQ July updates; July 2016 IBM Spectrum Scale V4.2.1 Functional Support Matrix 2.1 What levels of the AIX OS are supported by IBM Spectrum Scale? AIX 6 WPARs Beta Test. 10/08/2007. Chris Gibson. IBM released the AIX 6 Open Beta in July 2007. This is the first time IBM has allowed customers to download a beta. Caution. Always create a backup of existing databases before starting any configuration change. If you have an existing Oracle installation, then record the version numbers, patches, and other configuration information, and review upgrade procedures for your existing installation. Review Oracle upgrade documentation before proceeding with installation, to decide how you want to proceed. You can upgrade Oracle ASM 1. Oracle RAC database by performing a rolling upgrade either of individual nodes, or of a set of nodes in the cluster. However, if you have a standalone database on a cluster that uses Oracle ASM, then you must shut down the standalone database before upgrading. If you are upgrading from Oracle ASM 1. Oracle ASM cluster to perform the upgrade. If you have an existing Oracle Automatic Storage Management (Oracle ASM) installation, then review Oracle upgrade documentation. The location of the Oracle ASM home changes in this release, and you may want to consider other configuration changes to simplify or customize storage administration. If you have an existing Oracle ASM home from a previous release, then it should be owned by the same user that you plan to use to upgrade Oracle Clusterware. During rolling upgrades of the operating system, Oracle supports using different operating system binaries when both versions of the operating system are certified with the Oracle Database release you are using. Note. Using mixed operating system versions is only supported for the duration of an upgrade, over the period of a few hours. Oracle Clusterware does not support nodes that have processors with different instruction set architectures (ISAs) in the same cluster. Each node must be binary compatible with the other nodes in the cluster. For example, you cannot have one node using an Intel 6. ![]() ![]() IA- 6. 4 (Itanium) processor in the same cluster. You could have one node using an Intel 6. AMD6. 4 processor in the same cluster because the processors use the same x. ISA and run the same binary version of Oracle software. Your cluster can have nodes with CPUs of different speeds or sizes, but Oracle recommends that you use nodes with the same hardware configuration. To find the most recent software updates, and to find best practices recommendations about preupgrade, postupgrade, compatibility, and interoperability, refer to "Oracle Upgrade Companion." "Oracle Upgrade Companion" is available through Note 7. My Oracle Support: https: //support. Installation Fixup Scripts. With Oracle Clusterware 1. Oracle Universal Installer (OUI) detects when the minimum requirements for an installation are not met, and creates shell scripts, called fixup scripts, to finish incomplete system configuration steps. If OUI detects an incomplete task, then it generates fixup scripts (runfixup. You can run the fixup script after you click the Fix and Check Again Button. You also can have CVU generate fixup scripts before installation. The Fixup script does the following: If necessary sets kernel parameters to values required for successful installation, including: Shared memory parameters. Open file descriptor and UDP send/receive parameters. Sets permissions on the Oracle Inventory (central inventory) directory. Reconfigures primary and secondary group memberships for the installation owner, if necessary, for the Oracle Inventory directory and the operating system privileges groups. Sets shell limits if necessary to required values. If you have SSH configured between cluster member nodes for the user account that you will use for installation, then you can check your cluster configuration before installation and generate a fixup script to make operating system changes before starting the installation. To do this, log in as the user account that will perform the installation, navigate to the staging area where the runcluvfy command is located, and use the following command syntax, where node is a comma- delimited list of nodes you want to make cluster members: $ ./runcluvfy. For example, if you intend to configure a two- node cluster with nodes node. Logging In to a Remote System as root Using X Terminal. Before you install the Oracle software, you must complete several tasks as the root user on the system where you install Oracle software. To complete tasks as the root user on a remote server, you need to enable remote display as root. Note. If you log in as another user (for example, oracle), then you need to repeat this procedure for that user as well. To enable remote display, complete one of the following procedures: If you are installing the software from an X Window System workstation or X terminal, then: Start a local terminal session, for example, an X terminal (xterm). If you are not installing the software on the local system, then enter a command using the following syntax to enable remote hosts to display X applications on the local X server. For example. $ xhost + somehost. If you are not installing the software on the local system, then use the ssh, command to connect to the system where you want to install the software. For example. $ ssh somehost. If you are not logged in as the root user, then enter the following command to switch the user to root. If you are installing the software from a PC or other system with X server software installed, then: Note. If necessary, refer to your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order. Start the X server software. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system. Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm). If you are not logged in as the root user on the remote system, then enter the following command to switch user to root. Creating Groups, Users and Paths for Oracle Grid Infrastructure. Log in as root, and use the following instructions to locate or create groups and users required for installation. Note. Ensure that all group and user numbers are identical on all cluster member nodes. Note. During an Oracle Grid Infrastructure installation, both Oracle Clusterware and Oracle Automatic Storage Management are installed. You no longer can have separate Oracle Clusterware installation owners and Oracle Automatic Storage Management installation owners. Determining If the Oracle Inventory and Oracle Inventory Group Exists. When you install Oracle software on the system for the first time, OUI creates the ora. Inst. loc file. This file identifies the name of the Oracle Inventory group (by default, oinstall), and the path of the Oracle Central Inventory directory. An ora. Inst. loc file has contents similar to the following. In the preceding example, central_inventory_location is the location of the Oracle central inventory, and group is the name of the group that has permissions to write to the central inventory (the OINSTALL group privilege). If you have an existing Oracle central inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations, and ensure that all Oracle software users you intend to use for installation have permissions to write to this directory. To determine if you have an Oracle central inventory directory (ora. Inventory) on your system: Enter the following command. Inst. loc. If the ora. Inst. loc file exists, then the output from this command is similar to the following. Inventory. inst_group=oinstall. In the previous output example: The inventory_loc group shows the location of the Oracle Inventory. The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall). Use the command grepgroupname/etc/group to confirm that the group specified as the Oracle Inventory group still exists on the system. For example. $ grep oinstall /etc/group. Creating the Oracle Inventory Group If an Oracle Inventory Does Not Exist. If the ora. Inst.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |