Oracle RAC Assessment Report

System Health Score is 86 out of 100 (detail)

Cluster Summary

Cluster Name rac-cluster
OS/Kernel VersionLINUX X86-64 OELRHEL 6 2.6.32-358.el6.x86_64
CRS Home - Version/oracle/app/11.2.0/grid - 11.2.0.4.0
DB Home - Version - Names/oracle/app/oracle/product/11.2.0/db - 11.2.0.4.0 - orcl
Number of nodes2
   Database Servers 2
ORAchk Version12.2.0.1.4_20171212
Collectionorachk_rac1_orcl_012518_163134
Duration8 mins, 43 seconds
Executed byoracle
Arguments
Collection Date25-Jan-2018 16:36:12

Note! This version of ORAchk is considered valid for 76 days from today or until a new version is available

Table of Contents

  • Database Server
  • Patch Recommendation
  • Maximum Availability Architecture (MAA) Scorecard
  • Component Elapsed Times
  • Top 10 Time Consuming Checks

  • Report Feature


  • Show checks with the following status:
  •        

  • Show details of the following regions:
  •        
           
           
           

  • Show details of the checks:
  •        Expand AllCollapse All


    Database Server

    Check Id Status Type Message Status On Details
    FAILOS CheckOne or more network card used by clusterware do not have HOTPLUG=NOAll Database Servers
    FAILSQL CheckTable AUD$[FGA_LOG$] should use Automatic Segment Space ManagementAll Databases
    FAILOS CheckOperating system hugepages count does not satisfy total SGA requirementsAll Database Servers
    FAILOS CheckThe RMAN snapshot controlfile location is NOT shared on all database nodes in the clusterAll Database Servers
    FAILASM CheckASM_DISKSTRING parameter is either null or set to /dev/*All ASM Instances
    FAILOS CheckDatabase parameter CLUSTER_INTERCONNECTS is not set to the recommended valueAll Database Servers
    FAILOS CheckBash is vulnerable to code injection (CVE-2014-6271)All Database Servers
    WARNINGSQL CheckConsider investigating the frequency of SGA resize operations and take corrective actionAll Databases
    WARNINGSQL CheckConsider investigating changes to the schema objects such as DDLs or new object creationAll Databases
    WARNINGOS CheckPackage unixODBC-devel-2.2.14-11.el6-x86_64 is recommended but NOT installedAll Database Servers
    WARNINGOS CheckPackage unixODBC-devel-2.2.14-11.el6-i686 is recommended but NOT installedAll Database Servers
    WARNINGOS CheckPackage unixODBC-2.2.14-11.el6-i686 is recommended but NOT installedAll Database Servers
    WARNINGOS CheckCSS log file size has not been increased from default (50 MB) .All Database Servers
    WARNINGASM CheckAll disk groups should have compatible.asm attribute set to recommended valuesAll ASM Instances
    WARNINGASM CheckAll disk groups should have compatible.advm attribute set to recommended valuesAll ASM Instances
    WARNINGASM CheckAll disk groups should have compatible.rdbms attribute set to recommended valuesAll ASM Instances
    WARNINGOS CheckOSWatcher is not running as is recommended.All Database Servers
    WARNINGOS CheckNIC bonding is NOT configured for public network (VIP)All Database Servers
    WARNINGOS CheckNIC bonding is not configured for interconnectAll Database Servers
    WARNINGSQL Parameter CheckDatabase Parameter memory_target is not set to the recommended valueAll Instances
    WARNINGOS CheckSELinux is being Enforced.All Database Servers
    WARNINGSQL CheckOne or more redo log groups are not multiplexedAll Databases
    WARNINGSQL CheckControlfile is NOT multiplexedAll Databases
    WARNINGOS Check$ORACLE_HOME/bin/oradism setuid bit is NOT setAll Database Servers
    WARNINGOS CheckOCR is not being backed up dailyAll Database Servers
    WARNINGPatch CheckOracle patch 19855835 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 20907061 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 20476175 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 20879889 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 19174639 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 24739928 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 18498878 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 22113854 is not applied on RDBMS_HOMEAll Homes
    WARNINGPatch CheckOracle patch 23665623 is not applied on RDBMS_HOMEAll Homes
    WARNINGSQL CheckThere are some application objects with STALE statistics.All Databases
    WARNINGOS CheckCluster Health Monitor (CHM) repository does not provide recommended level of retentionAll Database Servers
    INFOOS CheckConsider increasing the COREDUMPSIZE sizeAll Database Servers
    INFOOS CheckParallel Execution Health-Checks and Diagnostics ReportsAll Database Servers
    INFOOS CheckInformation about hanganalyze and systemstate dumpAll Database Servers
    INFOPatch CheckIMPORTANT: Oracle Database Patch 17478514 PSU is NOT applied to RDBMS HomeAll Homes
    INFOOS CheckJumbo frames (MTU >= 9000) are not configured for interconnectAll Database Servers
    INFOOS CheckNumber of SCAN listeners is not equal to the recommended number of 3.All Database Servers
    INFOASM Checkoracleasm (asmlib) module is not loadedAll ASM Instances
    INFOOS Checkaudit_file_dest has audit files older than 30 daysAll Database Servers
    INFOOS CheckAt some times checkpoints are not being completedAll Database Servers
    INFOOS Checkbackground_dump_dest has files older than 30 daysAll Database Servers
    INFOOS Checkuser_dump_dest has trace files older than 30 daysAll Database Servers
    INFOOS Check$CRS_HOME/log/hostname/client directory has too many older log files.All Database Servers
    INFOOS CheckMost recent ADR incidentsAll Database Servers
    INFOOS CheckImportant Storage Minimum Requirements for Grid & Database HomesAll Database Servers
    INFOASM CheckOracle Data Pump Best practices.All ASM Instances
    INFOOS CheckImportant Automatic Storage Management (ASM) Notes and Technical White PapersAll Database Servers
    PASSOS CheckThere are no duplicate parameter entries in the database init.ora(spfile) fileAll Database Servers
    PASSOS CheckDatabase parameter service_names is not defined in spfileAll Database Servers
    PASSOS Checkkernel.panic_on_oops parameter is configured according to recommendationAll Database Servers
    PASSSQL CheckNo waiter sessions found currently for application usersAll Databases
    PASSSQL CheckThe database parameter session_cached_cursors is set to the recommended valueAll Databases
    PASSASM CheckASM disk permissions are set as recommendedAll ASM Instances
    PASSASM CheckASM disks have enough free space for rebalanceAll ASM Instances
    PASSSQL CheckAll optimizer related parameters are set to the default value (Parameter Set 2 of 3)All Databases
    PASSSQL CheckAll optimizer related parameters are set to the default value (Parameter Set 3 of 3)All Databases
    PASSSQL CheckNo obsolete initialization parameters are setAll Databases
    PASSSQL CheckDatabase parameter OPTIMIZER_FEATURES_ENABLE is set to the current database versionAll Databases
    PASSSQL CheckDatabase parameter NLS_SORT is set to BINARYAll Databases
    PASSOS CheckOnline (hot) patches are not applied to CRS_HOME.All Database Servers
    PASSSQL CheckTable containing SecureFiles LOB storage belongs to a tablespace with extent allocation type that is SYSTEM managed (AUTOALLOCATE)All Databases
    PASSASM CheckASM memory_target is set to recommended valueAll ASM Instances
    PASSOS CheckOnline (hot) patches are not applied to ORACLE_HOMEAll Database Servers
    PASSSQL CheckAll optimizer related parameters are set to the default value (Parameter Set 1 of 3)All Databases
    PASSOS CheckBerkeley Database location points to correct GI_HOMEAll Database Servers
    PASSASM CheckAll diskgroups from v$asm_diskgroups are registered in clusterware registryAll ASM Instances
    PASSOS CheckPackage cvuqdisk-1.0.9-1-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS Checkpam_limits configured properly for shell limitsAll Database Servers
    PASSOS Checkvm.min_free_kbytes is set as recommended.All Database Servers
    PASSOS CheckLinux transparent huge pages are disabledAll Database Servers
    PASSOS CheckOCR and Voting disks are stored in ASMAll Database Servers
    PASSOS CheckSystem clock is synchronized to hardware clock at system shutdownAll Database Servers
    PASSOS CheckTFA Collector is installed and runningAll Database Servers
    PASSOS CheckNo clusterware resource are in unknown stateAll Database Servers
    PASSASM CheckNo corrupt ASM header blocks indicated in ASM alert log (ORA-15196 errors)All ASM Instances
    PASSASM CheckNo disks found which are not part of any disk groupAll ASM Instances
    PASSOS Checkloopback address is configured as recommended in /etc/hostsAll Database Servers
    PASSOS CheckRedo log write time is less than 500 millisecondsAll Database Servers
    PASSOS CheckPackage libgcc-4.4.4-13.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSSQL CheckNo read/write errors found for ASM disksAll Databases
    PASSOS CheckPackage sysstat-9.0.4-11.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libgcc-4.4.4-13.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage binutils-2.20.51.0.2-5.11.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage glibc-2.12-1.7.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libstdc++-4.4.4-13.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libstdc++-4.4.4-13.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage glibc-2.12-1.7.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage gcc-4.4.4-13.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage make-3.81-19.el6 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libstdc++-devel-4.4.4-13.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libaio-devel-0.3.107-10.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libaio-0.3.107-10.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage compat-libstdc++-33-3.2.3-69.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage glibc-devel-2.12-1.7.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage glibc-devel-2.12-1.7.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage compat-libcap1-1.10-1-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage ksh-20100621-12.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libaio-0.3.107-10.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libstdc++-devel-4.4.4-13.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage gcc-c++-4.4.4-13.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage compat-libstdc++-33-3.2.3-69.el6-x86_64 meets or exceeds recommendationAll Database Servers
    PASSOS CheckPackage libaio-devel-0.3.107-10.el6-i686 meets or exceeds recommendationAll Database Servers
    PASSOS CheckRemote listener is set to SCAN nameAll Database Servers
    PASSOS CheckValue of remote_listener parameter is able to tnspingAll Database Servers
    PASSOS CheckNo server-side TNSNAMES.ora aliases resolve using SCAN EZ syntaxAll Database Servers
    PASSOS Checkezconnect is configured in sqlnet.oraAll Database Servers
    PASSSQL CheckNo Duplicate objects were found in the SYS and SYSTEM schemasAll Databases
    PASSSQL CheckNo Invalid Registry Components were foundAll Databases
    PASSSQL CheckAll bigfile tablespaces have non-default maxbytes values setAll Databases
    PASSOS Checkumask for RDBMS owner is set to 0022All Database Servers
    PASSOS CheckORA_CRS_HOME environment variable is not set for Grid infrastructure ownerAll Database Servers
    PASSOS CheckOracle database software owner hard stack shell limit is configured according to recommendationAll Database Servers
    PASSOS CheckOracle database software owner soft nofile shell limits is configured according to recommendationAll Database Servers
    PASSOS CheckOracle database software owner hard nproc shell limits is configured according to recommendationAll Database Servers
    PASSSQL Parameter Checkasm_power_limit is set to recommended value of 1All Instances
    PASSOS CheckCSS reboot time is set to the default value of 3All Database Servers
    PASSOS CheckCSS disktimeout is set to the default value of 200All Database Servers
    PASSOS Checkohasd Log Ownership is Correct (root root)All Database Servers
    PASSOS Checkohasd/orarootagent_root Log Ownership is Correct (root root)All Database Servers
    PASSOS Checkcrsd/orarootagent_root Log Ownership is Correct (root root)All Database Servers
    PASSOS Checkcrsd Log Ownership is Correct (root root)All Database Servers
    PASSASM CheckCRS version is higher or equal to ASM version.All ASM Instances
    PASSOS CheckLocal listener init parameter is set to local node VIPAll Database Servers
    PASSOS CheckAll voting disks are onlineAll Database Servers
    PASSOS CheckCSS misscount is set to the default value of 30All Database Servers
    PASSSQL CheckAll redo log files are of same sizeAll Databases
    PASSOS CheckPublic interface is configured and exists in OCRAll Database Servers
    PASSOS Checkip_local_port_range is configured according to recommendationAll Database Servers
    PASSOS Checkkernel.shmmax parameter is configured according to recommendationAll Database Servers
    PASSOS CheckKernel Parameter fs.file-max is configuration meets or exceeds recommendationAll Database Servers
    PASSOS CheckFree space in /tmp directory meets or exceeds recommendation of minimum 1GBAll Database Servers
    PASSOS CheckOracle database software owner soft nproc shell limit is configured according to recommendationAll Database Servers
    PASSOS CheckOracle database software owner hard nofile shell limit is configured according to recommendationAll Database Servers
    PASSOS CheckLinux swap configuration meets or exceeds recommendationAll Database Servers
    PASSOS Check/tmp is on a dedicated filesystemAll Database Servers
    PASSSQL CheckAll data and temporary files are autoextensibleAll Databases
    PASSOS Check$ORACLE_HOME/bin/oradism ownership is rootAll Database Servers
    PASSSQL CheckAvg message sent queue time on ksxp is <= recommendedAll Databases
    PASSSQL CheckAvg message sent queue time is <= recommendedAll Databases
    PASSSQL CheckAvg message received queue time is <= recommendedAll Databases
    PASSSQL CheckNo Global Cache lost blocks detectedAll Databases
    PASSSQL CheckFailover method (SELECT) and failover mode (BASIC) are configured properlyAll Databases
    PASSSQL CheckAvg GC CURRENT Block Receive Time Within Acceptable RangeAll Databases
    PASSSQL CheckAvg GC CR Block Receive Time Within Acceptable RangeAll Databases
    PASSSQL CheckTablespace allocation type is SYSTEM for all appropriate tablespacesAll Databases
    PASSOS CheckAlert log is not too bigAll Database Servers
    PASSOS CheckNo ORA-07445 errors found in alert logAll Database Servers
    PASSOS CheckNo ORA-00600 errors found in alert logAll Database Servers
    PASSOS Checkcore_dump_dest does not have too many older core dump filesAll Database Servers
    PASSOS CheckKernel Parameter SEMMNS OKAll Database Servers
    PASSOS CheckKernel Parameter kernel.shmmni OKAll Database Servers
    PASSOS CheckKernel Parameter SEMMSL OKAll Database Servers
    PASSOS CheckKernel Parameter SEMMNI OKAll Database Servers
    PASSOS CheckKernel Parameter SEMOPM OKAll Database Servers
    PASSOS CheckKernel Parameter kernel.shmall OKAll Database Servers
    PASSOS CheckThe number of async IO descriptors is sufficient (/proc/sys/fs/aio-max-nr)All Database Servers
    PASSSQL CheckThere are no Invalid Java Objects in the database.All Databases
    PASSOS Checknet.core.rmem_max is Configured ProperlyAll Database Servers
    PASSSQL Parameter CheckInstance is using spfileAll Instances
    PASSASM CheckASM Audit file destination file count <= 100,000All ASM Instances
    PASSOS CheckInterconnect is configured on non-routable network addressesAll Database Servers
    PASSOS CheckOCR is mirrored using Oracle redundancyAll Database Servers
    PASSOS CheckNone of the hostnames contains an underscore characterAll Database Servers
    PASSOS Checknet.core.rmem_default Is Configured ProperlyAll Database Servers
    PASSOS Checknet.core.wmem_max Is Configured ProperlyAll Database Servers
    PASSOS Checknet.core.wmem_default Is Configured ProperlyAll Database Servers
    PASSSQL Checkcluster_database_instances database parameter is set to default valueAll Databases
    PASSSQL CheckARCHIVELOG mode is enabledAll Databases
    PASSOS CheckNone of the hostnames contains an underscore characterAll Database Servers
    PASSSQL CheckSYS.AUDSES$ sequence cache size >= 10,000All Databases
    PASSSQL CheckSYS.IDGEN1$ sequence cache size >= 1,000All Databases
    PASSOS CheckOCR and OCR backup locations are not in the same pathAll Database Servers
    PASSOS CheckPrivate and public network subnet configuration is correct in OCRAll Database Servers
    PASSOS CheckCluster nodes appear to be correctly numberedAll Database Servers
    PASSSQL CheckAWR Space consumption is less than 50% of total SYSAUX spaceAll Databases
    PASSSQL CheckFailover method (SELECT) and failover mode (BASIC) are configured properlyAll Databases
    PASSOS Check/boot has enough free spaceAll Database Servers
    PASSOS CheckOracle database software owner soft stack shell limit is configured according to recommendationAll Database Servers
    PASSSQL CheckNone of the tablespaces have recyclebin objects consuming space more than 100 KB.All Databases
    PASSSQL CheckNone of the database users have more than 10 recyclebin objects in it.All Databases
    PASSSQL CheckDatabase parameter DB_FILE_MULTIBLOCK_READ_COUNT is unset as recommendedAll Databases
    PASSOS CheckPGA allocation for all databases is not more than total memory available on this systemAll Database Servers
    PASSOS CheckHidden database initialization parameters are not set per best practice recommendationsAll Database Servers
    PASSASM CheckHidden ASM initialization parameters are not set per best practice recommendationsAll ASM Instances
    PASSOS CheckFree space in /etc directory meets or exceeds recommendation of minimum 1GBAll Database Servers
    PASSOS CheckFree space in /var directory meets or exceeds recommendation of minimum 1GBAll Database Servers
    PASSSQL CheckNo non-default AWR settings found.All Databases
    PASSSQL CheckNon-AWR Space consumption is less than 50% of total SYSAUX spaceAll Databases
    PASSOS Checkfree physical memory is at sufficient level on systemAll Database Servers
    PASSOS Checksystem is started with runlevel 3 or 5All Database Servers
    PASSOS Check/boot is mountedAll Database Servers
    PASSOS Check/dev/shm is mounted as temporary file systemAll Database Servers
    PASSSQL CheckTIMED_STATISTICS is set to recommended value.All Databases
    PASSSQL CheckSTATISTICS_LEVEL is set to recommended value.All Databases
    PASSSQL CheckAWR_FLUSH_EMERGENCY_COUNT value is equal to ZEROAll Databases

    Top

    Maximum Availability Architecture (MAA) Scorecard

    Outage Type Check Id Status Type Message Status On Details
    .
    DATABASE FAILURE PREVENTION BEST PRACTICESPASS
     [Updated: 03/09/17]
    
    Oracle database can be configured with best practices that are applicable to all Oracle databases, including single-instance, Oracle RAC databases, Oracle RAC One Node databases, and the primary and standby databases in Oracle Data Guard or Oracle GoldenGate configurations.
    
    Key HA Benefits:
    
    (1) Improved recoverability
    (2) Improved stability
    
     
    
    PASSSQL CheckAll tablespaces are locally managed tablespaceAll Databases
    PASSSQL CheckAll tablespaces are using Automatic segment storage managementAll Databases
    PASSSQL CheckDefault temporary tablespace is setAll Databases
    PASSSQL CheckDatabase Archivelog Mode is set to ARCHIVELOGAll Databases
    PASSOS CheckRedo log files are appropriately sizedAll Database Servers
    PASSSQL CheckThe SYS and SYSTEM user ids have a default tablespace of SYSTEMAll Databases
    PASSOS CheckLocal archive destination has alternate destination configuredAll Database Servers
    .
    COMPUTER FAILURE PREVENTION BEST PRACTICESINFO
     [Updated: 03/09/17]
    
    Oracle RAC and Oracle Clusterware allow Oracle Database to run any packaged or custom application across a set of clustered servers. This capability provides server side high availability and scalability. If a clustered server fails, then Oracle Database continues running on the surviving servers. When more processing power is needed, you can add another server without interrupting access to data.
    
    Oracle RAC and Oracle Clusterware supports rolling upgrade for most hardware and software changes excluding Oracle RDBMS patch sets and new database releases.
    To achieve zero or near zero application downtime, integrated client failover best practices need to be incorporated which is covered in client failover operational best practices section of the MAA scorecard.

    Key HA Benefits:
    • Zero database downtime for node and instance failures. Application brownout can be zero or seconds compared to minutes and an hour with third party cold cluster failover solutions.
    • Zero database and potentially zero application downtime for most planned maintenance activities involving operating system, database or Grid Infrastructure software changes.
    WARNINGSQL Parameter Checkfast_start_mttr_target should be greater than or equal to 300.All Instances
    .
    DATA CORRUPTION PREVENTION BEST PRACTICESPASS
     [Updated: 03/09/17]
    
    To achieve the most comprehensive data corruption prevention and detection , use Oracle Active Data Guard and configure DB_BLOCK_CHECKSUM,DB_LOST_WRITE_PROTECT and DB_BLOCK_CHECKING database initialization parameters on the primary database and all standby databases in a Data Guard environment. Workload specific testing is required to assess whether the performance overhead with especially DB_BLOCK_CHECKING is acceptable.
    
    Using ASM, RMAN, Exadata Storage and Zero Data Loss Recovery Appliance (Recovery Appliance) provide additional data protection checks and repair for Oracle databases and backups.    
    
     Key HA Benefits
    
    • Application downtime due to data corruptions can be reduced from hours and days to seconds to no downtime.
    • Prevention, quick detection and fast repair of data block corruptions.
    • With Active Data Guard, physical data block corruptions can be repaired automatically using current blocks from primary or standby databases.
    • With ASM, Exadata Storage and Recovery Appliance, data corruptions can be detected in the background and in some cases repaired automatically.
    • With DB_BLOCK_CHECKING=MED or FULL, logical data block corruptions can be detected and prevented on the primary or standby database.
    FAILSQL Parameter CheckDatabase parameter DB_LOST_WRITE_PROTECT is not set to recommended valueAll Instances
    FAILSQL Parameter CheckDatabase parameter DB_BLOCK_CHECKSUM is not set to recommended valueAll Instances
    WARNINGOS CheckDatabase parameter DB_BLOCK_CHECKING on PRIMARY is NOT set to the recommended value.All Database Servers
    PASSSQL CheckThe data files are all recoverableAll Databases
    PASSSQL CheckNo reported block corruptions in V$DATABASE_BLOCK_CORRUPTIONSAll Databases
    .
    LOGICAL CORRUPTION PREVENTION BEST PRACTICESPASS
     [Updated: 03/09/17]
    
    Oracle Flashback Technology enables fast logical failure repair. Oracle recommends that you use automatic undo management with sufficient space to attain your desired undo retention guarantee, enable Oracle Flashback Database, and allocate sufficient space and I/O bandwidth in the fast recovery area.  Application monitoring is required for early detection.  Effective and fast repair comes from leveraging and rehearsing the most common application specific logical failures and using the different flashback features effectively (e.g flashback query, flashback version query, flashback transaction query, flashback transaction, flashback drop, flashback table, and flashback database, and 12.2 flashback pluggable database (PDB)).
    
    Key HA Benefits:
    
    • With application monitoring and rehearsed repair actions with flashback technologies, application downtime can reduce from hours and days to the time to detect the logical inconsistency.
    • Fast repair for logical failures caused by malicious or accidental DML or DDL operations.
    • Effect fast point-in-time repair at the appropriate level of granularity: transaction, table, pluggable database, or database.
    Questions that need to be addressed by your application and operations team:
    1. Can your application or monitoring infrastructure detect logical inconsistencies?
    2. Is your operations team prepared to use various flashback technologies to repair quickly and efficiently?
    3. Is security practices enforced to prevent unauthorized privileges that can result logical inconsistencies?
    FAILSQL CheckFlashback on PRIMARY is not configuredAll Databases
    PASSSQL Parameter CheckRECYCLEBIN on PRIMARY is set to the recommended valueAll Instances
    PASSSQL Parameter CheckDatabase parameter UNDO_RETENTION on PRIMARY is not nullAll Instances
    .
    DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICESINFO
     [Updated: 03/09/17]
    
    Active Data Guard is the real-time data protection and availability solution that eliminates single point of failure by maintaining one or more synchronized physical replicas of the production database. If an unplanned outage of any kind impacts the production database, applications and users can quickly failover to a synchronized standby, minimizing downtime and preventing data loss. An Active Data Guard standby can be used to offload read-only applications, ad-hoc queries, and backups from the primary database or be dual-purposed as a test system at the same time it provides disaster protection. An Active Data Guard standby can also be used to minimize downtime for planned maintenance when upgrading to new Oracle Database patch sets and major database releases and for select migrations.  
     
    For zero data loss protection and fastest recovery time, deploy a local Data Guard standby database with Data Guard Fast-Start Failover and integrated client failover. For protection against outages impacting the entire data center, or a broad geography, deploy a Data Guard standby database at a remote location. Oracle 12c Far Sync Standby can achieve zero data loss protection across Wide Area Network or across regions.
    
    Key HA Benefits:
    
    • Active Data Guard provides optimal data protection by using physical replication and comprehensive Oracle validation to maintain an exact byte-for-byte copy of the primary database that can be open read-only to offload reporting, ad-hoc queries and backups.
    • With Oracle 11g release 2 and higher Active Data Guard and real time apply, data block corruptions can be repaired automatically and downtime can be reduced from hours and days of application impact to zero downtime with zero data loss.
    • With MAA best practices, Data Guard Fast-Start Failover and integrated client failover, downtime from database, cluster and site failures can be reduced from hours to days to seconds.
    • With remote standby database (Disaster Recovery Site), you have protection from complete site failures.
    • In all cases, the Active Data Guard instances can be active and used for other activities.
    • Data Guard can reduce risks and downtime for planned maintenance activities by using Database rolling upgrade with transient logical standby or DBMS rolling, standby-first patch apply and database migrations.
    • For other advanced replication requirements where read-write access to a replica database is required while it is being synchronized with the primary database see Oracle GoldenGate logical replication. Oracle GoldenGate can be used to support heterogeneous database platforms and database releases, an effective read-write full or subset logical replica and to reduce or eliminate downtime for application, database or system changes. Oracle GoldenGate flexible logical replication solution's main trade-off is the additional administration for application developer and database administrators.
    FAILSQL CheckPrimary database is not protected with Data Guard (standby database) for real-time data protection and availabilityAll Databases
    .
    CLIENT FAILOVER OPERATIONAL BEST PRACTICESPASS
     [Updated: 03/09/17]
    
    A highly available architecture requires the ability of the application tier to transparently fail over to a surviving instance or database advertising the required service. This ensures that applications are generally available or minimally impacted in the event of node failure, instance failure, or database failures.
     
    
    WARNINGOS CheckNon-default database Services are not configuredAll Database Servers
    PASSOS CheckClusterware is runningAll Database Servers
    .
    ORACLE RECOVERY MANAGER(RMAN) BEST PRACTICESPASS
     [Updated: 03/09/17]
    
    Oracle Recovery Manager (RMAN) is an Oracle Database utility to manage database backup and, more importantly, the recovery of the database. RMAN eliminates operational complexity while providing superior performance and availability of the database.
    
    RMAN determines the most efficient method of executing the requested backup, restoration, or recovery operation and then submits these operations to the Oracle Database server for processing. RMAN and the server automatically identify modifications to the structure of the database and dynamically adjust the required operation to adapt to the changes.
    RMAN has many unique HA capabilities that can be challenging or impossible for third party backup and restore utilities to deliver such as
    • In-depth Oracle data block checks during every backup or restore operation
    • Efficient block media recovery
    • Automatic recovery through complex database state changes such as resetlogs or past Data Guard role transitions
    • Fast incremental backup and restore operations
    • Integrated retention policies and backup file management with Oracle’s fast recovery area
    • Online backups without the need to put the database or data file in hot backup mode.
    RMAN backups are strategic to MAA so a damaged database (complete database or subset of the database such as a data file or tablespace, log file, or controlfile) can be recovered but for the fastest recovery, use Data Guard or GoldenGate. RMAN operations are also important for detecting any corrupted blocks from data files that are not frequently accessed. Oracle also now has the Zero Data Loss Recovery Appliance (Recovery Appliance) which provides the following key benefits:
    • Eliminate or Minimize Data Loss.
    • Minimal Impact Backups by offloading reduplication, compression, recovery+merge, and validation to Recovery Appliance.
    • Database Level Recoverability and Validation.
    • Cloud-scale and Data Center wide Data Protection for all backups.
    WARNINGSQL CheckRMAN controlfile autobackup should be set to ONAll Databases
    PASSOS Checkcontrol_file_record_keep_time is within recommended range [1-9]All Database Servers
    .
    ORACLE GOLDENGATE FAILURE PREVENTION BEST PRACTICESINFO
     [Updated: 03/09/17]
    
    Oracle GoldenGate is Oracle's strategic logical replication solution for data distribution and data integration. Unlike replication solutions from other vendors, Oracle GoldenGate is more closely integrated with Oracle Database while also providing an open, modular architecture ideal for replication across heterogeneous database management systems. This combination of attributes eliminates compromise, making Oracle GoldenGate the preferred replication solution for addressing requirements that span Oracle Database and non-Oracle Database environments.
    
    Key HA Benefits:
    
    • Potential zero or near zero application downtime for platform migration, database or application upgrades.
    • Active/Active environment with the ability to update both databases. Conflict resolution techniques will need to be considered.
    To achieve the highest levels of availability resulting in zero or near-zero downtime for both unplanned outages and all planned maintenance activities, customers use the combination of Oracle Active Data Guard and Oracle GoldenGate.
    Oracle Active Data Guard and Oracle GoldenGate are essential components of the Gold and Platinum MAA tiers.
    .
    OPERATIONAL BEST PRACTICESINFO
     [Updated: 03/09/17]
    
    Operational best practices are an essential prerequisite to high availability.
     
    
    .
    DATABASE CONSOLIDATION BEST PRACTICESINFO
     [Updated: 03/09/17]
    
    Database consolidation requires additional planning and management to ensure HA requirements are met.
     
    

    Top

    Patch Recommendation

    Database server "rac1"




    1 Recommended CRS patches for 112040 from /oracle/app/11.2.0/grid
    Patch CRS ASM RDBMS RDBMS_HOME Patch-Description
    22502505not-appliedn/anot-applied/oracle/app/oracle/product/11.2.0/db ACFS PSU 11.2.0.4.160419
    26392168not-appliedn/anot-applied/oracle/app/oracle/product/11.2.0/db DB PSU 11.2.0.4.171017 (INCLUDES CPUOCT2017)
    26609929not-appliedn/anot-applied/oracle/app/oracle/product/11.2.0/db OCW PSU 11.2.0.4.170814
    Top

    1 Recommended RDBMS patches for 112040 from /oracle/app/oracle/product/11.2.0/db
    Patch RDBMS ASM Type Patch-Description
    26392168not-appliedn/amerge DB PSU 11.2.0.4.171017 (INCLUDES CPUOCT2017)
    26609929not-appliedn/amerge OCW PSU 11.2.0.4.170814
    Top

    Top

    Component Elapsed Times

    Component Name Component Type Elapsed Time

    Top

    Top 10 Time Consuming Checks

    NOTE: This information is primarily used for helping Oracle optimize the run time of ORAchk.

    These timings are not necessarily indicative of any problem and may vary widely from one system to another.

    Check Id Name Type Target Execution Duration
    Cluster interconnect (clusterware) OS Collection rac1:None 13 secs
    Monitoring Non-AWR space usage in SYSAUX SQL Check rac1:orcl 12 secs
    Patches for RDBMS Home OS Collection rac1:None 7 secs
    Parallel Execution Health-Checks and Diagnostics Reports OS Check rac1:orcl 7 secs
    Interconnect NIC bonding config. OS Check rac1 6 secs
    NIC Bonding Mode for interconnect OS Check rac1 6 secs
    Public interface existence OS Check rac1 6 secs
    Verify private and public network subnet configuration in Oracle Clusterware registry OS Check rac1 6 secs
    Subnet mask for cluster_interconnect NICS branch OS Check rac1 6 secs
    More than one card for interconnect? OS Check rac1 6 secs

    Switch to old format