Radha Swami - Whats is that? Who Started and Meaning ( What I understand ).

Seth Shiv Dayal Singh (also known as Swami Ji or Soami Ji) was born on August 25, 1818 in Agra, Uttar Pradesh, India. He was married at an early age to Naraini Devi whom Rai Saligram used to address as Radha Ji. His father was Seth Dilwali Singh ji and Mother's name was Maha Maya. They used to reside at Panni Gali in Agra and both had taken naam from Tulsi Sahib of Hath Ras. Seth Shiv Dayal ji had no guru.

Seth Shiv Dayal ji started his faith on "Satnaam" and "Anami" but Radha Soami name was coined by Rai Saligram. Rai Saligram used to address Naraini Devi (Wife of Shiv Dayal Ji) as "Radha Ji" and this is where the name "Radha Soami" originated. Later on the Gurus gave a meaning to this word "Radha Soami" with Radha meaning "Soul" and Soami meaning "Lord", hence "Lord of the Soul". But in reality Radha Soami is addressed to Shiv Dayal Ji because Narayani Devi ji was addressed as Radha ji and her husband as Radha's Soami.

During the terminal moments of his life, as written in the book "Saar Bachan Radha Soami" Seth Shiv Dayal ji made it very clear that he did not start the Radha Soami faith as his faith was that of "Satnaam & Anami" and said that Radha Soami faith has been started by Rai Saligram.

RACcheck – RAC Configuration Audit Tool

While reading new features of oracle 11gR2 ( 11.2.0.4),  raccheck really looks interesting to me. Initially, I was struggling to get its location ( I found it CRS_HOME/suptools/raccheck ) directory. Oracle has really improved this and for me it is working fine and telling few basic things which someone may miss. 

 RACcheck is a tool developed by the RAC Assurance development team for use by customers to automate the assessment of RAC systems for known configuration problems and best practices.

RACcheck is a RAC Configuration Audit tool  designed to audit various important configuration settings within a Real Application Clusters (RAC), Oracle Clusterware (CRS), Automatic Storage Management (ASM) and Grid Infrastructure environment. The tool audits configuration settings within the following categories:

• OS kernel parameters
• OS packages
• Many other OS configuration settings important to RAC.
• CRS/Grid Infrastructure
• RDBMS
• ASM
• Database parameters
• Many other database configuration settings important to RAC.

Features
1. RACcheck is NON-INTRUSIVE and does not change anything in the environment, except as detailed below:

- SSH user equivalence for the RDBMS software owner is assumed to be configured among all the database servers being audited in order for it to execute commands on the remote database server nodes. If the tool determines that this user equivalence is not established it will offer to set it up either temporarily or permanently at the option of the user. If the user chooses to set up SSH user equivalence temporarily then the script will do so for the duration of the execution of the tool but then it will return the system to the state in which it found SSH user equivalence originally. For those wishing to configure SSH user equivalence outside the tool (if not already configured), consult My Oracle Support Note: 372795.1.

- RACcheck creates a number of small output files into which the data necessary to perform the assessment is collected

- RACcheck creates and executes some scripts dynamically in order to accomplish some of the data collection

- RACcheck cleans up after itself any temporary files that are created and not needed as part of the collection.

2. RACcheck interrogates the system to determine the status of the Oracle stack components (ie., Grid Infrastructure, RDBMS, RAC, etc) and whether they are installed and/or running. Depending upon the status of each component, the tool runs the appropriate collections and audit checks. If due to local environmental configuration the tool is unable to properly determine the needed environmental information please refer to the TROUBLESHOOTING section.

3. Watchdog daemon – RACcheck automatically runs a daemon in the background to monitor command execution progress. If, for any reason, one of the commands run by the tool should hang or take longer than anticipated, the monitor daemon kills the hung command after a configurable timeout so that main tool execution can progress. If that happens then the collection or command that was hung is skipped and a notation is made in the log. If the default timeout is too short please see the TROUBLESHOOTING section regarding adjustment of the RAT_TIMEOUT, and RAT_ROOT_TIMEOUT parameters.

