exacheck (exadata篇)

官方文档是:Oracle Exadata Database Machine exachk or HealthCheck (文档 ID 1070954.1) 下载最新版本,上传服务器并解压. 查看帮助 [root@dm02db01 ht]# ./exachk -h         | -S         | -a         | -acchk         | -appjar         | -apptrc         | -asmhome         | -async         | -auto_restart         | -autostart         | -autostop         | -b         | -baseline         | -c         | -cells         | -celltmpdir         | -check         | -checkdbupload         | -checkfaileduploads         | -checktfafaileduploads         | -checktfaupload         | -classicjson         | -cleanup         | -clusternodes         | -cmupgrade         | -compute_user         | -configdir         | -credconfig         | -credfile         | -d         | -dball         | -dbconfig         | -dbnames         | -dbnone         | -dbparallel         | -dbparallelmax         | -dbserial         | -debug         | -decryptzip         | -diff         | -disabletfaupload         | -download         | -ebs32bit         | -enabletfaupload         | -encryptzip         | -event         | -exadiff         | -excludecheck         | -excludediscovery         | -excludeprofile         | -extzfsnodes         | -f         | -failedchecks         | -fileattr         | -fileattronly         | -force         | -get         | -getcheckxml         | -getdbupload         | -getfromwallet         | -gettfaupload         | -h         | -help         | -ibswitches         | -ibtmpdir         | -id         | -identitydir         | -idm         | -idm_config         | -idmdbpostinstall         | -idmdbpreinstall         | -idmdbruntime         | -idmdiscargs         | -idmhcargs         | -idmpostinstall         | -idmpreinstall         | -idmruntime         | -includedir         | -init_dstart         | -initcheck         | -initrmsetup         | -initsetup         | -javahome         | -jdbcver         | -json         | -key         | -localonly         | -lockcells         | -logconf         | -loglevel         | -m         | -merge         | -module         | -mserver_conf         | -n         | -nocleanup         | -nodaemon         | -nopass         | -nordbms         | -noreport         | -noscore         | -noupgrade         | -o         | -opc         | -oracle_compute         | -orainst         | -ords         | -ordscheck         | -ordscollectionretention         | -ordshomedir         | -ordsrmsetup         | -ordssetup         | -outfile         | -output         | -p         | -pdbnames         | -postupgrade         | -preupgrade         | -probe         | -profile         | -r         | -remotedestdir         | -remotehost         | -remoteuser         | -repaircheck         | -s         | -sendemail         | -sender_email         | -set         | -setasm         | -setcrs         | -setdbupload         | -setemagent         | -setiam         | -setinvloc         | -setinwallet         | -setjava         | -setjdbcver         | -settfaupload         | -setwls         | -short         | -show_critical         | -showpass         | -showrepair         | -silentforce         | -skip_security         | -skip_usr_def_checks         | -syslog         | -systemtype         | -t         | -tag         | -targetversion         | -testemail         | -tmpdir         | -topology         | -torswitches         | -trace         | -u         | -unlockcells         | -unset         | -unsetdbupload         | -unsetinwallet         | -unsettfaupload         | -updatezip         | -upgrade         | -uploadfailed         | -uploadtfafailed         | -username         | -v         | -vmguest         | -wallet_loc         | -zfsnodes         | -zfssa To see detailed help of each option use ./exachk <option> -h 运行exachk [root@dm02db01 ht]# ./exachk    Checking ssh user equivalency settings on all nodes in cluster for root Node dm02db02 is configured for ssh user equivalency for root user Node dm02db03 is configured for ssh user equivalency for root user Node dm02db04 is configured for ssh user equivalency for root user Searching for running databases . . . . . .  .  .  .  .  .   List of running databases registered in OCR 1. jccrm 2. jcdms 3. jctds 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]. 4 Searching out ORACLE_HOME for selected databases. .  .  .  .  .  .  .  .  .  . .   Checking Status of Oracle Software Stack - Clusterware, ASM, RDBMS .  .  .  . . . .  .  .  . . . .  .  .  . . . .   .  .  .  . . . .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . . . .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  . . . .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .   -------------------------------------------------------------------------------------------------------                                                  Oracle Stack Status                           -------------------------------------------------------------------------------------------------------   Host Name       CRS Installed  RDBMS Installed    CRS UP    ASM UP  RDBMS UP    DB Instance Name -------------------------------------------------------------------------------------------------------    dm02db01                   Yes          Yes          Yes      Yes      Yes          jctds1 jccrm1 jcdms1    dm02db02                   Yes          Yes          Yes      Yes      Yes          jctds2 jcdms2    dm02db03                   Yes          Yes           No      Yes      Yes              dm02db04                   Yes          Yes          Yes      Yes      Yes          jccrm4 jctds4 jcdms4 ------------------------------------------------------------------------------------------------------- Copying plug-ins . . Node dm02cel02-priv is configured for ssh user equivalency for root user Node dm02cel03-priv is configured for ssh user equivalency for root user Node dm02cel04-priv is configured for ssh user equivalency for root user Node dm02cel05-priv is configured for ssh user equivalency for root user Node dm02cel06-priv is configured for ssh user equivalency for root user Node dm02cel07-priv is configured for ssh user equivalency for root user Node dm02cel01-priv is configured for ssh user equivalency for root user .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .   *** Checking Best Practice Recommendations ( PASS / WARNING / FAIL ) *** .  .  .   Collections and audit checks log file is  /ht/exachk_dm02db01_jctds_120318_083313/log/exachk.log Starting to run exachk in background on dm02db02 Starting to run exachk in background on dm02db03 Starting to run exachk in background on dm02db04 ============================================================                Node name - dm02db01 ============================================================  Collecting - ASM Disk Group for Infrastructure Software and Configuration  Collecting - ASM Diskgroup Attributes  Collecting - ASM diskgroup usable free space  Collecting - ASM initialization parameters  Collecting - Database Parameters for jccrm database  Collecting - Database Parameters for jcdms database  Collecting - Database Parameters for jctds database  Collecting - Database Undocumented Parameters for jccrm database  Collecting - Database Undocumented Parameters for jcdms database  Collecting - Database Undocumented Parameters for jctds database  Collecting - RDBMS Feature Usage for jccrm database  Collecting - RDBMS Feature Usage for jcdms database  Collecting - RDBMS Feature Usage for jctds 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 - Maximum number of semaphores per semaphore set  Collecting - OS Packages  Collecting - Patches for Grid Infrastructure   Collecting - Patches for RDBMS Home   Collecting - RDBMS patch inventory  Collecting - Switch Version Information  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 - Check alerthistory for test open stateless alerts [Database Server]  Collecting - Clusterware patch inventory  Collecting - Discover switch type(spine or leaf)  Collecting - Enterprise Manager agent targets  Collecting - Exadata Critical Issue DB09  Collecting - Exadata Critical Issue EX30  Collecting - Exadata software version on database server  Collecting - Exadata system model number  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 - 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 Address Resolution Protocol (ARP) Configuration on Database Servers  Collecting - Verify InfiniBand Fabric Topology (verify-topology)  Collecting - Verify InfiniBand subnet manager is not running on database server  Collecting - Verify InfiniBand subnet manager is running on an InfiniBand switch  Collecting - Verify Master (Rack) Serial Number is Set [Database Server]  Collecting - Verify NTP configuration on database servers  Collecting - Verify RAID Controller Battery Condition [Database Server]  Collecting - Verify RAID Controller Battery Temperature [Database Server]  Collecting - Verify TCP Segmentation Offload (TSO) is set to off  Collecting - Verify basic Logical Volume(LVM) system devices configuration  Collecting - Verify database server disk controllers use writeback cache   Collecting - Verify database server file systems have Check interval = 0  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 no database server kernel out of memory errors   Collecting - Verify processor.max_cstate is 1 on database servers  Collecting - Verify proper ACFS drivers are installed for Spectre v2 mitigation  Collecting - Verify service exachkcfg autostart status on database server  Collecting - Verify that the SDP over IB option sdp_apm_enable is set to 0  Collecting - Verify the localhost alias is pingable [Database Server]  Collecting - Verify the Name Service Cache Daemon (NSCD) configuration  Collecting - Verify the storage servers in use configuration matches across the cluster  Collecting - Verify the vm.min_free_kbytes configuration  Collecting - Verify there are no files present that impact normal firmware update procedures [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 dm02cel02 (192.168.10.10) Starting to run root privileged commands in background on STORAGE SERVER dm02cel03 (192.168.10.11) Starting to run root privileged commands in background on STORAGE SERVER dm02cel04 (192.168.10.12) Starting to run root privileged commands in background on STORAGE SERVER dm02cel05 (192.168.10.13) Starting to run root privileged commands in background on STORAGE SERVER dm02cel06 (192.168.10.14) Starting to run root privileged commands in background on STORAGE SERVER dm02cel07 (192.168.10.15) Starting to run root privileged commands in background on STORAGE SERVER dm02cel01 (192.168.10.9) Collections from STORAGE SERVER: ------------------------------------------------------------  Collecting - Exadata Critical Issue EX10  Collecting - Exadata Critical Issue EX11  Collecting - Exadata Critical Issue EX22  Collecting - Exadata Critical Issue EX25  Collecting - Exadata Critical Issue EX28  Collecting - Exadata Critical Issue EX29  Collecting - Exadata Critical Issue EX31  Collecting - Exadata Critical Issue EX32  Collecting - Exadata Critical Issue EX45  Collecting - Exadata critical issue EX14  Collecting - Exadata critical issue EX15  Collecting - Exadata critical issue EX16  Collecting - Exadata critical issue EX17  Collecting - Exadata critical issue EX17  Collecting - Exadata critical issue EX19  Collecting - Exadata critical issue EX20  Collecting - Exadata critical issue EX21  Collecting - Exadata critical issue EX27  Collecting - Exadata critical issue EX42  Collecting - Exadata critical issue EX47  Collecting - Exadata software version on storage server  Collecting - Exadata software version on storage servers  Collecting - Exadata storage server system model number   Collecting - Infrastructure Software and Configuration for storage   Collecting - RAID controller version on storage servers  Collecting - Verify Disk Cache Policy on storage servers  Collecting - Verify Electronic Storage Module (ESM) Lifetime is within Specification   Collecting - Verify Exadata Smart Flash Cache is created  Collecting - Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Storage Server]  Collecting - Verify ILOM Power Up Configuration for HOST_AUTO_POWER_ON on storage servers  Collecting - Verify ILOM Power Up Configuration for HOST_LAST_POWER_STATE on storage servers  Collecting - Verify InfiniBand subnet manager is not running on storage server  Collecting - Verify Master (Rack) Serial Number is Set [Storage Server]  Collecting - Verify NTP configuration on storage servers  Collecting - Verify OSSCONF/cellinit.ora consistency across storage servers  Collecting - Verify PCI bridge is configured for generation II on storage servers  Collecting - Verify RAID Controller Battery Condition [Storage Server]  Collecting - Verify RAID Controller Battery Temperature [Storage Server]  Collecting - Verify Storage Server user CELLDIAG exists  Collecting - Verify active system values match those defined in configuration file cell.conf  [Storage Server]  Collecting - Verify data (non-system) disks on Exadata Storage Servers have no partitions  Collecting - Verify imageinfo on storage server  Collecting - Verify imageinfo on storage server to compare systemwide  Collecting - Verify release tracking bug on storage servers  Collecting - Verify service exachkcfg autostart status on storage server  Collecting - Verify storage server disk controllers use writeback cache   Collecting - Verify that griddisks are distributed as expected across celldisks  Collecting - Verify the localhost alias is pingable [Storage Server]  Collecting - Verify there are no files present that impact normal firmware update procedures [Storage Server]  Collecting - collect storage server flashcachemode data  Collecting - verify asr exadata configuration check via ASREXACHECK on storage servers  Collecting - Check alerthistory for non-test open stateless alerts [Storage Server]  Collecting - Check alerthistory for stateful alerts not cleared [Storage Server]  Collecting - Check alerthistory for test open stateless alerts [Storage Server]  Collecting - Configure Storage Server alerts to be sent via email  Collecting - Determine storage server type(All Flash/High Capacity)  Collecting - Exadata Celldisk predictive failures  Collecting - Exadata Critical Issue EX9  Collecting - Exadata storage server root filesystem free space  Collecting - HCA firmware version on storage server  Collecting - OFED Software version on storage server  Collecting - Operating system and Kernel version on storage server  Collecting - Storage server flash cache mode  Collecting - Storage server make and model  Collecting - Verify Data Network is Separate from Management Network on storage server  Collecting - Verify Datafiles are Placed on Diskgroups consisting of griddisks with correct attributes  Collecting - Verify Ethernet Cable Connection Quality on storage servers  Collecting - Verify ExaWatcher is executing [Storage Server]  Collecting - Verify Exadata Smart Flash Cache is actually in use  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 celldisk configuration on disk drives  Collecting - Verify celldisk configuration on flash memory devices  Collecting - Verify griddisk ASM status  Collecting - Verify griddisk count matches across all storage servers where a given prefix name exists  Collecting - Verify storage server metric CD_IO_ST_RQ  Collecting - Verify the percent of available celldisk space used by the griddisks  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 dm02db01. ------------------------------------------------------------  CRITICAL => Basic Logical Volume(LVM) system devices configuration should meet recommendations.  FAIL =>     The Name Service Cache Daemon (NSCD) configuration is not correct  FAIL =>     DB_UNIQUE_NAME on primary has not been modified from the default, confirm that database name is unique across your Oracle enterprise for jccrm  FAIL =>     DB_UNIQUE_NAME on primary has not been modified from the default, confirm that database name is unique across your Oracle enterprise for jcdms  FAIL =>     DB_UNIQUE_NAME on primary has not been modified from the default, confirm that database name is unique across your Oracle enterprise for jctds  CRITICAL => System is exposed to Exadata Critical issue EX19  WARNING =>  ASM parameter AUDIT_SYS_OPERATIONS should be set to the recommended value  INFO =>     Oracle GoldenGate failure prevention best practices  INFO =>     One or more non-default AWR baselines should be created for jccrm  INFO =>     One or more non-default AWR baselines should be created for jcdms  INFO =>     One or more non-default AWR baselines should be created for jctds  WARNING =>  Non-default database Services are not configured for jccrm  WARNING =>  Non-default database Services are not configured for jcdms  WARNING =>  Non-default database Services are not configured for jctds  CRITICAL => The InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers should be as recommended  CRITICAL => System is exposed to Exadata Critical Issue EX29  WARNING =>  Database parameter processes should be set to recommended value on jcdms1 instance  WARNING =>  Database parameter processes should be set to recommended value on jctds1 instance  CRITICAL => System is exposed to Exadata Critical Issue EX30  CRITICAL => System is exposed to Exadata Critical Issue DB36 /u01/app/11.2.0.3/grid  FAIL =>     Storage Server user "CELLDIAG" should exist  FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface  CRITICAL => The database server file systems should have "Maximum mount count" = "-1"  FAIL =>     Griddisks are not distributed as expected across celldisks  WARNING =>  SYS or SYSTEM objects were found to be INVALID for jccrm  WARNING =>  SYS or SYSTEM objects were found to be INVALID for jcdms  FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.3/dbhome_1  WARNING =>  System is not capable of Spectre v2 mitigation.  CRITICAL => System is exposed to Exadata Critical Issue EX44  WARNING =>  All disk groups should have compatible.advm attribute set to recommended values  WARNING =>  All disk groups should have compatible.rdbms attribute set to recommended values  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jccrm1 instance  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jcdms1 instance  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jctds1 instance  FAIL =>     Storage Server alerts are not configured to be sent via email  FAIL =>     Some data or temp files are not autoextensible for jccrm  FAIL =>     Some data or temp files are not autoextensible for jcdms  FAIL =>     Some data or temp files are not autoextensible for jctds  FAIL =>     Verify-topology returned some errors or warning.  WARNING =>  Key InfiniBand fabric error counters should not be present  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jccrm1 instance  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jcdms1 instance  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jctds1 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jccrm1 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jcdms1 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jctds1 instance  CRITICAL => Database parameter CLUSTER_INTERCONNECTS is not set to the recommended value for jcdms  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jccrm  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jcdms  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jctds  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jccrm  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jcdms  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jctds  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jccrm  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jcdms  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jctds  FAIL =>     Flashback on PRIMARY is not configured for jccrm  FAIL =>     Flashback on PRIMARY is not configured for jcdms  FAIL =>     Flashback on PRIMARY is not configured for jctds  INFO =>     Operational Best Practices  INFO =>     Database Consolidation Best Practices  INFO =>     Computer failure prevention best practices  INFO =>     Data corruption prevention best practices  INFO =>     Logical corruption prevention best practices  INFO =>     Database/Cluster/Site failure prevention best practices  INFO =>     Client failover operational best practices  FAIL =>     ASM parameter SGA_TARGET is not set according to recommended value.  FAIL =>     ASM parameter MEMORY_TARGET should be set according to recommended value  FAIL =>     ASM parameter MEMORY_MAX_TARGET should be set according to recommended value  INFO =>     Verify the percent of available celldisk space used by the griddisks  CRITICAL => The griddisk ASM status should match specification  CRITICAL => The celldisk configuration on flash memory devices should match Oracle best practices  WARNING =>  Application objects were found to be invalid for jccrm  WARNING =>  Application objects were found to be invalid for jcdms  WARNING =>  Application objects were found to be invalid for jctds  CRITICAL => Database control files are not configured as recommended for jccrm  CRITICAL => Database control files are not configured as recommended for jcdms  CRITICAL => Database control files are not configured as recommended for jctds  WARNING =>  Redo log files should be appropriately sized for jccrm  WARNING =>  Redo log files should be appropriately sized for jcdms  WARNING =>  Redo log files should be appropriately sized for jctds  WARNING =>  Shared Server are in use - verify they do not do serial full table scans on jcdms1 instance  FAIL =>     Table AUD$[FGA_LOG$] should use Automatic Segment Space Management for jcdms  INFO =>     Database failure prevention best practices  FAIL =>     Standby redo logs should be configured on the primary for jccrm  FAIL =>     Standby redo logs should be configured on the primary for jcdms  FAIL =>     Standby redo logs should be configured on the primary for jctds  WARNING =>  Unsupported data types preventing Data Guard (transient logical standby or logical standby) rolling upgrade for jcdms  WARNING =>  Unsupported data types preventing Data Guard (transient logical standby or logical standby) rolling upgrade for jctds  INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Primary Database for jccrm  INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Primary Database for jcdms  INFO =>     While initialization parameter LOG_ARCHIVE_CONFIG is set it should be verified for your environment on Primary Database for jctds  FAIL =>     Data Guard broker configuration does not exist for jccrm  FAIL =>     Data Guard broker configuration does not exist for jcdms  FAIL =>     Data Guard broker configuration does not exist for jctds  FAIL =>     Oracle Net service name RECV_BUF_SIZE, SEND_BUF_SIZE, and SDU should be set.  Please review for your environment. for jccrm  FAIL =>     Oracle Net service name RECV_BUF_SIZE, SEND_BUF_SIZE, and SDU should be set.  Please review for your environment. for jcdms  FAIL =>     Oracle Net service name RECV_BUF_SIZE, SEND_BUF_SIZE, and SDU should be set.  Please review for your environment. for jctds  FAIL =>     The bundle patch version installed does not match the bundle patch version registered in the database for jcdms  CRITICAL => ILOM Power Up Configuration for HOST_AUTO_POWER_ON should be set to recommended value  CRITICAL => ILOM Power Up Configuration for HOST_LAST_POWER_STATE should be set to recommended value  FAIL =>     No one high redundancy diskgroup configured for jccrm  FAIL =>     No one high redundancy diskgroup configured for jcdms  FAIL =>     No one high redundancy diskgroup configured for jctds  INFO =>     Storage failures prevention best practices  INFO =>     Software maintenance best practices  CRITICAL => The data files should be recoverable for jccrm  CRITICAL => The data files should be recoverable for jcdms  CRITICAL => The data files should be recoverable for jctds  CRITICAL => There should be no ASM corruption found.  INFO =>     Oracle recovery manager(rman) best practices  WARNING =>  RMAN controlfile autobackup should be set to ON for jccrm  WARNING =>  RMAN controlfile autobackup should be set to ON for jcdms  INFO =>     Exadata Critical Issues (Doc ID 1270094.1):- DB1-DB4,DB6,DB9-DB41, EX1-EX47 and IB1-IB3,IB5-IB8  CRITICAL => System is exposed to Exadata Critical Issue DB18 /u01/app/oracle/product/11.2.0.3/dbhome_1  FAIL =>     The ASM failure group configuration is not as recommended  CRITICAL => The database server file systems should have "Check interval" set to zero  CRITICAL => System is exposed to Exadata critical issue DB24 Collecting patch inventory on CRS HOME /u01/app/11.2.0.3/grid Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.3/dbhome_1 Copying results from dm02db02 and generating report. This might take a while. Be patient.   .   ============================================================                Node name - dm02db02 ============================================================  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 - Maximum number of semaphores per semaphore set  Collecting - OS Packages  Collecting - Patches for Grid Infrastructure   Collecting - Patches for RDBMS Home   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 - Check alerthistory for test open stateless alerts [Database Server]  Collecting - Clusterware patch inventory  Collecting - Exadata Critical Issue DB09  Collecting - Exadata Critical Issue EX30  Collecting - Exadata software version on database server  Collecting - Exadata system model number  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 - 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 Address Resolution Protocol (ARP) Configuration on Database Servers  Collecting - Verify InfiniBand subnet manager is not running on database server  Collecting - Verify Master (Rack) Serial Number is Set [Database Server]  Collecting - Verify NTP configuration on database servers  Collecting - Verify RAID Controller Battery Condition [Database Server]  Collecting - Verify RAID Controller Battery Temperature [Database Server]  Collecting - Verify TCP Segmentation Offload (TSO) is set to off  Collecting - Verify basic Logical Volume(LVM) system devices configuration  Collecting - Verify database server disk controllers use writeback cache   Collecting - Verify database server file systems have Check interval = 0  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 no database server kernel out of memory errors   Collecting - Verify processor.max_cstate is 1 on database servers  Collecting - Verify proper ACFS drivers are installed for Spectre v2 mitigation  Collecting - Verify service exachkcfg autostart status on database server  Collecting - Verify that the SDP over IB option sdp_apm_enable is set to 0  Collecting - Verify the localhost alias is pingable [Database Server]  Collecting - Verify the Name Service Cache Daemon (NSCD) configuration  Collecting - Verify the storage servers in use configuration matches across the cluster  Collecting - Verify the vm.min_free_kbytes configuration  Collecting - Verify there are no files present that impact normal firmware update procedures [Database Server]  Collecting - root time zone check  Collecting - verify asr exadata configuration check via ASREXACHECK on database server Data collections completed. Checking best practices on dm02db02. ------------------------------------------------------------  CRITICAL => Basic Logical Volume(LVM) system devices configuration should meet recommendations.  FAIL =>     The Name Service Cache Daemon (NSCD) configuration is not correct  WARNING =>  ASM parameter AUDIT_SYS_OPERATIONS should be set to the recommended value  INFO =>     Oracle GoldenGate failure prevention best practices  WARNING =>  Non-default database Services are not configured for jcdms  WARNING =>  Non-default database Services are not configured for jctds  CRITICAL => The InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers should be as recommended  WARNING =>  Database parameter processes should be set to recommended value on jctds2 instance  CRITICAL => System is exposed to Exadata Critical Issue EX30  CRITICAL => System is exposed to Exadata Critical Issue DB36 /u01/app/11.2.0.3/grid  FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface  FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.3/dbhome_1  WARNING =>  System is not capable of Spectre v2 mitigation.  CRITICAL => System is exposed to Exadata Critical Issue EX44  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jctds2 instance  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jctds2 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jctds2 instance  CRITICAL => Database parameter CLUSTER_INTERCONNECTS is not set to the recommended value for jcdms  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jcdms  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jctds  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jcdms  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jctds  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jcdms  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jctds  FAIL =>     ASM parameter SGA_TARGET is not set according to recommended value.  FAIL =>     ASM parameter MEMORY_TARGET should be set according to recommended value  FAIL =>     ASM parameter MEMORY_MAX_TARGET should be set according to recommended value  CRITICAL => Database control files are not configured as recommended for jcdms  CRITICAL => Database control files are not configured as recommended for jctds  WARNING =>  Redo log files should be appropriately sized for jcdms  WARNING =>  Redo log files should be appropriately sized for jctds  FAIL =>     The bundle patch version installed does not match the bundle patch version registered in the database for jcdms  CRITICAL => ILOM Power Up Configuration for HOST_AUTO_POWER_ON should be set to recommended value  CRITICAL => ILOM Power Up Configuration for HOST_LAST_POWER_STATE should be set to recommended value  CRITICAL => System is exposed to Exadata Critical Issue DB18 /u01/app/oracle/product/11.2.0.3/dbhome_1  CRITICAL => System is exposed to Exadata critical issue DB24 Collecting patch inventory on CRS HOME /u01/app/11.2.0.3/grid Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.3/dbhome_1 Copying results from dm02db03 and generating report. This might take a while. Be patient.   .   ============================================================                Node name - dm02db03 ============================================================  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 - Maximum number of semaphores per semaphore set  Collecting - OS Packages  Collecting - Patches for Grid Infrastructure   Collecting - Patches for RDBMS Home   Collecting - RDBMS patch inventory  Collecting - number of semaphore operations per semop system call  Collecting - Check alerthistory for non-test open stateless alerts [Database Server]  Collecting - Check alerthistory for stateful alerts not cleared [Database Server]  Collecting - Check alerthistory for test open stateless alerts [Database Server]  Collecting - Clusterware patch inventory  Collecting - Exadata Critical Issue DB09  Collecting - Exadata Critical Issue EX30  Collecting - Exadata software version on database server  Collecting - Exadata system model number  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 - 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 Address Resolution Protocol (ARP) Configuration on Database Servers  Collecting - Verify InfiniBand subnet manager is not running on database server  Collecting - Verify Master (Rack) Serial Number is Set [Database Server]  Collecting - Verify NTP configuration on database servers  Collecting - Verify RAID Controller Battery Condition [Database Server]  Collecting - Verify RAID Controller Battery Temperature [Database Server]  Collecting - Verify TCP Segmentation Offload (TSO) is set to off  Collecting - Verify basic Logical Volume(LVM) system devices configuration  Collecting - Verify database server disk controllers use writeback cache   Collecting - Verify database server file systems have Check interval = 0  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 no database server kernel out of memory errors   Collecting - Verify processor.max_cstate is 1 on database servers  Collecting - Verify proper ACFS drivers are installed for Spectre v2 mitigation  Collecting - Verify service exachkcfg autostart status on database server  Collecting - Verify that the SDP over IB option sdp_apm_enable is set to 0  Collecting - Verify the localhost alias is pingable [Database Server]  Collecting - Verify the Name Service Cache Daemon (NSCD) configuration  Collecting - Verify the storage servers in use configuration matches across the cluster  Collecting - Verify the vm.min_free_kbytes configuration  Collecting - Verify there are no files present that impact normal firmware update procedures [Database Server]  Collecting - root time zone check  Collecting - verify asr exadata configuration check via ASREXACHECK on database server Data collections completed. Checking best practices on dm02db03. ------------------------------------------------------------  CRITICAL => Basic Logical Volume(LVM) system devices configuration should meet recommendations.  FAIL =>     The Name Service Cache Daemon (NSCD) configuration is not correct  WARNING =>  ASM parameter AUDIT_SYS_OPERATIONS should be set to the recommended value  INFO =>     Oracle GoldenGate failure prevention best practices  CRITICAL => The clusterware state should be "Normal"  CRITICAL => There should be no failed diskgroup rebalance operations  CRITICAL => The InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers should be as recommended  CRITICAL => System is exposed to Exadata Critical Issue EX30  CRITICAL => System is exposed to Exadata Critical Issue DB36 /u01/app/11.2.0.3/grid  FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface  FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.3/dbhome_1  WARNING =>  System is not capable of Spectre v2 mitigation.  CRITICAL => System is exposed to Exadata Critical Issue EX44  CRITICAL => ASM parameter CLUSTER_INTERCONNECTS is not set to the recommended value  FAIL =>     ASM parameter SGA_TARGET is not set according to recommended value.  FAIL =>     ASM parameter MEMORY_TARGET should be set according to recommended value  FAIL =>     ASM parameter MEMORY_MAX_TARGET should be set according to recommended value  CRITICAL => There should be no ASM external redundancy diskgroups.  CRITICAL => There should be no ASM unprotected templates.  CRITICAL => ILOM Power Up Configuration for HOST_AUTO_POWER_ON should be set to recommended value  CRITICAL => ILOM Power Up Configuration for HOST_LAST_POWER_STATE should be set to recommended value  CRITICAL => System is exposed to Exadata Critical Issue DB18 /u01/app/oracle/product/11.2.0.3/dbhome_1  CRITICAL => System is exposed to Exadata critical issue DB24 Collecting patch inventory on CRS HOME /u01/app/11.2.0.3/grid Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.3/dbhome_1 Copying results from dm02db04 and generating report. This might take a while. Be patient.   .   ============================================================                Node name - dm02db04 ============================================================  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 - Maximum number of semaphores per semaphore set  Collecting - OS Packages  Collecting - Patches for Grid Infrastructure   Collecting - Patches for RDBMS Home   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 - Check alerthistory for test open stateless alerts [Database Server]  Collecting - Clusterware patch inventory  Collecting - Exadata Critical Issue DB09  Collecting - Exadata Critical Issue EX30  Collecting - Exadata software version on database server  Collecting - Exadata system model number  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 - 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 Address Resolution Protocol (ARP) Configuration on Database Servers  Collecting - Verify InfiniBand subnet manager is not running on database server  Collecting - Verify Master (Rack) Serial Number is Set [Database Server]  Collecting - Verify NTP configuration on database servers  Collecting - Verify RAID Controller Battery Condition [Database Server]  Collecting - Verify RAID Controller Battery Temperature [Database Server]  Collecting - Verify TCP Segmentation Offload (TSO) is set to off  Collecting - Verify basic Logical Volume(LVM) system devices configuration  Collecting - Verify database server disk controllers use writeback cache   Collecting - Verify database server file systems have Check interval = 0  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 no database server kernel out of memory errors   Collecting - Verify processor.max_cstate is 1 on database servers  Collecting - Verify proper ACFS drivers are installed for Spectre v2 mitigation  Collecting - Verify service exachkcfg autostart status on database server  Collecting - Verify that the SDP over IB option sdp_apm_enable is set to 0  Collecting - Verify the localhost alias is pingable [Database Server]  Collecting - Verify the Name Service Cache Daemon (NSCD) configuration  Collecting - Verify the storage servers in use configuration matches across the cluster  Collecting - Verify the vm.min_free_kbytes configuration  Collecting - Verify there are no files present that impact normal firmware update procedures [Database Server]  Collecting - root time zone check  Collecting - verify asr exadata configuration check via ASREXACHECK on database server Data collections completed. Checking best practices on dm02db04. ------------------------------------------------------------  CRITICAL => Basic Logical Volume(LVM) system devices configuration should meet recommendations.  FAIL =>     The Name Service Cache Daemon (NSCD) configuration is not correct  WARNING =>  ASM parameter AUDIT_SYS_OPERATIONS should be set to the recommended value  INFO =>     Oracle GoldenGate failure prevention best practices  WARNING =>  Non-default database Services are not configured for jccrm  WARNING =>  Non-default database Services are not configured for jctds  CRITICAL => The InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers should be as recommended  WARNING =>  Database parameter processes should be set to recommended value on jctds4 instance  CRITICAL => System is exposed to Exadata Critical Issue EX30  CRITICAL => System is exposed to Exadata Critical Issue DB36 /u01/app/11.2.0.3/grid  FAIL =>     Downdelay attribute is not set to recommended value on bonded client interface  FAIL =>     Oracle database does not meet certified platinum configuration for /u01/app/oracle/product/11.2.0.3/dbhome_1  WARNING =>  System is not capable of Spectre v2 mitigation.  CRITICAL => System is exposed to Exadata Critical Issue EX44  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jccrm4 instance  FAIL =>     Database parameter DB_BLOCK_CHECKSUM is not set to recommended value on jctds4 instance  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jccrm4 instance  FAIL =>     Database parameter GLOBAL_NAMES is not set to recommended value on jctds4 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jccrm4 instance  CRITICAL => Database parameter USE_LARGE_PAGES is not set to recommended value on jctds4 instance  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jccrm  CRITICAL => Database parameters log_archive_dest_n with Location attribute are not all set to recommended value for jctds  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jccrm  CRITICAL => Database parameter Db_create_online_log_dest_n is not set to recommended value for jctds  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jccrm  WARNING =>  Database parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value. for jctds  FAIL =>     ASM parameter SGA_TARGET is not set according to recommended value.  FAIL =>     ASM parameter MEMORY_TARGET should be set according to recommended value  FAIL =>     ASM parameter MEMORY_MAX_TARGET should be set according to recommended value  CRITICAL => Database control files are not configured as recommended for jccrm  CRITICAL => Database control files are not configured as recommended for jctds  WARNING =>  Redo log files should be appropriately sized for jccrm  WARNING =>  Redo log files should be appropriately sized for jctds  CRITICAL => ILOM Power Up Configuration for HOST_AUTO_POWER_ON should be set to recommended value  CRITICAL => ILOM Power Up Configuration for HOST_LAST_POWER_STATE should be set to recommended value  CRITICAL => System is exposed to Exadata Critical Issue DB18 /u01/app/oracle/product/11.2.0.3/dbhome_1  CRITICAL => System is exposed to Exadata critical issue DB24 Collecting patch inventory on CRS HOME /u01/app/11.2.0.3/grid Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/11.2.0.3/dbhome_1 ------------------------------------------------------------                       CLUSTERWIDE CHECKS ------------------------------------------------------------  CRITICAL => All Database and Storage Servers should be synchronized with the same NTP server ------------------------------------------------------------ Detailed report (html) -  /ht/exachk_dm02db01_jctds_120318_083313/exachk_dm02db01_jctds_120318_083313.html UPLOAD [if required] - /ht/exachk_dm02db01_jctds_120318_083313.zip 获取文件  /ht/exachk_dm02db01_jctds_120318_083313.zip 到本地.   根据报告进行升级调整.