Download Oracle Real Application Clusters 11g Release 2 and Grid Infrastructure Administration.1z0-058.PracticeTest.2018-09-27.74q.vcex

Controlling Oracle Clusterware The crsctl utility can be used to control Oracle Clusterware. To start or stop Oracle Clusterware on a specific node:# crsctl start crs # crsctl stop crs To enable or disable Oracle Clusterware on a specific node:# crsctl enable crs # crsctl disable crs D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 3 - 5

Oracle Automatic Storage Management Cluster File System (Oracle ACFS) and Oracle ASM Dynamic Volume Manager (Oracle ADVM) extend Oracle ASM support to include database and application executables, database trace files, database alert logs, application reports, BFILEs, and configuration files. Other supported files are video, audio, text, images, engineering drawings, and other general-purpose application file data.  Because of the fact that Oracle ADVM Volumes are technically spoken ASM files located on ASM Disk groups, and the fact that the Dynamic Volumes do not use the traditional device partitioning, it enables Oracle to extend some of the ASM features to the ASM Clustered File Systems, which are created inside these ADVM Volumes, such as dynamic resizing or dynamically adding volumes. This makes ADVM and ACFS a far more flexible solution than traditional physical devices. Important Notes:

# crsctl delete node -n node_to_be_deleted $ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home "CLUSTER_NODES={node_to_be_deleted}" CRS=TRUE -silent -local On any node other than the node you are deleting, run the following command from the Grid_home /oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your cluster:$ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home "CLUSTER_NODES={remaining_nodes_list}" CRS=TRUE -silent $ cluvfy stage -post nodedel -n node_list [-verbose] Oracle® Clusterware Administration and Deployment Guide

Cause You have logged in with SYSDBA privilege that is not allowed for ASM operations  Solution Login with SYSASM credentials for ASM operations MOS [ID 889810.1]

Resource Attributes NAME A case-sensitive alphanumeric string that names the resource. Oracle recommends a naming convention that starts with an alphanumeric prefix, such as myApache, and complete the name with an identifier to describe it. A resource name can contain any platform-supported characters except the exclamation point (!) and the tilde (~). A resource name cannot begin with a period (.) nor with the string ora. TYPE The type of resource indicated when you create a resource. This attribute is required when creating a resource. Local resource: Instances of local resources—type name is local_resource—run on each server of the cluster. When a server joins the cluster, Oracle Clusterware automatically extends local resources to have instances tied to the new server. When a server leaves the cluster, Oracle Clusterware automatically sheds the instances of local resources that ran on the departing server. Instances of local resources are pinned to their servers; they do not fail over from one server to another.Cluster resource: Cluster-aware resource types—type name is cluster_resource—are aware of the cluster environment and are subject to cardinality and cross-server switchover and failover.TARGET An internal, read-only attribute that describes the desired state of a resource. Using the crsctl start resource_name or crsctl stop resource_name commands, however, can affect the value of this attribute. STATE An internally-managed attribute that reflects the current state of the resource as reported by Oracle Clusterware. The state of a resource can be one of the following:ONLINE: The resource is online and resource monitoring is enabled (see CHECK_INTERVAL).OFFLINE: The resource is offline and only offline resource monitoring is enabled, if configured (see OFFLINE_CHECK_INTERVAL).INTERMEDIATE: The resource is either partially online or was known to be online before and subsequent attempts to determine its state have failed; resource monitoring is enabled (see CHECK_INTERVAL).UNKNOWN: The resource is unmanageable and its current state is unknown; manual intervention is required to resume its operation. A resource in this state is not monitored.Oracle® Clusterware Administration and Deployment Guide 11g Release 2 (11.2)

$ cluvfy stage -post nodeadd -n node3 [-verbose] Use the cluvfy comp peer component verification command to check the compatibility and properties of the specified nodes against a reference node. You can check compatibility for non-default user group names and for different releases of the Oracle software. This command compares physical attributes, such as memory and swap space, as well as user and group values, kernel settings, and installed operating system packages. Syntax cluvfy comp peer -n node_list [-refnode node] [-r {10gR1 | 10gR2 | 11gR1 | 11gR2}] [-orainv orainventory_group][-osdba osdba_group] [-verbose] Usage Notes Peer comparison with the -refnode option compares the system properties of other nodes against the reference node. If the value does not match (the value is not equal to reference node value), then CVU flags that comparison as a deviation from the reference node. If a group or user does not exist on reference node as well as on the other node, CVU reports this comparison as 'passed' because there is no deviation from the reference node. Similarly, CVU reports as 'failed' a comparison with a node that has more total memory than the reference node. $ cluvfy stage -pre nodeadd -n node3 [-fixup [-fixupdir fixup_dir]] [-verbose] You can specify the -fixup option and a directory into which CVU prints instructions to fix the cluster or node if the verification fails. Oracle® Clusterware Administration and Deployment Guide

On Linux and UNIX systems, dba is the default operating system group designated as OSASM, OSOPER, and OSDBA for Oracle ASM. On Windows systems, ora_dba is the default name designated as OSASM, OSOPER, and OSDBA. SQL*Plus commands, ASMCMD commands, and ASMCA use operating system authentication To connect locally as SYSASM to an Oracle ASM instance using operating system authentication with SQL*Plus, use the following statement: sqlplus / AS SYSASM OSASM group This group is granted the SYSASM privilege, which provides full administrative privileges for the Oracle ASM instance.  You can specify the --privilege option to choose the type of connection, either SYSASM or SYSDBA. The default value is SYSASM and is used when administering an Oracle ASM instance. Connect as SYSDBA when connecting to the database instance. For example:$ asmcmd --privilege sysasm usage: asmcmd [-V] [-v <errors|warnings|normal|info|debug>] [--privilege <sysasm|sysdba>] [-p] [command]

Installing a Patch with Minimum Down Time with OPatch In minimum down-time patching, the nodes are divided into two sets. One set of nodes is shut down and the patch is applied to those nodes. After the first set of nodes has been patched, the second set of nodes is shut down. The first set of nodes is then restarted and the patch is applied to the second set of nodes. After the patch has been applied to the second set of nodes, those nodes are restarted. This method leads to less down time for Oracle RAC, compared to having all the nodes shut down at the same time. When you use the minimum down-time patching method, the following actions occur:The local node is always patched first. The local node is used as a base to patch the other nodes. The user is prompted for the first set of nodes to patch. For each node in this first set, the user is asked to stop the instance and then the patch is propagated and applied to that node before continuing to the next node. When the first set of nodes has been patched, the user is asked to shut down Clusterware on the remaining nodes. The instances are stopped on the last set of remote nodes. The patch is propagated to the last set of nodes and the inventory is updated. You can then start up the patched nodes (the first set of nodes) before patching the remaining nodes. D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 4 – 44

If you are using Grid Naming Service (GNS):$ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2}" If you are not using GNS:$ ./addNode.sh -silent "CLUSTER_NEW_NODES={node2}" "CLUSTER_NEW_VIRTUAL_ HOSTNAMES={node2-vip}" Alternatively, you can specify the entries in a response file, where file_name is the name of the file, and run the addNode.sh script, as follows:$ addNode.sh -silent -responseFile file_name When the addNode.sh script completes, a message window displays a list of nodes in the cluster and root scripts that must be run on those nodes. Oracle® Clusterware Administration and Deployment Guide