4. If RACcheck’s driver files are older than 90 days, the driver files are considered to be “stale” and the script will notify the user of a stale driver file. A new version of the tool and its driver files (kit) must be obtained from MOS Note 1268927.1.

5. When the RACcheck completes the collection and analysis it produces two reports, summary and detailed. A output .zip file is also produced by RACcheck. This output .zip file can be provided to Oracle Support for further analysis if an SR needs to be logged. The detailed report will contain Benefit/Impact, Risk and Action/Repair information. In many cases it will also reference publicly available documents with additional information about the problem and how to resolve it.

6. The results of the audit checks can be optionally uploaded into database tables for reporting purposes. See below for more details on this subject.

7. In some cases customers may want to stage RACcheck on a shared filesystem so that it can be accessed from various systems but be maintained in a single location rather than being copied to each cluster on which it may be used. The default behavior of the tool is to create a subdirectory and its output files in the location where the tool is staged. If that staging area is a read only filesystem or if the user for any reason would like the output to be created elsewhere then there is an environment variable which can be used for that purpose. The RAT_OUTPUT parameter can be set to any valid writable location and the output will be created there.

Applies to:

• Oracle Server – Enterprise Edition – Version: 10.2.0.1 to 11.2.0.2 – Release: 10.2 to 11.2
• Linux x86
• IBM AIX on POWER Systems (64-bit)
• Oracle Solaris on SPARC (64-bit)
• Linux x86-64

To download RAC Check tool use this note on MoS:

RACcheck – RAC Configuration Audit Tool [ID 1268927.1]

http://docs.oracle.com/cd/E11882_01/rac.112/e41960/racchk.htm#RACAD8365

RACcheck Usage

•  When using RACcheck, consider the following:Run RACcheck on Oracle Database servers as the Oracle Database software owner (oracle).
•  RACcheck includes a daemon that enables RACcheck to run noninteractively (in batch or silent mode) at regular intervals.
• Oracle recommends that you install and run RACcheck from a local file system on a single database server to provide the best performance.
•  To maximize its usefulness, run RACcheck when Oracle Grid Infrastructure and at least one database are up and running.
•  Oracle recommends that you run RACcheck during times of least load on the system.
•  To avoid possible problems running RACcheck from terminal sessions on a network attached workstation or laptop, consider running the tool using VNC so that, if there is a network interruption, then the tool will continue to run until it is finished.
•  If RACcheck fails for some reason, then you can run it again from the beginning. RACcheck does not resume from the point of failure.
•  You can run RACcheck on all nodes, simultaneously. To take advantage of the root-specific checks while still running the tool in parallel, use the EXPECT utility installed on the system or configure sudo for RACcheck to use.
• To configure sudo, use the visudo command to add the following line to the sudoers file on each of the cluster nodes, replacing owner with the user that installed the database software:

owner ALL=(root)  NOPASSWD:/tmp/root_raccheck.sh

Ensure that permissions for RACcheck are 755 (-rwxr-xr-x). If the permissions are not set appropriately, then run the following command:

$ chmod 755 raccheck

Using RACcheck

You can run RACcheck interactively or silently, or you can run RACcheck automatically at specified intervals. To run RACcheck interactively, run the following command:

 $ raccheck

 RACcheck prompts you through the auditing process.

 Running RACcheck Using the RACcheck Daemon

 To use the RACcheck daemon, you must first configure the daemon parameters by running the raccheck -set parameter=value command. You can set the following configuration parameters:

AUTORUN_INTERVAL: This parameter defines the time interval at which RACcheck runs, specified in days or hours (d | h). For example:

$ raccheck -set AUTORUN_INTERVAL=1d

The preceding command configures the RACcheck daemon to run every day. If you set this parameter to 0, then the RACcheck daemon will not run automatically. This is the default setting for this parameter.

AUTORUN_FLAGS: This parameter defines how RACcheck runs, using the flags listed in Table D-1. For example:

