This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Grid Infrastructure software.
This chapter contains the following topics:
To download required patch updates:
Use a Web browser to view the My Oracle Support website:
Log in to My Oracle Support.
Note:If you are not a My Oracle Support registered user, then click Register for My Oracle Support and register.
On the main My Oracle Support page, click Patches & Updates.
On the Patches and Updates page, click Product or Family (Advanced).
In the Product field, select Oracle Database.
In the Release field, select one or more release numbers. For example, Oracle 126.96.36.199.0.
Any available patch updates are displayed in the Patch Search page.
Click the patch number to download the patch.
Select the patch number and click Read Me. The README page contains information about the patch set and how to apply the patches to your installation.
Return to the Patch Set page, click Download, and save the file on your system.
Use the unzip utility provided with Oracle Database 12c Release 1 (12.1) to uncompress the Oracle patch updates that you downloaded from My Oracle Support. The unzip utility is located in the
See Appendix B, "How to Upgrade to Oracle Grid Infrastructure 12c Release 1" for information about how to stop database processes in preparation for installing patches.
Oracle recommends that you complete the following tasks as needed after installing Oracle Grid Infrastructure:
Use the following guidelines only if the default semaphore parameter values are too low to accommodate all Oracle processes:
Note:Oracle recommends that you refer to the operating system documentation for more information about setting semaphore parameters.
Calculate the minimum total semaphore requirements using the following formula:
2 * sum (process parameters of all database instances on the system) + overhead for background processes + system and other application requirements
semmns (total semaphores systemwide) to this total.
semmsl (semaphores for each set) to 250.
semmni (total semaphores sets) to
semmns divided by
semmsl, rounded up to the nearest multiple of 1024.
See Also:My Oracle Support note 226209.01, "Linux: How to Check Current Shared Memory, Semaphore Values," which is available from the following URL:
During installation, by default you can create one disk group. If you plan to add an Oracle Database for a standalone server or an Oracle RAC database, then you should create the Fast Recovery Area for database files.
The Fast Recovery Area is a unified storage location for all Oracle Database files related to recovery. Database administrators can define the DB_RECOVERY_FILE_DEST parameter to the path for the Fast Recovery Area to enable on-disk backups, and rapid recovery of data. Enabling rapid backups for recent data can reduce requests to system administrators to retrieve backup tapes for recovery operations.
When you enable Fast Recovery in the
init.ora file, all RMAN backups, archive logs, control file automatic backups, and database copies are written to the Fast Recovery Area. RMAN automatically manages files in the Fast Recovery Area by deleting obsolete backups and archive files no longer required for recovery.
Oracle recommends that you create a Fast Recovery Area disk group. Oracle Clusterware files and Oracle Database files can be placed on the same disk group, and you can also place Fast Recovery Area files in the same disk group. However, Oracle recommends that you create a separate Fast Recovery Area disk group to reduce storage device contention.
The Fast Recovery Area is enabled by setting DB_RECOVERY_FILE_DEST. The size of the Fast Recovery Area is set with DB_RECOVERY_FILE_DEST_SIZE. As a general rule, the larger the Fast Recovery Area, the more useful it becomes. For ease of use, Oracle recommends that you create a Fast Recovery Area disk group on storage devices that can contain at least three days of recovery information. Ideally, the Fast Recovery Area should be large enough to hold a copy of all of your data files and control files, the online redo logs, and the archived redo log files needed to recover your database using the data file backups kept under your retention policy.
Multiple databases can use the same fast recovery area. For example, assume you have created one fast recovery area disk group on disks with 150 gigabyte (GB) of storage, shared by three different databases. You can set the size of the fast recovery area for each database depending on the importance of each database. For example, if test1 is your least important database, products is of greater importance and orders is of greatest importance, then you can set different DB_RECOVERY_FILE_DEST_SIZE settings for each database to meet your retention target for each database: 30 GB for test1, 50 GB for products, and 70 GB for orders.
To create a Fast Recovery Area disk group:
$ cd /u01/app/12.1.0/grid/bin $ ./asmca
ASMCA opens at the Disk Groups tab. Click Create to create a new disk group.
The Create Disk Groups window opens.
In the Disk Group Name field, enter a descriptive name for the Fast Recovery Area group. For example: FRA.
In the Redundancy section, select the level of redundancy you want to use.
In the Select Member Disks field, select eligible disks to be added to the Fast Recovery Area, and click OK.
The Diskgroup Creation window opens to inform you when disk group creation is complete. Click OK.
The Single Client Access Name (SCAN) is a name that is used to provide service access for clients to the cluster. Because the SCAN is associated with the cluster as a whole, rather than to a particular node, the SCAN makes it possible to add or remove nodes from the cluster without needing to reconfigure clients. It also adds location independence for the databases, so that client configuration does not have to depend on which nodes are running a particular database instance. Clients can continue to access the cluster in the same way as with previous releases, but Oracle recommends that clients accessing the cluster use the SCAN.
You can use the command
cluvfy comp scan (located in Grid home
/bin) to confirm that the DNS is correctly associating the SCAN with the addresses. For example:
$ cluvfy comp scan Verifying scan Checking Single Client Access Name (SCAN)... Checking TCP connectivity to SCAN Listeners... TCP connectivity to SCAN Listeners exists on all cluster nodes Checking name resolution setup for ”node1.example.com”... Verification of SCAN VIP and Listener setup passed Verification of scan was successful.
After installation, when a client sends a request to the cluster, the Oracle Clusterware SCAN listeners redirect client requests to servers in the cluster.
See Also:Oracle Clusterware Administration and Deployment Guide for more information about system checks and configurations
Download and install the ORAchk utility to perform proactive heath checks for the Oracle software stack.
ORAchk replaces the RACCheck utility, extends health check coverage to the entire Oracle software stack, and identifies and addresses top issues reported by Oracle users. ORAchk proactively scans for known problems with Oracle products and deployments, including the following:
Standalone Oracle Database
Oracle Grid Infrastructure
Oracle Real Application Clusters
Maximum Availability Architecture (MAA) Validation
Upgrade Readiness Validations
Oracle Golden Gate
For information about configuring and running the ORAchk utility, refer to My Oracle Support note 1268927.1:
After you have completed Oracle Grid Infrastructure installation, you can set resource limits in the Grid_home
_env.txt file. These resource limits apply to all Oracle Clusterware processes and Oracle databases managed by Oracle Clusterware. For example, to set a higher number of processes limit, edit the file and set
CRS_LIMIT_NPROC parameter to a high value.
Review the following sections for information about using earlier Oracle Database releases with Oracle Grid Infrastructure 12c Release 1 (12.1) installations:
You can use Oracle Database 10g Release 2 and Oracle Database 11g Release 1 and 2 with Oracle Clusterware 12c Release 1 (12.1).
Do not use the versions of
lsnrctl, or other Oracle Grid infrastructure home tools to administer earlier version databases. Only administer earlier Oracle Database releases using the tools in the earlier Oracle Database homes. To ensure that the versions of the tools you are using are the correct tools for those earlier release databases, run the tools from the Oracle home of the database or object you are managing.
Oracle Database homes can only be stored on Oracle ASM Cluster File System (Oracle ACFS) if the database version is Oracle Database 11g Release 2 or higher. Earlier releases of Oracle Database cannot be installed on Oracle ACFS because these releases were not designed to use Oracle ACFS.
If you upgrade an existing version of Oracle Clusterware and Oracle ASM to Oracle Grid Infrastructure 11g or later (which includes Oracle Clusterware and Oracle ASM), and you also plan to upgrade your Oracle RAC database to 12c Release 1 (12.1), then the required configuration of existing databases is completed automatically when you complete the Oracle RAC upgrade, and this section does not concern you.
Note:Before you start an Oracle RAC or Oracle Database installation on an Oracle Clusterware 12c Release 1 (12.1) installation, if you are upgrading from Oracle Database 11g Release 1 (188.8.131.52 or 184.108.40.206), or Oracle Database 10g Release 2 (10.2.0.4), then Oracle recommends that you check for the latest recommended patches for the release you are upgrading from, and install those patches as needed on your existing database installations before upgrading.
For more information on recommended patches, see Oracle 12c Upgrade Companion (My Oracle Support Note 1462240.1):
Starting with Oracle Grid Infrastructure 12c, Oracle Database server categories include roles such as Hub and Leaf that were not present in earlier releases. For this reason, you cannot create server pools using the Oracle RAC 11g version of Database Configuration Assistant (DBCA). To create server pools for earlier release Oracle RAC installations, use the following procedure:
Log in as the Oracle Grid Infrastructure installation owner (Grid user)
Change directory to the 12.1 Oracle Grid Infrastructure binaries directory in the Grid home. For example:
# cd /u01/app/12.1.0/grid/bin
Use the Oracle Grid Infrastructure 12c version of
srvctl to create a server pool consisting of Hub Node roles. For example, to create a server pool called p_hub with a maximum size of one cluster node, enter the following command:
srvctl add serverpool -serverpool p_hub -min 0 -max 1 -category hub;
Log in as the Oracle RAC installation owner, start DBCA from the Oracle RAC Oracle home. For example:
$ cd /u01/app/oracle/product/11.2.0/dbhome_1/bin $ dbca
DBCA discovers the server pool that you created with the Oracle Grid Infrastructure 12c
srvctl command. Configure the server pool as required for your services.
See Also:Oracle Clusterware Administration and Deployment Guide for more information about managing resources using policies
To use Oracle ASM with Oracle Database releases earlier than Oracle Database 12c, you must use Local ASM or set the cardinality for Flex ASM to ALL, instead of the default of 3. After you install Oracle Grid Infrastructure 12c, if you want to use Oracle ASM to provide storage service for Oracle Database releases that are earlier than Oracle Database 12c, then you must use the following command to modify the Oracle ASM resource (ora.asm):
$ srvctl modify asm -count ALL
This setting changes the cardinality of the Oracle ASM resource so that Oracle Flex ASM instances run on all cluster nodes. You must change the setting even if you have a cluster with three or less than three nodes, to ensure database releases earlier than 11g Release 2 can find the ora.node.sid.inst resource alias.
If you have Oracle Database 10g Release 2 databases that use Oracle ASM for storage, then set the
SQLNET.ALLOWED_LOGON_VERSION=8 in the
Use Oracle ASM Configuration Assistant (ASMCA) to create and modify disk groups when you install earlier Oracle databases and Oracle RAC databases on Oracle Grid Infrastructure installations. Starting with Oracle Database 11g Release 2 (11.2), Oracle ASM is installed as part of an Oracle Grid Infrastructure installation, with Oracle Clusterware. You can no longer use Database Configuration Assistant (DBCA) to perform administrative tasks on Oracle ASM.
See Also:Oracle Automatic Storage Management Administrator's Guide for details about configuring disk group compatibility for databases using Oracle Database 11g or earlier software with Oracle Grid Infrastructure 12c (12.1)
When Oracle Clusterware 12c Release 1 (12.1) is installed on a cluster with no previous Oracle software version, it configures the cluster nodes dynamically, which is compatible with Oracle Database Release 11.2 and later, but Oracle Database 10g and 11.1 require a persistent configuration. This process of association of a node name with a node number is called pinning.
Note:During an upgrade, all cluster member nodes are pinned automatically, and no manual pinning is required for existing databases. This procedure is required only if you install earlier database versions after installing Oracle Grid Infrastructure 12c Release 1 (12.1) software.
To pin a node in preparation for installing or using an earlier Oracle Database version, use
/bin/crsctl with the following command syntax, where
nodes is a space-delimited list of one or more nodes in the cluster whose configuration you want to pin:
crsctl pin css -n nodes
For example, to pin nodes
node4, log in as
root and enter the following command:
$ crsctl pin css -n node3 node4
To determine if a node is in a pinned or unpinned state, use
/bin/olsnodes with the following command syntax:
To list all pinned nodes:
olsnodes -t -n
# /u01/app/12.1.0/grid/bin/olsnodes -t -n node1 1 Pinned node2 2 Pinned node3 3 Pinned node4 4 Pinned
To list the state of a particular node:
olsnodes -t -n node3
# /u01/app/12.1.0/grid/bin/olsnodes -t -n node3 node3 3 Pinned
See Also:Oracle Clusterware Administration and Deployment Guide for more information about pinning and unpinning nodes
To administer local and SCAN listeners using the
lsnrctl command, set your
$ORACLE_HOME environment variable to the path for the Oracle Grid Infrastructure home (Grid home). Do not attempt to use the
lsnrctl commands from Oracle home locations for previous releases, as they cannot be used with the new release.
For example, if you want to apply a one-off patch, or if you want to modify an Oracle Clusterware configuration to run IPC traffic over RDS on the interconnect instead of using the default UDP, then you must unlock the Grid home.
Note:Before relinking executables, you must shut down all executables that run in the Oracle home directory that you are unlocking and relinking. In addition, shut down applications linked with Oracle shared libraries.
Unlock the home using the following procedure:
Log in as
root, and change directory to the path Grid_home/crs/install, where Grid_home is the path to the Grid home, and unlock the Grid home using the command
rootcrs.sh -unlock -crshome
Grid_home, where Grid_home is the path to your Grid infrastructure home. For example, with the Grid home
/u01/app/12.1.0/grid, enter the following command:
# cd /u01/app/12.1.0/grid/crs/install # perl rootcrs.sh -unlock -crshome /u01/app/12.1.0/grid
Change user to the Oracle Grid Infrastructure software owner, and relink binaries using the command syntax
make -f Grid_home
/rdbms/lib/ins_rdbms.mk target, where Grid_home is the Grid home, and target is the binaries that you want to relink. For example, where the Grid user is
$ORACLE_HOME is set to the Grid home, and where you are updating the interconnect protocol from UDP to IPC, enter the following command:
# su grid $ make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk ipc_rds ioracle
Note:To relink binaries, you can also change to the Oracle Grid Infrastructure installation owner and run the command
Relock the Grid home and restart the cluster using the following command:
# perl rootcrs.sh -patch
Repeat steps 1 through 3 on each cluster member node.
Note:Do not delete directories in the Grid home. For example, do not delete the directory Grid_home/Opatch. If you delete the directory, then the Grid infrastructure installation owner cannot use Opatch to patch the grid home, and Opatch displays the error message "
checkdir error: cannot createGrid_home