Satya's Oracle RAC Blog

50 frequently asked Oracle DBA RAC Interview Questions Part2 [ 2023 ]

2023-06-28T10:33:00.000+05:30

Oracle RAC Interview Questions/FAQs Part2 [2023]

22. What is split-brain syndrome?
Answer:
Split brain will arise when two or more instances attempt to control a cluster database. In a two-node environment, one instance attempts to manage updates simultaneously while the other instance attempts to manage updates.

23. What are various IPs used in RAC? Or How many IPs do we need in RAC?
Answer:
Public IP, Private IP, Virtual IP, SCAN IP

24. What is the use of virtual IP (VIP)?
Answer:
When a node fails, the VIP associated with it is automatically failed over to some other node and the new node re-arps the world indicating a new MAC address for the IP. Subsequent packets sent to the VIP go to the new node, which will send error RST packets back to the clients. This results in the clients getting errors immediately.

Without using VIPs or FAN, clients connected to a node that died will often wait for a TCP timeout period (which can be up to 10 min) before getting an error. As a result, you don't really have a good HA solution without using VIPs.

25. What is the use of SCAN IP (SCAN name) and will it provide load balancing?
Answer:
Single Client Access Name (SCAN) was introduced in Oracle Real Application Clusters (RAC) 11g Release 2, feature that provides a single name for clients to access an Oracle Database running in a cluster. The benefit is clients using SCAN do not need to change if you add or remove nodes in the cluster.

26. How many SCAN listeners will be running?
Answer:
Three SCAN listeners only, irrespective of the number of nodes in the cluster.

27. What is FAN?
Answer:
Applications can use Fast Application Notification (FAN) to enable rapid failure detection, balancing of connection pools after failures, and re-balancing of connection pools when failed components are repaired. The FAN process uses system events that Oracle publishes when cluster servers become unreachable or if network interfaces fail.

28. What is FCF?
Answer:
Fast Connection Failover (FCF) provides high availability to FAN integrated clients, such as clients that use JDBC, OCI, or ODP.NET. If you configure the client to use fast connection failover, then the client automatically subscribes to FAN events and can react to database UP and DOWN events. In response, Oracle gives the client a connection to an active instance that provides the requested database service.

29. What is TAF and TAF policies?
Answer:
Transparent Application Failover (TAF) - A runtime failover for high availability environments, such as Real Application Clusters, TAF refers to the failover and re-establishment of application-to-service connections. It enables client applications to automatically reconnect to the database if the connection fails, and optionally resume a SELECT statement that was in progress. This reconnect happens automatically from within the Oracle Call Interface (OCI) library.

30. How will you upgrade the RAC database?
Answer:

31. What are rolling patches and how to apply them?
Answer:

32. How to add/remove a node?
Answer:

33. What are nodeapps?
Answer:
VIP, listener, ONS, GSD

34. What is gsd (Global Service Daemon)?
Answer:

35. How to do load balancing in RAC?
Answer:

36. What are the uses of services? How to find out the services in the cluster?
Answer:
Applications should use the services to connect to the Oracle database. Services define rules and characteristics (unique name, workload balancing, failover options, and high availability) to control how users and applications connect to database instances.

37. How to find out the nodes in the cluster (or) how to find out the master node?
Answer:
To find out which is the master node, use any one of the below.
i) # olsnodes -- Which ever displayed first, is the master node of the cluster.
ii) select MASTER_NODE from v$ges_resource;
iii) check ocssd.log file and search for "master node number".
iv) oclumon manage -get master (From Oracle RAC 12c)
v) ocrconfig -manualbackup

https://satya-racdba.blogspot.com/2019/01/oracle-rac-master-node.html

38. How to know the public IPs, private IPs, VIPs in RAC?
Answer:
# olsnodes -n -p -i
node1-pub 1 node1-prv node1-vip
node2-pub 2 node2-prv node2-vip

39. What utility is used to start DB/instance?
Answer:
srvctl start database –d database_name
srvctl start instance –d database_name –i instance_name

40. How can you shutdown a single instance?
Answer:
Change cluster_database=false
srvctl stop instance –d database_name –i instance_name

Best 20 Oracle RAC Interview Questions/FAQs Part1 [ 2023 ]

2023-05-21T17:33:00.000+05:30

Oracle DBA RAC Interview Questions Part1

1. What is the use of Oracle RAC?
Answer:

2. What are the prerequisites for RAC setup?
Answer:

3. What are Oracle Clusterware/Daemon processes and what do they do?
Answer:
ohasd, orarootagent, oragent, ocssd, crsd, ctsd, evmd

4. What are the special background processes for RAC (or) what is the difference between stand-alone database & RAC database background processes?
Answer:
DIAG, LCKn, LMD, LMSn, LMON

5. What were the structural changes in Oracle 11g R2 RAC?
Answer:
http://satya-racdba.blogspot.com/2010/07/new-features-in-9i-10g-11g-rac.html
Grid & ASM are on one home,
Voting disk & ocrfile can be on the ASM,
SCAN,
By using srvctl, we can mange diskgroups, home, ons, eons, filesystem, srvpool, server, scan, scan_listener, gns, vip, oc4j
GSD

6. What were the new features in 11g (R2) Oracle RAC?
Answer:
http://satya-racdba.blogspot.com/2010/07/new-features-in-9i-10g-11g-rac.html

Grid & ASM are on one home,
Voting disk & ocrfile can be on the ASM,
SCAN,
By using srvctl, we can mange diskgroups, home, ons, eons, filesystem, srvpool, server, scan, scan_listener, gns, vip, oc4j
GSD

7. What is cache fusion?
Answer:
Transferring of data between RAC instances by using private network. Cache Fusion is the remote memory mapping of Oracle buffers, shared between the caches of participating nodes in the cluster. When a block of data is read from the datafile by an instance within the cluster and another instance is in need of the same block, it is easy to get the block image from the instance which has the block in its SGA rather than reading from the disk. Oracle RAC uses the interconnect for cache fusion (UDP/RDS).

8. What is the purpose of Private Interconnect?
Answer:
Clusterware uses the private interconnect for cluster synchronization (network heartbeat) and daemon communication between the clustered nodes. This communication is based on the TCP protocol. RAC uses the interconnect for cache fusion (UDP/RDS) and inter-process communication (TCP).

9. What are the Clusterware components?
Answer:
Voting Disk or Voting file - Oracle RAC uses the voting disk/file to manage cluster membership by way of a health check and arbitrates cluster ownership among the instances in case of network failures. The voting disk must reside on shared disk.

Oracle Cluster Registry (OCR) - Maintains cluster configuration information as well as configuration information about any cluster database within the cluster. The OCR must reside on shared disk that is accessible by all of the nodes in the cluster. The daemon OCSSd manages the configuration info in OCR and maintains the changes to the cluster in the registry.

Virtual IP (VIP) - When a node fails, the VIP associated with it is automatically failed over to some other node and new node re-arps the world indicating a new MAC address for the IP. Subsequent packets sent to the VIP go to the new node, which will send error RST packets back to the clients. This results in the clients getting errors immediately.

crsd – Cluster Resource Services Daemon
cssd – Cluster Synchronization Services Daemon
evmd – Event Manager Daemon

10. What is OCR file?
Answer:
RAC configuration information repository that manages information about the cluster node list and instance-to-node mapping information. The OCR also manages information about Oracle Clusterware resource profiles for customized applications. Maintains cluster configuration information as well as database configuration information. The OCR must reside on shared disk that is accessible by all of the nodes in the cluster. The daemon OCSSd manages the configuration info in OCR and maintains the changes to the cluster in the registry.

11. How to take backup of OCR file?
Answer:
#ocrconfig -manualbackup
#ocrconfig -export file_name.dmp
#ocrdump -backupfile my_file
$cp -p -R /u01/app/crs/cdata /u02/crs_backup/ocrbackup/RAC1

12. How to recover OCR file?
Answer:
#ocrconfig -restore backup_file.ocr
#ocrconfig -import file_name.dmp

13. What is local OCR or Oracle Local Registry (OLR)?

Answer:
/etc/oracle/local.ocr (or) /var/opt/oracle/local.ocr

14. How to check backup (location) of OCR files?
Answer:
#ocrconfig –showbackup

15. How do you identify the OCR file location?
Answer:
Check /var/opt/oracle/ocr.loc or /etc/ocr.loc
# ocrcheck

16. Who will manage OCR files?
Answer:
cssd will manage OCR.

17. Who will take backup of OCR files?
Answer:
crsd will take backup.

18. What is a Voting file/disk and how many files should be there?
Answer:
Voting Disk/File is a file on the shared cluster system or a shared raw device file. Oracle Clusterware uses the voting disk to determine which instances are members of a cluster. The voting disk is akin to the quorum disk, which helps to avoid the split-brain syndrome. Oracle RAC uses the voting disk to manage cluster membership by way of a health check and arbitrates cluster ownership among the instances in case of network failures. The voting disk must reside on shared disk.

Number of voting files must be odd i.e. 1, 3, 5, 7, 9, 11, 13, 15(max) etc.

19. How to take backup of voting files?
Answer:
dd if=/u02/ocfs2/vote/VDFile_0 of=$ORACLE_BASE/bkp/vd/VDFile_0
crsctl backup css votedisk -- from 11g R2

20. How do I identify the voting disk location?
Answer:
# crsctl query css votedisk

21. If the voting disk/OCR file got corrupted and doesn’t have backups, how to get them?
Answer:
We have to install Clusterware.

Oracle RAC DBA Interview Questions with answers [ 2023 ]

2023-02-19T13:18:00.000+05:30

Oracle RAC Online Quiz and Answers

Loading...

Related Oracle RAC Articles: Oracle RAC Interview Questions Part2 TFA (Trace File Analyzer)

Background processes in Oracle RAC

2023-01-09T22:02:00.000+05:30

Oracle Real Application Clusters (RAC) Specific Background Processes

Oracle RAC is composed of two or more database instances. They are composed of memory structures and background processes same as the single instance database.

Oracle RAC instances are composed of following background processes:
ACMS — Atomic Control file to Memory Service
GTX0-j — Global Transaction Process
LMON — Global Enqueue Service Monitor
LMD — Global Enqueue Service Daemon
LMS — Global Cache Service Process
LCK0 — Instance Enqueue Process

DIAG — Diagnosability Daemon
RMSn — RAC Management Processes
RSMN — Remote Slave Monitor
DBRM — Database Resource Manager (from 11g R2)

PING — Response Time Agent (from 11g R2)
LMHB — Global Cache/Enqueue Service Heartbeat Monitor
RCBG — Result Cache BackGround Process

These processes spawned for supporting the multi-instance coordination.

ACMS (from Oracle 11g) Atomic Control file Memory Service
In an Oracle RAC environment ACMS background process is an agent that ensures a distributed SGA memory update(ie) SGA updates are globally committed on success or globally aborted in event of a failure.

GTX0-j (from Oracle 11g) Global Transaction Process
The process provides transparent support for XA global transactions in a RAC environment. The database auto tunes the number of these processes based on the workload of XA global transactions.

LMON Global Enqueue Service Monitor (Lock monitor)

The LMON monitors the entire cluster to manage the global enqueues and the resources and performs global enqueue recovery operations. LMON manages instance and process failures and the associated recovery for the Global Cache Service (GCS) and Global Enqueue Service (GES). In particular, LMON handles the part of recovery associated with global resources. LMON provided services are also known as cluster group services (CGS). Lock monitor manages global locks and resources. It handles the redistribution of instance locks whenever instances are started or shutdown. Lock monitor also recovers instance lock information prior to the instance recovery process. Lock monitor co-ordinates with the Process Monitor (PMON) to recover dead processes that hold instance locks.

LMDx Global Enqueue Service Daemon

The LMD is the lock agent process that manages enqueue manager service requests for Global Cache Service enqueues to control access to global enqueues and resources. This process manages incoming remote resource requests within each instance. The LMD process also handles deadlock detection and remote enqueue requests. Remote resource requests are the requests originating from another instance. LMDn processes manage instance locks that are used to share resources between instances. LMDn processes also handle deadlock detection and remote lock requests.

LMSx Global Cache Service Processes

The LMSx are the processes that handle remote Global Cache Service (GCS) messages. Real Application Clusters software provides for up to 10 Global Cache Service Processes. The number of LMSx varies depending on the amount of messaging traffic among nodes in the cluster.

This process maintains statuses of datafiles and each cached block by recording information in a Global Resource Directory(GRD). This process also controls the flow of messages to remote instances and manages global data block access and transmits block images between the buffer caches of different instances. This processing is a part of cache fusion feature.

The LMSx handles the acquisition interrupt and blocking interrupt requests from the remote instances for Global Cache Service resources. For cross-instance consistent read requests, the LMSx will create a consistent read version of the block and send it to the requesting instance. The LMSx also controls the flow of messages to remote instances.

The LMSn processes handle the blocking interrupts from the remote instance for the Global Cache Service resources by:

Managing the resource requests and cross-instance call operations for the shared resources.
Building a list of invalid lock elements and validating the lock elements during recovery.
Handling the global lock deadlock detection and Monitoring for the lock conversion timeouts.

LCKx Instance Enqueue process

This process manages the global enqueue requests and the cross-instance broadcast. Workload is automatically shared and balanced when there are multiple Global Cache Service Processes (LMSx). This process is called as instance enqueue process. This process manages non-cache fusion resource requests such as library and row cache requests. The instance locks that are used to share resources between instances are held by the lock processes.

DIAG Diagnosability Daemon

Monitors the health of the instance and captures the data for instance process failures.

RMSn RAC Management Service
This process is called as Oracle RAC Management Service/Process. These processes perform manageability tasks for Oracle RAC. Tasks include creation of resources related Oracle RAC when new instances are added to the cluster.

RSMN Remote Slave Monitor
This process is called as Remote Slave Monitor. This process manages background slave process creation and communication on remote instances. This is a background slave process. This process performs tasks on behalf of a coordinating process running in another instance.

LMHB Global Cache/Enqueue Service Heartbeat Monitor
LMHB monitors the heartbeat of LMON, LMD, and LMSn processes to ensure they are running normally without blocking or spinning. LMBH trace reports low memory, swap space problem and system average load.

Oracle RAC instances use two processes GES(Global Enqueue Service), GCS(Global Cache Service) that enable cache fusion. The GES and GCS maintain records of the statuses of each datafile and each cached block using global resource directory (GRD). This process is referred to as cache fusion and helps in data integrity.

Oracle RAC is composed of two or more instances. When a block of data is read from datafile by an instance within the cluster and another instance is in need of the same block, it is easy to get the block image from the instance which has the block in its SGA rather than reading from the disk. To enable inter instance communication Oracle RAC makes use of interconnects. The Global Enqueue Service(GES) monitors and Instance enqueue process manages the cache fusion.

Related Oracle Articles: Background processes in normal/stand-alone Oracle Database instance

How to find out the master node ?

2022-03-24T14:44:00.000+05:30

How to find out the nodes in RAC cluster (or)
How to find out the master node in Oracle RAC?

There are several ways to find out which is the master node or all the nodes which are part of Oracle RAC cluster.

Use any one of the below.

i) oclumon manage -get master (in Oracle RAC 12c)

ii) select MASTER_NODE from v$ges_resource;

iii) ocrconfig -manualbackup

iv) check ocssd.log file and search for "master node number".

$ grep "master node number" /u01/app/crs/11.2.0.4/log/`hostname -s`/cssd/ocssd.log

Related Oracle Articles: cluster name of Oracle RAC cluster Oracle RAC Interview Questions Part3

RAID 5 vs RAID 0+1 and Standalone vs Cluster

2021-02-16T16:44:00.000+05:30

The below picture will help us to find out the differences between RAID levels.

(a) Standalone database and Clustered database

(b) RAID 0 and RAID 1

Related Oracle Articles: cluvfy commands RAC crsctl commands RAC srvctl commands RAC

Wait events in Oracle RAC

2020-12-01T12:38:00.000+05:30

Oracle RAC (11g / 12c) wait events

In Oracle 9i and prior, the "gc" was spelled out as "global cache" in the RAC wait events.

In RAC wait event names, CR stands for Consistent Read.
Current - is for DMLs
CR - is for Selects
The difference between CR and Current is that CR requires a block with a given SCN, whereas current does not (current mode fetches the block with the current SCN).

gc buffer busy release => specifies the time the remote instance locally spends accessing the requested data block. Caused may be because of not enough memory on your nodes, overloaded interconnect.
gc buffer busy acquire

gc current request
gc cr request => the time it takes to retrieve the data from the remote cache. Oracle may not pick private interconnect and instead route traffic over slower public network. RAC event similar to buffer busy waits, tune SQL to request less data, tune network latency between RAC nodes, localize data access.

gc cr failure
gc current block lost => Lost blocks due to Interconnect or CPU. Indicates interconnect issues and contention.
gc cr block lost => Lost blocks due to Interconnect or CPU. Indicates interconnect issues and contention.
gc current block corrupt
gc cr block corrupt

gc current block busy => The current block read request was delayed, most likely an I/O bottleneck. Block is already involved in GC operation, shows hot blocks or congestion.
gc cr block busy => The consistent read request was delayed, most likely an I/O bottleneck. Blocks are busy in another instance, check for block level contention or hot blocks.
gc current block congested => Long run queues and/or paging due to memory deficiency. Current block congestion, check for hot blocks or busy interconnect.
gc cr block congested => Long run queues and/or paging due to memory deficiency. cr block congestion, check for hot blocks or busy interconnect.

gc current block 2-way => Blocks are busy in another instance, check for block level contention or hot blocks.
gc cr block 2-way => Blocks are busy in another instance, check for block level contention or hot blocks.
gc current block 3-way => Blocks are busy in another instance, check for block level contention or hot blocks.
gc cr block 3-way => Blocks are busy in another instance, check for block level contention or hot blocks.

gc current grant 2-way
gc cr grant 2-way
gc current grant busy
gc current grant congested
gc cr grant congested

gc cr multi block read
gc current multi block request => Full table or index scans.
gc cr multi block request => Full table or index scans.
gc cr block build time
gc current block flush time
gc cr block flush time
gc current block send time
gc cr block send time
gc current block pin time
gc domain validation
gc current retry
ges inquiry response
gcs log flush sync

Related Oracle Articles: cluvfy commands RAC srvctl commands RAC crs_stat commands RAC

cluster name of Oracle RAC cluster

2020-08-17T16:50:00.001+05:30

How to find out cluster name of Oracle RAC cluster ?

The cluster name is case-insensitive, must be unique across environment, must be no more than 15 characters in length, must be alphanumeric and may contain hyphens (-). Underscore characters (_) are not allowed. But installation script/OUI will not fail, even if you provide more than 15 characters in cluster name.

1) cemutlo utility can be used to find out Oracle RAC Cluster name.

$GRID_HOME/bin/cemutlo -n

e.g.:
/u01/app/11.2/grid/bin/cemutlo -n

Below command will give number of characters in Oracle RAC Cluster name.
/u01/app/11.2/grid/bin/cemutlo -n|wc -c

Usage: ./cemutlo.bin [-n] [-w]
where:
-n prints the cluster name
-w prints the clusterware version in the following format: major_version:minor_version:vendor_info

2) olsnodes utility can be used to find out Oracle RAC Cluster name.
olsnodes -c

Related Oracle RAC Articles: ocrdump commands in RAC oclumon commands

init parameters in Oracle RAC

2019-12-24T16:16:00.002+05:30

Special init parameters in Oracle RAC
(which are not available in stand-alone Oracle Database instance)

instance_number
Oracle Real Application Clusters (RAC) parameter specifies a unique number that maps the instance.

instance_group
This RAC parameter specifies one or more instance groups and assigns the current instance to those groups.

thread
This RAC init parameter specifies the number of the redo thread to be used by an instance.

cluster_database
Oracle Real Application Clusters (RAC) parameter that specifies whether or not Real Application Clusters is enabled.

cluster_database_instances
Oracle Real Application Clusters (RAC) parameter that specifies the number of instances that are configured as part of the cluster database.

cluster_interconnects
This RAC parameter provides Oracle with information about additional cluster interconnects available for use in Real Application Clusters environments.

remote_listener

local_listener

parallel_instance

max_commit_propagation_delay

init parameters, in Oracle RAC, with SAME VALUE across all instances

active_instance_count

archive_lag_target

compatible

cluster_database

cluster_database_instances

cluster_interconnects

control_files

db_block_size

db_domain

db_files

db_name

db_recovery_file_dest

db_recovery_file_dest_size

db_unique_name

dml_locks -- when 0

instance_type -- rdbms or asm

max_commit_propagation_delay

parallel_max_servers

remote_login_password_file

trace_enabled

undo_management

For example,

*.cluster_database=true

*.cluster_database_instances=2

*.compatible='11.2.0.2'

*.undo_management='AUTO'

init parameters, in Oracle RAC, with Unique Values across all instances

instance_number

instance_name

thread

undo_tablespace/rollback_segments

For example,

INST1.instance_number=1

INST1.instance_name=rac1

INST1.thread=1

INST1.undo_tablespace='UNDOTBS1'

INST2.instance_number=2

INST2.instance_name=rac2

INST2.thread=2

INST2.undo_tablespace='UNDOTBS2'

Other Oracle RAC Articles: crsctl commands RAC srvctl commands RAC cluvfy commands RAC

Oracle RAC GDSCTL Commands

2019-12-19T17:33:00.003+05:30

GDSCTL - Global Data Services (GDS)

gdsctl
gdsctl @script_file_name

GDSCTL > help start
GDSCTL > start -h

GDSCTL > create catalog -database db_name -user user_name/password
GDSCTL > create catalog -database GSMTST -user c##gsm_admin/gsmadmin;

GDSCTL > add gsm -gsm gsm_name -listener listener_port -catalog catalogdb_name
GDSCTL > add gsm -gsm GSM1 -listener 1522 -catalog GSMTST -pwd gsmcatuser # Create listener
GDSCTL > add gsm -gsm gsm1 -catalog 127.0.0.1:1521:db1
GDSCTL > add database -connect edu400:1521/db01.apac.example.com -region APAC -gdspool hr_pool
GDSCTL > add database -connect edc007:1521/db14.east.example.com -region east -gdspool hr -pwd secret
GDSCTL > add region –region region_list
GDSCTL > add region -region EMCA, APAC
GDSCTL > add brokerconfig -connect HRTST -region EMCA -gdspool hr_pool -pwd gsmuser # Add TNS entry @GSM_home
GDSCTL > add brokerconfig -connect gsm02.training.com:1521/oltp_de -pwd password -gdspool sales -region germany"
$ gdsctl add gdspool -gdspool hr -catalog mygdscatlog
GDSCTL > add gdspool -dbpool database_pool_list [-users user_list]
GDSCTL > add service -gdspool hr -service emp_report1 -preferred_all
GDSCTL > add service -gdspool sales -service gsales_rw -role primary -preferred_all -failovertype SELECT -failovermethod BASIC -failoverretry 5 -failoverdelay 3 -locality LOCAL_ONLY -region_failover