$ raccheck -set "AUTORUN_INTERVAL=12h;AUTORUN_FLAGS=-profile sysadmin"

The preceding command configures RACcheck to run the sysadmin profile every 12 hours.

PASSWORD_CHECK_INTERVAL: This parameter defines the frequency (specified in hours) with which the running daemon validates the passwords entered when the daemon starts. If the daemon encounters an invalid password (due to a password change), then the daemon stops running and enters a notification in the daemon log (raccheck_daemon.log), and also sends an email, if configured to do so. For example:

$ raccheck -set PASSWORD_CHECK_INTERVAL=1

The preceding command validates passwords every hour.

NOTIFICATION_EMAIL: This parameter configures the RACcheck daemon to email notifications to a specific person. For example:

$ raccheck -set NOTIFICATION_EMAIL=firstname.lastname@company.comTo obtain the current configuration of all of the parameters of the RACcheck daemon, run the following command:

$ raccheck -get all

The preceding command returns output similar to the following:

AUTORUN_INTERVAL = 1d

AUTORUN_FLAGS = -o verbose

NOTIFICATION_EMAIL = firstname.lastname@company.com

PASSWORD_CHECK_INTERVAL = 1

You can set or modify RACcheck parameters after the RACcheck daemon has started.

 To start the RACcheck daemon, run the following command:

 $ raccheck –d start

 RACcheck launches an interactive graphical user interface to collect the required information and start the daemon process.

 You can run RACcheck on demand while the RACcheck daemon is running by entering raccheck on the command line without any arguments as the user that started the daemon process from the same directory from which you launched the RACcheck daemon. Running RACcheck this way is non-interactive, because the daemon passes parameters at all the prompts, and produces output on the screen similar to that which RACcheck produces when running interactively.

Note:

If the RACcheck daemon is running and want to run RACcheck interactively, then run the following command:

$ raccheck -nodaemon

Comparing Reports with RACcheck

 You can use RACcheck to compare results from two RACcheck reports. You can use the results of comparisons to monitor trends and best practice changes over time or after planned maintenance presented in a user-friendly HTML report. Ensure that the RACcheck reports in the RACcheck output directories, .zipoutput files, or HTML reports are accessible.

 To compare two RACcheck reports, run the following command:

 $ raccheck -diff report_1 report_2

 Specify the names of the two report files you want to compare. When RACcheck finishes comparing the two files, the utility prints a summary and provides a location of the comparison report for viewing.

 Excluding Audit Checks

 Optionally, you can exclude one or more audit checks after the first run of RACcheck, as follows:

Create a text file named excluded_check_ids.txt in the same directory as the RACcheck script and driver files.

Open the raccheck.log file, which is located in the output directory of the previous run of the tool.

Search for the audit checks that you want to exclude in subsequent runs.

Note the CHECK_ID of the audit checks you want to exclude. The CHECK ID is an alphanumeric string similar to CHECK_ID = 65E4DC8B76BC4DA6E040E50A1EC03704. If the audit check block does not contain a CHECK_ID line, then you cannot exclude that audit check.

Enter the CHECK_IDs for the audit checks that you want to exclude in the excluded_check_ids.txt file, one CHECK_ID per line.

Subsequently, when you run RACcheck, before the tool runs an audit check, it checks the excluded_check_ids.txt file for any excluded checks and skips them.

Certified - MongoDB - For DBA and Adv Deployments

Details SRVCTL - Oracle RAC Command

config

The srvctl config command displays the configuration stored in the Oracle Clusterware resource attributes.

If you disabled an object for which you are trying to obtain configuration information using the srvctl disable object -nnode_name command, then bear in mind that using the srvctl disable object -n node_name command on a per-node basis in your cluster to disable an object throughout the cluster is not the same as globally disabling an object using the srvctl disable object command without the -n option. In the former case, the srvctl config object command may report that the object is still enabled.

disable

Disables a specified object (cluster database, database instance, Oracle ASM instance, or service). Use the srvctl disable command when you must shut down an object for maintenance. The disabled object does not automatically restart.

