Skip to main content

What all you can query with crsctl query command in Oracle 12c


<<Back to Oracle RAC Main Page

Using crsctl query command in Oracle 12c

Display CRS admin list

$ crsctl query crs administrator
CRS Administrator List: oracle root
     
Gets the value of automatic start delay and server Count
$ crsctl query crs autostart
'Autostart delay':       0
'Autostart servercount': 1

Lists the Oracle Clusterware active Version
$ crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [12.2.0.1.0]

List the cluster state and active patch Level
$ crsctl query crs activeversion -f
Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].

Lists the Oracle Clusterware release version    
$ crsctl query crs releaseversion
Oracle High Availability Services release version on the local node is [12.2.0.1.0]


Lists the version of Oracle Clusterware software installed
$ crsctl query crs softwareversion -all
Oracle Clusterware version on node [node1] is [12.2.0.1.0]
Oracle Clusterware version on node [node2] is [12.2.0.1.0]

Lists the Oracle Clusterware release patch level
$ crsctl query crs releasepatch
Oracle Clusterware release patch level is [0] and no patches have been applied on the local node.


Lists the patch level of Oracle Clusterware software installed
$ crsctl query crs softwarepatch
Oracle Clusterware patch level on node node1 is [0].


Lists the Last active timestamp of a leaf node in case of Flex Cluster
$ crsctl query crs lastactivetimestamp
  CRS-41006: Node node1 is not a leaf node.
Note:- you will get proper oputput if you have Flex Cluster configurtion
 
List the site to which the node or disk belongs.
$ crsctl query crs site -n node1
Node 'node1' belongs to site 'rac01'
$ crsctl query crs site -d DISK1
Disk 'DISK1' belongs to site 'rac01'

Checks whether Oracle Clusterware has been configured for IPMI
$   crsctl query css ipmiconfig
CRS-4237: Oracle Clusterware is not fully configured to use IPMI

Checks whether the IPMI device/driver is present
$ crsctl query css ipmidevice
CRS-4218: Unable to access an IPMI device on this system
    
Lists the voting files used by Cluster Synchronization Services
$ crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   c3723335e2f14f2abf29a7f3e1f8d2cf (/dev/oracleasm/disks/DISK2) [OCR_VOT]
 2. ONLINE   d70e3c6100f34f32bff4d18de037ed7b (/dev/oracleasm/disks/DISK1) [OCR_VOT]
 3. ONLINE   c28a7ab739174f41bf61e9fef170a291 (/dev/oracleasm/disks/DISK3) [OCR_VOT]
Located 3 voting disk(s).

Check if the designated wallet or user exists
crsctl query wallet -type [-name ] [-user | -all]
where
     wallet_type     Type of wallet i.e. APPQOSADMIN, APPQOSUSER, APPQOSDB, MGMTDB, OSUSER or CVUDB.
     name            Name is required for APPQOSDB and CVUDB wallets.
     user_name       User to be queried from wallet.
     all             List all users in wallet

List the system configured DNS server, search paths, attempt and timeout values
$ crsctl query dns -servers
CRS-10018: the following configuration was found on the system:
CRS-10019: There are 1 domains in search order. They are:
oracle.com
CRS-10022: There are 1 name servers. They are:
192.9.1.102
CRS-10020: number of retry attempts for name lookup is: 4
CRS-10021: timeout for each name lookup is: 5

Query the resolution of Server from DNS
  crsctl query dns -name [-dnsserver ] [-type ] [-port ] [-attempts ] [-timeout ] [-v]   
Where
    name                Fully qualified domain name to lookup
    DNS_server_address  Address of the DNS server on which name needs to be looked up
    query_type          The query type is A or AAAA for IPv4 or IPv6 respectively. The default query_type is A.
    port                Port on which DNS server is listening
    attempts            Number of retry attempts
    timeout             Timeout in seconds
$ crsctl query dns -name node1.oracle.com -dnsserver 192.9.1.102
CRS-10024: DNS server returned 192.9.1.100  for name node1.oracle.com
$ crsctl query dns -name scan -dnsserver 192.9.1.102
CRS-10024: DNS server returned 192.9.1.120 192.9.1.121 192.9.1.122  for name scan

List the cluster resource Activity log.
crsctl query calog [-aftertime ] [-beforetime ] [-duration | -follow] [-filter ] [-fullfmt | -xmlfmt]

 List the valid credentials targets to be used with credentials commands
$ crsctl query credentials targetlist

 List the valid credentials under a specific target
$crsctl query credentials -target
List the nodes and disks that the sites contain.
  crsctl query cluster site { | -all}
Where
       site_name             The site name to be queried
       -all                  List all sites.
$ crsctl query cluster site -all
Site 'rac01' identified by GUID 'b8d38f6a064f6f7aff8334e9061f3cc4' in state 'ENABLED' contains nodes 'node1,node2' and no disk.
Obtain Member Cluster Configuration Information
crsctl query member_cluster_configuration []
where
        member_cluster_name    Name of the Member Cluster
         If no member cluster name is provided then the details of all
         the member clusters are displayed.

Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more