GDSCTL > connect admin/pass@catalog
GDSCTL > connect c##gsm_admin/gsmadmin@GSMTST # Connect to gsmcatuser on catalog

GDSCTL > start gsm -gsm GSM1 # Start listener
GDSCTL > stop gsm -gsm GSM1 # Stop listener
GDSCTL > start service -service gsales_rw
GDSCTL > start service -service emp_report1 -gdspool hr
GDSCTL > stop service -service gsales_ro

GDSCTL > modify gsm -gsm GSM1 -listener 1522 -catalog GSMTST -pwd gsmcatuser # Modify listener
GDSCTL > modify catalog -oldpwd oldpassword -newpwd newpassword
GDSCTL > modify database -database oltp_ch1 -region switzerland

GDSCTL > config database # To check all the changes at region, pool, service and database level
GDSCTL > config
GDSCTL > config region

GDSCTL > services

GDSCTL > remove region -region EMCA
GDSCTL > remove brokerconfig
GDSCTL > remove brokerconfig -gdspool
GDSCTL > remove service -service gsales_rw
GDSCTL > remove gdspool -gdspool sales

GDSCTL > synchronize brokerconfig -gdspool

GDSCTL > export catalog file_name_with_full_path
GDSCTL > import catalog file_name_with_full_path

Related Oracle RAC Articles:

Oracle RAC 19c new features

2019-11-25T19:53:00.000+05:30

New features in Oracle Clusterware 19c

Zero downtime Grid/ Infrastructure Patching
Secure Cluster Communication - cluster interconnect traffic uses Transport Layer Security (TLS).
ASM is not required anymore for Voting disks and OCR so we can get rid of the ASM instance when using dNFS
Root.sh script automation
Read-only Instances
SERVICE_NAMES parameter has been deprecated

Related Oracle RAC Articles: New Features in Oracle Database 19c New features in Oracle Clusterware 18c

SCAN in Oracle RAC

2019-09-05T18:53:00.000+05:30

Single Client Access Name (SCAN) in Oracle RAC

Oracle RAC 11g release 2 introduces the Single Client Access Name (SCAN), which provides a single name for clients to access Oracle Databases running in a cluster and simplify the database connection strings that an Oracle Client uses to connect.

Without SCAN, till Oracle Clusterware 11g release 1, TNSNAMES has 1 entry per node.

RACDB =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = node1-vip)(PORT = 1521))

(ADDRESS = (PROTOCOL = TCP)(HOST = node2-vip)(PORT = 1521))
. . .

(ADDRESS = (PROTOCOL = TCP)(HOST = nodeN-vip)(PORT = 1521))

(CONNECT_DATA =

. . . ))

With every cluster change, like node addition or removal, all client TNSNAMES need to be changed.

With SCAN, from Oracle Clusterware 11g release2, only 1 entry per cluster is used, regardless of the number of nodes.

RACDB =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = SCANname)(PORT = 1521))

(CONNECT_DATA =

. . . ))

Single Client Access Name (SCAN) - eliminates the need to change TNSNAMES entry when nodes are added to or removed from the Cluster. RAC instances register to SCAN listeners as remote listeners. Oracle recommends assigning 3 addresses to SCAN, which will create 3 SCAN listeners, though the cluster has got dozens of nodes. SCAN is a domain name registered to at least one and up to three IP addresses, either in DNS (Domain Name Service) or GNS (Grid Naming Service). The SCAN must resolve to at least one address on the public network. For high availability and scalability, Oracle recommends configuring the SCAN to resolve to three addresses.

SCAN components in a cluster:

SCAN Name
SCAN IPs (3)
SCAN Listeners (3)

Public network addresses are used to provide services to clients. If clients are connecting to the Single Client Access Name (SCAN) addresses, then we may need to change public and virtual IP addresses as we add or remove nodes from the cluster, but you do not need to update clients with new cluster addresses. SCANs function like a cluster alias. SCANs are resolved on any node in the cluster, so unlike a VIP address for a node, clients connecting to the SCAN no longer require updated VIP addresses as nodes are added to or removed from the cluster. Because the SCAN addresses resolve to the cluster, rather than to a node address in the cluster, nodes can be added to or removed from the cluster without affecting the SCAN address configuration.

Oracle Database 11g release 2 (11.2) instances only register with SCAN listeners as remote listeners. Databases register with SCAN listeners as remote listeners, and also continue to register with all node listeners. It's highly recommended that the clients are Oracle 11g R2 or later version clients, to allow them to fully take advantage of the failover with the SCAN settings.

Because of the Oracle Clusterware installation requirement that we provide a SCAN name during installation, if we resolved at least one IP address using the server /etc/hosts file to bypass the installation requirement, but we do not have the infrastructure required for SCAN, after the installation, we can ignore the SCAN and connect to the databases in the cluster using VIPs. Oracle does not support removing the SCAN address. Oracle recommends that we should not configure SCAN IP addresses in the hosts file. But if we use the hosts file to resolve SCAN name, we can have only one SCAN IP address.

Each cluster will have 3 SCAN-Listeners, combined with a SCAN-VIP defined as cluster resources. The root.sh script automatically configures the Single Client Access Name (SCAN) VIPs and SCAN listeners. When we run root.sh on the first node, all 3 scan IPs are plugged on to the first node’s public interface. The SCAN VIP/LISTENER combination will failover to another node in the cluster, if the current node fails. SCAN VIP addresses must be on the same subnet as virtual IP addresses and public IP addresses.

Cluster Resources
--------------------------------------------

ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE node1

ora.LISTENER_SCAN2.lsnr 1 ONLINE ONLINE node2

ora.LISTENER_SCAN3.lsnr 1 ONLINE ONLINE node3

Domain Name Service (DNS)

The SCAN is a fully qualified name (hostname+domain) that is configured to resolve to all the addresses allocated for the SCAN. The addresses resolve using Round Robin DNS either on the DNS server, or within the cluster in a GNS configuration. SCAN listeners can run on any node in the cluster. SCANs provide location independence for the databases, so that client configuration does not have to depend on which nodes run a particular database.

To use the DNS method for defining SCAN, the network administrator must create a single name that resolves to 3 separate IP addresses using round-robin algorithms. Regardless of how many systems are part of cluster, Oracle recommends that 3 IP addresses are configured to allow for failover and load-balancing. SCAN Name needs to be registered in DNS and resolved using round-robin algorithm. To test the round-robin algorithm, perform nslookup on the SCAN Name. The DNS server should return those 3 set of IP Address in different order each time.

It is important that the IP addresses are on the same subnet as the public network for the server. The other two requirements are that the name (not including the domain suffix) are 15 characters or less in length and that the name can be resolved without using the domain suffix. Also, the IP addresses should not be specifically assigned to any of the nodes in the cluster.

Grid Naming Service (GNS)

Grid Naming Service (GNS) is a new feature introduced in Oracle RAC 11g R2.

As part of the Grid Infrastructure installation process, optionally we can also provide Grid Naming Service (GNS) information, which includes the GNS Sub Domain Name and the GNS VIP Address.

Using GNS assumes that a DHCP server is running on the public network with enough available addresses to assign the required IP addresses and the SCAN VIP. Only one static IP address is required to be configured and it should be in the DNS domain.

Oracle Clusterware 11g release 2 (11.2) supports the use of Dynamic Host Configuration Protocol (DHCP) for the VIP addresses and the SCAN address, but not the public address. DHCP provides dynamic configuration of the host's IP address, but it does not provide an optimal method of producing names that are useful to external clients. When using GNS and DHCP, Oracle Clusterware configures the VIP addresses for the SCAN name that is provided during cluster configuration. The node VIP and the three SCAN VIPs are obtained from the DHCP server when using GNS. If a new server joins the cluster, then Oracle Clusterware dynamically obtains the required VIP address from the DHCP server, updates the cluster resource, and makes the server accessible through GNS.

Summary of points about SCAN:

SCAN Name will represent the cluster in the network.
SCAN used by clients to connect to any database in the cluster.
SCAN is a GSD resource, which is managed by CRS.
SCAN provides a single domain name (via DNS), allowing end-users to address a RAC cluster as-if it were a single IP address.
Removes the requirement to change the client connection if cluster changes.
Load balances across the instances providing a service. SCAN listener selects least loaded node.
SCAN requires a DNS entry or GNS to be used.
SCAN is an alternative to the transparent application failover (TAF) for automatic load balancing.
Provides failover between instances.
SCAN VIP/LISTENER will failover to another node in the cluster.
Clients do not require VIP information.
Must resolve to at least one address on the public network.
SCAN provides location independence for the databases.
Allow clients to use EZConnect or JDBC connections.
SCAN Listener would forward the request to local listener that’s running on VIPs.
Each cluster will have 3 SCAN listeners, each having a SCAN VIP defined as cluster resources.
Instance registers with local listener on its node. Database “REMOTE_LISTENER” registers instances with all SCAN listeners.
SCAN listeners on each node in the cluster, which are not replacements for a regular listener.
PMON process of each instance registers the database services with the default listener on the local node and with each SCAN listener, which is specified by the REMOTE_LISTENER database parameter.
Client queries DNS to resolve to SCAN.

SCAN (Single Client Access Name) commands in Oracle RAC

cluvfy comp scan -> Use the cluvfy comp scan component verification command to check the Single Client Access Name (SCAN) configuration.

crsctl status resource -w "TYPE = ora.scan_listner.type"

SCAN:

srvctl add scan -n scan_name [-k network_number] [-S subnet/netmask[/if1[|if2|...]]]

#srvctl add scan -n scan.mycluster.example.com -- Adds new SCAN information for a cluster

srvctl remove scan [-f] -- Removes SCAN information

srvctl remove scan

srvctl remove scan -f

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

srvctl start scan

srvctl start scan -i 1 -n node1

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

srvctl stop scan

srvctl stop scan -i 1

srvctl status scan [-i ordinal_number]

srvctl status scan

srvctl status scan -i 1

srvctl enable scan [-i ordinal_number]

srvctl enable scan

srvctl enable scan -i 1

srvctl disable scan [-i ordinal_number]

srvctl disable scan

srvctl disable scan -i 3

srvctl config scan [-i ordinal_number] -- Shows the current SCAN configuration

srvctl config scan

srvctl config scan -i 2

srvctl modify scan -n scan_name

srvctl modify scan -n scan1
-- Modifies SCAN information (used when changing SCAN to DNS after initially using /etc/hosts)

srvctl relocate scan -i ordinal_number [-n node_name]

srvctl relocate scan -i 2 -n node2

ordinal_number=1,2,3 --> this refers to the SCAN VIPs

Scan_listener:

srvctl add scan_listener [-l lsnr_name_prefix] [-s] [-p "[TCP:]port_list[/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"]