When you issue the disable command, the object is disabled and unavailable to run under Oracle Clusterware for automatic startup, failover, or restart. Additionally, you cannot run the srvctl start command on a disabled object until you first re-enable the object. If you specify -i instance_name or -nnode_name, then SRVCTL only disables the object on the specified instance or node.

If you do not specify -i instance_name or -n node_name, then the disable action applies to the object that you specified, globally, on all nodes in the cluster. Any object you disable globally is also disabled on any nodes you add to the cluster in the future.

Disabling an object globally is not the same as disabling an object locally on each node in the cluster. For example, if you disable a database on several nodes, individually, in a cluster, then, when you run the srvctl start database command, the database starts only on nodes where the database is enabled. If, however, you disable the database globally, then the srvctl start database is rejected because the database is disabled, clusterwide.

enable

The srvctl enable command enables the specified object so that it can run under Oracle Clusterware for automatic startup, failover, or restart. The Oracle Clusterware application supporting the object may be up or down to use this function. The default value is enable. If the object is already enabled, then the command is ignored. Enabled objects can be started, and disabled objects cannot be started.

getenv

Gets and displays values for the environment variables from the configuration file. Use SRVCTL with the setenv, getenv, and unsetenv verbs to administer the environment configurations for databases, instances, services, and node applications.

setenv

The setenv command sets values for the environment in the configuration file. Use setenv to set environment variables—items such as language or TNS_ADMIN—for Oracle Clusterware that you would typically set in your profile or session when you manage this database or database instance.

ASM

srvctl status asm [-n node_name] [-a] [-v]

srvctl start asm –n racdb1

srvctl stop asm -n racdb1 -i +asm1

srvctl config asm [-a]

srvctl config asm -a

srvctl disable asm [-n node_name]

srvctl disable asm -n crmnode1

srvctl enable asm [-n node_name]

srvctl enable asm -n crmnode1

Database

srvctl status database –d racdb -v

srvctl stop database -d db_unique_name [-o stop_options] [-f]

srvctl stop database -d racdb –o immediate

srvctl start database -d db_unique_name [-o start_options] [-n node_name]

srvctl start database -d racdb [-o start_options] [-n node_name]

srvctl config database [-d db_unique_name] [-a]

srvctl config database -d myDB

srvctl disable database -d db_unique_name [-n node_name]

srvctl disable database -d mydb1

srvctl enable database -d db_unique_name [-n node_name]

srvctl enable database -d mydb1

Diskgroup

srvctl status diskgroup DATA –v -a

srvctl stop diskgroup -g diskgroup_name [-n node_list] [-f]

srvctl stop diskgroup -g Data [-n node_list] [-f]

srvctl start diskgroup -g diskgroup_name [-n node_list]

srvctl start diskgroup -g diskgroup1 -n mynode1,mynode2

srvctl disable diskgroup -g diskgroup_name [-n node_list]

srvctl disable diskgroup -g diskgroup1 -n mynode1, mynode2

srvctl enable diskgroup -g diskgroup_name [-n node_list]

srvctl enable diskgroup -g diskgroup1 -n mynode1,mynode2

Instance

srvctl status instance -d db_unique_name {-n node_name | -i "instance_name_list"}

srvctl status instance -d racdb –i racdb1,racdb2 –v 

srvctl start instance -d db_unique_name {-n node_name -i "instance_name_list"}

     [-o start_options]

srvctl start instance -d crm -n node2

srvctl start instance -d crm -i "crm2,crm3"

srvctl stop instance -d db_unique_name {[-n node_name]|[-i "instance_name_list"]}

     [-o stop_options] [-f]

srvctl stop instance -d crm -n node1

srvctl stop instance -d crm -i crm1

srvctl disable instance -d db_unique_name -i instance_name_list

srvctl disable instance -d crm -i "crm1,crm3"

srvctl enable instance -d db_unique_name -i instance_name_list

