Download Oracle.1z0-058.CertKiller.2018-08-19.83q.tqb

$ 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