#srvctl add scan_listener -l myscanlistener -- Adds a new SCAN listener for a cluster on the default port of 1521

#srvctl add scan_listener -p 1565 -- Adds a new SCAN listener on a different port

srvctl remove scan_listener [-f]

srvctl remove scan_listener -- Removes the SCAN listener

srvctl remove scan_listener -f

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

srvctl start scan_listener

srvctl start scan_listener -i 1

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

srvctl stop scan_listener

srvctl stop scan_listener -i 3

srvctl status scan_listener [-i ordinal_number]

srvctl status scan_listener

srvctl status scan_listener -i 1

srvctl enable scan_listener [-i ordinal_number]

srvctl enable scan_listener

srvctl enable scan_listener -i 2

srvctl disable scan_listener [-i ordinal_number]

srvctl disable scan_listener

srvctl disable scan_listener -i 1

srvctl config scan_listener [-i ordinal_number] -- Shows the existence and port numbers for the SCAN listeners

srvctl config scan_listener

srvctl config scan_listener -i 3

srvctl modify scan_listener {-p [TCP:]port[/IPC:key][/NMP:pipe_name] [/TCPS:s_port][/SDP:port] | -u }

srvctl modify scan_listener –u -- Modifies the SCAN listener information to match the new SCAN VIP information

srvctl modify scan_listener -p 1521

srvctl relocate scan_listener -i ordinal_number [-n node_name]

srvctl relocate scan_listener -i 1

ordinal_number=1,2,3

GNS (Grid Naming Service):

srvctl add gns -i ip_address -d domain

srvctl add gns -i 192.124.16.96 -d cluster.mycompany.com

srvctl remove gns [-f]

srvctl remove gns

srvctl start gns [-l log_level] [-n node_name]

srvctl start gns

srvctl stop gns [-n node_name [-v] [-f]

srvctl stop gns

srvctl status gns [-n node_name]

srvctl status gns

srvctl enable gns [-n node_name]

srvctl enable gns

srvctl disable gns [-n node_name]

srvctl disable gns -n devnode2

srvctl config gns [-a] [-d] [-k] [-m] [-n node_name] [-p] [-s] [-V] [-q name] [-l] [-v]

srvctl config gns -n lnx03

srvctl modify gns [-i ip_address] [-d domain]

srvctl modify gns -i 192.100.010.007

srvctl relocate gns [-n node_name]

srvctl relocate gns -n node2

Related Oracle Articles: Virtual IP (VIP) in RAC srvctl commands RAC cluvfy commands RAC crsctl commands RAC

Oracle RAC 18c new features

2019-07-29T09:27:00.000+05:30

New features in Oracle RAC/Clusterware 18c

In stand-alone databases and Oracle RAC databases, sequence can be made scalable by specifying the SCALE clause in the CREATE SEQUENCE or ALTER SEQUENCE statement.

Shared Scan Listeners - From Oracle 18c, we can have Shared Scan Listeners between clusters instead of having different scan listener for each cluster. This will save a lot of IP's and configuration aspect.

srvctl add scan_listener -clientcluster cluster_name
srvctl export scan_listener -clientcluster cluster_name -clientdata satyascan
srvctl export ons -clientcluster cluster_name -clientdata satyascandata

In DBCA silent mode, a copy of an Oracle RAC database can be created using the -createDuplicateDB command option -databaseConfigType with the value of RAC or RACONENODE.

Related Oracle RAC Articles: Enhancements in Oracle Database Release 18c What is new in Oracle 19c RAC

Virtual IP (VIP) in Oracle RAC

2019-07-15T15:47:00.000+05:30

What is (use of) Virtual IP (VIP) in Oracle Real Application Clusters (RAC)?

When installing Oracle 10g/11g R1 RAC, three network interfaces(IPs) are required for each node in the RAC cluster, they are:

Public Interface: Used for normal network communications to the node
Private Interface: Used as the cluster interconnect
Virtual (Public) Interface: Used for failover and RAC management

When installing Oracle 11g R2 RAC, we need one more network interface(IP) is required for each node in the RAC cluster.

SCAN Interface (IP): Single Client Access Name (SCAN) is a new Oracle Real Application Clusters (RAC) 11g Release 2 feature, that provides a single name for clients to access an Oracle Database running in a cluster. The benefit is clients using SCAN do not need to change if you add or remove nodes in the cluster.

When a client connects to a tns-alias, it uses a TCP connection to an IP address, defined in the tnsnames.ora file. When using RAC, we define multiple addresses in our tns-alias, to be able to failover when an IP address, listener or instance is unavailable. TCP timeouts can differ from platform to platform or implementation to implementation. This makes it difficult to predict the failover time.

Oracle 10g Cluster Ready Services enables databases to use a Virtual IP address to configure the listener ON. This feature is to assure that oracle clients quickly failover when a node fails. In Oracle Database 10g RAC, the use of a virtual IP address to mask the individual IPO addresses of the clustered nodes is required. The virtual IP addresses are used to simplify failover and are automatically managed by CRS.

To create a Virtual IP (VIP) address, the Virtual IP Configuration Assistant (VIPCA) is called from the root.sh script of a RAC install, which then configures the virtual IP addresses for each node specified during the installation process. In order to be able to run VIPCA, there must be unused public IP addresses available for each node that has been configured in the /etc/hosts file.

One public IP address for each node to use for its Virtual IP address for client connections and for connection failover. This IP address is in addition to the operating system managed public host IP address that is already assigned to the node by the operating system. This public Virtual IP must be associated with the same interface name on every node that is a part of the cluster. The IP addresses that are used for all of the nodes that are part of a cluster must be from the same subnet. The host names for the VIP addresses must be registered with the domain name server (DNS). The Virtual IP address should not be in use at the time of the installation because this is a Virtual IP address that Oracle manages internally to the RAC processes. This virtual IP address does not require a separate NIC. The VIPs should be registered in the DNS. The VIP addresses must be on the same subnet as the public host network addresses. Each Virtual IP (VIP) configured requires an unused and resolvable IP address.

Using virtual IP we can save our TCP/IP timeout problem because Oracle notification service (ONS) maintains communication between each nodes and listeners. Once ONS found any listener down or node down, it will notify another nodes and listeners. While new connection is trying to establish connection to failure node or listener, virtual IP of failure node automatically divert to surviving node and session will be establishing in another surviving node. This process doesn't wait for TCP/IP timeout event. Due to this new connection gets faster session establishment to another surviving nodes/listener.

Virtual IP (VIP) is for fast connection establishment in failover dictation. Still we can use physical IP address in Oracle 10g in listener if we have no worry for failover timing. We can change default TCP/IP timeout using operating system utilities/commands and kept smaller. But taking advantage of VIP (Virtual IP address) in Oracle 10g RAC database is advisable.

Oracle RAC SRVCTL commands related to VIP

# srvctl start nodeapps -n node_name -- Starts GSD, VIP, listener and ONS
# srvctl start nodeapps -n rac99

# srvctl stop nodeapps -n node_name [-r] -- Stops GSD, VIP, listener and ONS
# srvctl stop nodeapps -n lnx03

# srvctl config nodeapps -n node_name [-a] [-g] [-o] [-s] [-l]
-a Display VIP configuration
# srvctl config nodeapps -n node33 -a

# srvctl modify nodeapps -n node_name [-A new_vip_address]
# srvctl modify nodeapps -n lnx06 -A 10.50.99.43/255.255.252.0/eth0

srvctl modify nodeapps [-n node_name -A new_vip_address] [-S subnet/netmask[/if1[|if2|...]] [-m multicast_ip_address] [-p multicast_port_number] [-e eons_listen_port] [-l ons_local_port] [-r ons_remote_port] [-t host[:port][,host:port,...]] [-v]
srvctl modify nodeapps -n node1 -A 100.200.300.40/255.255.255.0/eth0

srvctl add vip -n node_name -A {name|ip}/netmask[/if1[if2|...]] [-k network_number] [-v]
# srvctl add vip -n node96 -A 192.124.16.96/255.255.255.0 -k 2

srvctl remove vip -i "vip_name_list" [-f] [-y] [-v]
srvctl remove vip -i "vip1,vip2,vip3" -f -y -v

srvctl start vip {-n node_name|-i vip_name} [-v]
srvctl start vip -i dev1-vip -v

srvctl stop vip {-n node_name|-i vip_name} [-r] [-v]
srvctl stop vip -n node1 -v

srvctl status vip {-n node_name|-i vip_name}
srvctl status vip -i node1-vip

srvctl enable vip -i vip_name [-v]
srvctl enable vip -i prod_vip -v

srvctl disable vip -i vip_name [-v]
srvctl disable vip -i vip3 -v

srvctl config vip {-n node_name|-i vip_name}
srvctl config vip -n devnode2

srvctl getenv vip -i vip_name [-t "name_list"] [-v]
srvctl getenv vip -i node1-vip

srvctl setenv vip -i vip_name {-t "name=val[,name=val,...]" | -T "name=val"}
srvctl setenv vip -i dev1-vip -t LANG=en

srvctl unsetenv vip -i vip_name -t "name_list" [-v]
srvctl unsetenv vip -i myvip -t CLASSPATH

# olsnodes -i ==> will show VIPs of the nodes.
node1 168.192.1.1
node2 168.192.2.1
node3 168.192.3.1
node4 168.192.4.1

$ vipca - VIP Configuration Assistant
$ vipca -nodelist node1,node3

Other Oracle Articles: crsctl commands RAC srvctl commands RAC cluvfy commands RAC SCAN in RAC

Difference between SRVCTL and CRSCTL

2019-06-24T19:14:00.005+05:30

What is the difference between SRVCTL and CRSCTL utility commands in Oracle RAC.

srvctl

Use SRVCTL to manage Oracle supplied resources such as

Listener
Instances
Disk groups
Networks

srvctl is used to manage the elements of the cluster like databases, instances, listeners, services etc.

srvtcl was introduced with Oracle 9i.

If the resource name begins with ora then use SRVCTL.

Oracle suggests DBAs use the srvctl command to start the databases.

SRVCTL manages Oracle resource related operations:

Starting and stopping database instances and services
Also from 11gR2 manages the cluster resources like network, vip, disks etc

We can use the SRVCTL to manage configuration information. Use SRVCTL commands to add, remove, start, stop, modify, enable, and disable a number of entities, such as Databases, instances, listeners, SCAN listeners, services, grid naming Service (GNS), and Oracle ASM.

crsctl

Use CRSCTL for managing Oracle Clusterware and its resources.

crsctl command is used to manage the elements of the Clusterware like crs, css, evm.

crsctl was introduced with Oracle 10g.

CRSCTL manages Oracle Clusterware related operations like:

Starting and stopping Oracle Clusterware
Enabling and disabling Oracle Clusterware daemons
Checking the health of the cluster
Registering cluster resources

dd commands

2019-03-19T15:27:00.000+05:30

Linux dd commands for Oracle DBAs

dd -- data(set) definition, useful for taking backup of votedisks/Voting Disks

dd is a command line utility for Unix/Linux operating systems whose primary purpose is to convert files, copy files and to take backup.
dd commands are used - restores/clone a hard disk drive from a previously created image. Clones one partition to another.

Arguments:
if -- input file
of -- output file
bs -- block size

dd if=/u02/ocfs2/vote/VDFile_0 of=$ORACLE_BASE/bkp/VDFile_0

dd if=/dev/hdb2 of=/dev/sda5 bs=8192

dd if=/dev/sda2 of=/dev/sdb2 bs=4096 conv=notrunc,noerror

dd if=/dev/zero of=/abc bs=1 count=1 conv=notrunc,ucase

dd if=/dev/cdrom of=/home/satya/myCD.iso bs=2048 conv=sync,notrunc,lcase

dd if=/dev/hda3 skip=9200 of=/home/satya/backup_set_3.img bs=1M count=4600

dd if=/home/satya/1Gb.file bs=64k | dd of=/dev/null

dd if=testwrite.dbf bs=8192 count=1 skip=1246 of=blk1246.dmp

dd of=testwrite.dbf bs=8192 count=1 seek=3407 if=blk 3407.dmp conv=notrunc

Related Oracle Articles: ocrcheck in Oracle RAC ocrdump in Oracle RAC ocrconfig commands in Oracle RAC

Oracle RAC 12c srvctl commands

2019-01-29T20:22:00.002+05:30

srvctl commands in Oracle RAC 12c

srvctl -help
srvctl -V

Database related commands in RAC 12c
srvctl add database -db db_unique_name -oraclehome oracle_home [-dbtype {RACONENODE | RAC | SINGLE} [-server server_list] [-instance inst_name] [-timeout timeout]] [-domain domain_name] [-spfile spfile] [-pwfile password_file_path] [-role {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY | SNAPSHOT_STANDBY | FAR_SYNC}] [-startoption start_options] [-stopoption stop_options] [-startconcurrency start_concurrency] [-stopconcurrency stop_concurrency] [-dbname db_name] [-policy {AUTOMATIC | MANUAL | NORESTART}] [-serverpool "serverpool_list" [-pqpool pq_server_pools]] [-node node_name] [-diskgroup "diskgroup_list"] [-acfspath "acfs_path_list"] [-eval] [-fixed] [-verbose]
srvctl config database [-db db_unique_name [-all] | -serverpool serverpool_name] [-verbose]
srvctl start database -db db_unique_name [-startoption start_options] [-startconcurrency start_concurrency] [-node node] [-eval] [-verbose]
srvctl stop database -db db_unique_name [-stopoption stop_options] [-stopconcurrency stop_concurrency] [-force] [-eval] [-verbose]
srvctl status database {-db db_unique_name [-serverpool serverpool_name] | -serverpool serverpool_name | -thisversion | -thishome} [-force] [-verbose]
srvctl enable database -db db_unique_name [-node node_name]
srvctl disable database -db db_unique_name [-node node_name]
srvctl modify database -db db_unique_name [-dbname db_name] [-instance instance_name] [-oraclehome oracle_home] [-user oracle_user] [-server server_list] [-timeout timeout] [-domain domain] [-spfile spfile] [-pwfile password_file_path] [-role {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY | SNAPSHOT_STANDBY}] [-startoption start_options] [-stopoption stop_options] [-startconcurrency start_concurrency] [-stopconcurrency stop_concurrency][-policy {AUTOMATIC | MANUAL | NORESTART}] [-serverpool "serverpool_list" [-node node_name]] [-pqpool pq_server_pools] [-diskgroup "diskgroup_list"|-nodiskgroup] [-acfspath "acfs_path_list"] [-force] [-eval] [-verbose]
srvctl remove database -db db_unique_name [-force] [-noprompt] [-verbose]
srvctl getenv database -db db_unique_name [-envs "name[,...]"]
srvctl setenv database -db db_unique_name {-envs "name=val[,...]" | -env "name=val"}
srvctl unsetenv database -db db_unique_name -envs "name[,...]"
srvctl predict database -db database_name [-verbose]
srvctl convert database -db db_unique_name -dbtype RAC [-node node]
srvctl convert database -db db_unique_name -dbtype RACONENODE [-instance inst_name] [-timeout timeout]
srvctl relocate database -db db_unique_name {[-node target] [-timeout timeout] [-stopoption stop_option] | -abort [-revert]} [-verbose]
srvctl upgrade database -db db_unique_name -oraclehome oracle_home
srvctl downgrade database -db db_unique_name -oraclehome oracle_home -targetversion to_version
srvctl update database -db db_unique_name [-startoption start_options [-node node_name]]

Instance related commands in Oracle RAC 12c
srvctl add instance -db db_unique_name -instance inst_name -node node_name [-force]
srvctl start instance -db db_unique_name {-node node_name [-instance inst_name] | -instance inst_name_list} [-startoption start_options]
srvctl stop instance -db db_unique_name {-node node_name | -instance inst_name_list} [-stopoption stop_options] [-force] [-failover]
srvctl status instance -db db_unique_name {-node node_name | -instance inst_name_list} [-force] [-verbose]
srvctl enable instance -db db_unique_name -instance "inst_name_list"
srvctl disable instance -db db_unique_name -instance "inst_name_list"
srvctl modify instance -db db_unique_name -instance inst_name -node node_name
srvctl remove instance -db db_unique_name -instance inst_name [-force] [-noprompt]
srvctl update instance -db db_unique_name {-instance instance_name | -node node_name} -startoption start_options

RAC 12c srvctl - Service related commands
srvctl add service -db db_unique_name -service service_name {-preferred "preferred_list" [-available "available_list"] [-tafpolicy {BASIC | NONE | PRECONNECT}] | -serverpool pool_name [-cardinality {UNIFORM | SINGLETON}] } [-netnum network_number] [-role "[PRIMARY][,PHYSICAL_STANDBY][,LOGICAL_STANDBY][,SNAPSHOT_STANDBY]"] [-policy {AUTOMATIC | MANUAL}] [-notification {TRUE|FALSE}] [-dtp {TRUE|FALSE}] [-clbgoal {SHORT|LONG}] [-rlbgoal {NONE|SERVICE_TIME|THROUGHPUT}] [-failovertype {NONE|SESSION|SELECT|TRANSACTION}] [-failovermethod {NONE|BASIC}] [-failoverretry failover_retries] [-failoverdelay failover_delay] [-edition edition] [-pdb pluggable_database] [-global {TRUE|FALSE}] [-maxlag max_lag_time] [-sql_translation_profile sql_translation_profile] [-commit_outcome {TRUE|FALSE}] [-retention retention] [-replay_init_time replay_initiation_time] [-session_state {STATIC|DYNAMIC}] [-pqservice pq_service] [-pqpool pq_pool_list] [-gsmflags gsm_flags] [-force] [-eval] [-verbose]
srvctl add service -db db_unique_name -service service_name -update {-preferred "new_pref_inst" | -available "new_avail_inst"} [-force] [-verbose]
srvctl config service {-db db_unique_name [-service service_name] | -serverpool serverpool_name [-db db_unique_name]} [-verbose]
srvctl enable service -db db_unique_name -service "service_name_list" [-instance inst_name | -node node_name] [-global_override]
srvctl disable service -db db_unique_name -service "service_name_list" [-instance inst_name | -node node_name] [-global_override]
srvctl status service {-db db_unique_name [-service "service_name_list"] | -serverpool serverpool_name [-db db_unique_name]} [-force] [-verbose]
srvctl predict service -db database_name -service service_name [-verbose]
srvctl modify service -db db_unique_name -service service_name -oldinst old_inst_name -newinst new_inst_name [-force]
srvctl modify service -db db_unique_name -service service_name -available avail_inst_name -toprefer [-force]
srvctl modify service -db db_unique_name -service service_name -modifyconfig -preferred "preferred_list" [-available "available_list"] [-force]
srvctl modify service -db db_unique_name -service service_name [-serverpool pool_name] [-pqservice pqsvc_name] [-pqpool pq_pool_list] [-cardinality {UNIFORM | SINGLETON}] [-tafpolicy {BASIC|NONE}] [-role [PRIMARY][,PHYSICAL_STANDBY][,LOGICAL_STANDBY][,SNAPSHOT_STANDBY]] [-policy {AUTOMATIC | MANUAL}][-notification {TRUE|FALSE}] [-dtp {TRUE|FALSE}] [-clbgoal {SHORT|LONG}] [-rlbgoal {NONE|SERVICE_TIME|THROUGHPUT}] [-failovertype {NONE|SESSION|SELECT|TRANSACTION}] [-failovermethod {NONE|BASIC}] [-failoverretry integer] [-failoverdelay integer] [-edition edition] [-pdb pluggable_database] [-sql_translation_profile sql_translation_profile] [-commit_outcome {TRUE|FALSE}] [-retention retention] [-replay_init_time replay_initiation_time] [-session_state {STATIC|DYNAMIC}] [-maxlag max_lag_time] [-gsmflags gsm_flags] [-global_override] [-eval] [-verbose] [-force]
srvctl relocate service -db db_unique_name -service service_name {-oldinst old_inst_name -newinst new_inst_name | -currentnode current_node -targetnode target_node} [-pq] [-force [-noreplay]] [-eval] [-verbose]
srvctl remove service -db db_unique_name -service service_name [-instance inst_name] [-global_override] [-force]
srvctl start service -db db_unique_name [-service "service_name_list"] [-serverpool pool_name] [-node node_name | -instance inst_name] [-pq] [-global_override] [-startoption start_options] [-eval] [-verbose]
srvctl stop service -db db_unique_name [-service "service_name_list"] [-serverpool pool_name] [-node node_name | -instance inst_name] [-pq] [-global_override] [-force [-noreplay]] [-eval] [-verbose]

NodeApps related commands in RAC 12c
srvctl add nodeapps { { -node node_name -address {vip_name|ip}/netmask[/if1[|if2...]] [-skip]} | { -subnet subnet/netmask[/if1[|if2...]] } } [-emport em_port] [-onslocalport ons_local_port] [-onsremoteport ons_remote_port] [-remoteservers host[:port][,host[:port]...]] [-clientdata file] [-pingtarget "pingtarget_list"] [-verbose]
srvctl config nodeapps [-viponly] [-onsonly]
srvctl modify nodeapps {[-node node_name -address {vip_name|ip}/netmask[/if1[|if2...]] [-skip]] | [-subnet subnet/netmask[/if1[|if2|...]]]} [-nettype {STATIC|DHCP|AUTOCONFIG|MIXED}] [-emport em_port] [ -onslocalport ons_local_port ] [-onsremoteport ons_remote_port ] [-remoteservers host[:port][,host[:port]...]] [-clientdata file] [-pingtarget "pingtarget_list"] [-verbose]
srvctl start nodeapps [-node node_name] [-adminhelper | -onsonly] [-verbose]
srvctl stop nodeapps [-node node_name] [-adminhelper | -onsonly | -relocate] [-force] [-verbose]
srvctl status nodeapps [-node node_name]
srvctl enable nodeapps [-adminhelper] [-verbose]
srvctl disable nodeapps [-adminhelper] [-verbose]
srvctl remove nodeapps [-force] [-noprompt] [-verbose]
srvctl getenv nodeapps [-viponly] [-onsonly] [-envs "name[,...]"]
srvctl setenv nodeapps {-envs "name=val[,...]" | -env "name=val"} [-viponly | -onsonly] [-verbose]
srvctl unsetenv nodeapps -envs "name[,...]" [-viponly | -onsonly] [-verbose]

VIP related commands in RAC 12c
srvctl add vip -node node_name -netnum network_number -address {name|ip}/netmask[/if1[|if2...]] [-skip] [-verbose]
srvctl config vip {-node node_name | -vip vip_name}
srvctl disable vip -vip vip_name [-verbose]
srvctl enable vip -vip vip_name [-verbose]
srvctl remove vip -vip vip_name_list [-force] [-noprompt] [-verbose]
srvctl getenv vip -vip vip_name [-envs "name[,...]"]
srvctl start vip {-node node_name [-netnum network_number] | -vip vip_name} [-verbose]
srvctl stop vip {-node node_name [-netnum network_number] | -vip vip_name} [-force] [-relocate] [-verbose]
srvctl relocate vip -vip vip_name [-node node_name] [-force] [-verbose]
srvctl status vip {-node node_name | -vip vip_name} [-verbose]
srvctl setenv vip -vip vip_name {-envs "name=val[,...]" | -env "name=val"} [-verbose]
srvctl unsetenv vip -vip vip_name -envs "name[,...]" [-verbose]
srvctl predict vip -vip vip_name [-verbose]

Network related commands in RAC 12c
srvctl add network [-netnum network_number] -subnet subnet/netmask[/if1[|if2...]] [-nettype {STATIC|DHCP|AUTOCONFIG|MIXED}] [-pingtarget "pingtarget_list"] [-leaf] [-verbose]
srvctl config network [-netnum network_number]
srvctl modify network [-netnum network_number] [-subnet subnet/netmask[/if1[|if2...]]] [-nettype {STATIC|DHCP|AUTOCONFIG|MIXED}] [-iptype {IPV4|IPV6|BOTH}] [-pingtarget "pingtarget_list"] [-verbose]
srvctl remove network {-netnum network_number | -all} [-force] [-verbose]
srvctl predict network [-netnum network_number] [-verbose]

ASM related commands in Oracle RAC 12c
srvctl add asm [-listener lsnr_name] [-pwfile password_file_path] [-flex [-count {number_of_instances|ALL}]|-proxy]
srvctl start asm [-proxy] [-node node_name] [-startoption start_options]
srvctl stop asm [-proxy] [-node node_name] [-stopoption stop_options] [-force]
srvctl config asm [-proxy] [-detail]
srvctl status asm [-proxy] [-node node_name] [-detail] [-verbose]
srvctl enable asm [-proxy] [-node node_name]
srvctl disable asm [-proxy] [-node node_name]
srvctl modify asm [-listener lsnr_name] [-pwfile password_file_path] [-count {number_of_instances|ALL}] [-force]
srvctl remove asm [-proxy] [-force]
srvctl relocate asm -currentnode current_node [-targetnode target_node] [-force]
srvctl getenv asm [-envs "name[,...]"]
srvctl setenv asm {-envs "name=val[,...]" | -env "name=value"}
srvctl unsetenv asm -envs "name[,...]"
srvctl predict asm [-node node_name] [-verbose]

Diskgroup related commands in RAC 12c
srvctl start diskgroup -diskgroup dg_name [-node "node_list"]
srvctl stop diskgroup -diskgroup dg_name [-node "node_list"] [-force]
srvctl status diskgroup -diskgroup dg_name [-node "node_list"] [-detail] [-verbose]
srvctl enable diskgroup -diskgroup dg_name [-node "node_list"]
srvctl disable diskgroup -diskgroup dg_name [-node "node_list"]
srvctl remove diskgroup -diskgroup dg_name [-force]
srvctl predict diskgroup -diskgroup diskgroup_name [-verbose]

Listener related commands in RAC 12c
srvctl add listener [-listener lsnr_name] {[-netnum network_number] [-oraclehome path] [-user oracle_user] | -asmlistener [-subnet subnet] | -leaflistener [-subnet subnet]} [-skip] [-endpoints "[TCP:]port[, ...][/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"] [-invitednodes node_list] [-invitedsubnets subnet_list]
srvctl config listener [-listener lsnr_name | -asmlistener | -leaflistener] [-all]
srvctl start listener [-listener lsnr_name] [-node node_name]
srvctl stop listener [-listener lsnr_name] [-node node_name] [-force]
srvctl status listener [-listener lsnr_name] [-node node_name] [-verbose]
srvctl enable listener [-listener lsnr_name] [-node node_name]
srvctl disable listener [-listener lsnr_name] [-node node_name]
srvctl modify listener [-listener lsnr_name] [-oraclehome path] [-endpoints "[TCP:]port[, ...][/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"] [-user oracle_user] [-netnum network_number]
srvctl remove listener [-listener lsnr_name | -all] [-force]
srvctl getenv listener [-listener lsnr_name] [-envs "name[,...]"]
srvctl setenv listener [-listener lsnr_name] {-envs "name=val[,...]" | -env "name=value"}
srvctl unsetenv listener [-listener lsnr_name] -envs "name[,...]"
srvctl predict listener -listener listener_name [-verbose]

SCAN related commands in RAC 12c
srvctl add scan -scanname scan_name [-netnum network_number]
srvctl config scan [[-netnum network_number] [-scannumber scan_ordinal_number] | -all]
srvctl start scan [-netnum network_number] [-scannumber scan_ordinal_number] [-node node_name]
srvctl stop scan [-netnum network_number] [-scannumber scan_ordinal_number] [-force]
srvctl relocate scan -scannumber scan_ordinal_number [-netnum network_number] [-node node_name]
srvctl status scan [[-netnum network_number] [-scannumber scan_ordinal_number] | -all] [-verbose]
srvctl enable scan [-netnum network_number] [-scannumber scan_ordinal_number]
srvctl disable scan [-netnum network_number] [-scannumber scan_ordinal_number]
srvctl modify scan -scanname scan_name [-netnum network_number]
srvctl remove scan [-netnum network_number] [-force] [-noprompt]
srvctl predict scan -scannumber scan_ordinal_number [-netnum network_number] [-verbose]

SCAN Listener related commands in RAC 12c
srvctl add scan_listener [-netnum network_number] [-listener lsnr_name_prefix] [-skip] [-endpoints [TCP:]port[/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]] [-invitednodes node_list] [-invitedsubnets subnet_list]
srvctl config scan_listener [[-netnum network_number] [-scannumber scan_ordinal_number] | -all]
srvctl start scan_listener [-netnum network_number] [-scannumber scan_ordinal_number] [-node node_name]
srvctl stop scan_listener [-netnum network_number] [-scannumber scan_ordinal_number] [-force]
srvctl relocate scan_listener -scannumber scan_ordinal_number [-netnum network_number] [-node node_name]
srvctl status scan_listener [[-netnum network_number] [-scannumber scan_ordinal_number] | -all] [-verbose]
srvctl enable scan_listener [-netnum network_number] [-scannumber scan_ordinal_number]
srvctl disable scan_listener [-netnum network_number] [-scannumber scan_ordinal_number]
srvctl modify scan_listener {-update|-endpoints [TCP:]port[/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]} [-netnum network_number] [-invitednodes node_list] [-invitedsubnets subnet_list]
srvctl update scan_listener
srvctl remove scan_listener [-netnum network_number] [-force] [-noprompt]
srvctl predict scan_listener -scannumber scan_ordinal_number [-netnum network_number] [-verbose]

Server Pool related commands in RAC 12c
srvctl add srvpool -serverpool pool_name [-min min] [-max max] [-importance importance] [-servers "server_list" | -category server_category] [-force] [-eval] [-verbose]
srvctl config srvpool [-serverpool pool_name]
srvctl status srvpool [-serverpool pool_name] [-detail]
srvctl status server -servers "server_list" [-detail]
srvctl relocate server -servers "server_list" -serverpool pool_name [-force] [-eval] [-verbose]
srvctl modify srvpool -serverpool pool_name [-min min] [-max max] [-importance importance] [-servers "server_list" | -category server_category] [-force] [-eval] [-verbose]
srvctl remove srvpool -serverpool pool_name [-eval] [-verbose]

OC4J related commands in RAC 12c
srvctl add oc4j [-verbose]
srvctl config oc4j
srvctl start oc4j [-node node_name] [-verbose]
srvctl stop oc4j [-force] [-verbose]
srvctl relocate oc4j [-node node_name] [-verbose]
srvctl status oc4j [-node node_name] [-verbose]
srvctl enable oc4j [-node node_name] [-verbose]
srvctl disable oc4j [-node node_name] [-verbose]
srvctl modify oc4j [-rmiport oc4j_rmi_port] [-httpport oc4j_http_port] [-verbose] [-force]
srvctl remove oc4j [-force] [-verbose]
srvctl predict oc4j [-verbose]

RHP server related commands in RAC 12c
srvctl add rhpserver -storage base_path -diskgroup dg_name
srvctl config rhpserver
srvctl start rhpserver [-node node_name]
srvctl stop rhpserver
srvctl relocate rhpserver [-node node_name]
srvctl status rhpserver
srvctl enable rhpserver [-node node_name]
srvctl disable rhpserver [-node node_name]
srvctl modify rhpserver [-port rmi_port [-force]]
srvctl remove rhpserver [-force]

HA VIP related commands in RAC 12c
srvctl add havip -id id -address {name|ip} [-netnum network_number] [-description text] [-skip] [-homenode node_name]
srvctl config havip [-id id]
srvctl start havip -id id [-node node_name]
srvctl stop havip -id id [-node node_name] [-force]
srvctl relocate havip -id id [-node node_name] [-force]
srvctl status havip [-id id]
srvctl enable havip -id id [-node node_name]
srvctl disable havip -id id [-node node_name]
srvctl modify havip -id id [-address {name|ip} [-netnum network_number] [-skip]] [-description text] [-homenode node_name]
srvctl remove havip -id id [-force]

Export FS related commands in RAC 12c
srvctl add exportfs -name expfs_name -id id -path exportpath [-clients export_clients] [-options export_options]
srvctl config exportfs [-name expfs_name | -id havip id]
srvctl start exportfs {-name expfs_name | -id havip id }
srvctl stop exportfs {-name expfs_name | -id havip id } [-force]
srvctl status exportfs [-name expfs_name |-id havip id]
srvctl enable exportfs -name expfs_name
srvctl disable exportfs -name expfs_name
srvctl modify exportfs -name expfs_name [-path exportpath] [-clients export_clients] [-options export_options]
srvctl remove exportfs -name expfs_name [-force]

RHP Client related commands in RAC 12c
srvctl add rhpclient -clientdata file [-diskgroup dg_name -storage base_path]
srvctl config rhpclient
srvctl start rhpclient [-node node_name]
srvctl stop rhpclient
srvctl relocate rhpclient [-node node_name]
srvctl status rhpclient
srvctl enable rhpclient [-node node_name]
srvctl disable rhpclient [-node node_name]
srvctl modify rhpclient [-clientdata file] [-port rmi_port] [-diskgroup dg_name -storage base_path]
srvctl remove rhpclient [-force]

Oracle Home related commands in Oracle RAC 12c
srvctl start home -oraclehome oracle_home -statefile state_file -node node_name
srvctl stop home -oraclehome oracle_home -statefile state_file -node node_name [-stopoption stop_options] [-force]
srvctl status home -oraclehome oracle_home -statefile state_file -node node_name

File System related commands in RAC 12c
srvctl add filesystem -device volume_device -path mountpoint_path [-volume volume_name] [-diskgroup dg_name] [-node node_list | -serverpool serverpool_list] [-user user_list] [-fstype {ACFS|EXT3|EXT4}] [-fsoptions options] [-description description] [-appid application_id] [-autostart {ALWAYS|NEVER|RESTORE}] [-auxvolumes volume_device]
srvctl config filesystem [-device volume_device]
srvctl start filesystem -device volume_device [-node node_name]
srvctl stop filesystem -device volume_device [-node node_name] [-force]
srvctl relocate filesystem -device volume_device [-node node_name] [-force] [-verbose]
srvctl status filesystem [-device volume_device] [-verbose]
srvctl enable filesystem -device volume_device
srvctl disable filesystem -device volume_device
srvctl modify filesystem -device volume_device [-user {[/+ | /-]user | user_list}] [-path mountpoint_path] [-node node_list | -serverpool serverpool_list] [-fsoptions options] [-description description] [-autostart {ALWAYS|NEVER|RESTORE}] [-force]
srvctl remove filesystem -device volume_device [-force]
srvctl predict filesystem -device volume_device [-verbose]

RAC 12c srvctl - Volume related commands
srvctl config volume [-volume volume_name] [-diskgroup group_name] [-device volume_device]
srvctl start volume {-volume volume_name -diskgroup group_name | -device volume_device} [-node node_list]
srvctl stop volume {-volume volume_name -diskgroup group_name | -device volume_device} [-node node_list] [-force]
srvctl status volume [-device volume_device] [-volume volume_name] [-diskgroup group_name] [-node node_list | -all]
srvctl enable volume {-volume volume_name -diskgroup group_name | -device volume_device} [-node node_name]
srvctl disable volume {-volume volume_name -diskgroup group_name | -device volume_device} [-node node_name]

GNS related commands in RAC 12c
srvctl start gns [-loglevel log_level] [-node node_name] [-verbose]
srvctl stop gns [-node node_name] [-force] [-verbose]
srvctl config gns [-detail] [-subdomain] [-multicastport] [-node node_name] [-port] [-status] [-version] [-query name] [-list] [-clusterguid] [-clustername] [-clustertype] [-loglevel] [-network] [-verbose]
srvctl status gns [-node node_name] [-verbose]
srvctl enable gns [-node node_name] [-verbose]
srvctl disable gns [-node node_name] [-verbose]
srvctl relocate gns [-node node_name] [-verbose]
srvctl add gns {-vip {vip_name | ip} [-skip] [-domain domain] [-verbose] | -clientdata filename}
srvctl modify gns {-loglevel log_level | [-resolve name] [-verify name] [-parameter name:value[,name:value...]] [-vip {vip_name | ip} [-skip]] [-clientdata filename] [-verbose]}
srvctl remove gns [-force] [-verbose]
srvctl import gns -instance filename
srvctl export gns {-instance filename | -clientdata filename}
srvctl update gns {-advertise name -address address [-timetolive time_to_live] | -delete name [-address address] | -alias alias -name name [-timetolive time_to_live] | -deletealias alias | -createsrv service -target target -protocol protocol [-weight weight] [-priority priority] [-port port_number] [-timetolive time_to_live] [-instance instance_name] | -deletesrv service_name -target target -protocol protocol [-instance instance_name] | -createtxt name -target target [-timetolive time_to_live] [-namettl name_ttl] | -deletetxt name -target target | -createptr name -target target [-timetolive time_to_live] [-namettl name_ttl] | -deleteptr name -target target} [-verbose]

CVU related commands in RAC 12c
srvctl add cvu [-checkinterval check_interval_in_minutes]
srvctl config cvu
srvctl start cvu [-node node_name]
srvctl stop cvu [-force]
srvctl relocate cvu [-node node_name]
srvctl status cvu [-node node_name]
srvctl enable cvu [-node node_name]
srvctl disable cvu [-node node_name]
srvctl modify cvu -checkinterval check_interval_in_minutes
srvctl remove cvu [-force]

MGMT DB related commands in Oracle RAC 12c
srvctl add mgmtdb [-domain domain_name]
srvctl config mgmtdb [-verbose] [-all]
srvctl start mgmtdb [-startoption start_option] [-node node_name]
srvctl stop mgmtdb [-stopoption stop_option] [-force]
srvctl update mgmtdb -startoption start_options
srvctl status mgmtdb [-verbose]
srvctl enable mgmtdb [-node node_name]
srvctl disable mgmtdb [-node node_name]
srvctl modify mgmtdb [-pwfile password_file_path] [-spfile server_parameter_file]
srvctl remove mgmtdb [-force] [-noprompt] [-verbose]
srvctl getenv mgmtdb [-envs "name[,...]"]
srvctl setenv mgmtdb {-envs "name=value[,...]" | -env "name=value"}
srvctl unsetenv mgmtdb -envs "name[,..]"
srvctl relocate mgmtdb [-node node_name]

RAC 12c srvctl - MGMT Listener related commands
srvctl add mgmtlsnr [-endpoints "[TCP:]port[, ...][/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"] [-skip]
srvctl config mgmtlsnr [-all]
srvctl start mgmtlsnr [-node node_name]
srvctl stop mgmtlsnr [-node node_name] [-force]
srvctl status mgmtlsnr [-verbose]
srvctl enable mgmtlsnr [-node node_name]
srvctl disable mgmtlsnr [-node node_name]
srvctl modify mgmtlsnr -endpoints "[TCP:]port[,...][/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"
srvctl remove mgmtlsnr [-force]
srvctl getenv mgmtlsnr [ -envs "name[,...]"]
srvctl setenv mgmtlsnr { -envs "name=val[,...]" | -env "name=value"}
srvctl unsetenv mgmtlsnr -envs "name[,...]"

Mount FS related commands in RAC 12c
srvctl add mountfs -name mountfs_name -path mount_path -exportserver server_name -exportpath path [-mountoptions mount_options] [-user user]
srvctl config mountfs [-name mountfs_name]
srvctl start mountfs -name mountfs_name [-node node_list]
srvctl stop mountfs -name mountfs_name [-node node_list] [-force]
srvctl status mountfs -name mountfs_name
srvctl enable mountfs -name mountfs_name [-node node_list]
srvctl disable mountfs -name mountfs_name [-node node_list]
srvctl modify mountfs -name mountfs_name [-path mount_path] [-exportserver server_name] [-exportpath path] [-mountoptions mount_options] [-user user]
srvctl remove mountfs -name mountfs_name [-force]

Related Oracle RAC Articles: srvctl commands in Oracle RAC 11g Oracle RAC Online Quiz

cluvfy commands in Oracle RAC

2019-01-06T18:22:00.002+05:30

CLUVFY: Cluster Verification Utility commands in Oracle 11g / 12c RAC

cluvfy [-help] or cluvfy -h

cluvfy stage {-pre|-post} stage_name stage_specific_options [-verbose]

Valid stage options and stage names are:

-post hwos : post-check for hardware and operating system

-pre cfs : pre-check for CFS setup

-post cfs : post-check for CFS setup

-pre crsinst : pre-check for CRS installation

-post crsinst : post-check for CRS installation

-pre hacfg : pre-check for HA configuration

-post hacfg : post-check for HA configuration

-pre dbinst : pre-check for database installation

-pre acfscfg : pre-check for ACFS Configuration.

-post acfscfg : post-check for ACFS Configuration.

-pre dbcfg : pre-check for database configuration

-pre nodeadd : pre-check for node addition.

-post nodeadd : post-check for node addition.

-post nodedel : post-check for node deletion.

cluvfy stage -post hwos -n node_list [-verbose]

./runcluvfy.sh stage -post hwos -n node1,node2 -verbose

-- Installation checks after hwos - Hardware and Operating system installation

cluvfy stage -pre cfs -n node_list [-verbose]

cluvfy stage -post cfs -n node_list [-verbose]

-- Installation checks before/after Cluster File System

cluvfy stage -pre crsinst -n node_list [-c ocr_location] [-r {10gR1|10gR2|11gR1|11gR2}] [-q voting_disk] [-osdba osdba_group] [-orainv orainventory_group] [-verbose]

cluvfy stage -pre crsinst -n node1,node2,node3

./runcluvfy.sh stage -pre crsinst -n all -verbose

cluvfy stage -post crsinst -n node_list [-verbose]

-- Installation checks before/after CRS installation

cluvfy stage -pre dbinst -n node_list [-r {10gR1|10gR2|11gR1|11gR2}] [-osdba osdba_group] [-orainv orainventory_group] [-verbose]

cluvfy stage -pre dbcfg -n node_list -d oracle_home [-verbose]

-- Installation checks before/after DB installation/configuration

====================================

cluvfy comp component_name component_specific_options [-verbose]

Valid components are:

nodereach : checks reachability between nodes

nodecon : checks node connectivity

cfs : checks CFS integrity

ssa : checks shared storage accessibility

space : checks space availability

sys : checks minimum system requirements

clu : checks cluster integrity

clumgr : checks cluster manager integrity

ocr : checks OCR integrity

olr : checks OLR integrity

ha : checks HA integrity

crs : checks CRS integrity

nodeapp : checks node applications existence

admprv : checks administrative privileges

peer : compares properties with peers

software : checks software distribution

asm : checks ASM integrity

acfs : checks ACFS integrity

gpnp : checks GPnP integrity

gns : checks GNS integrity

scan : checks SCAN configuration

ohasd : checks OHASD integrity

clocksync : checks Clock Synchronization

vdisk : check Voting Disk Udev settings

cluvfy comp nodereach -n node_list [-srcnode node] [-verbose]

cluvfy comp nodecon -n node_list [-i interface_list] [-verbose]

cluvfy comp nodecon -n node1,node2,node3 –i eth0 -verbose

cluvfy comp nodeapp [-n node_list] [-verbose]

cluvfy comp peer [-refnode node] -n node_list [-r {10gR1|10gR2|11gR1|11gR2}] [-orainv orainventory_group] [-osdba osdba_group] [-verbose]

cluvfy comp peer -n node1,node2 -r 10gR2 -verbose

cluvfy comp crs [-n node_list] [-verbose]

cluvfy comp cfs [-n node_list] -f file_system [-verbose]

cluvfy comp cfs -f /oradbshare –n all -verbose

cluvfy comp ocr [-n node_list] [-verbose]

cluvfy comp clu -n node_list -verbose

cluvfy comp clumgr [-n node_list] [-verbose]

cluvfy comp sys [-n node_list] -p {crs|database} [-r {10gR1|10gR2|11gR1|11gR2}] [-osdba osdba_group] [-orainv orainventory_group] [-verbose]

cluvfy comp sys -n node1,node2 -p crs -verbose

cluvfy comp admprv [-n node_list] [-verbose] |-o user_equiv [-sshonly] |-o crs_inst [-orainv orainventory_group] |-o db_inst [-orainv orainventory_group] [-osdba osdba_group] |-o db_config -d oracle_home

cluvfy comp ssa [-n node_list] [-s storageID_list] [-verbose]

cluvfy comp space [-n node_list] -l storage_location -z disk_space{B|K|M|G} [-verbose]

cluvfy comp space -n all -l /home/dbadmin/products –z 2G -verbose

cluvfy comp olr

Related Oracle Articles: crsctl commands RAC srvctl commands RAC crs_stat commands RAC

ocrconfig commands in Oracle RAC

2019-01-06T15:23:00.000+05:30

Oracle RAC ocrconfig commands

OCRCONFIG: -- OCR (Oracle Cluster Registry) CONFIGuration tool / Oracle Local Registry (OLR) config tool

#ocrconfig -help or ocrconfig -h

ocrconfig [option]
option:
[-local] -export filename - Export OCR/OLR contents to a file
[-local] -import filename - Import OCR/OLR contents from a file
[-local] -upgrade [user [group]] - Upgrade OCR from previous version
-downgrade [-version version string] - Downgrade OCR to the specified version
[-local] -backuploc [dirname | +diskgroupname ] - Configure OCR/OLR backup location
[-local] -showbackup [auto|manual] - Show OCR/OLR backup information
[-local] -manualbackup - Perform OCR/OLR backup
[-local] -restore filename - Restore OCR/OLR from physical backup
-replace current filename -replacement new filename - Replace an OCR device or file current filename with new filename
-add filename - Add a new OCR device/file
-delete filename - Remove a OCR device/file
-overwrite - Overwrite OCR configuration on disk
-repair -add filename | -delete filename | -replace current filename -replacement new filename - Repair OCR configuration on the local node
-help - Print out this help information

In Oracle 12c RAC,
[-local] -showbackuploc - Show OCR/OLR backup location
-copy source_filename destination_filename - Copy OCR physical backup from source to destination

# ocrconfig -showbackup [auto|manual] -- default location is $ORA_CRS_HOME/cdata/cluster_name

# ocrconfig -showbackup
# ocrconfig -backuploc dir_name -- change OCR autobackup directory location
# ocrconfig -backuploc /u02/backups

# ocrconfig -manualbackup -- Oracle RAC 11g command, to perform OCR backup manually
# ocrconfig -restore backup_file.ocr -- recovering from autobackup file
# ocrconfig -restore /u02/backups/backup00.ocr
# ocrconfig -restore /u01/app/11.2.0/gi/cdata/cluster-name/backup02.ocr

# ocrconfig -export file_name.dmp [-s online] -- exports OCR content to a file

# ocrconfig -export /tmp/ocr_exp
# ocrconfig -import file_name.dmp -- recover OCR logically, must be done on all nodes

# ocrconfig -import /tmp/ocr_exp

# ocrconfig -replace ocr [file_name] -- adding/replacing an OCR file

# ocrconfig -replace ocrmirror [file_name]

# ocrconfig -replace ocrmirror /data/ocr/ocrfile2

# ocrconfig -repair ocr file_name

# ocrconfig -repair ocrmirror file_name

# ocrconfig -repair -replace current_OCR_location -replacement target_OCR_location

# ocrconfig -upgrade [user [group]] -- upgrades OCR

# ocrconfig -downgrade [-version version_string] -- downgrades OCR

# ocrconfig -overwrite

# ocrconfig –local –import file_name

# ocrconfig –local –manualbackup

# ocrconfig -local -backuploc new_olr_backup_path

# ocrconfig -local -restore file_name

# ocrconfig -local -restore $GRID_HOME/cdata/host06/backup_20171106_02946.olr --restoring OLR file

# ocrconfig -add +new_disk_group

# ocrconfig -add file_location

# ocrconfig -add /dev/sdd1

# ocrconfig -delete +unused_disk_group

# ocrconfig -delete old_storage_location

# ocrconfig -delete /dev/raw/raw2

Log file will be $ORACLE_HOME/log/node_name/client/ocrconfig_pid.log

Debugging can be controlled through $ORA_CRS_HOME/srvm/admin/ocrlog.ini

How to take backup of OCR / OLR file?

# ocrconfig -manualbackup

# ocrconfig -export file_name.dmp

How to recover OCR / OLR file?

# ocrconfig -restore backup_file.ocr

# ocrconfig -import file_name.dmp

Related Oracle RAC Articles: ocrdump commands RAC ocrcheck commands RAC

ocrdump commands in Oracle RAC

2019-01-06T15:19:00.000+05:30

Oracle RAC ocrdump commands

OCRDUMP: -- dumps OCR (Oracle Cluster Registry) / OLR (Oracle Local Registry) contents to a file

# ocrdump -help or ocrdump -h

# ocrdump [-local] [file_name|-stdout] [-backupfile backup_filename] [-keyname key_name] [-xml] [-noheader]

# ocrdump -- default filename is OCRDUMPFILE

# ocrdump MYFILE

# ocrdump ${HOST}_OCRDUMP

# ocrdump -backupfile my_file

# ocrdump -stdout -keyname SYSTEM

# ocrdump -stdout -xml

$ ocrdump -local olr.lst --> Normal Text Format

$ ocrdump -local -xml olr_xml.lst --> XML format

$ ocrdump -local -backupfile olr_backup_file_name
$ ocrdump -backupfile $CRS_HOME/backup.ocr -stdout -xml

Log file will be $ORACLE_HOME/log/node_name/client/ocrdump_pid.log

Debugging can be controlled through $ORA_CRS_HOME/srvm/admin/ocrlog.ini

How to take backup of OCR file?

# ocrdump -backupfile my_file

Related Oracle Articles: ocrconfig commands RAC ocrcheck commands RAC

ocrcheck commands in Oracle RAC

2019-01-06T14:59:00.001+05:30

Oracle RAC 11g / 12c ocrcheck cheatsheet

OCRCHECK: -- Displays health of OCR (Oracle Cluster Registry) / Oracle Local Registry (OLR).

$ ocrcheck -help or ocrcheck -h
Usage in Oracle 11g: ocrcheck [-config] [-local]
Usage in Oracle 12c: ocrcheck [-config | -backupfile backupfilename] [-details] [-local]
-config Displays the configured locations of the Oracle Cluster Registry (OCR). This can be used with the -local option to display the configured location of the Oracle Local Registry (OLR).
-details Displays detailed configuration information.
-local The operation will be performed on the Oracle Local Registry.
-backupfile backupfilename The operation will be performed on the backup file.

$ ocrcheck

Version : 2

Total space (kbytes) : 262144

Used space (kbytes) : 16256

Available space (kbytes) : 245888

ID : 1918913332

Device/File Name : /dev/raw/raw1 Device/File integrity check succeeded

Device/File Name : /dev/raw/raw2 Device/File integrity check succeeded

Cluster registry integrity check succeeded

# ocrcheck -local

Status of Oracle Cluster Registry is as follows :

Version : 3

Total space (kbytes) : 262132

Used space (kbytes) : 9200

Available space (kbytes) : 252932

ID : 604793089

Device/File Name : /u02/crs/cdata/localhost/lnx6.olr Device/File integrity check succeeded

Local OCR integrity check succeeded

$ ocrcheck -local -config

Log file will be $ORACLE_HOME/log/node_name/client/ocrcheck_pid.log

Debugging can be controlled through $ORA_CRS_HOME/srvm/admin/ocrlog.ini

How do I identify the OCR (or OLR) file location?
# ocrcheck

Related Oracle RAC Articles: ocrconfig commands RAC ocrdump commands RAC

onsctl commands in Oracle RAC

2019-01-03T18:08:00.001+05:30

ONSCTL commands in 12c / 11g Oracle RAC

To manage ONS (Oracle Notification Service)

ONS - A publish and subscribe service for communicating information about all FAN events.

In Oracle RAC 11g Release 1,
onsctl or onsctl help or onsctl -h

onsctl start -- to start ONS

onsctl stop -- to stop ONS

onsctl ping -- to find out the status of ONS

onsctl debug -- to display debug information for the ons daemon

onsctl reconfig -- to reload the ons configuration

onsctl detailed -- to print a verbose syntax description

from Oracle 11g release 2
onsctl command [options]

onsctl or onsctl help or onsctl -h

onsctl start -- to start ONS

onsctl shutdown -- to shutdown ONS

onsctl ping [max-retry] -- to ping local ons

onsctl debug [attr=val ...] -- to display ons server debug information

onsctl reload -- to trigger ons to reread its configuration file

onsctl set [attr=val ...] -- to set ons log parameters

onsctl query [attr=val] -- to query ons log parameters

onsctl usage [command] -- to print detailed usage description

Related Oracle Articles: oifcfg commands RAC crsctl commands RAC srvctl commands RAC

Oracle oclumon utility/commands

2018-11-26T20:43:00.001+05:30

oclumon (Oracle Cluster Health Monitor) in Oracle 11g / 12c RAC

oclumon -help
oclumon version

oclumon debug version
oclumon debug [log daemon module:log_level] [version]
oclumon debug [log all/osysmond/ologgerd/client debuglevel] [0-3]
oclumon debug log osysmond CRFMOND:3
oclumon debug log ologgerd CRFLOGD:2
oclumon debug log client allcomp:1
oclumon debug log all allcomp:0

oclumon dumpnodeview [[-allnodes] | [-n node1 node2 ... noden] [-last "duration"] | [-s "time_stamp" -e "time_stamp"] [-i interval] [-v]] [-h]
oclumon dumpnodeview -n host01
oclumon dumpnodeview -n racnode2 -last "00:15:00"
oclumon dumpnodeview -n node1 node3 node5 -last "12:00:00"
oclumon dumpnodeview -allnodes -last "00:15:00" -i 30
oclumon dumpnodeview -v -allnodes -alert -last "01:00:00"
oclumon dumpnodeview -allnodes -s "2016-11-04 10:05:00" -e "2016-11-04 10:10:00"
oclumon dumpnodeview -allnodes -warning -v -s "2016-11-04 10:05:00" -e "2016-11-04 10:05:10"

oclumon manage -repos {{changeretentiontime time} | {changerepossize memory_size}} | -get {key1 [key2 ...] | alllogger [-details] | mylogger [-details]}
oclumon manage -get master # will give master node
oclumon manage -get master path
oclumon manage -get reppath
oclumon manage -get repsize
oclumon manage -get alllogger -details
oclumon manage -get mylogger
oclumon manage -repos changeretentiontime 86400
oclumon manage -repos changerepossize 6000
oclumon manage -repos reploc /nfs/orarac/chm
oclumon manage -db resize 43200

oclumon showtrail -n node1 -nicid eth0 effectivebw errors -c "red" "yellow" "orange" -last "00:15:00"
oclumon showtrail -n node1 -sys usagepc cpuqlen cpunumprocess memfree numrt numofiosps openfds -c "red" "yellow" "orange" -last "00:15:00"

oclumon showobjects
oclumon showobjects -n racnode6 -time "2017-10-24 15:00:00"

Related Oracle Articles: What's new in Oracle 9i/10g/11g RAC What's New in Oracle Database 12c Release1

Oracle RacOneNode Omotion

2018-11-20T05:30:00.000+05:30

RacOneNode Omotion in Oracle RAC

raconeinit - to convert database to RacOneNode.

$ ./raconeinit

raconefix - to fix RacOneNode database in case of failure.

$ ./raconefix

racone2rac - to convert RacOneNode back to RAC.

$ ./racone2rac

raconestatus - Check the status of RAC One Node database

$ ./raconestatus

Omotion - to move from 1 node to other.

$ ./Omotion

$ ./Omotion -v --> v - Verbose

$ ./Omotion -d rac2 -m 15 --> d - database name, m - migration time

Related Oracle RAC Articles: cluvfy commands RAC crsctl commands RAC srvctl commands RAC