srvctl enable instance  -d crm -i "crm1,crm2"

Listener

srvctl status listener 

srvctl start listener –n racdb1

srvctl stop listener –n racdb1 

srvctl config listener [-l listener_name] [-a]

srvctl disable listener [-l listener_name] [-n node_name]

srvctl disable listener -l listener_crm -n node5

srvctl enable listener [-l listener_name] [-n node_name]

srvctl enable listener -l listener_crm -n node5

  

Node Apps

srvctl status nodeapps 

srvctl start nodeapps

srvctl stop nodeapps [-n node_name] [-g] [-r] [-f] [-v]

srvctl stop nodeapps

srvctl disable nodeapps [-g] [-v]

srvctl disable nodeapps -g -v

srvctl enable nodeapps [-g] [-v]

srvctl enable nodeapps -g -v

SCAN and SCAN Listener

srvctl status scan_listener

srvctl status scan –i 1

srvctl start scan [-i ordinal_number] [-n node_name]

srvctl start scan -i 1 -n node1

srvctl stop scan [-i ordinal_number] [-f]

srvctl stop scan -i 1

srvctl disable scan_listener [-i ordinal_number]

srvctl disable scan_listener -i 1

srvctl enable scan_listener [-i ordinal_number]

srvctl enable scan_listener -i 1

Server Status

srvctl status server –n racdb1 -a

VIP Status

srvctl status vip –n racdb1 -a

srvctl disable vip -i vip_name [-v]

srvctl disable vip -i vip1 -v

srvctl enable vip -i vip_name [-v]

srvctl enable vip -i crm1-vip -v

Oracle RAC Commands

The following example lists all the background processes initially started by Grid Infrastructure after a fresh installation:

crsctl status resource -init -t

Listing Vote Disk

crsctl query css votedisk

Checking Cluster

crsctl check cluster -all

Checking Cluster Resources

crsctl status res |grep -v "^$"|awk -F "=" 'BEGIN {print " "} {printf("%s",NR%4 ? $2"|" : $2"\n")}'|sed -e 's/  *, /,/g' -e 's/, /,/g'|\
awk -F "|" 'BEGIN { printf "%-40s%-35s%-20s%-50s\n","Resource Name","Resource Type","Target ","State" }{ split ($3,trg,",") split ($4,st,",")}{for (i in trg) {printf "%-40s%-35s%-20s%-50s\n",$1,$2,trg[i],st[i]}}'

Start Oracle Clusterware

#crsctl start crs

Stop Oracle Clusterware

#crsctl stop crs

Enable Oracle Clusterware

#crsctl enable crs

It enables automatic startup of Clusterware daemons

Disable Oracle Clusterware

#crsctl disable crs

Checking Voting disk Location

$crsctl query css votedisk

Check CRS Status

$crsctl check crs

$crsctl check cssd

$crsctl check crsd

$crsctl check evmd

$crsctl check cluster

crsctl check cluster -all

Checking Oracle Clusterware Version

To determine software version (binary version of the software on a particular cluster node) use

$crsctl query crs softwareversion

$ crsctl query crs activeversion

To get database status and etails

srvctl status database -d racdb

Cluvfy commands - Oracle RAC

If you type ‘cluvfy’ on the command prompt, cluvfy displays the high level generic usage text, which talks about valid stage and component syntax.

If you type ‘cluvfy comp -list’, cluvfy will show valid components with brief description on each of them.
If you type ‘cluvfy comp -help’, cluvfy will show detail syntax for each of the valid components.
Similarly, ‘cluvfy stage -list’ and ‘cluvfy stage -help’ will list valid stages and their syntax respectively.

If you type an invalid command, cluvfy will show the appropriate usage for that particular command.
For example, if you type ‘cluvfy stage -pre dbinst’, cluvfy will show the syntax for pre-check of dbinst stage.

