To determine the RAM size, enter the following command:. Between 1 GB and 2 GB 1. More than 16 GB 16 GB. To determine the available RAM and swap space, enter the following command:. The following tables describe the disk space requirements for software files and data files for each installation type on Linux x Enterprise Edition 3.
Standard Edition 3. Enterprise Edition 1. Standard Edition 1. Linux version 2. Oracle Linux Server release 6. Starting udev: [ OK ]. Configuring Kernel Parameters for Linux. Starting Oracle Universal Installer Checking Temp space: must be greater than MB. Actual MB Passed. Checking swap space: must be greater than MB.
Checking monitor: must be configured to display at least colors. Actual Passed. Please wait Setting Kernel Parameters Oracle Linux 6.
Adding read,write permissions for group. Removing read,write,execute permissions for world. The execution of the script is complete. Running Oracle 11g root. The following environment variables are set as:. Database Configuration Assistant when a database is created. Finished running generic part of root.
Now product-specific root actions will be performed. To configure Grid Infrastructure for a Cluster perform the following steps:. For details on how to do this, see the installation guide.
Run the following command as the root user:. To update inventory properties for Grid Infrastructure, perform the following. If a pre Always execute the following to register the current home:. If either home is shared, provide the additional argument -cfs. Creating trace directory.
Refer to your operating system-specific installation guide for more information about the default search path. Oracle ASM cannot use a disk unless all of the Oracle ASM instances in the cluster can discover the disk through one of their own discovery strings. The names do not have to be the same on every node, but all disks must be discoverable by all of the nodes in the cluster. This may require dynamically changing the initialization parameter to enable adding new storage.
IOServer instances are started automatically in the Oracle Grid Infrastructure configuration when generating the credential file for a client cluster. You can configure the number of IOServer instances running in the client cluster.
The default value should work in most cases. However, under heavy IO loads a higher value than the default may be appropriate. The range of values is 0 to The default value is 1. A value of 0 disables rebalancing. For disk groups that have the disk group ASM compatibility set to For disk groups that have the disk group ASM compatibility set to less than The specification of the power of the rebalancing operation in a disk group only affects rebalance operations, not new allocations to a disk group.
Disk Group Compatibility for information about disk group compatibility. The default value is NULL. This parameter is generally used for clustered Oracle ASM instances and its value can be different on different nodes. If preferred read functionality is enabled, then this functionality enables an instance to determine and read from disks at the same site as itself, which can improve performance. Preferred Read Failure Groups for more information about preferred read failure groups. Oracle Real Application Clusters Administration and Deployment Guide for more information about configuring preferred disks in extended clusters.
This buffer cache stores metadata blocks. The default value for this parameter is suitable for most environments. Oracle Database Performance Tuning Guide for more information about memory configuration. The main components of ASM are disk groups, each of which comprise of several physical disks that are controlled as a single unit. The locations and names for the files are controlled by ASM, but user-friendly aliases and directory structures can be defined for ease of reference.
The level of redundancy and the granularity of the striping can be controlled using templates. Default templates are provided for each file type stored by ASM, but additional templates can be defined as needed. Failure groups are defined within a disk group to support the required level of redundancy. For two-way mirroring you would expect a disk group to contain two failure groups so individual files are written to two locations.
It is worth taking a quick look at the following section of the documentation to familiarize yourself with the basic requirements recommendations for ASM. The ASM instance is now ready to use for creating and mounting disk groups.
To shutdown the ASM instance issue the following command. ASM instance are started and stopped in a similar way to normal database instances. This statement allows you to specify the level of redundancy:. In addition failure groups and preferred names for disks can be defined.
0コメント