[root@hs10dbadm01 u01]# which exachk
/usr/bin/exachk
[root@hs10dbadm01 u01]# exachk
Searching for running databases . . . . .
. . . . . .
List of running databases registered in OCR
1. ggfws
2. orcl
3. rstods
4. All of above
5. None of above
Select databases from list for checking best practices. For multiple databases, select 4 for All or comma separated number like 1,2 etc [1-5][4]. 3
Reading storage servers password from wallet.
Node hs10cel02-priv2 is configured for ssh user equivalency for root user
Node hs10cel03-priv2 is configured for ssh user equivalency for root user
Node hs10cel04-priv2 is configured for ssh user equivalency for root user
Node hs10cel05-priv2 is configured for ssh user equivalency for root user
Node hs10cel06-priv2 is configured for ssh user equivalency for root user
Node hs10cel07-priv2 is configured for ssh user equivalency for root user
Node hs10cel01-priv2 is configured for ssh user equivalency for root user
. . . . . . . . . . . . . . . . . . . . . . . . . .
Either Cluster Verification Utility pack (cvupack) does not exist at /u01/oracle.ahf/common/cvu or it is an old or invalid cvupack
Checking Cluster Verification Utility (CVU) version at CRS Home - /u01/app/19.0.0.0/grid
This version of Cluster Verification Utility (CVU) was released on 06-Jan-2020 and it is older than 180 days. It is highly recommended that you download the latest version of CVU from MOS patch 30839369 to ensu
re the highest level of accuracy of the data contained within the report
Do you want to download latest version of Cluster Verification Utility (CVU) from my oracle support? [y/n] [y] n
Running older version of Cluster Verification Utility (CVU) from CRS Home - /u01/app/19.0.0.0/grid
Starting to run exachk in background on hs10dbadm02 using socket
Starting to run exachk in background on hs10dbadm03 using socket
Starting to run exachk in background on hs10dbadm04 using socket
. .
. .
Checking Status of Oracle Software Stack - Clusterware, ASM, RDBMS on hs10dbadm01
.
. . . . . . . . . .
-------------------------------------------------------------------------------------------------------
Oracle Stack Status
-------------------------------------------------------------------------------------------------------
Host Name CRS Installed RDBMS Installed CRS UP ASM UP RDBMS UP DB Instance Name
-------------------------------------------------------------------------------------------------------
hs10dbadm01 Yes Yes Yes Yes No
-------------------------------------------------------------------------------------------------------
.
. . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
*** Checking Best Practice Recommendations ( Pass / Warning / Fail ) ***
.
Collections and audit checks log file is
/u01/oracle.ahf/data/hs10dbadm01/exachk/user_root/output/exachk_hs10dbadm01_102622_102127/log/exachk.log
============================================================
Node name - hs10dbadm01
============================================================
. . . . . .
Collecting - ASM Disk Group for Infrastructure Software and Configuration
Collecting - ASM Diskgroup Attributes
Collecting - ASM High Redundancy Grid Disks
Collecting - ASM diskgroup usable free space
Collecting - ASM initialization parameters
Collecting - CELL ID Info
Collecting - CPU Information
Collecting - Compute node PCI bus slot speed for infiniband HCAs
Collecting - Kernel parameters
Collecting - Maximum number of semaphore sets on system
Collecting - Maximum number of semaphores on system
Collecting - OS Packages
Collecting - Patches for Grid Infrastructure
Collecting - Patches for RDBMS Home
Collecting - RDBMS and GRID software owner UID across cluster
Collecting - RDBMS patch inventory
Collecting - number of semaphore operations per semop system call
Collecting - CRS user limits configuration
Collecting - CRS user time zone check
Collecting - Check alerthistory for non-test open stateless alerts [Database Server]
Collecting - Check alerthistory for stateful alerts not cleared [Database Server]
Collecting - Clusterware patch inventory
Collecting - Collect ksplice fixes [Database Server]
Collecting - Database server system model number
Collecting - Discover switch type(spine or leaf)
Collecting - Exadata Critical Issue DB09
Collecting - Exadata Critical Issue EX30
Collecting - Exadata Critical Issue EX56
Collecting - Exadata Critical Issue EX57
Collecting - Exadata Critical Issue EX58
Collecting - Exadata Critical Issue EX64
Collecting - Exadata Critical Issue EX69
Collecting - Exadata Critical Issue EX73
Collecting - Exadata critical issue EX48
Collecting - Exadata critical issue EX50
Collecting - Exadata critical issue EX55
Collecting - Exadata software version on database server
Collecting - Exadata version on database server
Collecting - HCA firmware version on database server
Collecting - HCA transfer rate on database server
Collecting - Infrastructure Software and Configuration for compute
Collecting - MaxStartups setting in sshd_config
Collecting - OFED Software version on database server
Collecting - Obtain hardware information
Collecting - Operating system and Kernel version on database server
Collecting - Oracle monitoring agent and/or OS settings on ADR diagnostic directories
Collecting - Raid controller bus link speed
Collecting - Review Non-Exadata components in use on the InfiniBand fabric
Collecting - System Event Log
Collecting - Validate key sysctl.conf parameters on database servers
Collecting - Verify Data Network is Separate from Management Network
Collecting - Verify Database Server Disk Controller Configuration
Collecting - Verify Database Server Physical Drive Configuration
Collecting - Verify Database Server Virtual Drive Configuration
Collecting - Verify Disk Cache Policy on database server
Collecting - Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]
Collecting - Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON
Collecting - Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE
Collecting - Verify IP routing configuration on database servers
Collecting - Verify InfiniBand network parameters on Database Servers
Collecting - Verify Master (Rack) Serial Number is Set [Database Server]
Collecting - Verify Quorum disks configuration
Collecting - Verify RAID Controller Battery Temperature [Database Server]
Collecting - Verify RAID disk controller CacheVault capacitor condition [Database Server]
Collecting - Verify TCP Selective Acknowledgement is enabled
Collecting - Verify active kernel version matches expected version for installed Exadata Image
Collecting - Verify available ksplice fixes are installed [Database Server]
Collecting - Verify basic Logical Volume(LVM) system devices configuration
Collecting - Verify database server InfiniBand network MTU size
Collecting - Verify database server disk controllers use writeback cache
Collecting - Verify database server file systems have Maximum mount count = -1
Collecting - Verify imageinfo on database server
Collecting - Verify imageinfo on database server to compare systemwide
Collecting - Verify installed rpm(s) kernel type match the active kernel version
Collecting - Verify key InfiniBand fabric error counters are not present
Collecting - Verify proper ACFS drivers are installed for Spectre v2 mitigation
Collecting - Verify service exachkcfg autostart status on database server
Collecting - Verify sysctl.conf parameter vm.nr_hugepages value is same or less in initramfs [Database Server]
Collecting - Verify the InfiniBand Fabric Topology (verify-topology)
Collecting - Verify the Master Subnet Manager is running on an InfiniBand switch
Collecting - Verify the Name Service Cache Daemon (NSCD) configuration
Collecting - Verify the Subnet Manager is properly disabled [Database Server]
Collecting - Verify the currently active image status [Database Server]
Collecting - Verify the ib_sdp module is not loaded into the kernel
Collecting - Verify the storage servers in use configuration matches across the cluster
Collecting - Verify the vm.min_free_kbytes configuration
Collecting - collect time server data [Database Server]
Collecting - root time zone check
Collecting - verify asr exadata configuration check via ASREXACHECK on database server
Starting to run root privileged commands in background on storage server hs10cel02 (192.168.10.12)
Starting to run root privileged commands in background on storage server hs10cel03 (192.168.10.14)
Starting to run root privileged commands in background on storage server hs10cel04 (192.168.10.16)
Starting to run root privileged commands in background on storage server hs10cel05 (192.168.10.18)
Starting to run root privileged commands in background on storage server hs10cel06 (192.168.10.20)
Starting to run root privileged commands in background on storage server hs10cel07 (192.168.10.22)
Starting to run root privileged commands in background on storage server hs10cel01 (192.168.10.10)
Collections from storage server:
------------------------------------------------------------
Collecting - Exadata server system model number
Collecting - Exadata Critical Issue EX31
Collecting - Exadata Critical Issue EX65
Collecting - Exadata Critical Issue EX28
Collecting - Exadata Critical Issue EX11
Collecting - Exadata critical issue EX47
Collecting - Exadata Critical Issue EX54
Collecting - Exadata Critical Issue EX73
Collecting - Cell ID for dom0 and Baremetal
Collecting - Exadata Critical Issue EX70
Collecting - Exadata Critical Issue EX58
Collecting - Verify Disk Cache Policy on storage servers
Collecting - Exadata software version on storage server
Collecting - Exadata software version on storage servers
Collecting - Exadata Critical Issue EX10
Collecting - Exadata critical issue EX51
Collecting - Exadata critical issue EX37
Collecting - Exadata critical issue EX14
Collecting - Verify Exadata Smart Flash Cache is created
Collecting - Exadata Critical Issue EX45
Collecting - Exadata Critical Issue EX69
Collecting - Exadata Critical Issue EX57
Collecting - Exadata Critical Issue EX64
Collecting - RAID controller version on storage servers
Collecting - Exadata critical issue EX48
Collecting - Exadata Critical Issue EX22
Collecting - Exadata critical issue EX16
Collecting - Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Storage Server]
Collecting - Verify Master (Rack) Serial Number is Set [Storage Server]
Collecting - Verify RAID Controller Battery Temperature [Storage Server]
Collecting - Verify OSSCONF/cellinit.ora consistency across storage servers
Collecting - Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE on storage servers
Collecting - Verify RAID Controller Battery Condition [Storage Server]
Collecting - Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON on storage servers
Collecting - Verify RAID disk controller CacheVault capacitor condition [Storage Server]
Collecting - Verify active system values match those defined in configuration file cell.conf [Storage Server]
Collecting - Verify Storage Server Hidden Parameter Usage
Collecting - Verify Storage Server user CELLDIAG exists
Collecting - Verify data (non-system) disks on Exadata Storage Servers have no partitions
Collecting - Verify available ksplice fixes are installed [Storage Server]
Collecting - Verify imageinfo on storage server
Collecting - Verify imageinfo on storage server to compare systemwide
Collecting - Verify release tracking bug on storage servers
Collecting - collect storage server flashcachemode data
Collecting - Verify there are no files present that impact normal firmware update procedures [Storage Server]
Collecting - Check alerthistory for stateful alerts not cleared [Storage Server]
Collecting - Verify that package exadata-sun-cellnode is installed
Collecting - Verify the Subnet Manager is properly disabled [Storage Server]
Collecting - Verify service exachkcfg autostart status on storage server
Collecting - collect time server data [Storage Server]
Collecting - Check alerthistory for non-test open stateless alerts [Storage Server]
Collecting - verify asr exadata configuration check via ASREXACHECK on storage servers
Collecting - Exadata storage server root filesystem free space
Collecting - Exadata Celldisk predictive failures
Collecting - HCA firmware version on storage server
Collecting - OFED Software version on storage server
Collecting - Determine storage server type(All Flash/High Capacity)
Collecting - Operating system and Kernel version on storage server
Collecting - Storage server flash cache mode
Collecting - Storage server make and model
Collecting - Verify Datafiles are Placed on Diskgroups consisting of griddisks with correct attributes
Collecting - Verify Ethernet Cable Connection Quality on storage servers
Collecting - Verify Data Network is Separate from Management Network on storage server
Collecting - Verify Exadata Smart Flash Cache is actually in use
Collecting - Verify ExaWatcher is executing [Storage Server]
Collecting - Verify Exadata Smart Flash Cache status is normal
Collecting - Verify Exadata Smart Flash Log is Created
Collecting - Verify InfiniBand Cable Connection Quality on storage servers
Collecting - Verify average ping times to DNS nameserver [Storage Server]
Collecting - Verify griddisk ASM status
Collecting - Verify storage server metric CD_IO_ST_RQ
Collecting - Verify the percent of available celldisk space used by the griddisks
Collecting - Verify the currently active image status [Storage Server]
Collecting - Verify there are no griddisks configured on flash memory devices
Collecting - mpt_cmd_retry_count from /etc/modprobe.conf on Storage Servers
Data collections completed. Checking best practices on hs10dbadm01.
------------------------------------------------------------
FAIL => One or more storage servers have stateful alerts that have not been cleared.
FAIL => One or more database servers have stateful alerts that have not been cleared
CRITICAL => Active system values should match those defined in configuration file "cell.conf"
FAIL => ASM parameter SGA_TARGET is not set according to recommended value.
FAIL => The vm.min_free_kbytes configuration is not set as recommended
FAIL => Automatic Storage Management Cluster File System (ACFS) filesystems and critical database files are in the same ASM disk group
CRITICAL => System is exposed to Exadata Critical Issue EX58
CRITICAL => System is exposed to Exadata Critical Issue EX58
WARNING => Key InfiniBand fabric error counters should not be present
CRITICAL => System is exposed to Exadata critical issue DB47
FAIL => One or more InfiniBand network cables are not connected.
FAIL => One or more Ethernet network cables are not connected.
FAIL => One or more InfiniBand network parameters on Database Servers are not as expected
FAIL => ASM parameter PGA_AGGREGATE_TARGET should be set according to recommended value
WARNING => Average ping times to DNS nameserver may be negatively impacting SSH operations.
FAIL => Exadata software version on database server does not meet certified platinum configuration
FAIL => Exadata software version on storage server does not meet certified platinum configuration
INFO => CPU Capacity sizing data activity monitoring information
INFO => Exadata Critical Issues (Doc ID 1270094.1):- DB1-DB4,DB6,DB9-DB49, EX1-EX65,EX67,EX69-EX76 and IB1-IB3,IB5-IB9
Copying results from hs10dbadm02 and generating report. This might take a while. Be patient.
============================================================
Node name - hs10dbadm02
============================================================
. . . . . .
Collecting - ASM Disk Group for Infrastructure Software and Configuration
Collecting - ASM Diskgroup Attributes
Collecting - ASM High Redundancy Grid Disks
Collecting - ASM diskgroup usable free space
Collecting - ASM initialization parameters
Collecting - CELL ID Info
Collecting - CPU Information
Collecting - Compute node PCI bus slot speed for infiniband HCAs
Collecting - Kernel parameters
Collecting - Maximum number of semaphore sets on system
Collecting - Maximum number of semaphores on system
Collecting - OS Packages
Collecting - Patches for Grid Infrastructure
Collecting - Patches for RDBMS Home
Collecting - RDBMS and GRID software owner UID across cluster
Collecting - RDBMS patch inventory
Collecting - number of semaphore operations per semop system call
Data collections completed. Checking best practices on hs10dbadm02.
------------------------------------------------------------
FAIL => One or more database servers have stateful alerts that have not been cleared
FAIL => ASM parameter SGA_TARGET is not set according to recommended value.
FAIL => The vm.min_free_kbytes configuration is not set as recommended
CRITICAL => System is exposed to Exadata Critical Issue EX58
CRITICAL => System is exposed to Exadata critical issue DB47
FAIL => One or more InfiniBand network cables are not connected.
FAIL => One or more Ethernet network cables are not connected.
FAIL => One or more InfiniBand network parameters on Database Servers are not as expected
FAIL => ASM parameter PGA_AGGREGATE_TARGET should be set according to recommended value
FAIL => Exadata software version on database server does not meet certified platinum configuration
Copying results from hs10dbadm03 and generating report. This might take a while. Be patient.
============================================================
Node name - hs10dbadm03
============================================================
. . . . . .
Collecting - ASM Disk Group for Infrastructure Software and Configuration
Collecting - ASM Diskgroup Attributes
Collecting - ASM High Redundancy Grid Disks
Collecting - ASM diskgroup usable free space
Collecting - ASM initialization parameters
Collecting - CELL ID Info
Collecting - Database Parameters for rstods database
Collecting - Database Undocumented Parameters for rstods database
Collecting - CPU Information
Collecting - Clusterware and RDBMS software version
Collecting - Compute node PCI bus slot speed for infiniband HCAs
Collecting - Kernel parameters
Collecting - Maximum number of semaphore sets on system
Collecting - Maximum number of semaphores on system
Collecting - OS Packages
Collecting - Patches for Grid Infrastructure
Collecting - Patches for RDBMS Home
Collecting - RDBMS and GRID software owner UID across cluster
Collecting - RDBMS patch inventory
Collecting - number of semaphore operations per semop system call
Data collections completed. Checking best practices on hs10dbadm03.
------------------------------------------------------------
FAIL => Hidden database Initialization Parameter usage is not correct for rstods
FAIL => One or more database servers have stateful alerts that have not been cleared
INFO => Oracle GoldenGate failure prevention best practices
FAIL => ASM parameter SGA_TARGET is not set according to recommended value.
WARNING => One or more open PDBs do not have non-default services defined for rstods
FAIL => The vm.min_free_kbytes configuration is not set as recommended
FAIL => One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for rstods
INFO => Please refer to data and guidance provided for database parameter processes for rstods
WARNING => filesystemio_options is not set to recommended value on rstods1 instance
CRITICAL => System is exposed to Exadata Critical Issue EX58
FAIL => One or more log archive destination and alternate log archive destination settings are not as recommended for rstods
FAIL => Table AUD$[FGA_LOG$] should use Automatic Segment Space Management for rstods
CRITICAL => System is exposed to Exadata critical issue DB47
FAIL => Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on rstods1 instance
FAIL => Database parameter OS_AUTHENT_PREFIX is not set to recommended value on rstods1 instance
CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on rstods1 instance
FAIL => One or more InfiniBand network cables are not connected.
FAIL => One or more Ethernet network cables are not connected.
WARNING => Database parameter DB_BLOCK_CHECKING on primary is not set to the recommended value. for rstods
FAIL => Flashback on primary is not configured for rstods
WARNING => fast_start_mttr_target should be greater than or equal to 300 on rstods1 instance
FAIL => One or more InfiniBand network parameters on Database Servers are not as expected
FAIL => ASM parameter PGA_AGGREGATE_TARGET should be set according to recommended value
FAIL => Database parameter target_pdbs is not set within best practice thresholds for rstods
FAIL => Database control files are not configured as recommended for rstods
WARNING => Redo log files should be appropriately sized for rstods
FAIL => Standby redo logs should be configured on the primary for rstods
FAIL => Standby is not running in MANAGED REAL TIME APPLY mode for rstods
WARNING => Database parameter LOG_FILE_NAME_CONVERT and DB_CREATE_ONLINE_LOG_DEST_1 are null for rstods
INFO => While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Primary Database for rstods
FAIL => Data Guard broker configuration does not exist for rstods
INFO => The Optimizer fixes for 19c database version is disabled by default for bugs with status value 0 for rstods
FAIL => Exadata software version on database server does not meet certified platinum configuration
FAIL => Oracle database does not meet certified platinum configuration for rstods
WARNING => Some Auto Extensible datafiles are not expanding by at least one stripe width for rstods
WARNING => RMAN controlfile autobackup should be set to ON for rstods
INFO => Database feature usage statistics for rstods
Copying results from hs10dbadm04 and generating report. This might take a while. Be patient.
============================================================
Node name - hs10dbadm04
============================================================
. . . . . .
Collecting - ASM Disk Group for Infrastructure Software and Configuration
Collecting - ASM Diskgroup Attributes
Collecting - ASM High Redundancy Grid Disks
Collecting - ASM diskgroup usable free space
Collecting - ASM initialization parameters
Collecting - CELL ID Info
Collecting - Database Parameters for rstods database
Collecting - Database Undocumented Parameters for rstods database
Collecting - CPU Information
Collecting - Clusterware and RDBMS software version
Collecting - Compute node PCI bus slot speed for infiniband HCAs
Collecting - Kernel parameters
Collecting - Maximum number of semaphore sets on system
Collecting - Maximum number of semaphores on system
Collecting - OS Packages
Collecting - Patches for Grid Infrastructure
Collecting - Patches for RDBMS Home
Collecting - RDBMS and GRID software owner UID across cluster
Collecting - RDBMS patch inventory
Collecting - number of semaphore operations per semop system call
Data collections completed. Checking best practices on hs10dbadm04.
------------------------------------------------------------
FAIL => Hidden database Initialization Parameter usage is not correct for rstods
FAIL => One or more database servers have stateful alerts that have not been cleared
INFO => Oracle GoldenGate failure prevention best practices
FAIL => ASM parameter SGA_TARGET is not set according to recommended value.
WARNING => One or more open PDBs do not have non-default services defined for rstods
FAIL => The vm.min_free_kbytes configuration is not set as recommended
FAIL => One or more of SYSTEM, SYSAUX, USERS, TEMP tablespaces are not of type bigfile for rstods
INFO => Please refer to data and guidance provided for database parameter processes for rstods
WARNING => filesystemio_options is not set to recommended value on rstods2 instance
CRITICAL => System is exposed to Exadata Critical Issue EX58
FAIL => One or more log archive destination and alternate log archive destination settings are not as recommended for rstods
CRITICAL => System is exposed to Exadata critical issue DB47
FAIL => Database parameter DB_LOST_WRITE_PROTECT is not set to recommended value on rstods2 instance
FAIL => Database parameter OS_AUTHENT_PREFIX is not set to recommended value on rstods2 instance
CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on rstods2 instance
FAIL => One or more InfiniBand network cables are not connected.
WARNING => Database parameter DB_BLOCK_CHECKING on primary is not set to the recommended value. for rstods
WARNING => fast_start_mttr_target should be greater than or equal to 300 on rstods2 instance
FAIL => One or more InfiniBand network parameters on Database Servers are not as expected
FAIL => ASM parameter PGA_AGGREGATE_TARGET should be set according to recommended value
FAIL => Database parameter target_pdbs is not set within best practice thresholds for rstods
FAIL => Database control files are not configured as recommended for rstods
WARNING => Redo log files should be appropriately sized for rstods
INFO => The Optimizer fixes for 19c database version is disabled by default for bugs with status value 0 for rstods
FAIL => Exadata software version on database server does not meet certified platinum configuration
FAIL => Oracle database does not meet certified platinum configuration for rstods
WARNING => Some Auto Extensible datafiles are not expanding by at least one stripe width for rstods
------------------------------------------------------------
CLUSTERWIDE CHECKS
------------------------------------------------------------
------------------------------------------------------------
Detailed report (html) - /u01/oracle.ahf/data/hs10dbadm01/exachk/user_root/output/exachk_hs10dbadm01_102622_102127_1842XC200J/exachk_hs10dbadm01_102622_102127_1842XC200J.html
UPLOAD [if required] - /u01/oracle.ahf/data/hs10dbadm01/exachk/user_root/output/exachk_hs10dbadm01_102622_102127_1842XC200J.zip
「喜欢这篇文章，您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容，转载时必须标注文章的来源（墨天轮），文章链接，文章作者等基本信息，否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容，欢迎发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。