Cluvfy comp commands:
===========================
cluvfy comp nodereach -n all — verifying node reachability
cluvfy comp nodecon -n all — verifying node connectivity
cluvfy comp ssa -n all — verifying shared storage raw devices
cluvfy comp space -n all -l /soft/app/oracle -z 500G — verifying space requirement
cluvfy comp sys -n all -p crs — verifying system requirement
cluvfy comp sys -n all -p database — verifying system requirement
cluvfy comp clu -n all – verifying cluster intergrity
cluvfy comp clumgr -n all — verifying cluster manager intergrity
cluvfy comp ocr -n all — Verifying OCR integrity. Run ocrcheck in addition to this.
cluvfy comp olr — Verifying OLR integrity. Run ocrcheck -local’ to verify the contents of OLR
cluvfy comp ha — Verifying Oracle Restart integrity, not valid for RAC
cluvfy comp freespace -n all — Verifying Free Space
cluvfy comp crs -n all — Verifying CRS integrity
cluvfy comp nodeapp -n all —- Verifying node application existence
cluvfy comp admprv -n all -o crs_inst —- Verifying administrative privileges for crs instance
cluvfy comp admprv -n all -o db_inst —- Verifying administrative privileges for db instance
cluvfy comp admprv -n all -o db_config -d /soft/app/oracle/product/11.2.0 —- Verifying administrative privileges for db instance
cluvfy comp peer -n all — verifying peer compatbility
cluvfy comp software -n all — Verifying software
cluvfy comp acfs -n all — Verifying ACFS Integrity
cluvfy comp asm -n all — Verifying ASM Integrity
cluvfy comp gpnp -n all — verify Grid Plug and Play integrity. This feature is used to extend the RAC, addition of nodes
without the help of network admins.
cluvfy comp gns -precrsinst -n all — Verify global name service when DHCP is used instead of the DNS.
cluvfy comp gns -postcrsinst — Verify global name service when DHCP is used instead of the DNS. We are not using this.
cluvfy comp scan —- Verifying scan, Checking Single Client Access Name (SCAN).
cluvfy comp ohasd — Verifying OHASD integrity
cluvfy comp clocksync -n all — Verifying Clock Synchronization across the cluster nodes
cluvfy comp vdisk -n all — verifying voting disk
cluvfy comp healthcheck -collect cluster -mandatory -deviations -html -save /soft/app/oracle — Verifying OS mandatory requirements
cluvfy comp healthcheck -collect database -mandatory -deviations — same as above for the database
cluvfy comp dhcp -clustername crs-cluster — verifying DHCP check. Run as root.
cluvfy comp dns -server -domain — For DHCP connectivity.
cluvfy comp dns -client -domain — For DHCP connectivity.

Cluvfy comp USAGE:
——————-
cluvfy comp [-verbose]

SYNTAX (for Components):
cluvfy comp nodereach -n [-srcnode ] [-verbose]
cluvfy comp nodecon -n [-i ] [-verbose]
cluvfy comp ssa [-n ] [-s ] [-t {software|data|ocr_vdisk}] [-verbose]
cluvfy comp space [-n ] -l -z {B|K|M|G} [-verbose]
cluvfy comp sys [-n ] -p {crs|ha|database} [-r {10gR1|10gR2|11gR1|11gR2}] [-osdba ]
[-orainv ] [-fixup [-fixupdir ]]
[-verbose]
cluvfy comp clu [-n ] [-verbose]
cluvfy comp clumgr [-n ] [-verbose]
cluvfy comp ocr [-n ] [-verbose]
cluvfy comp olr [-verbose]
cluvfy comp ha [-verbose]
cluvfy comp freespace [-n ]
cluvfy comp crs [-n ] [-verbose]
cluvfy comp nodeapp [-n ] [-verbose]
cluvfy comp peer -n [-refnode ] [-r {10gR1|10gR2|11gR1|11gR2}] [-osdba ]
[-orainv ] [-verbose]
cluvfy comp software [-n ] [-d ] [-r {10gR1|10gR2|11gR1|11gR2}] [-verbose]
cluvfy comp acfs [-n ] [-f ] [-verbose]
cluvfy comp asm [-n ] [-verbose]
cluvfy comp gpnp [-n ] [-verbose]
cluvfy comp
gns -precrsinst -domain -vip [-n ] [-verbose]
gns -postcrsinst [-verbose]
cluvfy comp scan [-verbose]
cluvfy comp ohasd [-n ] [-verbose]
cluvfy comp clocksync [-n ] [-noctss] [-verbose]
cluvfy comp vdisk [-n ] [-verbose]
cluvfy comp healthcheck [-collect {cluster|database}] [-db ] [-bestpractice|-mandatory] [-deviations]
[-html] [-save [-savedir ]]
cluvfy comp dhcp -clustername [-vipresname ] [-port ] [-n ]
[-verbose]
cluvfy comp
dns -server -domain -vipaddress [-port ] [-verbose]
dns -client -domain -vip [-port ] [-last]
[-verbose]

