User Tools

Site Tools


rac

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
rac [2018/12/08 12:49] – created 0.0.0.0rac [2019/01/30 11:32] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== RAC ======+==== Oracle RAC Overview ==== 
 +  *  [[https://dbaprakash.wordpress.com/2015/03/30/oracle-rac-overview/|dbaprakash.wordpress.com]] 
 +  *  [[http://www.dba-oracle.com/real_application_clusters_rac_grid/srvctl.htm|Server Control Utility (SRVCTL)]] 
 +  * [[https://frankdba.wordpress.com/2011/12/13/srvctl-stop-home/|One command to stop all processes running out of that home - srvctl stop home]] 
 +Real Application Clusters (RAC) is an clustering solution whereby multiple Oracle instances can communicate with one database located on shared storage.\\ 
 +Datafiles and controlfiles are shared but each instance will have its own redo log files and undo tablespace.\\ 
 +Use crsctl to manage the clusterware\\ 
 +Use srvctl to manage the cluster\\
  
-=====Oracle RAC Overview===== +  *  [[https://saruamit4.wordpress.com/2013/04/10/cloning-oracle-home-in-rac/|cloning oracle home in RAC - Amit Saraswat]] 
-  [[https://dbaprakash.wordpress.com/2015/03/30/oracle-rac-overview/|dbaprakash.wordpress.com]] +  *  [[http://www.oracledbasupport.co.uk/rac-asm-crash-scenario/|Loss of a voting disk - oracledbasupport.co.uk]] 
-Real Application Clusters (RAC) is an clustering solution whereby multiple Oracle instances can communicate with one database located on shared storage.<br /> +Know nothing about RAC? Go through the RAC Attack labs step-by-step installation for [[https://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home|11g RAC_Attack!]]\\ 
-Datafiles and controlfiles are shared but each instance will have its own redo log files and undo tablespace.<br /> +or [[https://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home/RAC_Attack_12c|12c RACAttack]] for an excellent (hands on) introduction.\\ 
-Use crsctl to manage the clusterware<br /> +  *  [[RAC Attack template]] 
-Use srvctl to manage the cluster<br /> +==== How to Backup and Restore a RAC Database ==== 
-<br /> +  *  [[https://dbaprakash.wordpress.com/category/backup-and-recovery/|dbaprakash.wordpress.com]] 
-  [[https://saruamit4.wordpress.com/2013/04/10/cloning-oracle-home-in-rac/|cloning oracle home in RAC - Amit Saraswat]] +==== RAC components ==== 
-  * [[http://www.oracledbasupport.co.uk/rac-asm-crash-scenario/|Loss of a voting disk - oracledbasupport.co.uk]] +=== Virtual IP ===
-Know nothing about RAC? Go through the RAC Attack labs step-by-step installation for [[https://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home|11g RAC_Attack!]]<br /> +
-or [[https://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home/RAC_Attack_12c|12c RACAttack]] for an excellent (hands on) introduction.<br /> +
-  * [[RAC Attack template]] +
-=====How to Backup and Restore a RAC Database===== +
-  * [[https://dbaprakash.wordpress.com/category/backup-and-recovery/|dbaprakash.wordpress.com]] +
-=====RAC components===== +
-====Virtual IP====+
 A virtual IP address is an IP address setup to "float" between the real IP addresses associated with each instance in the cluster. If the IP address assigned to the virtual IP becomes unavailable, the IP address from the still available instance will be assigned to the virtual IP thus maintaining database availability for the users. A virtual IP address is an IP address setup to "float" between the real IP addresses associated with each instance in the cluster. If the IP address assigned to the virtual IP becomes unavailable, the IP address from the still available instance will be assigned to the virtual IP thus maintaining database availability for the users.
-====Voting Disk==== +=== Voting Disk === 
-A Voting Disk is a file on a shared filesystem. It maintains a list of available cluster nodes and can resolve split-brain scenarios.<br />+A Voting Disk is a file on a shared filesystem. It maintains a list of available cluster nodes and can resolve split-brain scenarios.\\
 All instances write to the voting disk to indicate that they are still active. All instances write to the voting disk to indicate that they are still active.
-====Cluster Registry====+=== Cluster Registry ===
 The Cluster Registry (OCR) is used to store cluster wide settings and status information such as node names, IP and VIP addresses, voting disk locations, node applications, database names, instance names, listener names, etc. The Cluster Registry (OCR) is used to store cluster wide settings and status information such as node names, IP and VIP addresses, voting disk locations, node applications, database names, instance names, listener names, etc.
  
-====Clusterware processes==== +=== Clusterware processes === 
-A RAC cluster consists of the following daemons<br /> +A RAC cluster consists of the following daemons\\ 
-  * crsd – Cluster Resource Services Daemon +  *  crsd – Cluster Resource Services Daemon 
-  * cssd – Cluster Synchronisation Services Daemon +  *  cssd – Cluster Synchronisation Services Daemon 
-  * evmd – Event Manager Daemon  +  *  evmd – Event Manager Daemon 
-=====RAC commands===== +==== RAC commands ==== 
-====Location of Oracle Local Registry configuration file (olr.loc)====+=== Location of Oracle Local Registry configuration file (olr.loc) ===
 This file points to the clusters local node repository and depending on the OS, it is in one of these 2 locations This file points to the clusters local node repository and depending on the OS, it is in one of these 2 locations
-<code>0@@</code>+<code> 
 +cat /etc/oracle/olr.loc 
 +cat /var/loc/oracle/olr.loc 
 +</code>
 This file is managed by OHASD and will point to the olrconfig_loc and the crs_home This file is managed by OHASD and will point to the olrconfig_loc and the crs_home
-====Location of cluster config files==== +=== Location of cluster config files === 
-<code>1@@</code>+<code> 
 +/etc/oracle/scls_scr/$HOSTNAME 
 +</code>
  
-====Some cluster control commands to check the status / health of the clusterware==== +=== Some cluster control commands to check the status / health of the clusterware === 
-<code>2@@</code> +<code> 
-====List network interfaces available to this cluster node==== +crsctl status resource -t 
-<code>3@@</code> +crsctl status server 
-====Is Oracle Restart (High Availability Service) enabled?==== +crsctl check cluster 
-<code>4@@</code>+crsctl check crs 
 +crsctl query css votedisk 
 +crsctl query crs activeversion 
 +crsctl query crs releaseversion 
 +crsctl query crs softwareversion 
 +</code> 
 +=== List network interfaces available to this cluster node === 
 +<code> 
 +oifcfg iflist -p 
 +</code> 
 +=== Is Oracle Restart (High Availability Service) enabled? === 
 +  * [[https://docs.oracle.com/cd/E18283_01/server.112/e17120/restart004.htm|Stopping and Restarting Oracle Restart for Maintenance Operations]] 
 +<code> 
 +cat /etc/oracle/scls_scr/$HOSTNAME/oracle/ohasdstr 
 +crsctl check has 
 +crsctl config has 
 +crsctl start has 
 +crsctl stop has 
 +crsctl disable has 
 +crsctl enable has 
 +</code>
  
-====Is ASM autostart enabled?==== +=== Is ASM autostart enabled? === 
-<code>5@@</code> +<code> 
-====Are diskgroups registered?==== +crsctl stat res ora.asm 
-<code>6@@</code> +</code> 
-====Is database registered and autostart enabled?==== +=== Are diskgroups registered? === 
-<code>7@@</code>+<code> 
 +srvctl status diskgroup -g DATA 
 +crsctl stat res ora.DATA.dg 
 +</code> 
 +=== Is database registered and autostart enabled? === 
 +<code> 
 +srvctl config database -d <database> 
 +</code>
 if not... if not...
-<code>8@@</code> +<code> 
-====Set ASM diskgroups to be used by database==== +srvctl add database <database> 
-<code>9@@</code> +srvctl enable database <database> 
-====Stop and start the clusterware services====+</code> 
 +=== Set ASM diskgroups to be used by database === 
 +<code> 
 +srvctl modify database -d <database> -diskgroup "DATA,FRA" 
 +</code> 
 +=== Stop and start the clusterware services ===
 To set the correct home, can also search /etc/oratab for the relevant ASM instance and use . oraenv To set the correct home, can also search /etc/oratab for the relevant ASM instance and use . oraenv
-<code>10@@</code>+<code> 
 +export ORA_CRS_HOME=$(awk -F: '/+ASM/ {print $2}' /etc/oratab) 
 +$ORA_CRS_HOME/bin/crsctl start crs 
 +$ORA_CRS_HOME/bin/crsctl stop crs 
 +</code>
  
-=====Prevent cluster services from starting up on boot===== +==== Prevent cluster services from starting up on boot ==== 
-<code>11@@</code> +<code> 
-=====Re-enable clusterware services===== +$ORA_CRS_HOME/bin/crsctl disable crs 
-<code>12@@</code>+</code> 
 +==== Re-enable clusterware services ==== 
 +<code> 
 +$ORA_CRS_HOME/bin/crsctl enable crs 
 +</code>
  
-=====List the resources under cluster control===== +==== List the resources under cluster control ==== 
-<code>13@@</code>+<code> 
 +$ORA_CRS_HOME/bin/crsctl status resource -t
 or or
-<code>14@@</code>+$ORA_CRS_HOME/bin/crsctl stat res -t 
 +</code> 
 +or 
 +<code> 
 +crsctl status res |grep -v "^$"|awk -F "=" 'BEGIN {print " "} {printf("%s",NR%4 ? $2"|" : $2"\ 
 +")}'|sed -e 's/  *, /,/g' -e 's/, /,/g'|\\ 
 +awk -F "|" 'BEGIN { printf "%-40s%-35s%-20s%-50s\ 
 +","Resource Name","Resource Type","Target ","State" }{ split ($3,trg,",") split ($4,st,",")}{for (i in trg) {printf "%-40s%-35s%-20s%-50s\ 
 +",$1,$2,trg[[i]],st[[i]]}}' 
 +</code>
  
-=====Find the ORACLE_HOME from a database cluster metadata file===== +==== Find the ORACLE_HOME from a database cluster metadata file ==== 
-<code>15@@</code> +<code> 
-=====Stop all the cluster resources for a particular ORACLE_HOME===== +crsctl stat res ora.proddb11.db -p | grep ORACLE_HOME 
-If all resources for a home need to go down (e.g. for patching), this should do it.<br />+</code> 
 +==== Stop all the cluster resources for a particular ORACLE_HOME ==== 
 +If all resources for a home need to go down (e.g. for patching), this should do it.\\
 Save the state so that the start command knows what to start and what not to. Save the state so that the start command knows what to start and what not to.
-<code>16@@</code>+<code> 
 +srvctl stop home -o /oracle/product/11.2.0.4 -s /oracle/state_file_11204 
 +or 
 +srvctl stop home -oraclehome /oracle/product/11.2.0.4 -statefile /oracle/state_file_11204 
 +or 
 +srvctl stop home -oraclehome /u01/app/oracle/product/12.1.0.2/dbhome_1 -statefile /home/oracle/home_state_20170111 -node sdtcsynoda02-rac -stopoption IMMEDIATE -force 
 +</code>
 Before running the startup, the state file can be edited and instances added/removed as it is a simple text file Before running the startup, the state file can be edited and instances added/removed as it is a simple text file
-<code>17@@</code>+<code> 
 +srvctl start home -o /u01/app/oracle/product/12.1.0.2/dbhome_1 -s /oracle/state_file_12102 -node sdtcsynoda02-rac 
 +</code>
  
-====General syntax for starting and stopping a RAC instance==== +=== General syntax for starting and stopping a RAC instance === 
-<code>18@@</code> +<code> 
-====Stop one instance of a RAC database==== +srvctl start|stop instance -d <db_unique_name> -i <inst_name_list> [[-o start_options]]|[[-o stop_options]]  [[-c connect_str | -q]] 
-<code>19@@</code>+</code> 
 +=== Stop one instance of a RAC database === 
 +<code> 
 +srvctl stop instance –d <db_name> –i <instance_name> 
 +</code>
  
-====Start an ASM instance on a specific node==== +=== Start an ASM instance on a specific node === 
-<code>20@@</code> +<code> 
-====Stop all instances of a RAC database==== +srvctl start instance –n <node_name> 
-<code>21@@</code> +e.g. 
-====Start all instances of a RAC database==== +srvctl start prodctl –n asmnode1 
-<code>22@@</code> +</code> 
-====Start a database in mount mode==== +=== Stop all instances of a RAC database === 
-<code>23@@</code>+<code> 
 +srvctl stop database –db <db_name> 
 +e.g. 
 +srvctl stop database -db ACCINGPX 
 +</code> 
 +=== Start all instances of a RAC database === 
 +<code> 
 +srvctl start database –db <db_name> 
 +e.g. 
 +srvctl start database -db ACCINGPX 
 +</code> 
 +=== Start a database in mount mode === 
 +<code> 
 +srvctl start database –db <db_name> -o <start option> 
 +e.g. 
 +srvctl start database -db ACCINGPX -o mount 
 +</code>
  
-====Stop ASM on a RAC node==== +=== Stop ASM on a RAC node === 
-<code>24@@</code>+<code> 
 +srvctl stop asm –n <rac node> 
 +e.g. 
 +srvctl stop asm –n asmnode1 -o immediate 
 +</code>
  
-====Start / Stop all node applications on a RAC node==== +=== Start / Stop all node applications on a RAC node === 
-<code>25@@</code>+<code> 
 +srvctl start nodeapps –n <rac node> 
 +srvctl stop nodeapps –n <rac node> 
 +srvctl status nodeapps –n <rac node> 
 +</code>
  
-====Start / Stop a listener on a RAC node==== +=== Start / Stop a listener on a RAC node === 
-<code>26@@</code>+<code> 
 +srvctl start|stop listener -n node_name [[-l listener_name_list]] 
 +e.g. 
 +srvctl start listener -n node2 
 +srvctl start listener -n node2 -l DATAGUARD_LISTENER 
 +srvctl stop LISTENER_SCAN1 
 +</code>
  
-====Start / Stop services on a RAC node==== +=== Start / Stop services on a RAC node === 
-**srvctl stop database command implicity does a srvctl stop services (because services are dependent on database).**<br />+**srvctl stop database command implicity does a srvctl stop services (because services are dependent on database).**\\
 **However, a subsequent srvctl start database requires an explicit srvctl start service** **However, a subsequent srvctl start database requires an explicit srvctl start service**
-  * service name list is optional and if not provided, the SRVCTL starts all of the database's services<br /> +  *  service name list is optional and if not provided, the SRVCTL starts all of the database's services\\ 
-  * -c connect_str Connect string (default: / as sysdba)<br /> +  *  -c connect_str Connect string (default: / as sysdba)\\ 
-  * -q Query connect string from standard input +  *  -q Query connect string from standard input 
-<code>27@@</code>+<code> 
 +srvctl start service -d <db_unique_name> [[-s service_name_list [[-i <inst_name>]]  [[-o <start_options>]] [[-c connect_str | -q]] 
 +srvctl stop service -d db_unique_name [[-s service_name_list [[-i inst_name]]  [[-c connect_str | -q]] [[-f]] 
 +</code>
  
-====Status of an ASM instance on a RAC node==== +=== Status of an ASM instance on a RAC node === 
-<code>28@@</code> +<code> 
-====Status of the database, all instances and all services==== +srvctl status asm -n sdtcsynoda01-rac 
-<code>29@@</code> +srvctl status asm -n sdtcsynoda02-rac 
-<code>30@@</code> +</code> 
-====Status of named instances with their current services (if on local node)==== +=== Status of the database, all instances and all services === 
-<code>31@@</code> +<code> 
-<code>32@@</code> +srvctl status database -d TSTEV3 -v 
-<code>33@@</code> +</code> 
-<code>34@@</code> +<code> 
-====Add a new node==== +Instance TSTEV31 is running on node sdtcsynoda01-rac 
-<code>35@@</code> +Instance TSTEV32 is running on node sdtcsynoda02-rac 
-====Add a new database==== +</code> 
-<code>36@@</code>+=== Status of named instances with their current services (if on local node) === 
 +<code> 
 +srvctl status instance -d TSTEV3 -i TSTEV31 -v 
 +</code> 
 +<code> 
 +Instance TSTEV31 is running on node sdtcsynoda01-rac. Instance status: Open. 
 +</code> 
 +<code> 
 +srvctl status instance -d TSTEV3 -i TSTEV32 -v 
 +</code> 
 +<code> 
 +Instance TSTEV32 is running on node sdtcsynoda02-rac with online services DOTS. Instance status: Open. 
 +</code> 
 +=== Add a new node === 
 +<code> 
 +srvctl add nodeapps -n myclust-1 -o $ORACLE_HOME –A 139.184.201.1/255.255.255.0/hme0 
 +</code> 
 +=== Add a new database === 
 +<code> 
 +srvctl add database -d ORACLE -o $ORACLE_HOME 
 +eg. 
 +srvctl add database -d MASTASPO -o /u01/app/oracle/product/12.1.0.2/dbhome_1 -r PHYSICAL_STANDBY -s MOUNT 
 +</code>
  
-====Add named instances to an existing database==== +=== Add named instances to an existing database === 
-<code>37@@</code>+<code> 
 +srvctl add instance -d ORACLE -i RAC01 -n myclust-1 
 +srvctl add instance -d ORACLE -i RAC02 -n myclust-2 
 +srvctl add instance -d ORACLE -i RAC03 -n myclust-3 
 +eg. 
 +srvctl add instance -d MASTASPO -i MASTASPO -n sdtcoda01-rac 
 +</code>
  
-====Add a service to an existing database with preferred instances (-r) and available instances (-a). Use basic failover to the available instances==== +=== Add a service to an existing database with preferred instances (-r) and available instances (-a). Use basic failover to the available instances === 
-<code>38@@</code>+<code> 
 +srvctl add service -d ORACLE -s STD_BATCH -r RAC01 -a RAC02 
 +</code>
  
-====Add a service to an existing database with preferred instances (-r) and available instances (-a). Use preconnect at the available instances==== +=== Add a service to an existing database with preferred instances (-r) and available instances (-a). Use preconnect at the available instances === 
-<code>39@@</code> +<code> 
-====Remove the applications for a database==== +srvctl add service -d ORACLE -s STD_BATCH -r RAC01 -a RAC02 -P PRECONNECT 
-<code>40@@</code> +</code> 
-====Remove the applications for named instances of an existing database==== +=== Remove the applications for a database === 
-<code>41@@</code> +<code> 
-====Remove the service==== +srvctl remove database -d ORACLE 
-<code>42@@</code> +</code> 
-====Remove the service from the instances==== +=== Remove the applications for named instances of an existing database === 
-<code>43@@</code> +<code> 
-====Remove all node applications from a node==== +srvctl remove instance -d ORACLE -i RAC03 
-<code>44@@</code> +srvctl remove instance -d ORACLE -i RAC04 
-====Modify an instance to execute on another node==== +</code> 
-<code>45@@</code> +=== Remove the service === 
-====Modify a service to execute on another node==== +<code> 
-<code>46@@</code> +srvctl remove service -d ORACLE -s STD_BATCH 
-====Modify an instance to be a preferred instance for a service==== +</code> 
-<code>47@@</code> +=== Remove the service from the instances === 
-====Relocate a service from one instance to another==== +<code> 
-<code>48@@</code> +srvctl remove service -d ORACLE -s STD_BATCH -i RAC03,RAC04 
-====Switchover / failover a database from one node (server) to another==== +</code> 
-<code>49@@</code>+=== Remove all node applications from a node === 
 +<code> 
 +srvctl remove nodeapps -n myclust-4 
 +</code> 
 +=== Modify an instance to execute on another node === 
 +<code> 
 +srvctl modify instance -d ORACLE -n myclust-4 
 +</code> 
 +=== Modify a service to execute on another node === 
 +<code> 
 +srvctl modify service -d ORACLE -s HOT_BATCH -i RAC01 -t RAC02 
 +</code> 
 +=== Modify an instance to be a preferred instance for a service === 
 +<code> 
 +srvctl modify service -d ORACLE -s HOT_BATCH -i RAC02 –r 
 +</code> 
 +=== Relocate a service from one instance to another === 
 +<code> 
 +srvctl relocate service -d orac -s CRM -i RAC04 -t RAC01 
 +</code> 
 +=== Switchover / failover a database from one node (server) to another === 
 +<code> 
 +srvctl relocate db -d orac -n server02 
 +</code>
  
-=====Enable CRS resources (resources can be up or down when these commands are issued)===== +==== Enable CRS resources (resources can be up or down when these commands are issued) ==== 
-====Enable the database==== +=== Enable the database === 
-<code>50@@</code> +<code> 
-====Enable the named instances==== +srvctl enable database -d ORACLE 
-<code>51@@</code> +</code> 
-====Enable the service==== +=== Enable the named instances === 
-<code>52@@</code> +<code> 
-====Enable the service at the named instance==== +srvctl enable instance -d ORACLE -i RAC01, RAC02 
-<code>53@@</code> +</code> 
-=====Disable CRS resources (resources must be down when these commands are issued)===== +=== Enable the service === 
-====Disable the database globally==== +<code> 
-<code>54@@</code> +srvctl enable service -d ORACLE -s ERP,CRM 
-====Disable the named instances==== +</code> 
-<code>55@@</code> +=== Enable the service at the named instance === 
-====Disable the service(s) globally==== +<code> 
-<code>56@@</code>+srvctl enable service -d ORACLE -s CRM -i RAC03 
 +</code> 
 +==== Disable CRS resources (resources must be down when these commands are issued) ==== 
 +=== Disable the database globally === 
 +<code> 
 +srvctl disable database -d ORACLE 
 +</code> 
 +=== Disable the named instances === 
 +<code> 
 +srvctl disable instance -d ORACLE -i RAC01, RAC02 
 +</code> 
 +=== Disable the service(s) globally === 
 +<code> 
 +srvctl disable service -d ORACLE -s ERP,CRM 
 +</code>
  
-====Disable the service on the named instance==== +=== Disable the service on the named instance === 
-<code>57@@</code>+<code> 
 +srvctl disable service -d ORACLE -s CRM -i RAC02 
 +</code>
  
-====Status of a named services==== +=== Status of a named services === 
-<code>58@@</code>+<code> 
 +srvctl status service -d TSTEV3 -s DOTS -v 
 +</code>
  
-====Status of all nodes supporting database applications==== +=== Status of all nodes supporting database applications === 
-<code>59@@</code>+<code> 
 +srvctl status nodeapps 
 +</code>
  
-====How to tell if database is a RAC cluster====+=== How to tell if database is a RAC cluster ===
 This will be TRUE if RAC database This will be TRUE if RAC database
-<code>60@@</code>+<code> 
 +show parameter cluster 
 +</code>
 or, the GV$ views will show more than 1 record or, the GV$ views will show more than 1 record
-<code>61@@</code>+<code> 
 +select * from gv$instance; 
 + 
 +   INST_ID INSTANCE_NUMBER INSTANCE_NAME    HOST_NAME                                                        VERSION           STARTUP_T STATUS       PAR    THREAD# ARCHIVE LOG_SWITCH_WAIT LOGINS     SHU DATABASE_STATUS   INSTANCE_ROLE      ACTIVE_ST BLO     CON_ID INSTANCE_MO EDITION FAMILY 
 +---------- --------------- ---------------- ---------------------------------------------------------------- ----------------- --------- ------------ --- ---------- ------- --------------- ---------- --- ----------------- ------------------ --------- --- ---------- ----------- ------- -------------------------------------------------------------------------------- 
 +                       2 DEV32          oda02-rac                                                 12.1.0.2.0        20-JUL-16 OPEN         YES         2 STARTED                  ALLOWED    NO  ACTIVE            PRIMARY_INSTANCE   NORMAL    NO           0 REGULAR     EE 
 +                       1 DEV31          oda01-rac                                                 12.1.0.2.0        13-OCT-16 OPEN         YES         1 STARTED                  ALLOWED    NO  ACTIVE            PRIMARY_INSTANCE   NORMAL    NO           0 REGULAR     EE 
 + 
 +2 rows selected. 
 +</code>
 or or
-<code>62@@</code>+<code> 
 +set serverout on 
 +begin 
 +    if dbms_utility.is_cluster_database then 
 +        dbms_output.put_line('Running in RAC mode.'); 
 +    else 
 +        dbms_output.put_line('Running in EXCLUSIVE mode.'); 
 +    end if; 
 +end; 
 +
 +</code>
 or or
-<code>63@@</code>+<code> 
 +select * from v_$active_instances; 
 +</code>
 or or
-<code>64@@</code> +<code> 
-====Show session distribution across the RAC nodes==== +select * from v_$thread; 
-<code>65@@</code>+</code> 
 +=== Show session distribution across the RAC nodes === 
 +<code> 
 +select inst_id 
 +,      count(*) sessions 
 +from   gv$session 
 +where  type = 'USER' 
 +group  by inst_id 
 +
 +</code> 
rac.1544273361.txt.gz · Last modified: 2018/12/08 12:49 by 0.0.0.0

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki