Download Oracle Real Application Clusters 11g Release 2 and Grid Infrastructure Administration.1z0-058.CertKiller.2018-08-19.83q.vcex

$ 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

There are buttons for Create, Show Mount All, and Show Dismount All commands root privilege is required to run mount. Windows Administrator privileges are required to mount an Oracle ACFS On this page, you can choose to mount, dismount, delete, create snapshot, view content, register, and deregister a selected file system. In addition, you can create a file system, mount all file systems, or dismount all file systems. Oracle® Automatic Storage Management Administrator's Guide

Stripe column and stripe width are two important attributes that can be specified for a volume determining how space is allocated for a volume and how space is allocated within a volume after ACFS or third party file system is created on a volume and a file is created or extended on the file system built on that volume. Both attributes are specified at volume creation time and cannot be changed later. If there is no value a default value is used. Volume Allocation Unit (VAU) is the smallest allocation for a volume. Whenever a volume is created or extended space is allocated in multiple of VAU. VAU size is determined by the Volume Extent (VE) and the stripe column. VAU is the product of VE and the stripe column. Volume Extent is based on the Allocation Unit (AU) specified on a disk group and for AU with size of 1MB the VE is 64MB. Whenever a VAU is allocated VE are allocated in a round robin fashion across the disks in a disk group. Volume size is always multiple of the VAU. For example if a volume is requested with size 200MB and stripe column is 4 and AU is 1MB one VAU with size 256MB will be allocated and the volume size will be 256MB

Start Dependencies hard Define a hard start dependency for a resource if another resource must be running before the dependent resource can start. For example, if resource A has a hard start dependency on resource B, then resource B must be running before resource A can start. Note:Oracle recommends that resources with hard start dependencies also have pullup start dependencies. weak If resource A has a weak start dependency on resource B, then an attempt to start resource A attempts to start resource B, if resource B is not running. The result of the attempt to start resource B is, however, of no consequence to the result of starting resource A. attraction If resource A has an attraction dependency on resource B, then Oracle Clusterware prefers to place resource A on servers hosting resource B. Dependent resources, such as resource A in this case, are more likely to run on servers on which resources to which they have attraction dependencies are running. Oracle Clusterware places dependent resources on servers with resources to which they are attracted. pullup Use the pullup start dependency if resource A must automatically start whenever resource B starts. This dependency only affects resource A if it is not running. As is the case for other dependencies, pullup may cause the dependent resource to start on any server. Use the pullup dependency whenever there is a hard stop dependency, so that if resource A depends on resource B and resource B fails and then recovers, then resource A is restarted. dispersion If you specify the dispersion start dependency for a resource, then Oracle Clusterware starts this resource on a server that has the fewest number of resources to which this resource has dispersion. Resources with dispersion may still end up running on the same server if there are not enough servers to disperse them to. Oracle® Clusterware Administration and Deployment Guide 11g Release 2 (11.2)

There are always failure groups even if they are not explicitly created. If you do not specify a failure group for a disk, then Oracle automatically creates a new failure group containing just that disk, except for disk groups containing disks on Oracle Exadata cells.  Oracle® Automatic Storage Management Administrator's Guide

Changing the Automatic OCR Backup Location The automatic backup location should be changed to a location shared by all nodes. # ocrconfig –backuploc <path to shared CFS or NFS> The backup location will be used for both automatic and manual backups. It is recommended that these files be included in routine scheduled backups to an offline location. If CRS has been stopped on all nodes, the schedule of backups is suspended. On restart, a backup is not immediately taken and the backup timer is reset. D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 3 - 12

The ALTER DISKGROUP VOLUME SQL statements enable you to manage Oracle ADVM volumes, including the functionality to add, modify, resize, disable, enable, and drop volumes.  You can create an Oracle ASM Dynamic Volume Manager (Oracle ADVM) volume in a disk group. The volume device associated with the dynamic volume can then be used to host an Oracle ACFS file system.  If the volume is hosting an Oracle ACFS file system, then you cannot resize that volume with the SQL ALTER DISKGROUP statement. Instead you must use the acfsutil size command. volcreate  Creates an Oracle ADVM volume in the specified disk group. Syntax and Description volcreate -G diskgroup -s size [ --column number ] [ --width stripe_width ]  [--redundancy {high|mirror|unprotected} ]  Redundancy of the Oracle ADVM volume which can be specified for normal redundancy disk groups. The range of values is as follows: unprotected for non-mirrored redundancy, mirror for double-mirrored redundancy, or high for triple-mirrored redundancy. If redundancy is not specified, the setting defaults to the redundancy level of the disk group.