————————————————————————–

cluvfy stage commands:
—————————

cluvfy stage -pre crsinst -n all — Performing pre-checks for cluster services setup
cluvfy stage -pre acfscfg -n all — Performing pre-checks for ACFS Configuration, could not find the type for shared storage.
cluvfy stage -pre dbinst -n all —- Performing pre-checks for database installation
cluvfy stage -pre dbcfg -n all -d /soft/app/oracle/product/crs — Performing pre-checks for database configuration
cluvfy stage -pre hacfg — Pre-check for Oracle Restart configuration
cluvfy stage -pre nodeadd -n all — Pre-check for node addition was successful
cluvfy stage -post hwos -n all — Performing post-checks for hardware and operating system setup
cluvfy stage -post crsinst -n all — Performing post-checks for cluster services setup
cluvfy stage -post acfscfg -n all — Performing post-checks for ACFS Configuration, could not find the type for shared storage.
cluvfy stage -post hacfg — Post-check for Oracle Restart configuration
cluvfy stage -post nodeadd -n all — Post-check for node addition was successful
cluvfy stage -post nodedel -n all — Post-check for node deletion was successful

Cluvfy stage USAGE:
——————
USAGE:
cluvfy stage {-pre|-post} [-verbose]

SYNTAX (for Stages):
cluvfy stage -pre
crsinst -file [-fixup [-fixupdir ]] [-verbose]
crsinst -upgrade [-n ] [-rolling] -src_crshome -dest_crshome
-dest_version [-fixup [-fixupdir ]] [-verbose]
crsinst -n [-r {10gR1|10gR2|11gR1|11gR2}]
[-c ] [-q ]
[-osdba ] [-orainv ]
[-asm [-asmgrp ] [-asmdev ]] [-crshome ]
[-fixup [-fixupdir ]] [-networks ]
[-verbose]
cluvfy stage -pre acfscfg -n [-asmdev ] [-verbose]
cluvfy stage -pre
dbinst -n [-r {10gR1|10gR2|11gR1|11gR2}] [-osdba ] [-d ]
[-fixup [-fixupdir ]] [-verbose]
dbinst -upgrade -src_dbhome [-dbname ] -dest_dbhome -dest_version
[-fixup [-fixupdir ]] [-verbose]
cluvfy stage -pre dbcfg -n -d [-fixup [-fixupdir ]] [-verbose]
cluvfy stage -pre hacfg [-osdba ] [-orainv ] [-fixup [-fixupdir ]] [-verbose]
cluvfy stage -pre nodeadd -n [-vip ] [-fixup [-fixupdir ]] [-verbose]
cluvfy stage -post hwos -n [-s ] [-verbose]
cluvfy stage -post crsinst -n [-verbose]
cluvfy stage -post acfscfg -n [-verbose]
cluvfy stage -post hacfg [-verbose]
cluvfy stage -post nodeadd -n [-verbose]
cluvfy stage -post nodedel -n [-verbose]

———————————————————————–

crsctl commands:
———————
$ crsctl -help
Usage: crsctl add – add a resource, type or other entity
crsctl check – check a service, resource or other entity
crsctl config – output autostart configuration
crsctl debug – obtain or modify debug state
crsctl delete – delete a resource, type or other entity
crsctl disable – disable autostart
crsctl discover – discover DHCP server
crsctl enable – enable autostart
crsctl get – get an entity value
crsctl getperm – get entity permissions
crsctl lsmodules – list debug modules
crsctl modify – modify a resource, type or other entity
crsctl query – query service state
crsctl pin – pin the nodes in the node list
crsctl relocate – relocate a resource, server or other entity
crsctl replace – replaces the location of voting files
crsctl release – release a DHCP lease
crsctl request – request a DHCP lease
crsctl setperm – set entity permissions
crsctl set – set an entity value
crsctl start – start a resource, server or other entity
crsctl status – get status of a resource or other entity
crsctl stop – stop a resource, server or other entity
crsctl unpin – unpin the nodes in the node list
crsctl unset – unset an entity value, restoring its default

Below commands are deprecated in 11gr2:
—————————————-
The following commands are deprecated in Oracle Clusterware 11g release 2 (11.2):

crs_stat
crs_register
crs_unregister
crs_start
crs_stop
crs_getperm
crs_profile
crs_relocate
crs_setperm
crsctl check crsd
crsctl check cssd
crsctl check evmd
crsctl debug log
crsctl set css votedisk
crsctl start resources
crsctl stop resources

CRSCTL Overview
——————
CRSCTL is an interface between you and Oracle Clusterware, parsing and calling Oracle Clusterware
APIs for Oracle Clusterware objects.
Oracle Clusterware 11g release 2 (11.2) introduces cluster-aware commands with which you can perform check,
start, and stop operations on the cluster. You can run these commands from any node in the cluster on another
node in the cluster, or on all nodes in the cluster, depending on the operation.

You can use CRSCTL commands to perform several operations on Oracle Clusterware, such as:
———————————————————-
Starting and stopping Oracle Clusterware resources
Enabling and disabling Oracle Clusterware daemons
Checking the health of the cluster
Managing resources that represent third-party applications
Integrating Intelligent Platform Management Interface (IPMI) with Oracle Clusterware to provide
failure isolation support and to ensure cluster integrity
Debugging Oracle Clusterware components

Clusterized commands:
———————-
crsctl check cluster
crsctl start cluster
crsctl stop cluster

Add resource commands: —- command to register a resource to be managed by Oracle Clusterware.
A resource could be an application process, a database, a service, a listener, and so on.
——————-
crsctl add resource

To register a VIP as a resource with Oracle Clusterware:
———————
$ crsctl add resource app.appvip -type app.appvip.type -attr “RESTART_ATTEMPTS=2,
START_TIMEOUT=100,STOP_TIMEOUT=100,CHECK_INTERVAL=10,
USR_ORA_VIP=172.16.0.0,
START_DEPENDENCIES=hard(ora.net1.network)pullup(ora.net1.network),
STOP_DEPENDENCIES=hard(ora.net1.network)”

To register a resources based on the test_type1 resource type:
———————————-
$ crsctl add resource r1 -type test_type1 -attr “PATH_NAME=/tmp/r1.txt”
$ crsctl add resource r1 -type test_type1 -attr “PATH_NAME=/tmp/r2.txt”

Add type commands: — Use the crsctl add type command to create a resource type in Oracle Clusterware.
——————–
crsctl add type test_type1 -basetype cluster_resource
-attr “ATTRIBUTE=FOO,TYPE=integer,DEFAULT_VALUE=0″

crsctl check css: — Use the crsctl check css command to check the status of Cluster Synchronization Services.
——————
crsctl check css

crsctl delete resource: — Use the crsctl delete resource command to remove
resources from the Oracle Clusterware configuration

Learning Amazon - https://run.qwiklabs.com/

Hi Guys,

If you would like to have test, how to setup ec2 or Amazon RDS, you can use below quick labs which are really helpful.

https://run.qwiklabs.com/

Cheers.