Oracle Exadata Assessment Report

System Health Score is derived using following formula.

Every check has 10 points
Failure will deduct 10 points
Warning will deduct 5 points
Info will deduct 3 points

Total checks	271
Passed checks	222
Failed(fail/warn/info) checks	49

..Hide

dm01db02
dm01db01 ..Hide

  dm01cel03
  dm01cel02
  dm01cel01 ..Hide

dm01sw-ib2
dm01sw-ib3 ..Hide

Status	Type	Message	Status On	Details
FAIL	OS Check	Database control files are not configured as recommended	All Database Servers	View
FAIL	Patch Check	System may be exposed to Exadata Critical Issue DB11	All Homes	View
FAIL	OS Check	Database Server Physical Drive Configuration does not meet recommendation	All Database Servers	View
FAIL	SQL Parameter Check	Database parameter USE_LARGE_PAGES is NOT set to recommended value	All Instances	View
FAIL	SQL Parameter Check	Database parameter GLOBAL_NAMES is NOT set to recommended value	All Instances	View
FAIL	OS Check	InfiniBand network error counters are non-zero	All Database Servers	View
FAIL	SQL Check	Some data or temp files are not autoextensible	All Databases	View
FAIL	SQL Parameter Check	Database parameter _lm_rcvr_hang_allow_time is NOT set to the recommended value	All Instances	View
FAIL	SQL Parameter Check	Database parameter _kill_diagnostics_timeout is not set to recommended value	All Instances	View
WARNING	OS Check	All voting disks are not online	All Database Servers	View
WARNING	SQL Check	Some tablespaces are not using Automatic segment storage management.	All Databases	View
INFO	OS Check	ASM griddisk,diskgroup and Failure group mapping not checked.	All Database Servers	View

Status	Type	Message	Status On	Details
FAIL	Storage Server Check	The griddisk ASM status should match specification	dm01cel01	View
FAIL	Storage Server Check	The celldisk configuration on disk drives should match Oracle best practices	dm01cel01	View
FAIL	Storage Server Check	one or storage server has open critical alerts.	All Storage Servers	View
FAIL	Storage Server Check	Storage Server alerts are not configured to be sent via email	All Storage Servers	View
WARNING	Storage Server Check	Free space in root(/) filesystem is less than recommended on one or more storage servers.	All Storage Servers	View

Outage Type	Status	Type	Message	Status On	Details

COMPUTER FAILURE PREVENTION BEST PRACTICES	PASS	Description Oracle RAC and Oracle Clusterware allow Oracle Database to run any packaged or custom application across a set of clustered servers. This capability provides the highest levels of availability and the most flexible 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. For RAC and clusterware MAA best practices please consult chapter 6 and 7 of the HA Best Practices guide Links: Chapter 6 - Configuring Oracle Database with Oracle Clusterware Chapter 7 - Configuring Oracle Database with Oracle RAC
PASS	SQL Parameter Check	fast_start_mttr_target has been changed from default	All Instances	View

STORAGE FAILURES PREVENTION BEST PRACTICES	PASS	Description The Oracle Storage Grid is implemented using either Oracle Automatic Storage Management (ASM) and Oracle Exadata Storage Server Software or ASM and third-party storage. The Oracle Storage Grid with Exadata seamlessly supports MAA-related technology, improves performance, provides unlimited I/O scalability, is easy to use and manage, and delivers mission-critical availability and reliability to your enterprise. For additional information and best practices consult the Oracle Exadata Storage Server Web site at http://www.oracle.com/exadata Links: Oracle Exadata Database Machine Configuring Storage
PASS	SQL Check	At least one high redundancy diskgroup configured	All Databases	View

DATA CORRUPTION PREVENTION BEST PRACTICES	FAIL	Description The MAA recommended way to achieve the most comprehensive data corruption prevention and detection is to use Oracle Data Guard and configure the DB_BLOCK_CHECKING, DB_BLOCK_CHECKSUM, and DB_LOST_WRITE_PROTECT database initialization parameters on the Data Guard primary and standby databases. Links: Note: 1302539.1 - Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration - Protect Against Data Corruption Oracle® Database Reference
FAIL	SQL Parameter Check	Database parameter DB_BLOCK_CHECKSUM is NOT set to recommended value	All Instances	View
WARNING	OS Check	Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.	All Database Servers	View
WARNING	OS Check	Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.	All Database Servers	View
PASS	SQL Parameter Check	Database parameter DB_LOST_WRITE_PROTECT is set to recommended value	All Instances	View
PASS	OS Check	Shell limit soft nofile for DB is configured according to recommendation	All Database Servers	View

LOGICAL CORRUPTION PREVENTION BEST PRACTICES	FAIL	Description 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) Links: HA Best Practices guide - 5.1.4 Enable Flashback Database
FAIL	SQL Check	Flashback is not configured	All Databases	View
PASS	SQL Parameter Check	Database parameter UNDO_RETENTION is not null	All Instances	View

DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES	FAIL	Description Oracle Data Guard is a high availability and disaster-recovery solution that provides very fast automatic failover (referred to as fast-start failover) in database failures, node failures, corruption, and media failures. Furthermore, the standby databases can be used for read-only access and subsequently for reader farms, for reporting, for backups and for testing and development. For zero data loss protection and fastest recovery time, deploy a local Data Guard standby database with Data Guard Fast-Start Failover. For protection against outages impacting both the primary and the local standby, deploy a second Data Guard standby database at a remote location. Links: Use Standby Redo Logs and Configure Size Appropriately Use Oracle Active Data Guard Best Practices Oracle Data Guard: Disaster Recovery for Oracle Exadata Database Machine Use Data Guard Redo Apply Best Practices Oracle Data Guard Role Transition Best Practices Determine Support for Data Types and Storage Attributes for Tables
FAIL	OS Check	Oracle Net service name to ship redo to the standby is not configured properly	All Database Servers	View
FAIL	SQL Check	Remote destination not is using either ASYNC or SYNC transport for redo transport	All Databases	View
FAIL	SQL Check	Standby is not running in MANAGED REAL TIME APPLY mode	All Databases	View
FAIL	SQL Check	Standby redo logs are not configured on both sites	All Databases	View
FAIL	SQL Check	Physical standby status is not valid	All Databases	View
WARNING	SQL Check	Logical standby unsupported datatypes found	All Databases	View
PASS	SQL Check	Database parameter LOG_FILE_NAME_CONVERT or DB_CREATE_ONLINE_LOG_DEST_1 is not null	All Databases	View

NETWORK FAILURE PREVENTION BEST PRACTICES	INFO	Description Redundant InfiniBand network connectivity using dual-ported Quad Data Rate (QDR) Host Channel Adapters (HCAs) and redundant switches are pre-configured. Configuring the same redundancy for client access by network bonding is recommended and can be done at deployment time. Additional servers such as media and ETL servers should also be configured with redundant networks. Links: Deploying Oracle Maximum Availability Architecture with Exadata Database Machine

CLIENT FAILOVER OPERATIONAL BEST PRACTICES	FAIL	Description 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, data corruption, or database failures. For client failover best practices and network best practices, see the MAA white paper "Client Failover Best Practices for Data Guard 11g Release 2" from the MAA Best Practices area for Oracle Database. Links: Client Failover Best Practices for Highly Available Oracle Databases: Oracle Database 11g Release 2
FAIL	OS Check	Dataguard broker configuration does not exist	All Database Servers	View
PASS	OS Check	Clusterware is running	All Database Servers	View

OPERATIONAL BEST PRACTICES	INFO	Description The integration of Oracle Maximum Availability Architecture (MAA) operational and configuration best practices with Oracle Exadata Database Machine (Exadata MAA) provides the most comprehensive high availability solution available for the Oracle Database Links: Operational Prerequisites to Maximizing Availability MAA Best Practices for Oracle Exadata Database Machine (technical white paper)

CONSOLIDATION DATABASE PRACTICES	INFO	Description Managing multiple databases on Exadata require following additional guidelines Links: Best Practices For Database Consolidation On Exadata Database Machine Note: 1339769.1 - Master Note for Oracle Database Resource Manager - Using Oracle Database Resource Manage

Status	Type	Message	Status On	Details
PASS	ASM Check	ASM processes parameter is set to recommended value	All ASM Instances	View
PASS	SQL Parameter Check	RECYCLEBIN is set to the recommended value	All Instances	View
PASS	SQL Parameter Check	ASM parameter ASM_POWER_LIMIT is set to the default value.	All Instances	View
PASS	OS Check	DNS Server ping time is in acceptable range	All Database Servers	View
PASS	OS Check	Database Server Disk Controller Configuration meets recommendation	All Database Servers	View
PASS	SQL Parameter Check	ASM parameter MEMORY_MAX_TARGET is set according to recommended value	All Instances	View
PASS	SQL Parameter Check	ASM parameter PGA_AGGREGATE_TARGET is set according to recommended value	All Instances	View
PASS	SQL Parameter Check	ASM parameter MEMORY_TARGET is set according to recommended value	All Instances	View
PASS	SQL Parameter Check	ASM parameter SGA_TARGET is set according to recommended value.	All Instances	View
PASS	SQL Check	All bigfile tablespaces have non-default maxbytes values set	All Databases	View
PASS	OS Check	subnet manager is running on an InfiniBand switch	All Database Servers	View
PASS	OS Check	Address Resolution Protocol (ARP) is configured properly on database server.	All Database Servers	View
PASS	OS Check	Only one non-ASM instance discovered	All Database Servers	View
PASS	OS Check	Database parameter Db_create_online_log_dest_n is set to recommended value	All Database Servers	View
PASS	OS Check	Database parameters log_archive_dest_n with Location attribute are all set to recommended value	All Database Servers	View
PASS	OS Check	Database parameter COMPATIBLE is set to recommended value	All Database Servers	View
PASS	OS Check	All Ethernet network cables are connected	All Database Servers	View
PASS	OS Check	All InfiniBand network cables are connected	All Database Servers	View
PASS	OS Check	Database parameter db_recovery_file_dest_size is set to recommended value	All Database Servers	View
PASS	OS Check	Database DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST are in different diskgroups	All Database Servers	View
PASS	OS Check	Database parameter CLUSTER_INTERCONNECTS is set to the recommended value	All Database Servers	View
PASS	ASM Check	ASM parameter CLUSTER_INTERCONNECTS is set to the recommended value	All ASM Instances	View
PASS	SQL Parameter Check	Database parameter PARALLEL_EXECUTION_MESSAGE_SIZE is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter SQL92_SECURITY is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter OPEN_CURSORS is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter OS_AUTHENT_PREFIX is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter PARALLEL_THREADS_PER_CPU is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter _ENABLE_NUMA_SUPPORT is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter PARALLEL_ADAPTIVE_MULTI_USER is set to recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter _file_size_increase_increment is set to the recommended value	All Instances	View
PASS	SQL Parameter Check	Database parameter LOG_BUFFER is set to recommended value	All Instances	View
PASS	OS Check	Disk cache policy is set to Disabled on database server	All Database Servers	View
PASS	OS Check	Exadata software version supports Automatic Service Request functionality	All Database Servers	View
PASS	OS Check	Oracle ASM Communication is using RDS protocol on Infiniband Network	All Database Servers	View
PASS	OS Check	Database server disk controllers use writeback cache	All Database Servers	View
PASS	OS Check	Verify-topology executes without any errors or warning	All Database Servers	View
PASS	OS Check	Hardware and firmware profile check is successful. [Database Server]	All Database Servers	View
PASS	OS Check	Local listener init parameter is set to local node VIP	All Database Servers	View
PASS	OS Check	ohasd/orarootagent_root Log Ownership is Correct (root root)	All Database Servers	View
PASS	OS Check	Remote listener is set to SCAN name	All Database Servers	View
PASS	OS Check	NTP is running with correct setting	All Database Servers	View
PASS	OS Check	Interconnect is configured on non-routable network addresses	All Database Servers	View
PASS	SQL Check	SYS.IDGEN1$ sequence cache size >= 1,000	All Databases	View
PASS	OS Check	crsd Log Ownership is Correct (root root)	All Database Servers	View
PASS	OS Check	OSWatcher is running	All Database Servers	View
PASS	OS Check	ORA_CRS_HOME environment variable is not set	All Database Servers	View
PASS	SQL Check	GC blocks lost is not occurring	All Databases	View
PASS	OS Check	NIC bonding mode is not set to Broadcast(3) for cluster interconnect	All Database Servers	View
PASS	SQL Check	SYS.AUDSES$ sequence cache size >= 10,000	All Databases	View
PASS	OS Check	SELinux is not being Enforced.	All Database Servers	View
PASS	OS Check	crsd/orarootagent_root Log Ownership is Correct (root root)	All Database Servers	View
PASS	OS Check	$ORACLE_HOME/bin/oradism ownership is root	All Database Servers	View
PASS	OS Check	NIC bonding is configured for interconnect	All Database Servers	View
PASS	OS Check	$ORACLE_HOME/bin/oradism setuid bit is set	All Database Servers	View
PASS	OS Check	ohasd Log Ownership is Correct (root root)	All Database Servers	View
PASS	OS Check	NIC bonding is configured for public network (VIP)	All Database Servers	View
PASS	OS Check	Open files limit (ulimit -n) for current user is set to recommended value >= 65536 or unlimited	All Database Servers	View
PASS	OS Check	NIC bonding mode is not set to Broadcast(3) for public network	All Database Servers	View
PASS	OS Check	Shell limit hard stack for GI is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit soft nproc for DB is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit hard stack for DB is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit hard nofile for DB is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit hard nproc for DB is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit hard nproc for GI is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit hard nofile for GI is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit soft nproc for GI is configured according to recommendation	All Database Servers	View
PASS	OS Check	Shell limit soft nofile for GI is configured according to recommendation	All Database Servers	View
PASS	OS Check	Management network is separate from data network	All Database Servers	View
PASS	OS Check	RAID controller battery temperature is normal [Database Server]	All Database Servers	View
PASS	ASM Check	ASM Audit file destination file count <= 100,000	All ASM Instances	View
PASS	OS Check	Database Server Virtual Drive Configuration meets recommendation	All Database Servers	View
PASS	ASM Check	Correct number of FailGroups per ASM DiskGroup are configured	All ASM Instances	View
PASS	OS Check	System model number is correct	All Database Servers	View
PASS	OS Check	Number of Mounts before a File System check is set to -1 for system disk	All Database Servers	View
PASS	OS Check	Free space in root(/) filesystem meets or exceeds recommendation.	All Database Servers	View
PASS	OS Check	Oracle RAC Communication is using RDS protocol on Infiniband Network	All Database Servers	View
PASS	OS Check	Database Home is properly linked with RDS library	All Database Servers	View
PASS	OS Check	InfiniBand is the Private Network for Oracle Clusterware Communication	All Database Servers	View
PASS	SQL Check	RDBMS Version is 11.2.0.2 or higher as expected	All Databases	View
PASS	SQL Check	All tablespaces are locally manged tablespace	All Databases	View
PASS	ASM Check	ASM Version is 11.2.0.2 or higher as expected	All ASM Instances	View
PASS	OS Check	NUMA is OFF at operating system level.	All Database Servers	View
PASS	OS Check	Database Server InfiniBand network MTU size is 65520	All Database Servers	View
PASS	OS Check	Clusterware Home is properly linked with RDS library	All Database Servers	View
PASS	OS Check	CSS misscount is set to the recommended value of 60	All Database Servers	View
PASS	OS Check	Database server InfiniBand network is in "connected" mode.	All Database Servers	View
PASS	ASM Check	All disk groups have compatible.asm parameter set to recommended values	All ASM Instances	View
PASS	ASM Check	All disk groups have CELL.SMART_SCAN_CAPABLE parameter set to true	All ASM Instances	View
PASS	ASM Check	All disk groups have compatible.rdbms parameter set to recommended values	All ASM Instances	View
PASS	ASM Check	All disk groups have allocation unit size set to 4MB	All ASM Instances	View

Status	Type	Message	Status On	Details
PASS	Storage Server Check	The celldisk configuration on flash memory devices matches Oracle best practices	All Storage Servers	View
PASS	Storage Server Check	The griddisk count matches across all storage servers where a given prefix name exists	All Storage Servers	View
PASS	Storage Server Check	The total number of griddisks with a given prefix name is evenly divisible by the number of celldisks	All Storage Servers	View
PASS	Storage Server Check	The total size of all griddisks fully utilizes celldisk capacity	All Storage Servers	View
PASS	Storage Server Check	DNS Server ping time is in acceptable range	All Storage Servers	View
PASS	Storage Server Check	Smart flash log is created on all storage server	All Storage Servers	View
PASS	Storage Server Check	Storage Server Flash Memory is configured as Exadata Smart Flash Cache	All Storage Servers	View
PASS	Storage Server Check	Peripheral component interconnect (PCI) bridge is configured for generation II on all storage servers	All Storage Servers	View
PASS	Storage Server Check	There are no griddisks configured on flash memory devices	All Storage Servers	View
PASS	Storage Server Check	No Storage Server conventional or flash disks have a performance problem	All Storage Servers	View
PASS	Storage Server Check	All InfiniBand network cables are connected on all Storage Servers	All Storage Servers	View
PASS	Storage Server Check	All Ethernet network cables are connected on all Storage Servers	All Storage Servers	View
PASS	Storage Server Check	Disk cache policy is set to Disabled on all storage server	All Storage Servers	View
PASS	Storage Server Check	Electronic Storage Module (ESM) Lifetime is within specification for all flash cards on all storage servers	All Storage Servers	View
PASS	Storage Server Check	Management network is separate from data network on all storage servers	All Storage Servers	View
PASS	Storage Server Check	Ambient temperature is within the recommended range.	All Storage Servers	View
PASS	Storage Server Check	Software profile check is successful on all storage servers.	All Storage Servers	View
PASS	Storage Server Check	Hardware and firmware profile check is successful on all storage servers.	All Storage Servers	View
PASS	Storage Server Check	OSWatcher is running on all storage servers	All Storage Servers	View
PASS	Storage Server Check	RAID controller battery temperature is normal [Storage Server]	All Storage Servers	View
PASS	Storage Server Check	All Exadata storage server meet system model number requirement	All Storage Servers	View
PASS	Storage Server Check	All storage server disk controllers use writeback cache	All Storage Servers	View
PASS	Storage Server Check	No celldisks have status of predictive failure	All Storage Servers	View
PASS	Storage Server Check	RAID controller version matches on all storage servers	All Storage Servers	View
PASS	Storage Server Check	No Storage Server Memory (ECC) Errors found.	All Storage Servers	View

Status	Type	Message	Status On	Details
PASS	Cluster Wide Check	RDBMS home /u01/app/oracle/product/11.2.0.3/dbhome_1 has same number of patches installed across the cluster	Cluster Wide	-
PASS	Cluster Wide Check	Clusterware active version matches across cluster.	Cluster Wide	View
PASS	Cluster Wide Check	Grid Infrastructure software owner UID matches across cluster	Cluster Wide	View
PASS	Cluster Wide Check	Timezone matches for current user across cluster.	Cluster Wide	View
PASS	Cluster Wide Check	Private interconnect interface names are the same across cluster	Cluster Wide	View
PASS	Cluster Wide Check	RDBMS software version matches across cluster.	Cluster Wide	View
PASS	Cluster Wide Check	Public network interface names are the same across cluster	Cluster Wide	View
PASS	Cluster Wide Check	OS Kernel version(uname -r) matches across cluster.	Cluster Wide	View
PASS	Cluster Wide Check	RDBMS software owner UID matches across cluster	Cluster Wide	View
PASS	Cluster Wide Check	Time zone matches for Grid Infrastructure software owner across cluster	Cluster Wide	View
PASS	Cluster Wide Check	Time zone matches for root user across cluster	Cluster Wide	View
PASS	Cluster Wide Check	Master (Rack) Serial Number matches across database servers and storage servers	Cluster Wide	View

Top

Clusterware version comparison

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability, Standardization Risk: Potential cluster instability due to clusterware version mismatch on cluster nodes. It is possible that if the clusterware versions do not match that some incompatibility could exist which would make diagnosing problems difficult or bugs fixed in the later clusterware version still being present on some nodes but not on others. Action / Repair: Unless in the process of a rolling upgrade of the clusterware it is assumed that the clusterware versions will match across the cluster. If they do not then it is assumed that some mistake has been made and overlooked. The purpose of this check is to bring this situation to the attention of the customer for action and remedy.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Clusterware active version matches across cluster.


dm01db01 = 112030
dm01db02 = 112030

Top

UID for GI software owner across cluster

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Availability, stability Risk: Potential OCR logical corruptions and permission problems accessing OCR keys when multiple O/S users share the same UID which are difficult to diagnose. Action / Repair: For GI and RDBMS software owners ensure one unique user ID with a single name is in use across the cluster.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Grid Infrastructure software owner UID matches across cluster


dm01db01 = 1000
dm01db02 = 1000

Top

Timezone for current user

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Clusterware deployment requirement Risk: Potential cluster instability Action / Repair: Oracle Clusterware requires the same time zone setting on all cluster nodes. During installation, the installation process picks up the time zone setting of the Grid installation owner on the node where OUI runs, and uses that on all nodes as the default TZ setting for all processes managed by Oracle Clusterware. This default is used for databases, Oracle ASM, and any other managed processes. If for whatever reason the time zones have gotten out of sych then the configuration should be corrected. Consult with Oracle Support about the proper method for correcting the time zones.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Timezone matches for current user across cluster.


dm01db01 = CST
dm01db02 = CST

Top

Grid Infrastructure - Private interconnect interface name check

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability, Standardization Risk: Potential cluster or application instability due to incorrectly named network interfaces. Action / Repair: The Oracle clusterware expects and it is required that the network interfaces used for the cluster interconnect be named the same on all nodes of the cluster.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Private interconnect interface names are the same across cluster


dm01db01 = bondib0
dm01db02 = bondib0

Top

RDBMS software version comparison

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability, Standardization Risk: Potential database or application instability due to version mismatch for database homes. It is possible that if the versions of related RDBMS homes on all the cluster nodes do not match that some incompatibility could exist which would make diagnosing problems difficult or bugs fixed in the later RDBMS version still being present on some nodes but not on others. Action / Repair: It is assumed that the RDBMS versions of related database homes will match across the cluster. If the versions of related RDBMS homes do not match then it is assumed that some mistake has been made and overlooked. The purpose of this check is to bring this situation to the attention of the customer for action and remedy.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => RDBMS software version matches across cluster.


dm01db01 = 112030
dm01db02 = 112030

Top

Grid Infrastructure - Public interface name check (VIP)

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability, Standardization Risk: Potential application instability due to incorrectly named network interfaces used for node VIP. Action / Repair: The Oracle clusterware expects and it is required that the network interfaces used for the public interface used for the node VIP be named the same on all nodes of the cluster.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Public network interface names are the same across cluster


dm01db01 = bondeth0
dm01db02 = bondeth0

Top

Kernel version comparison across cluster

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability, Standardization Risk: Potential cluster instability due to kernel version mismatch on cluster nodes. It is possible that if the kernel versions do not match that some incompatibility could exist which would make diagnosing problems difficult or bugs fixed in the l ater kernel still being present on some nodes but not on others. Action / Repair: Unless in the process of a rolling upgrade of cluster node kernels it is assumed that the kernel versions will match across the cluster. If they do not then it is assumed that some mistake has been made and overlooked. The purpose of this check is to bring this situation to the attention of the customer for action and remedy.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => OS Kernel version(uname -r) matches across cluster.


dm01db01 = 2632-40011el5uek
dm01db02 = 2632-40011el5uek

Top

RDBMS software owner UID across cluster

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Availability, stability Risk: Potential OCR logical corruptions and permission problems accessing OCR keys when multiple O/S users share the same UID which are difficult to diagnose. Action / Repair: For GI and Oracle software owners ensure one unique user ID with a single name is in use across the cluster.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => RDBMS software owner UID matches across cluster


dm01db01 = 1001
dm01db02 = 1001

Top

Grid Infrastructure software owner time zone

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Clusterware deployment requirement Risk: Potential cluster instability Action / Repair: Oracle Clusterware requires the same time zone setting on all cluster nodes. During installation, the installation process picks up the time zone setting of the Grid installation owner on the node where OUI runs, and uses that on all nodes as the default TZ setting for all processes managed by Oracle Clusterware. This default is used for databases, Oracle ASM, and any other managed processes. If for whatever reason the time zones have gotten out of sych then the configuration should be corrected. Consult with Oracle Support about the proper method for correcting the time zones.
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Time zone matches for Grid Infrastructure software owner across cluster


dm01db01 = CST
dm01db02 = CST

Top

Root time zone

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Time zone matches for root user across cluster


dm01db01 = CST
dm01db02 = CST

Top

Verify Master (Rack) Serial Number is Set [Database Server and storage server]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Setting the Master Serial Number (MSN) (aka Rack Serial Number) assists Oracle Support Services to resolve entitlement issues which may arise. The MSN is listed on a label on the front and the rear of the chassis but is not electronically readable unless this value is set. The impact to set the MSN is minimal. Risk: Not having the MSN set for the system may hinder entitlement when opening Service Requests. Action / Repair: Use the following command to verify that all the MSN's are set correctly and all match: # ipmitool sunoem cli "show /SP system_identifier" The output should resemble one of the following: EV2: Sun Oracle Database Machine xxxxAKyyyy X2-2: Exadata Database Machine X2-2 xxxxAKyyyy X2-8: Exadata Database Machine X2-8 xxxAKyyyy (MSN's will be of the format either 4 numbers, the letters 'AK' followed by 4 more numbers or letters A-F, or the letters 'AK followed by 8 numbers or letters A-F) On any server where the MSN is not set correctly, use the following command as the "root" userid to set it: ipmitool sunoem cli 'set /SP system_identifier="text_identifier_string serial_number"' Where "text_identifier_string" is one of: For X2-2(4170): "Sun Oracle Database Machine" For X2-2: "Exadata Database Machine X2-2" For X2-8: "Exadata Database Machine X2-8" and "serial_number" is the MSN from the label attached to the rack. NOTE: The label with the Master Serial Number is located on the top left side wall (viewed from rear) inside the rack on the rear of the chassis. NOTE: In the command to set the Master Serial Number there is a space between the "text_identifier_string" and the "serial_number".
Needs attention on	-
Passed on	Cluster Wide

Status on Cluster Wide: PASS => Master (Rack) Serial Number matches across database servers and storage servers


dm01db01 = AK00030945
dm01cel01 = AK00030945
dm01cel02 = AK00030945
dm01cel03 = AK00030945
dm01db02 = AK00030945

Top

High Redundancy Controlfile

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: A high redundancy diskgroup optimizes availability. 1. Control file should be in a high redundancy disk group. 2. One controlfile members is recommended for high redundancy and two members in separate disk groups are recommended for normal redundancy Query to find out number of control files and respective disk group and redundancy:- select substr(cf.name,1,instr(cf.name,'/',1,1) - 1) cf_name,dg.name dg_name,dg.type redundancy from v$controlfile cf,v$asm_diskgroup dg where replace(substr(cf.name,1,instr(cf.name,'/',1,1) - 1),'+') = dg.name;
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: FAIL => Database control files are not configured as recommended


DATA FROM DM01DB01 - MCSDB DATABASE - HIGH REDUNDANCY CONTROLFILE



Number of Control files = 	  3
High redundancy diskgroups = 	  1
High redundancy diskgroups where control files are multiplexed = 		       1
Normal redundancy diskgroups where control files are multiplexed = 		       0

Status on dm01db02: FAIL => Database control files are not configured as recommended


Number of Control files = 	  3
High redundancy diskgroups = 	  1
High redundancy diskgroups where control files are multiplexed = 		       1
Normal redundancy diskgroups where control files are multiplexed = 		       0

Top

Check ORACLE_PATCH 13667791 13734832 for RDBMS home

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Issues:-Bug 13257247 - AWR Snapshot collection hangs due to slow inserts into WRH$_TEMPSTATXS.. Please follow guidelines in the following link in section DB11 for corrective action
Links	Note: 1270094.1 - Exadata Critical Issues - Note: 13257247.8 - AWR Snapshot collection hangs due to slow inserts into WRH$_TEMPSTATXS -
Needs attention on	dm01db01:/u01/app/oracle/product/11.2.0.3/dbhome_1, dm01db02:/u01/app/oracle/product/11.2.0.3/dbhome_1
Passed on	-

Status on dm01db01:/u01/app/oracle/product/11.2.0.3/dbhome_1: FAIL => System may be exposed to Exadata Critical Issue DB11


Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/11.2.0.3/dbhome_1
Central Inventory : /u01/app/oraInventory
from           : /u01/app/oracle/product/11.2.0.3/dbhome_1/oraInst.loc
OPatch version    : 11.2.0.3.0
OUI version       : 11.2.0.3.0
Log file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/opatch2014-04-16_11-03-29AM_1.log

Lsinventory Output file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2014-04-16_11-03-29AM.txt

------------------------------------------------------------------------------------------------------
Installed Top-level Products (1):

Oracle Database 11g                                                  11.2.0.3.0
There are 1 products installed in this Oracle Home.



List of Bugs fixed by Installed Patches:

Bug        Fixed by  Installed at                   Description
Patch
---        --------  ------------                   -----------

13350234   14307915  Wed Nov 28 11:23:28 CST 2012   DISKMON PATCH FOR EXADATA (DEC 2011 - 11.2.0.3.1)
13513982   14307915  Wed Nov 28 11:23:28 CST 2012   QUARTERLY DISKMON PATCH FOR EXADATA (JAN 2012 - 11
.2.0.3.2)
13688022   14307915  Wed Nov 28 11:23:28 CST 2012   DISKMON PATCH FOR EXADATA (MAR 2012 - 11.2.0.3.4)
14050993   14307915  Wed Nov 28 11:23:28 CST 2012   DISKMON PATCH FOR EXADATA (JUN 2012 - 11.2.0.3.7)
14184077   14307915  Wed Nov 28 11:23:28 CST 2012   DISKMON PATCH FOR EXADATA (JUL 2012 - 11.2.0.3.8)
14307915   14307915  Wed Nov 28 11:23:28 CST 2012   QUARTERLY DISKMON PATCH FOR EXADATA (OCT 2012 - 11
.2.0.3.11)
10114953   14275572  Wed Nov 28 11:23:12 CST 2012   HPI-SG 10205->11202 ONLY ONE HAIP UP IF 2 PRIVATE
NICS CONFIGURED BEFORE UPGRADE
10317921   14275572  Wed Nov 28 11:23:12 CST 2012   11202_GI_BUND_CRF-MEMORY ALERT SHOULD BE PROVIDED
UNDER EXTREME WORKLOAD
10418841   14275572  Wed Nov 28 11:23:12 CST 2012   LNX64-11203-CRF CHM SHOULD ALERT FOR BDB
FILESYSTEM CLOSE TO FULL
11675721   14275572  Wed Nov 28 11:23:12 CST 2012   11203-UTL DIAGCOLLECTION.PL SHOULD COLLECT
ACFS-ADVM RELATED LOGS
11772838   14275572  Wed Nov 28 11:23:12 CST 2012   DB AGENT OVERWRITE POLICY ON LOCAL_LISTENER
11836951   14275572  Wed Nov 28 11:23:12 CST 2012   ONLY 32 RLB EVENTS DEQUEUED EVERY 10 SECONDS,
EVEN IF THERE ARE MANY MORE QUEUED
12349553   14275572  Wed Nov 28 11:23:12 CST 2012   VIP ON FORMER PRIMARY NIC CAN NOT BE CLEARD WHEN
GLS NIC FAIL OVER HAPPENS
12398492   14275572  Wed Nov 28 11:23:12 CST 2012   SIHA DOES NOT SET ULIMIT FOR MEMLOCK
12538907   14275572  Wed Nov 28 11:23:12 CST 2012   ORAAGENT KEEPS EXITING AFTER APPLYING PATCH 123478
44
12594616   14275572  Wed Nov 28 11:23:12 CST 2012   AN ERROR OCCUR WHEN CHOOSE ACFS TO STORE THE
DATAFILES DURING DBCA
12639013   14275572  Wed Nov 28 11:23:12 CST 2012   POTENTIAL SPLIT AT STARTUP - LRG PROBLEM ID 556736
1
12650672   14275572  Wed Nov 28 11:23:12 CST 2012   255.255.255.255 BAD VALUE IS RECORDED IN SYSLOG
AND ORAROOTAGENT_ROOTOUT.LOG
12659561   14275572  Wed Nov 28 11:23:12 CST 2012   INSTANCE DOES NOT REGISTER SERVICES WHEN SCAN FAIL
OVERED
12680491   14275572  Wed Nov 28 11:23:12 CST 2012   STOP DEPENDENCY BETWEEN NETWORK AND VIP MUST HAVE
INTERMEDIATE MODIFYER
12709476   14275572  Wed Nov 28 11:23:12 CST 2012   CRSD ORAAGENT MEMORY LEAK AT 1.5M 1.2H ON NON-PE N
ODES
12720728   14275572  Wed Nov 28 11:23:12 CST 2012   GIPCHALOWERPROCESSNODE NO VALID INTERFACES FOUND
TO NODE
12726222   14275572  Wed Nov 28 11:23:12 CST 2012   11203 DB CREATION USING ASM...DISKGROUP ..
RESOURCES ARE NOT RUNNING ON NODES
12728585   14275572  Wed Nov 28 11:23:12 CST 2012   CRSCTL STOP CRS HANGS
12730342   14275572  Wed Nov 28 11:23:12 CST 2012   CAN'T FOUND LOGICAL CORRUPTION OF VOTEDISK ON 11.2
.0.2
12758736   14275572  Wed Nov 28 11:23:12 CST 2012   11203_WIN.X64_110713 INSTALL HANGED WHILE
REGISTERING ORAOLEDB11.DLL
12765467   14275572  Wed Nov 28 11:23:12 CST 2012   W2K3_11203 INCOMPATIBLE PERL CODE IN ROOTCRS.PL
LEADS TO MESSY OUTPUT FOR NT CMD
12771830   14275572  Wed Nov 28 11:23:12 CST 2012   ORA.ASM CRSD RESOURCE CHECK TIMED OUT -REFERENCE B
UG-12754555
12784559   14275572  Wed Nov 28 11:23:12 CST 2012   [11203-WIN64-110713]DURING DECONFIG,THE OUTPUT
'FAILED TO WRITE THE CHECKPOINT'
12791719   14275572  Wed Nov 28 11:23:12 CST 2012   USING LINK-BASED IPMP STANDBY INTERFACE'S IP IS 0.
0.0.0
12794268   14275572  Wed Nov 28 11:23:12 CST 2012   HPI-SG-11203 VIP START UP TIMEOUT WHEN RUN ROOT.SH
12829429   14275572  Wed Nov 28 11:23:12 CST 2012   11203-WIN64 ERR PRKC-1069 FAILED TO GET SUB KEYS
OF {0} WHILE CRS DEINSTALL
12829917   14275572  Wed Nov 28 11:23:12 CST 2012   WARNING DURING ADDNODE SCRIPT INVOCATION
12848480   14275572  Wed Nov 28 11:23:12 CST 2012   a b f DOS WINDOW EXIT WHILE CRS ADD NODE,PRVF-1020
9.
12849377   14275572  Wed Nov 28 11:23:12 CST 2012   11203_INST_WIN [INS-41112]THE INSTALLATION WAS
FAILED BY THE NETWORK CHECKING
12857064   14275572  Wed Nov 28 11:23:12 CST 2012   EXADA-SOL_X64-11203-UD SUNOS 5.11, HAIP STARTUP
FAILED, UPGRADING 11202 TO 11203
12867511   14275572  Wed Nov 28 11:23:12 CST 2012   ALERT IS MISSING WHEN RESOURCE RESTART-FAILOVER FA
ILS
12876314   14275572  Wed Nov 28 11:23:12 CST 2012   HPI-SG-11203 PRVF-5150 ASM DISK PATH CHECK FAILED
IN OUI PRE CHECK
12878750   14275572  Wed Nov 28 11:23:12 CST 2012   AIX-11203-CVU FOUND VALUE REPORTED BY CVU FOR
UNSATISFIED PARAMETER IS NULL
12885323   14275572  Wed Nov 28 11:23:12 CST 2012   NT OCLUMON GET MASTER FAILS TO REACH LOGGER SERVIC
E
12896850   14275572  Wed Nov 28 11:23:12 CST 2012   11203HPI 10203->11203 SIHA + DB UPGRADE, UPGRADE
SIHA ROOTUPGRADE THROW ERR
12897651   14275572  Wed Nov 28 11:23:12 CST 2012   SRGRSC TKPCWRSLG_ASM.DIF - CRS-2545
12897902   14275572  Wed Nov 28 11:23:12 CST 2012   11203_WINX64_110817 MULTICAST COMMUNICATION CHECK
FAILED
12899169   14275572  Wed Nov 28 11:23:12 CST 2012   HPI-SG-11203-UD RUN $CH-BIN-CLUVFY FROM NEW
HOME,ROOTUPGRADE.SH TERMINATE
12914824   14275572  Wed Nov 28 11:23:12 CST 2012   START CLUSTER,CSSD CAN ABORT DUE TO DISKMON
RESOURCE-AGENT TIMING ISSUES
12917897   14275572  Wed Nov 28 11:23:12 CST 2012   CLSSSCEXIT CSSD ABORTING FROM THREAD GMCLIENTLISTE
NER
12925041   14275572  Wed Nov 28 11:23:12 CST 2012   112024GIPSU OLOGGERD CORE DUMP AT 'CRFLOGDB.C
855' DURING START HAS STACK
12934171   14275572  Wed Nov 28 11:23:12 CST 2012   W2K8_11203 CVU VERIFICATION CANNOT PROCEED WITH
[CLUVFY COMP HEALTHCHECK -HTML]
12947871   14275572  Wed Nov 28 11:23:12 CST 2012   11203 WIN.X64 GI CONFIGURATION FAILED DURING
11202->11203 SIHA ASM UPG
12950823   14275572  Wed Nov 28 11:23:12 CST 2012   AIX-11203-HA-CRS SRVCTL STOP NODEAPPS WITH -R
OPTION FAIL TO STOP NETWORK RES
12959140   14275572  Wed Nov 28 11:23:12 CST 2012   VIP'S SOMETIMES DO NOT FAILOVER WHEN PRIVATE
INTERCONNECT GOES DOWN
12965049   14275572  Wed Nov 28 11:23:12 CST 2012   SOL-X64-CRF OLOGGERD WAS REPEATLY DISABLED DUE TO
DEFINED BDB SIZE REACHED
12971251   14275572  Wed Nov 28 11:23:12 CST 2012   11203_WINX64_110907 [INS-40711] CLUSTER NAME IS
BLANK (WHILE CRS UPGRADE)
12975811   14275572  Wed Nov 28 11:23:12 CST 2012   11203-WIN64 INSTALLER FAIED TO PERFORM STATUS
CHECK WHILE UPGRADE 10205 TO 11203
12990582   14275572  Wed Nov 28 11:23:12 CST 2012   AIX-11203-CVU-MSG CONFUSED SYMBOL <> IN CLUVFY
COMP HEALTHCHECK
12995950   14275572  Wed Nov 28 11:23:12 CST 2012   a b f 11107->11203 CVU CHECK NODE CONNECTIVITY FAI
LED
13000491   14275572  Wed Nov 28 11:23:12 CST 2012   RMI SSL PORT EXPOSED ON ORA.OC4J RESOURCE
13001901   14275572  Wed Nov 28 11:23:12 CST 2012   W2K3_11203 GRID INSTALLATION FAILED FOR ORA.ASM
NOT ONLINE
13001955   14275572  Wed Nov 28 11:23:12 CST 2012   11203-WIN64 ASMCA FAILED IN CONFIGURING EXISTING D
ISKGROUP
13002015   14275572  Wed Nov 28 11:23:12 CST 2012   SOL-VC-11203-CVU CSS MISSCOUNT CHECK WRONG WHEN
RUN COMP HEALTHCHECK
13011520   14275572  Wed Nov 28 11:23:12 CST 2012   [11203-SOL64-110916]UPGRADE 10205->11203 CVU POST
CHECK FAILED
13023609   14275572  Wed Nov 28 11:23:12 CST 2012   HPI_11203_CRS-CRSD MEM LEAK AT ABOUT 0.8M-1H ON
PE MASTER
13024624   14275572  Wed Nov 28 11:23:12 CST 2012   W2K8_11203 HIT ERROR [INS-20802] IN THE END OF
GRID INSTALLATION
13036424   14275572  Wed Nov 28 11:23:12 CST 2012   CHMOS HAS AN ERROR IN CALCULATING THE TOTAL
NUMBER OF OPEN FDS ON A SYSTEM
13037709   14275572  Wed Nov 28 11:23:12 CST 2012   INTERMITTENT FREE IP DETERMINATION ISSUE IN SRGSRV
13039908   14275572  Wed Nov 28 11:23:12 CST 2012   AGENT PROCESSES TAKE ABOUT 10 SECONDS TO EXIT AND
RESTART
13058611   14275572  Wed Nov 28 11:23:12 CST 2012   ROOTCRS.PL DECONFIG KEEPDG DOES NOT KEEP
DISKGROUP IN UPGRADED ENVIRONMENT
13066371   14275572  Wed Nov 28 11:23:12 CST 2012   W2K3_11203_UD UPGRADE 11201->11203 FAILED TO
CREATE ORAHOME ON ACFS
13074261   14275572  Wed Nov 28 11:23:12 CST 2012   11203-WIN64 PRKU-1058 FAILED TO RETRIEVE THE LIST
OF SERVICES DURING DEINTAL
13077654   14275572  Wed Nov 28 11:23:12 CST 2012   [11203-AIX-110901.100927]CVU CANNT GET CORRECT
NETWORK PARA FOR ERROR SCRIPT
13079948   14275572  Wed Nov 28 11:23:12 CST 2012   CVU FILES NOT BEING PICKED UP FOR 11.2.0.2.4GIPSU
13082238   14275572  Wed Nov 28 11:23:12 CST 2012   11203-WIN64 FAILED TO START THE CLUSTERWARE STACK
FROM THE LOWER VERSION
13085732   14275572  Wed Nov 28 11:23:12 CST 2012   W2K3_11203_CMP CRFMOND CORE DUMP HAPPENED SOMETIME
S
13090686   14275572  Wed Nov 28 11:23:12 CST 2012   AIX-11203-UD SERVICE FAIL TO FAILOVER AFTER DOWN
PUB NIC(11203 CRS + 10205 RAC)
13111013   14275572  Wed Nov 28 11:23:12 CST 2012   W2K8_11203 KERNEL PANIC FOR NTKRNLMP AFTER RAC
SOFTWARE INSTALLATION
13241779   14275572  Wed Nov 28 11:23:12 CST 2012   COREADM.CONF IS UPDATED IN EXECUTING CRSCTL COMMAN
D
13251796   14275572  Wed Nov 28 11:23:12 CST 2012   LNX64-12.1-EVM ORAAGENT DUMPS CORE IN
INSTCONNECTION DISCONNECT AT CLSNINSTCON
13323698   14275572  Wed Nov 28 11:23:12 CST 2012   CVUOS KERNEL PARAMETER CHECK IN GRID INFRA
INSTALLATION INCORRECT ON EXADATA
13332363   14275572  Wed Nov 28 11:23:12 CST 2012   BUG 9795321 HAS REAPPEARED IN 11.2.0.3
13334158   14275572  Wed Nov 28 11:23:12 CST 2012   REBOOT OF ONE OF THE SWITCH EVICTS INSTANCES
13339443   14275572  Wed Nov 28 11:23:12 CST 2012   ESSC CRS AGENT KILLS ASM INSTANCE DUE TO ORA-15042
13348650   14275572  Wed Nov 28 11:23:12 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.1
(INCLUDES DB PSU 11.2.0.3.1)
13355963   14275572  Wed Nov 28 11:23:12 CST 2012   NT POST-INSTALL, NODE CONNECTIVITY CHECK FAILED
ON CLUSTER NODES
13371153   14275572  Wed Nov 28 11:23:12 CST 2012   SCAN VIPS FAIL PING AFTER RELOCATE EVEN WITH NEW
ARP DRIVER (PATCH 10124639)
13396284   14275572  Wed Nov 28 11:23:12 CST 2012   11.2.0.3 GI PSU 1 HAS-CRS TRACKING BUG
13425727   14275572  Wed Nov 28 11:23:12 CST 2012   ROOTCRS.PL DOES NOT UNLOCK THE 11.2.0.3 CLONED
HOME PROPERLY
13430715   14275572  Wed Nov 28 11:23:12 CST 2012   FUJITSU-GLS-11203 ORAROOTAGENT DOESN'T RECOGNIZE
GLS ON SOLARIS SPARC
13440962   14275572  Wed Nov 28 11:23:12 CST 2012   DIFFERENT SUBNET FAILED TO CONNECT TO VIP AFTER
RESTART VIP
13460353   14275572  Wed Nov 28 11:23:12 CST 2012   REGISTRATION OF 11.2.0.3 DATABASE FAILS AGAINST
12.1 CRS STACK
13483672   14275572  Wed Nov 28 11:23:12 CST 2012   LNX64-12.1-RAC GEN0 HIT ORA-07445 [STRLEN()+16] [S
IGSEGV]
13498267   14275572  Wed Nov 28 11:23:12 CST 2012   AIX-11202-CRS HIGH CPU OVERHEAD OF AN IDLE RAC CLU
STER
13523527   14275572  Wed Nov 28 11:23:12 CST 2012   VIP DOESNT FAILOVER INTO OTHER NODE
13531373   14275572  Wed Nov 28 11:23:12 CST 2012   11.2.0.3.1GIPSU CVU CHECK FAIL FOR NETWORK
PARAMETERS EVEN THEY ARE SATISFIED
13540563   14275572  Wed Nov 28 11:23:12 CST 2012   MERGE REQUEST ON TOP OF 11.2.0.3.1PSU FOR BUGS
13425727 13440962
13550689   14275572  Wed Nov 28 11:23:12 CST 2012   TT12.1VALGRIND MLK MEMORY LEAK IN SCLS_META_CTX_IN
IT
13569812   14275572  Wed Nov 28 11:23:12 CST 2012   11.2.0.3.1GIPSU CVU FAIL TO DETERMINE IF ORACLE
HOME (ON ACFS) IS SHARED
13582411   14275572  Wed Nov 28 11:23:12 CST 2012   RAC ONE NODE SCAN_LISTENER GO OFF LINE AFTER
NETWORK HICCUP PSU4 HAS BEEN APP
13620816   14275572  Wed Nov 28 11:23:12 CST 2012   ROOTUPGRADE.SH BREAKS USER EQUIVALENCE
13652088   14275572  Wed Nov 28 11:23:12 CST 2012   EMGC OUT OF PLACE PATCHING NOT ADJUSTING
INIT.OHASD TO POINT TO NEW GI HOME
13696251   14275572  Wed Nov 28 11:23:12 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.2
(INCLUDES DB PSU 11.2.0.3.2)
13719731   14275572  Wed Nov 28 11:23:12 CST 2012   SCLSIDELADDRS() RETURNS THE WRONG RETURN CODE ON S
UCCESS
13727853   14275572  Wed Nov 28 11:23:12 CST 2012   ORACLE RESTART SIHA- OHAS IS TAKING ABOUT 11
MINUTES TO START
13776758   14275572  Wed Nov 28 11:23:12 CST 2012   GI UPGRADE 11.2.0.1 TO 11.2.0.3 ASMCA FAILED
ROOTUPGRADE.SH LAST ORA-1034
13789135   14275572  Wed Nov 28 11:23:12 CST 2012   OCLUMON REPORTS SWAPFREE 0 , SWAPTOTAL 0 AFTER
CHANGING THE SWAP-DEVICE
13806545   14275572  Wed Nov 28 11:23:12 CST 2012   CLUSTER_NAME NOT POPULATED DURING NON-ROLLING UPGR
ADE
13811209   14275572  Wed Nov 28 11:23:12 CST 2012   LNX64-11203-GIPC ONE OF THE REDUNDANT SWITCH
RESET CAUSE DB INSTANCES EVICTION
13825231   14275572  Wed Nov 28 11:23:12 CST 2012   CLSSNMREADNODEINFO SIGNALS DURING STARTUP
CLUSTERWARE WONT START
13843080   14275572  Wed Nov 28 11:23:12 CST 2012   STBH11.2.0.3 ROOTUPGRADE.SH FOR GI-CRS UPGRADE
TAKES 40-55 MINUTES
13857364   14275572  Wed Nov 28 11:23:12 CST 2012   FIX OF BUG 13791953 DOES NOT WORK
13869978   14275572  Wed Nov 28 11:23:12 CST 2012   W2K8_12.1_CSS KERNEL PANIC FOR CSS ERROR
13919095   14275572  Wed Nov 28 11:23:12 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.3
(INCLUDES DB PSU 11.2.0.3.3)
13924431   14275572  Wed Nov 28 11:23:12 CST 2012   OSYSMOND.BIN PROCESS CAUSES 100percent CPU LOAD
13947200   14275572  Wed Nov 28 11:23:12 CST 2012   DBCA DOES NOT ENABLE THE CONFIGURE DATABASE OPTION
13965075   14275572  Wed Nov 28 11:23:12 CST 2012   CRS AGENT FRAMEWORK INTERMITTENTLY DOES NOT RUN
ACTIONS IN PARALLEL
14082976   14275572  Wed Nov 28 11:23:12 CST 2012   BUG TO COORDINATE CI REGRESSION OF BUG 12709476
14275572   14275572  Wed Nov 28 11:23:12 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.4
(INCLUDES DB PSU 11.2.0.3.4)
3522216    14474780  Wed Nov 28 11:22:20 CST 2012   WRONG PREDICATE DISPLAYING BY UTLXPLS.SQL
8316255    14474780  Wed Nov 28 11:22:20 CST 2012   SPARC T SERIES MACHINES ARE SIZED INCORRECTLY
9095696    14474780  Wed Nov 28 11:22:20 CST 2012   CF ENQUEUE USAGE IN KCRFWL() IMPACTS LGWR PERFORMA
NCE
9163477    14474780  Wed Nov 28 11:22:20 CST 2012   ERROR ORA-39726 WHILE DROPPING COLUMN ON
COMPRESSED PARTITIONED TABLE
9659614    14474780  Wed Nov 28 11:22:20 CST 2012   HUGE ORA-8103 TRACE FILES GENERATED AFTER PATCH
7519406 APPLIED
9703627    14474780  Wed Nov 28 11:22:20 CST 2012   ROOT USE OF ASMCMD PLACES ALERT.LOG IN USER DIRECT
ORY
9706792    14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KCRPDV_NOENT] IN CRASH RECOVERY WITH PARA
LLELISM
9725536    14474780  Wed Nov 28 11:22:20 CST 2012   ORA-7445 IS SEEN WHEN LOADING AN EHCC TABLE WITH
A DOMAIN INDEX
9761357    14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[QKEISEXPRRE...ED1] WHEN QUERYING DUAL
WITH PREDICATE INVOLVING ORA_ROWSN
9782075    14474780  Wed Nov 28 11:22:20 CST 2012   ASMCMD CP COMMAND SHOULD SUPPORT NAMED_PIPE
9847699    14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [17090] MAY BE SEEN WHEN A DISK GOES
OFFLINE DURING RESIZE
9858539    14474780  Wed Nov 28 11:22:20 CST 2012   DATA PUMP IMPORT FAILS TO IMPORT LOGON TRIGGER
DUE TO ORA-04072
9873405    14474780  Wed Nov 28 11:22:20 CST 2012   MV FAST REFRESH FAILS DUE TO INTERNAL ERROR AFTER
UPGRADING FROM 11201 TO 11202
9876287    14474780  Wed Nov 28 11:22:20 CST 2012   SIGNIFICANT PERFORMANCE SLOWDOWN DUE TO WAIT
EVENT PXNSQ;PQLOADINFOQUERY
9906567    14474780  Wed Nov 28 11:22:20 CST 2012   FILE CREATION CAN GET OFFLOADED TO THE EXADATA
CELL WRONGLY WHEN DISKS ARE TAKEN OFFLINE
10133521   14474780  Wed Nov 28 11:22:20 CST 2012   LOGICAL STANDBY APPLY COULD FAIL WITH
ORA-26808/26786 FOR SOME NLS_SORT VALUES
10136532   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT OVER TEMPORARY TABLE IN PARALLEL MAY
RETURN WRONG RESULTS
10214323   14474780  Wed Nov 28 11:22:20 CST 2012   LOB-BASED REPLICATION MV REFRESH USE ROW-BY-ROW PR
OCESSING
10248538   14474780  Wed Nov 28 11:22:20 CST 2012   OPTIMIZER COST MODEL NOT EXADATA-AWARE
10263668   14474780  Wed Nov 28 11:22:20 CST 2012   SELECTING CLOB SOMETIMES FAIL WITH ORA-600 [KOKEGP
INLOB1]
10287724   14474780  Wed Nov 28 11:22:20 CST 2012   STALE FILE DESCRIPTORS USED BY CLIENTS(RDBMS)
CAUSING CELLSRV CRASH WHEN CONSUMED
10297948   14474780  Wed Nov 28 11:22:20 CST 2012   FREQUENT PX MISMATCHES OCCURRING FOR PARTICULAR SQ
L
10332676   14474780  Wed Nov 28 11:22:20 CST 2012   DB KEEPS CRASHING DUE TO STALE PIN
10350832   14474780  Wed Nov 28 11:22:20 CST 2012   DML LOCK STARVATION IS SEEN IN FINISH_REDEF_TABLE
EXECUTION
10387201   14474780  Wed Nov 28 11:22:20 CST 2012   EHCC WITH CELL PASSTHRU CAUSES DOUBLE I/OS
10418524   14474780  Wed Nov 28 11:22:20 CST 2012   ANALYZE TABLE VALIDATE STRUCTURE CASCADE FAST -
SPECIAL CHARACTERS
10625145   14474780  Wed Nov 28 11:22:20 CST 2012   SWITCH_CONSUMER_GROUP_FOR_SESS DOES NOT ALLOW A
SWITCH TO CANCEL_SQL
11063191   14474780  Wed Nov 28 11:22:20 CST 2012   KGL LOCKS MAY LEAK WHEN CURSOR_SHARING WAS SET TO
A NON-DEFAULT VALUE
11071989   14474780  Wed Nov 28 11:22:20 CST 2012   VIEW INVALIDATED WHEN ADDING COLUMNS TO BASE
TABLE WITH FUNCTIONAL INDEX
11708510   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY AGAINST REMOTE PRE-11G DB USING JDBC CLIENT
WITH E2E_CONTEXT NAMESPACE MAY RESULT IN ORA-28267
11715084   14474780  Wed Nov 28 11:22:20 CST 2012   ACTIVE DUPLICATE SHOULD WORK WHEN CONNECTED TO
STANDBY AS SOURCE DB
11837095   14474780  Wed Nov 28 11:22:20 CST 2012   TIME DRIFT DETECTED APPEARS INTERMITTENTLY IN
ALERT LOG, THO' EVENT 10795 SET
11840910   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-3212 IS SEEN WHILE RUNNING THE QUERY WHEN
CONNECTED WITH SYSOPER PRIVILEGE
11841048   14474780  Wed Nov 28 11:22:20 CST 2012   WITH QUERY REWRITE ENABLED, QURIES WITH 'WITH'
CLAUSE MAY FAIL WITH INTERNAL ERROR
11855445   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH CPU UTILIZATION ON ASM LMS0 DUE TO
INEFFICIENT RESOURCE HASHING
11868640   14474780  Wed Nov 28 11:22:20 CST 2012   DB CRASH DUE TO ORA-600 [KJUSCV] OR ORA-600
[KJUCVL;!BUSY] IN PMON
11877623   14474780  Wed Nov 28 11:22:20 CST 2012   RENAMING A TRIGGER AND THEN RENAMING IT BACK TO
THE ORIGINAL NAME MAY CAUSE AN ORA-600 [17273]
11896575   14474780  Wed Nov 28 11:22:20 CST 2012   ORA ERRORS REPORTED WHEN CREATING OBJECTS WITH
SAME NAME AS EXISTING PUBLIC SYNONYMS
12312133   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN INCREMENTAL BACKUP WITH BLOCK CHANGE
TRACKING MAY CAUSE STANDBY DB CRASH
12325243   14474780  Wed Nov 28 11:22:20 CST 2012   SLOW PERFORMANCE ON EXPDP FUNCTIONAL AND BITMAP IN
DEXES
12325317   14474780  Wed Nov 28 11:22:20 CST 2012   ALTER TABLE MOVE SUBPARTITION MAY FAIL FOR
INTERVAL PARTITIONED TABLES
12326708   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULTS (WRONG TRANSACTION) WITH
MATERIALIZED TABLE FUNCTION
12328803   14474780  Wed Nov 28 11:22:20 CST 2012   BLOCKER FOR WAIT EVENT 'GC CURRENT REQUEST' NOT ID
ENTIFIED
12353494   14474780  Wed Nov 28 11:22:20 CST 2012   EXCESSIVE TRACE WRITTEN FOR LOG_ARCHIVE_TRACE=1
IN RFS TRACE FILE
12358083   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[KKQSFCS-1] DURING REWRITE OF QRY WITH
FUNCTIONAL INDEX'S VIRTUAL COLUMN
12387467   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE COULD CRASH WHEN SMART SCAN WAS
INTERRUPTED WHILE TABLESPACE IS BEING SHRUNK
12391034   14474780  Wed Nov 28 11:22:20 CST 2012   COREDUMP IS SEEN DURING RMAN BACKUP TO NFS MOUNT
12401111   14474780  Wed Nov 28 11:22:20 CST 2012   ERROR ORA-00600 [KDLIXFMCHECK] MAY BE SEEN JUST
AFTER ORA-1551 WAS THROWN
12425262   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-00600 [5400] REPORTED FOR PARALLEL INSERT ON
GLOBAL TEMP TABLES
12535346   14474780  Wed Nov 28 11:22:20 CST 2012   DML ON TABLE W/ RI AND INTERVAL PARTITIONED
PARENT TABLE MAY FAIL WITH SIGSEGV
12536287   14474780  Wed Nov 28 11:22:20 CST 2012   ODCITABLECLOSE CALLOUTS ARE NOT INVOKED IN PQ MODE
12539239   14474780  Wed Nov 28 11:22:20 CST 2012   SIGSEGV IN QSMQ_GET_SUMM_MFLAG WHILE DOING MV REFR
ESH
12556843   14474780  Wed Nov 28 11:22:20 CST 2012   IN MULTIBYTE DB, SQL PARSER SOMETIMES INCORRECTLY
REPORTS ORA-600 [QCPL.*] ERROR
12564614   14474780  Wed Nov 28 11:22:20 CST 2012   XDMG CANCELS DISK DROP WHEN CELLSRV TELLS ASM TO
REDISCOVER DISK
12582664   14474780  Wed Nov 28 11:22:20 CST 2012   DEDUPLICATION WITH SECUREFILES NOT WORKING AS EXPE
CTED
12583611   14474780  Wed Nov 28 11:22:20 CST 2012   EXCESSIVE ENQ;TX CONTENTION WITH HEAVY SECUREFILE
INSERT WORKLOAD ON RAC
12585543   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN BACKUP PERFORMANCE DROPS SIGNIFICANTLY AFTER
UPGRADE TO 11.2
12588744   14474780  Wed Nov 28 11:22:20 CST 2012   SECUREFILE WASTES STORAGE WHEN SPECIFY INITIAL EXT
ENT
12591252   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 WAS POSSIBLE DURING OPTIMIZATION OF
QUERIES USING ORDER BY WHILE REMOVING SORT USING
INDEX ACCESS
12591399   14474780  Wed Nov 28 11:22:20 CST 2012   PARTITION PRUNING FOR JOINS BETWEEN LOCAL
PARTITIONED TABLES AND REMOTE TABLES MAY FAIL
WITH INTERNAL ERRORS
12594032   14474780  Wed Nov 28 11:22:20 CST 2012   POSSIBLE MEMORY CORRUPTION WHEN USING CDC
EXTEND_WINDOW OR EXTEND_WINDOW_LIST
12596444   14474780  Wed Nov 28 11:22:20 CST 2012   CURSOR NOT SHARED WHEN CURSOR_SHARING=FORCE AND
SQL WITH CASE EXPRESSION
12612118   14474780  Wed Nov 28 11:22:20 CST 2012   CREATION OF MVIEW FOR A QUERY INVOLVING 'WITH',
'UNION ALL', 'ANSI JOIN' MIGHT DUMP CORE
12614359   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KSSDEL; BAD LIVE] MAY BE SEEN WHILE
INSERTING INTO SECUREFILE VIA JDBC
12617123   14474780  Wed Nov 28 11:22:20 CST 2012   SPLIT SUBPARTITION ON TABLE W/ CHILD
REFERENCE-PARTITIONED TABLE FAIL WITH ORA-1
12618817   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULTS WITH ABSOLUTE PARTITION-WISE JOIN
12620823   14474780  Wed Nov 28 11:22:20 CST 2012   SOL-SP64-11203;ASM INSTANCE HANG DURING CRS STACK
STARTING ON THE SECOND NODE
12621588   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-7445 [KOKSOPNHASOBJWTEMPLOB2()+39] WITH QUERY
CONTAINING LOTS OF ANSI JOINS
12625563   14474780  Wed Nov 28 11:22:20 CST 2012   STANDBY DB FAILS TO ADD DATAFILE WITH SYMBOLIC LIN
KS
12627504   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT WHERE THERE IS A JOIN BETWEEN TWO
REFERENCE PARTITIONED TABLES MAY CAUSE INTERNAL ER
ROR
12628286   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[15800] IS SEEN DUE TO INCORRECT
COMPUTATION OF KXFQR FOR PARTIION KEY
DISTRIBUTION TABLE QUEUE.
12637294   14474780  Wed Nov 28 11:22:20 CST 2012   BLOOM PARTITION PRUNING MAY CAUSE DEADLOCK ORA-60
12641849   14474780  Wed Nov 28 11:22:20 CST 2012   CUSTOMER MIGHT RECEIVE AN INTERNAL ERROR IF
CHANNEL CLEANUP FAILS AFTER ANOTHER ERROR IS SIGNA
LLED.
12646784   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KKPOFFOC] MAY BE SEEN WHILE ADDING A
COLUMN TO A TABLE WITH LOB COLUMN
12655301   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [13013] FROM MERGE WITH ADD COL OPTIMIZATI
ON
12656535   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1555 DURING DIRECT PATH READ OF SECUREFILE LOB
12658411   14474780  Wed Nov 28 11:22:20 CST 2012   SETTING RESULT CACHE TO A VALUE HIGHER THAN 1G
COULD LEAD TO INSTANCE HANG
12662040   14474780  Wed Nov 28 11:22:20 CST 2012   SECUREFILE LOB SEGMENT KEEPS GROWING IN CASE OF
PLENTY OF FREE SPACE
12672969   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY INVOLVING ORDER-BY CLAUSE DUMPS CORE IF
ORDER-BY ELIMINATION IS ENABLED
12675009   14474780  Wed Nov 28 11:22:20 CST 2012   INPUT_BYTES AND OUTPUT_BYTES COLUMN NOT ACCURATE
IN V$RMAN_BACKUP_JOB_DETAILS VIEW
12678920   14474780  Wed Nov 28 11:22:20 CST 2012   CONCURRENT SPLIT/MERGE,DROP PARTITION OPERATIONS
ON TABLE MAY FAIL WITH SIGSEGV
12685263   14474780  Wed Nov 28 11:22:20 CST 2012   NEED TO ASSERT WHEN ASM DETECTS IO BUFFER HARD
CHECK FAILURE
12693573   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH CPU W/ SPARSE IVAL PARTITIONS AND PART RANGE
ALL
12693626   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH CPU USAGE BY QUERY ON PARTITIONING KEY WITH
INTERVAL PARTITIONING
12698747   14474780  Wed Nov 28 11:22:20 CST 2012   ASM MAY HANG OR LEAKS MEMORY DUE TO MOP'S LEAK
12709059   14474780  Wed Nov 28 11:22:20 CST 2012   FIXES INTERNAL ERROR [KCBIVBR_2]
12714023   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULT OCCURS WHEN DYNAMIC SAMPLING IS DONE
12717125   14474780  Wed Nov 28 11:22:20 CST 2012   REBALANCE IS POKING EXTENT HOLES IN OFFLINE DISKS
EVEN WHEN DATA IS NOT MOVING
12718090   14474780  Wed Nov 28 11:22:20 CST 2012   LNX64-11203-RAC;DB FG RROC HIT ORA-00600[KCLCHKBLK
_3]
12723359   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY INVOLVING SUBQUERY WITH HAVING CLAUSE AND
AGGREGATES MAY LEAD TO CORE DUMP
12731940   14474780  Wed Nov 28 11:22:20 CST 2012   ANALYZE COMMAND ON TABLE WITH 'ADD COLUMN
OPTIMIZATION ENABLED' COLUMNS MAY FAIL
12734325   14474780  Wed Nov 28 11:22:20 CST 2012   PERFORMANCE ISSUE WHEN USING TIMESTAMP_TO_SCN
12748240   14474780  Wed Nov 28 11:22:20 CST 2012   Fix for Bug 12748240
12748538   14474780  Wed Nov 28 11:22:20 CST 2012   ONLINING DISKS IN ONE 11GR2 ASM DISK GROUP ABORTS
10GR2 DBS USING OTHER ASM DISK
12748795   14474780  Wed Nov 28 11:22:20 CST 2012   PARALLEL QUERY FAILS WITH ORA-600 [KKFDJOI;KKFDNPA
RT_DIM1]
12749597   14474780  Wed Nov 28 11:22:20 CST 2012   SAME TYPE IN TARGET SCHEMA GENERATES DIFFERENT
HASHCODE FROM SOURCE SCHEMA
12757532   14474780  Wed Nov 28 11:22:20 CST 2012   LOG FILE PARALLEL WRITE TAKES 300 SECONDS AFTER
SINGLE CELLSRV PROCESS DIES
12764337   14474780  Wed Nov 28 11:22:20 CST 2012   KGL ROUTINE HAS BEEN HITTING SIGSEGV WHILE
FETCHING AN OBJECT
12764658   14474780  Wed Nov 28 11:22:20 CST 2012   DBMS_STATS.GATHER_TABLE_STATS GATHERS INCORRECT
STATS FOR PARTITIONED TABLE
12766987   14474780  Wed Nov 28 11:22:20 CST 2012   INTERNAL TEST CONFIGURATION SUPPORT FOR EXADATA
12771704   14474780  Wed Nov 28 11:22:20 CST 2012   DISKMON SM QUERY DOES NOT WORK ON SOLARIS DB NODES
12772404   14474780  Wed Nov 28 11:22:20 CST 2012   SIGNIFICANT ROW CACHE OBJECTS LATCH CONTENTION
WHEN USING VPD
12778873   14474780  Wed Nov 28 11:22:20 CST 2012   COREDUMP IS SEEN IN KCLXPH WHILE QUERYING GV$POLIC
Y_HISTORY
12780098   14474780  Wed Nov 28 11:22:20 CST 2012   Fix for Bug 12780098
12780983   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-955 IS BEING HIT WHEN TRYING TO CREATE THE
INTERNALLY-GENERATED TYPE
12793917   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN CHANNEL IS TERMINATED WHILE SETTING UP BACKUP
12794025   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-12899 WHEN EXECUTING
DBMS_STATS.SET_TABLE_STATS WITH MULTI-BYTE OBJECT
NAME
12794305   14474780  Wed Nov 28 11:22:20 CST 2012   REDO SHIPMENT COULD FAIL AT THE STANDBY WITH ORA-6
00;[KRSR_PIC_COMPLETE.8]
12797420   14474780  Wed Nov 28 11:22:20 CST 2012   KGLHDGH CONTENTION ON THE DB INSTANCE HANDLE WHEN
CURSOR_SHARING IS SET TO FORCE
12797765   14474780  Wed Nov 28 11:22:20 CST 2012   SOL_SP64; AFTER ALL DISKS FAILURE, DG CAN'T BE
DISMOUNTED ON T2000-3
12829021   14474780  Wed Nov 28 11:22:20 CST 2012   COMMIT TO SWITCHOVER COULD FAIL WHEN USING THE
DATABASE FTP, HTTP OR NFS SERVERS
12831782   14474780  Wed Nov 28 11:22:20 CST 2012   ASYNC TRANSPORT PROCESS FAILS TO READ SECONDARY
MIRROR LOGFILE
12833442   14474780  Wed Nov 28 11:22:20 CST 2012   GATHERING CONCURRENT STATISTICS ON A TABLE WITH
SUB PARTITIONS IS VERY SLOW
12834027   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-00600 [KJBMPRLST;SHADOW] & [KJBRASR;PKEY] IN
A READ MOSTLY & SKIP LOCK ENV
12837280   14474780  Wed Nov 28 11:22:20 CST 2012   SHARED CURSOR MEMORY WAS LEAKING IN COMPLETE
REFRESH PROCESS
12842402   14474780  Wed Nov 28 11:22:20 CST 2012   APPLICATIONS CAN HANG ON DFS LOCK HANDLE WHEN
ACCESSING THE SAME ORDERED SEQUENCE OBJECT FROM 2
NODES IN THE CLUSTER.
12845115   14474780  Wed Nov 28 11:22:20 CST 2012   SELF DEADLOCKS ARE SEEN WHILE DROPPING MV
CONTAINER TABLE WITH SPECIAL INDEXES
12847466   14474780  Wed Nov 28 11:22:20 CST 2012   AROLTP-C; HANG SIGNATURE; 'GC CURRENT
REQUEST'<='GC BUFFER BUSY ACQUIRE'
12849688   14474780  Wed Nov 28 11:22:20 CST 2012   EXPORTING AND IMPORTING MAY CAUSE 'NEW VALUES'
CLAUSE WRONG
12861463   14474780  Wed Nov 28 11:22:20 CST 2012   RAC PERF; DEFAULT VALUE FOR
_LM_SINGLE_INST_AFFINITY_LOCK SHOULD BE FALSE
12865902   14474780  Wed Nov 28 11:22:20 CST 2012   NOWAIT LOCK REQUESTS COULD HANG
12866794   14474780  Wed Nov 28 11:22:20 CST 2012   EHCC DOES NOT SUPPORT INDEX MAINTENANCE ON DOMAIN
INDEXES FOR OCIDIRPATH
12873183   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY WITH ROWNUM IN SELECT LIST AND IN STOP
PREDICATE MAY RETURN WRONG RESULTS
12876939   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[15570] WAS POSSIBLE DURING PARALLEL
EXECUTION OF QUERIES WITH UNION ALL PUSHED
PREDICATE VIEWS ON THE RHS OF NL JOINS
12879027   14474780  Wed Nov 28 11:22:20 CST 2012   LMON PROCESS CAN GET STUCK IN THE DRM QUIESCE
STEP TRIGGERING PSEUDO RECONFIGURATION
12880299   14474780  Wed Nov 28 11:22:20 CST 2012   RAC TCP HANDLERS BLOCK IF LISTENER REGISTRATION
IS RESTRICTED TO IPC W/COST
12889054   14474780  Wed Nov 28 11:22:20 CST 2012   SNAPSHOT HANGS ON DC_OBJECTS ROW_CACHE_LOCK HELD
BY CTAS JOB
12894807   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT FOR UPDATE OVER A DB LINK ON ACTIVE
DATAGUARD STANDBY RAISES ORA-16000
12898733   14474780  Wed Nov 28 11:22:20 CST 2012   CONTROLFILE NOT CACHED IN FLASH CACHE LEADING TO
SLOW IO
12899094   14474780  Wed Nov 28 11:22:20 CST 2012   SMART SCAN WHEN EXECUTED IN SERIAL MODE MAY HAVE
A TAIL-OFF EFFECT IN SOME CASES
12899768   14474780  Wed Nov 28 11:22:20 CST 2012   PROCESSED MESSAGES REMAIN IN QUEUE CAUSING SPACE I
SSUES
12900077   14474780  Wed Nov 28 11:22:20 CST 2012   INCREASING VERSIONS COUNTS WITH BASELINE WHEN
_OPTIM_PEEK_USER_BINDS' = TRUE
12900964   14474780  Wed Nov 28 11:22:20 CST 2012   PERFORMANCE IMPROVEMENT FOR SERIAL SMART SCAN
12904429   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN DELETE ARCHIVELOG COMMAND TAKES LONG TIME
12905058   14474780  Wed Nov 28 11:22:20 CST 2012   REBOOT 2 CELL NODES, CHECKFILE FOUND CORRUPTION
BLOCK IN 3 UNDO DATAFILES
12910565   14474780  Wed Nov 28 11:22:20 CST 2012   SPAWNING MORE EMON SLAVES PROCESSES CAUSES DB
HANG ON SHUTDOWN
12912297   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [25026] WHEN INSERT INTO TEMPORARY TABLE
12913474   14474780  Wed Nov 28 11:22:20 CST 2012   DISABLED INVALID TABLE TRIGGER CAN STILL BLOCK DML
12917230   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY WITH TEMP TABLE TRANSFORMATION RUNS 5X
SLOWER WAITING FOR REMASTERING
12918738   14474780  Wed Nov 28 11:22:20 CST 2012   34708; DROPPING TABLE OF SECUREFILE LOB (CACHE)
IS VERY SLOW
12919564   14474780  Wed Nov 28 11:22:20 CST 2012   ENCOUNTERED ORA-600 [KTBESC_PLUGGED] WHILE
RUNNING APPS RTS
12922105   14474780  Wed Nov 28 11:22:20 CST 2012   PREVENT DISKMON CRASH DURING RAC SHUTDOWN
12923168   14474780  Wed Nov 28 11:22:20 CST 2012   CANNOT USE QUOTED FUNCTION NAME FOR VPD POLICY FUN
CTION
12924835   14474780  Wed Nov 28 11:22:20 CST 2012   KCFIS SHOULD RETURN CONTIGUOUS CORRUPT BLOCKS FOR
RMAN
12925089   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-4031 DURING PROCESS STARTUP SOME TIMES
ASSERTS WITH 'KSXP_RM_CHECK0'
12929644   14474780  Wed Nov 28 11:22:20 CST 2012   KCFIS TRANSLATIONS SHOULD BE MULTIPLE OF RDBMS
BLOCK SIZE
12938841   14474780  Wed Nov 28 11:22:20 CST 2012   11203_ASM_SOL_SP64;RACE BETWEEN ADD DISK AND
DISMOUNT MAY CAUSE KFGUSENUM01
12939232   14474780  Wed Nov 28 11:22:20 CST 2012   DUMPING HEADER OF TEMP FILES IN MOUNT MODE COULD
RAISE ORA-1157 AND ORA-1110
12944766   14474780  Wed Nov 28 11:22:20 CST 2012   DBFS PERFORMANCE ON EXTERNAL TABLES LOADING IS
VERY SLOW
12950644   14474780  Wed Nov 28 11:22:20 CST 2012   ASM INSTANCE CRASHES WITH ORA-07445
(KFDGLOBALOPEN) MESSAGE IN THE ASM ALERT.LOG
12950694   14474780  Wed Nov 28 11:22:20 CST 2012   UTL_RECOMP FOR SPECIFIC DATABASE EDITION
12953092   14474780  Wed Nov 28 11:22:20 CST 2012   INCORRECT RESULTS FOR QUERIES INVOLVING BLOOM
PRUNING AND CHAR COLUMNS
12959852   14474780  Wed Nov 28 11:22:20 CST 2012   INTERNAL ERROR RAISED IN BUFFER CACHE WHEN
PROCESSING A NESTED PING
12960279   14474780  Wed Nov 28 11:22:20 CST 2012   CORE DUMP IS SEEN IN STREAMS APPLY COODINATOR AS
TRANSACTION IS NOT IN THE UNASSIGNED TRANSACTION L
IST
12960455   14474780  Wed Nov 28 11:22:20 CST 2012   DB INSTANCE ABORT DUE TO ORA-600[KFFMXPGET]
12960925   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-932 ON OCISTMTEXECUTE AFTER ONLINE
REDEFINITION OF LONG TO CLOB COLUMN
12966665   14474780  Wed Nov 28 11:22:20 CST 2012   QUERIES WITH LOT OF JOINS MAY FAIL WITH INTERNAL
ERROR WHEN EVALUATION POSSIBILITY OF FULL
PARTITION WISE JOINS
12971388   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN BACKUP DOESN'T EMIT UNSTABLE WRITES VIA DNFS
12971775   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-0600 WHILE RUNNING PARALLEL DML WHILE ONLINE
INDEX IS CREATING
12974145   14474780  Wed Nov 28 11:22:20 CST 2012   CRASH IN THE EXTPROC PROCESS MAY BE SEEN WHEN
EXECUTING C CALLOUTS THAT RETURN OCINUMBER
12974860   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[QKEISEXPRREFERENCED1] SEEN WHEN
PROJECTION PUSHDOWN ENABLED ON MERGEJOIN
12976376   14474780  Wed Nov 28 11:22:20 CST 2012   MEMORY LEAK IN SHARED CURSOR LAYER; 'KKSFBC;HASH1'
12978794   14474780  Wed Nov 28 11:22:20 CST 2012   DBMS_FILE_TRANSFER FAILS THE HARD CHECKS TEST
WHEN THE SOURCE FILE CANNOT BE HARD-CHECKED AT
THE TARGET
12979199   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1466 WHEN A GLOBAL TEMPORARY TABLE IS QUERIED
FROM READ ONLY TXN
12983611   14474780  Wed Nov 28 11:22:20 CST 2012   UNDER RARE CIRCUMSTANCES ASYNC PROCESS CAN READ
THE LOG ENTRY WHILE LGWR IS MODIFYING IT.
12998795   14474780  Wed Nov 28 11:22:20 CST 2012   AROLTP-C; HANG SIGNATURE; 'GC CURRENT
REQUEST'<='GC BUFFER BUSY ACQUIRE'
13000553   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN BACKUP FAILS WITH RMAN-20999 ERROR AT
STANDBY DATABASE
13001379   14474780  Wed Nov 28 11:22:20 CST 2012   DATAPUMP TRANSPORT_TABLESPACES PRODUCES WRONG
METADATA FOR SOME TABLES
13004894   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY RETURNS WRONG RESULTS WITH A HASH JOIN IN
THE PLAN AND 10046 ENABLED
13022416   14474780  Wed Nov 28 11:22:20 CST 2012   PERFORMANCE IMPACT IN PASSTHRU MODE FOR SMART
SCAN ON EHCC TABLES
13023541   14474780  Wed Nov 28 11:22:20 CST 2012   INTERMITTENT CORE DUMP IN KNTXSLT FOR QUERIES ON
TABLE WITH MV LOG
13032258   14474780  Wed Nov 28 11:22:20 CST 2012   SMART SCAN MAY RESULT IN ORA-27618 EXTERNAL ERROR
WHEN THERE ARE LARGE NUMBER OF CONCURRENT SESSIONS
13035360   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-2303 WHEN TRYING TO CREATE A TYPE IN A CHILD
EDITION DUE TO PARENT EDITION DEPENDENCY
13035804   14474780  Wed Nov 28 11:22:20 CST 2012   CHANGE NONDESCRIPTIVE NUMBERS WHICH GIVE THE
REASON FOR PSEUDO RECONFIGURATION TO READABLE STRI
NGS
13036331   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1031 MAY BE SEEN WHILE GRANTING PRIVILEGES TO
A USER BY ANOTHER USER MULTIPLE TIMES
13040331   14474780  Wed Nov 28 11:22:20 CST 2012   MESSAGES NOT PROCESSED BY AQ TIME MANAGER
13041324   14474780  Wed Nov 28 11:22:20 CST 2012   HCC ON ZFS AND PILLAR STORAGE
13054713   14474780  Wed Nov 28 11:22:20 CST 2012   VERSION_COUNT OF KEPT STATEMENTS HAVING BINDS INCR
EASING
13059165   14474780  Wed Nov 28 11:22:20 CST 2012   EXEC OF UTLRP.SQL MAY RETURN INCORRECT COUNT FOR
'OBJECTS WITH ERRORS' RESULT
13063120   14474780  Wed Nov 28 11:22:20 CST 2012   INSERTS CAUSING HIGH DB FILE SEQUENTIAL READS
13070939   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY WITH SET OPERATION WITH A BIND VARIABLE IN
THE SELECT LIST RAISES ORA-1790 DURING DESCRIBE
ONLY EXECUTION
13079417   14474780  Wed Nov 28 11:22:20 CST 2012   EXTERNAL TABLE PREPROCESSOR SUPPORT FOR DATAPUMP
DUMP FILES
13080778   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-00942 RETURNED IN SQL ON MULTIPLE SCHEMAS DATA
BASE
13098318   14474780  Wed Nov 28 11:22:20 CST 2012   CTRL-C OR A SESSION KILL DURING DML INVOLVING
TEMP BLOCKS LEADS TO ORA-600[6856]
13099577   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1460 ERROR MAY BE SEEN IN PARALLEL QUERY
SERVERS DUE TO CURSOR SHARING ISSUE
13103913   14474780  Wed Nov 28 11:22:20 CST 2012   INSERT INTO A TABLE WITH AN UNUSABLE INDEX W/O
ANY SEGMENTS AND REBUILDING THE UNUSABLE INDEX
ONLINE IN PARALLEL RAISES INTERNAL ERROR.
13117043   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [13009] WAS RAISED FOR SELECT FOR UPDATE
INVOLVING HIERARCHIC QUERIES
13146182   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KDSGRP1] ERROR WHEN QUERYING A TABLE
WITH BITMAP INDEXES
13146719   14474780  Wed Nov 28 11:22:20 CST 2012   EVENT 10995 NEEDS TO BE SET ALWAYS IF MV DEFINING
QUERY LENGTH > 64K
13242070   14474780  Wed Nov 28 11:22:20 CST 2012   IMBALANCE IN NORMAL REDUNDANCY DISKGROUP WHILE
3RD QUORAM DISK IS IN SAME DG
13250244   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-4031 ERRORS SEEN WHEN PARAMETER
_KGHDSIDX_COUNT IS SET TO >1 DUE TO MEM LEAK
13253549   14474780  Wed Nov 28 11:22:20 CST 2012   FILE ALLOCATION FROM ONE ASM INSTANCE IS VERY SLOW
13256841   14474780  Wed Nov 28 11:22:20 CST 2012   COST BASED STAR TRANSFORMATION OF A QUERY WITH
DIMENSION TABLE COULD DUMP CORE
13257247   14474780  Wed Nov 28 11:22:20 CST 2012   AWR SNAPSHOTS COULD TAKE A LONG TIME, DUE TO AN
INSERT INTO WRH$_TEMPSTATXS USING A PROBLEMATIC PL
AN
13259364   14474780  Wed Nov 28 11:22:20 CST 2012   IN CASE OF LONG-LOB NULL SCENARIO FETCHING NULL
DATA MIGHT RAISE AN ERROR
13326736   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-959 RENAMING A TABLESPACE TO ALREADY DROPPED
TABLESPACE NAME
13328193   14474780  Wed Nov 28 11:22:20 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO THE INTEGRATED
EXTRACT COMPONENT OF ORACLE GOLDENGATE
13329145   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[KXFRGRADISTNUM3] ERROR MAY BE SEEN DUE TO
WRONG DECISION ON PARTITION LEVEL(DIMENSION) FOR
SLAVE MAPPING FOR PQ SLAVES
13332439   14474780  Wed Nov 28 11:22:20 CST 2012   UTL_RECOMP.RECOMP_PARALLEL CAN DEADLOCK IN AN
EDITIONED ENVIRONMENT
13338048   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1476 OCCURRED WHILE OUTPUTTING THE AWR REPORT
FOR STREAMS-RELATED SECTIONS
13340388   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KZAXPOPR14...] WHILE READING XML AUDIT
FILES WITH XML EXTENDED AUDITING
13340960   14474780  Wed Nov 28 11:22:20 CST 2012   MOUONT_DBFS.SH -FOUND POTENTIAL ERROR OR TIMEOUT
WHILE CHECKING STATUS
13343438   14474780  Wed Nov 28 11:22:20 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.1
13344323   14474780  Wed Nov 28 11:22:20 CST 2012   BUFFER BUSY WAIT TIMEOUT IN HIGH CONTENTION WORKLO
ADS
13345786   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[KJBMPCLO;CVT] SEEN WHEN CLOSING CLIENT
LOCK WITH NONZERO PISCN AT MASTER
13350245   14474780  Wed Nov 28 11:22:20 CST 2012   FALSE SCN CORRUPTIONS REPORTED FOR V7 BLOCKS IN 11
G
13352237   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KJCVG04] MAY BE SEEN DUE TO ENQUEUE LEAK
FOR ABORTED CHECKPOINTS
13354082   14474780  Wed Nov 28 11:22:20 CST 2012   REPLICATION FAIL TO RESUME AFTER ASM INST RESTART
ON STANDBY
13355095   14474780  Wed Nov 28 11:22:20 CST 2012   CONVENTIONAL INSERT IN PARALLEL INTO PARTITIONED
TABLE COULD CORRUPT LOCAL INDEX
13358531   14474780  Wed Nov 28 11:22:20 CST 2012   SLOWER PERFORMANCE ON MMON SLAVES ACQUIRING THE
THRESHOLD ENQUEUE
13358781   14474780  Wed Nov 28 11:22:20 CST 2012   THE FIELD DBA_HIST_SQLSTAT.CCWAIT_DELTA WAS
ALWAYS ZERO FROM 11.2 ONWARDS
13362079   14474780  Wed Nov 28 11:22:20 CST 2012   HCC SHOULD NOT BE ENABLED FOR NON ZFS/ PILLAR
STORAGE ARRAY
13364795   14474780  Wed Nov 28 11:22:20 CST 2012   TABLE SCAN ON EXADATA COULD FAIL TO LOOK FOR A
GOOD BLOCK FROM THE PHYSICAL STANDBY AFTER
FINDING A CORRUPT BLOCK
13366202   14474780  Wed Nov 28 11:22:20 CST 2012   DBNEWID DOESN'T ALLOW TARGET=/
13370330   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600[QKEISEXPRREFERENCED1] FROM QUERY W/
VIRTUAL COLUMN WITH A CONSTANT VALUE
13377816   14474780  Wed Nov 28 11:22:20 CST 2012   DON'T SEND IN DIA0 IF SOCKET CLOSED - HANDLE
FAILURE APPROPRIATELY
13384182   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [DELROW;IOT1] RAISED FOR DELETE OR
MERGE..DELETE SQL
13384397   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULT WITH STAR_TRANSFORMATION_ENABLED = TR
UE
13385346   14474780  Wed Nov 28 11:22:20 CST 2012   GCR0 TRACE FILES CONTINUOUSLY CREATED WITH
KJGCR_DELETESO MESSAGES
13388104   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1733 ERRORS WERE POSSIBLE DURING SELECT FOR
UPDATE OF CLOB COLUMNS FROM NESTED VIEWS
13395403   14474780  Wed Nov 28 11:22:20 CST 2012   LATCH 'ENQUEUE HASH CHAINS' CONTENTION ON
SECUREFILE BLOB
13397104   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE CRASH WITH ORA-600 [KJBLPKEYDRMQSCCHK;PKE
Y]
13397256   14474780  Wed Nov 28 11:22:20 CST 2012   ASM AND DISKMON MASTER HUNG AFTER A CELL WAS REBOO
TED
13399435   14474780  Wed Nov 28 11:22:20 CST 2012   KJFCDRMRCFG WAITED 249 SECS FOR LMD TO RECEIVE
ALL FTDONES, REQUESTING KILL
13419660   14474780  Wed Nov 28 11:22:20 CST 2012   UNSHARED DATAPUMP SESSION STATE THROUGH
DBMS_REDEFINITION CALLS CAUSE MEMORY LEAK
13419747   14474780  Wed Nov 28 11:22:20 CST 2012   GATHER STATS SESSION HUNG WITH WAIT EVENT 'ENQ;
KO FAST OBJECT CHECKPOINT'
13420224   14474780  Wed Nov 28 11:22:20 CST 2012   I/O ERROR DURING INSTANCE RECOVERY WHEN ONE OF
THE MIRRORS BECOMES UNAVAILABLE
13421009   14474780  Wed Nov 28 11:22:20 CST 2012   DBMS_CACHEUTIL STILL WON'T WORK WHEN
_GC_POLICY_TIME IS SET TO 0
13422949   14474780  Wed Nov 28 11:22:20 CST 2012   SELECTING COLUMNS WHICH WERE ADDED AFTER THE
TABLE WAS CREATED COULD DUMP CORE
13426605   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KGMGCHD1] SEEN IN RAC ENVIRONMENT
13429678   14474780  Wed Nov 28 11:22:20 CST 2012   UNDER RARE CIRCUMSTANCES PARALLEL OPERATIONS ON
OLTP COMPRESSED TABLES MAY CAUSE INTERNAL ERROR
13430938   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-4031 ERRORS WITH HIGH 'KTC LATCH SUBH' MEMORY
USAGE
13440068   14474780  Wed Nov 28 11:22:20 CST 2012   MEMORY LEAK OBSERVED IN DSKM_PROCESS_CMDLINE
13440516   14474780  Wed Nov 28 11:22:20 CST 2012   SKIP SCAN CAN NOT BE INTERRUPTED BY SHUTDOWN/CTRL-
C
13448206   14474780  Wed Nov 28 11:22:20 CST 2012   TOO MANY OCCURRENCES OF NOTE; ATTEMPTING VOTING
FILE REFRESH ON DISKGROUP
13454210   14474780  Wed Nov 28 11:22:20 CST 2012   UNRELEASED BUILD LOCK IN SOME ERROR CASES MAY
CAUSE HANG
13457537   14474780  Wed Nov 28 11:22:20 CST 2012   SPORADIC WRONG VALUES FROM SELECTS ON GV$ OBJECTS
ON RAC
13457582   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE CRASH DUE TO INTERNAL ERROR ORA-600
[KCLANTILOCK_8] IN LMS
13464002   14474780  Wed Nov 28 11:22:20 CST 2012   PREFETCH INVOLVING TEMP OBJECTS MAY CAUSE
INTERNAL ERROR
13466801   14474780  Wed Nov 28 11:22:20 CST 2012   CPUJAN2012 DATABASE 11.2.0.3
13467683   14474780  Wed Nov 28 11:22:20 CST 2012   JOIN OF TEMP AND PERMANENT TABLES IN RAC MIGHT
CAUSE CORRUPTION ON PERMANENT TABLES
13470240   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-7445 [QKSBGPARSELIST()] MAY BE SEEN DURING
DDL OPERATION
13471777   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-00600[4400] COULD OCCUR IN A TRANSACTION
USING MULTIPLE DATABASE LINKS
13476583   14474780  Wed Nov 28 11:22:20 CST 2012   DROPPING OF A DISK CAN CAUSE DISMOUNT OF
DISKGROUP IN OTHER ASM INSTANCES.
13477790   14474780  Wed Nov 28 11:22:20 CST 2012   QUERIES INVLOVING XMLFOREST OR XMLELEMENT SOME
TIMES DUMP CORE IN MEMORY RELATED FUNCTIONS
13478060   14474780  Wed Nov 28 11:22:20 CST 2012   BACKING UP CONTROL FILE CONCURRENTLY ON TWO
INSTANCES OF RAC GENERATES INTERNAL ERROR
13484963   14474780  Wed Nov 28 11:22:20 CST 2012   INVALID TTC BUFFER LENGTH IN CASE OF PROPAGATION
MAY RAISE ORA-3146
13492735   14474780  Wed Nov 28 11:22:20 CST 2012   DISALLOW ADDING NON-HCC DATAFILE TO HCC TABLESPACE
13495307   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT QUERY WITH ORAOLAP TABLE FUNCTION MAY FAIL
WITH INTENAL ERROR
13498646   14474780  Wed Nov 28 11:22:20 CST 2012   SQL*LOADER DIRECT PATH LOAD WITH 'SUBPARTITION
FOR' CLAUSE FAILS
13499128   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-001-CPUJAN2012
13502183   14474780  Wed Nov 28 11:22:20 CST 2012   VALID PACKAGE BODY IN CHILD EDITION MARKED AS
INVALID DURING UTL_RECOMP
13503598   14474780  Wed Nov 28 11:22:20 CST 2012   ALLOW MECHANISM FOR REJECTING HIGH SCN BASED ON
DIFFERENCE IN SCN VALUES
13505390   14474780  Wed Nov 28 11:22:20 CST 2012   REPEATED ASSERTS ARE SEEN FOR A SQL DURING
DYNAMIC SAMPLING ON AN INTERVAL PARTITIONED TABLE
13506110   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY WITH EDITIONING VIEW AND SINGLE POLICY ON
BASE TABLE COULD CRASH
13515918   14474780  Wed Nov 28 11:22:20 CST 2012   VARCHAR2 ACCEPTS MORE THAN 4000 BYTES INSERTING
FROM DBLINK
13516727   14474780  Wed Nov 28 11:22:20 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO THE INTEGRATED
EXTRACT COMPONENT OF ORACLE GOLDENGATE
13524237   14474780  Wed Nov 28 11:22:20 CST 2012   UNNEEDED TEMPORARY TABLES CREATED FOR STAR TRANSFO
RMATION
13524899   14474780  Wed Nov 28 11:22:20 CST 2012   LONG TURNAROUND TIME WAS OBSERVED WHILE EXECUTING
A QUERY DUE TO TEMP TABLES CREATION BY DB SERVER
13527323   14474780  Wed Nov 28 11:22:20 CST 2012   AWR REPORT GENERATION COULD FAIL WITH ORA-6502
WITH MULTIBYTE CHARS IN SQL TEXT
13528551   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-002-CPUJAN2012
13533487   14474780  Wed Nov 28 11:22:20 CST 2012   CLOSE CALLOUT NOT INVOKED INTERMITTENTLY FOR
PARALLEL TABLE FUNCTION QUERIES
13534412   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KCLCHKBLKDMA_3] IS SEEN AS LE BSCN IS
UPDATED WITH NEWED SCN
13544396   14474780  Wed Nov 28 11:22:20 CST 2012   INTERNAL ERROR IS SEEN IN QUERIES OR DML ON A
TABLE AFTER ALTERING CLOB COLUMN TO LONG
13548053   14474780  Wed Nov 28 11:22:20 CST 2012   UNDER HEAVY LOAD DROP TABLE STATEMENT MAY LEAD TO
ORA-00600 [12869]
13550185   14474780  Wed Nov 28 11:22:20 CST 2012   QUERIES ON V$SQLSTATS MAY CAUSE CRASH OR HANG
13553883   14474780  Wed Nov 28 11:22:20 CST 2012   WHEN THE ARCHIVE PROCESS IS UNABLE TO ARCHIVE
REDO LOG FILES, IT DOES NOT PROVIDE A STANDARD
ERROR IN THE ALERT LOG FILE
13554409   14474780  Wed Nov 28 11:22:20 CST 2012   Fix for Bug 13554409
13564720   14474780  Wed Nov 28 11:22:20 CST 2012   SEVERE PERFORMANCE DEGRADATION WITH TURNING ON FGA
.
13566938   14474780  Wed Nov 28 11:22:20 CST 2012   DML WITH BINDS ON A REFERENCE PARTITIONED TABLE
MAY RAISE ORA-600 [KCBGTCR_1]
13572659   14474780  Wed Nov 28 11:22:20 CST 2012   DBMS_REDEFINITION DISABLES FKS USED FOR REFERENCE
PARTITIONING
13575265   14474780  Wed Nov 28 11:22:20 CST 2012   PARSING ERROR IN CHECK_LOB_POLICYAUTH WHEN
USERNAME/TABLE NAME IS 30 CHARACTERS
13579992   14474780  Wed Nov 28 11:22:20 CST 2012   CREATION OF IN MEMORY TEMPORARY TABLE PRODUCES
TOO MUCH RECURSIVE SQL
13580513   14474780  Wed Nov 28 11:22:20 CST 2012   RETRY TIMEOUT OF SNAPSHOT CONTROLFILE ENQUEUE IS
NOT ONE HOUR
13584130   14474780  Wed Nov 28 11:22:20 CST 2012   COMPILING LIBRARY UNIT WITH _LOAD_WITHOUT_COMPILE
IN NON-BASE EDITION CAUSES CRASH
13588248   14474780  Wed Nov 28 11:22:20 CST 2012   SOMETIMES CORE DUMP IS SEEN IN RAC ENV WITH
SESSION POOLING, DRCP, FLASH CACHE, SERVER CACHE
AND AC ENABLED
13599864   14474780  Wed Nov 28 11:22:20 CST 2012   PERFORMANCE OF RMAN BACKUPS FROM AN EXADATA TO A
ZFSSA IS SLOW
13612575   14474780  Wed Nov 28 11:22:20 CST 2012   PROCEDURES RETURNING REFCURSOR BIND VARIABLES MAY
HIT ORA-600 [15419]
13624984   14474780  Wed Nov 28 11:22:20 CST 2012   DATAPUMP HANGS ON PACKAGE BODY COMPILATION
LIBRARY CACHE PIN
13629056   14474780  Wed Nov 28 11:22:20 CST 2012   PARALLEL INSERT AS SELECT FAILED W/ ORA-29771
13632717   14474780  Wed Nov 28 11:22:20 CST 2012   CPUAPR2012 DATABASE 11.2.0.3
13632809   14474780  Wed Nov 28 11:22:20 CST 2012   RMAN BZ2 COMPRESSION BACKUP HANGS
13642207   14474780  Wed Nov 28 11:22:20 CST 2012   ENABLE IN-MEMORY PQ OPTIMIZATIONS FOR HCC
13645917   14474780  Wed Nov 28 11:22:20 CST 2012   PMON ONLINE BLOCK RECOVERY IN LOOP COULD LEAD TO
INSTANCE HANG
13649031   14474780  Wed Nov 28 11:22:20 CST 2012   WHEN SHRINK ON PARTITIONED TABLE WHICH CONTAINS
PARTITIONS WITH DEFERRED SEGMENT MAY CAUSE ERROR
13652437   14474780  Wed Nov 28 11:22:20 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO INTEGRATED EXTRACT
COMPONENT OF ORACLE GOLDENGATE
13657605   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KKZGBTCOLS] DURING BUILD DEFERRED REMOTE
WITH ROWID MV CREATION
13687870   14474780  Wed Nov 28 11:22:20 CST 2012   DBWR RECONNECTS TO CELLSRV UNDER HEAVY LOAD
13696023   14474780  Wed Nov 28 11:22:20 CST 2012   FIX OF BUG;12765572 CAUSE I/O PERFORMANCE DOWN
13696216   14474780  Wed Nov 28 11:22:20 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.2 (INCLUDES
CPU APR2012)
13699124   14474780  Wed Nov 28 11:22:20 CST 2012   AWR COMPARE PERIOD; SPINNING WHEN QUERYING DIFF
OF KEY INSTANCE STATS
13700577   14474780  Wed Nov 28 11:22:20 CST 2012   PARALLEL LOAD INTO HCC TABLE W/ HWM BROKERING
ENABLED MAY HIT ORA-600[KDBLDDR_2]
13705338   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULTS ON IOT SECONDARY INDEX THROUGH JOIN
13711695   14474780  Wed Nov 28 11:22:20 CST 2012   IN RARE CASES INTERNAL ERROR RAISED WHEN CHECKING
FOR CLUSTER CONFIGUARATION.
13717748   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULT WITH SIMPLE SELECT ON PARTITIONED TAB
LE
13718279   14474780  Wed Nov 28 11:22:20 CST 2012   DB INSTANCE TERMINATED DUE TO ORA-29770 WHEN
_GC_DEFER_TIME IS SET TO 1MS
13718476   14474780  Wed Nov 28 11:22:20 CST 2012   IGNORE PRED BAST TO EXCLUSIVE LOCK
13719081   14474780  Wed Nov 28 11:22:20 CST 2012   UPGRADE INVALIDATE VIEWS IS SLOW
13719292   14474780  Wed Nov 28 11:22:20 CST 2012   DB UPGRADE MAY TAKE LONGER WHEN ARCHIVELOG MODE
AND SUPPLEMENTAL LOGGING ENABLED
13720544   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULTS ON UPDATE WITH PARALLEL DML
13724193   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-01089 FROM REMOTE DATABASE, EVEN THOUGH THE
DB IS NOT SHUTTING DOWN
13725395   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH WATER MARK BROKERED LOAD INTO AN HCC TABLE
COULD LEAD TO INTERNAL ERROR
13732226   14474780  Wed Nov 28 11:22:20 CST 2012   NODE GETS EVICTED WITH REASON CODE 0X2
13737746   14474780  Wed Nov 28 11:22:20 CST 2012   BACKGROUND MEDIA RECOVERY COULD BE TERMINATED DUE
TO ORA-600[KRR_ASSEMBLE_CV_12]
13742433   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-004-CPUAPR2012
13742434   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-005-CPUAPR2012
13742435   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-006-CPUAPR2012
13742436   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-007-CPUAPR2012
13742437   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-008-CPUAPR2012
13742438   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-009-CPUAPR2012
13742464   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-003-CPUAPR2012
13743987   14474780  Wed Nov 28 11:22:20 CST 2012   ASM INSTANCE TERMINATES WITH DR CHANGE IN CPU
COUNT PARALLE_MAX_SERVERS
13767790   14474780  Wed Nov 28 11:22:20 CST 2012   EXADATA AUTOMATION MANAGER MAY NOT AUTO ONLINE
DISKS THAT ARE ADDED TO DISKGROUP WITH FORCE OPTIO
N
13769887   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KRVUATLA20] SEEN WITH SIMULATED LOG FILE
CORRUPTION
13772618   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-010-CPUAPR2012
13773133   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KTSFLMERGE-CYCLE-1] DURING INSERTS INTO
FREELIST MANAGED SEGMENT
13775960   14474780  Wed Nov 28 11:22:20 CST 2012   LATCH ENQUEUE CONTENTION SEEN IN DELETE/INSERT SF
WORKLOAD AFTER 13395403
13780816   14474780  Wed Nov 28 11:22:20 CST 2012   UTL_RECOMP LEAVES DEPENDENT MATERIALIZED VIEW INVA
LID
13784384   14474780  Wed Nov 28 11:22:20 CST 2012   NO CONSTRAINT TO BE INHERITED BY TEMP TABLE
CREATED DURING STATS COLLECTION
13786142   14474780  Wed Nov 28 11:22:20 CST 2012   DROP TRIGGER IN EDITIONING ENVIRONMENT COULD FAIL
WITH ORA-4045/ORA-4098
13786778   14474780  Wed Nov 28 11:22:20 CST 2012   WRONG RESULTS WITH USING THE INDEX_COMBINE HINT
13787482   14474780  Wed Nov 28 11:22:20 CST 2012   CDC PURGE ROUTINE INVALIDATING CUSTOM INDEXES
13790109   14474780  Wed Nov 28 11:22:20 CST 2012   REFRESH RETURN WRONG RESULTS FOR ON-COMMIT MV
WITH ROLLUP
13801740   14474780  Wed Nov 28 11:22:20 CST 2012   IMBALANCE IN NUMBER OF WORKING SETS PER DBWR ON
NUMA X2-8 10 CORES
13804294   14474780  Wed Nov 28 11:22:20 CST 2012   INTERNAL ERRORS, CORRUPTIONS, USING PIPELINED
FUNCTION WHOSE ROWS CAUSE ERRS
13811172   14474780  Wed Nov 28 11:22:20 CST 2012   DBMS_DBVERIFY MAY FAIL WITH DBV-111; OCI FAILURE
(4157) ORA-600 [KUDBVSLFW1]
13814905   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE CRASHED WITH ORA-7445 [KQLMBIVG()+711]
IN LCK0
13816397   14474780  Wed Nov 28 11:22:20 CST 2012   PST; TRIGGER TOOMANYOFFLINES WHEN DEGENERATE &
SUFFICIENT FAILGROUPS SEEN
13839641   14474780  Wed Nov 28 11:22:20 CST 2012   INCORRECT ENTRIES FOR DESCRIPTION COLUMN IN DBA_TR
IGGERS
13851078   14474780  Wed Nov 28 11:22:20 CST 2012   PQ SLAVES EXECUTING SAME STMT REFERENCING PL/SQL
FUNCTION COULD LEAD TO DEADLOCK
13863326   14474780  Wed Nov 28 11:22:20 CST 2012   UPDATE TABLE ERRORS WITH ORA-00942 EVEN THOUGH
TABLE DOES IN FACT EXIST.
13871495   14474780  Wed Nov 28 11:22:20 CST 2012   IMPROVE ASM OFFLINE HANDLING AFTER CELL FAILURE
13871547   14474780  Wed Nov 28 11:22:20 CST 2012   REDUCE DISKMON->SLAVE DISKMON NOTIFICATION
LATENCY ON CELL FAILURE
13879553   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT QUERY WITH 'FOR UPDATE', 'CONNECT BY' AND
'ORDER BY' CLAUSE MAY CAUSE INTERNAL ERROR
13880971   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-1779 FALSE DETECTION OF NON KEY-PRESERVED
TABLE IN CORRECT UPDATE STATEMENT
13882317   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH CACHE BUFFERS CHAINS LATCH CONTENTION DURING
IN-MEMORY PQ SCAN
13887875   14474780  Wed Nov 28 11:22:20 CST 2012   DEADLOCK WHILE ADDING A USER TO RESOURCE GROUP,
WHILE GATHER_STATS IS RUNNING
13901039   14474780  Wed Nov 28 11:22:20 CST 2012   LONG BUFFER BUSY WAITS WHEN LOST WRITE PROTECTION
IS ENABLED
13903046   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [4417] WHILE PERFORMING BLOCK CLEANOUTS
ON HCC COMPRESSED TABLE BLOCKS
13906496   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [15800] MAY BE SEEN WHILE CREATING THE
PARTITION TABLE
13910420   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-8103 DURING UPDATE OF BASICFILE CLOB IN ASSM
SEGMENT USING SPACE SEARCH CACH
13911821   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE TERMINATION DUE A CRASH HIT BY PMON IN
SHARED CURSORS CODE
13912192   14474780  Wed Nov 28 11:22:20 CST 2012   PQ SLAVES COULD RAISE ORA-942 FOR QUERY W/
SUBQUERY PARTITION PRUNING,TEMP TABLE
13912642   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [504] [TABLESPACE KEY CHAIN] WITH KCBI
FUNCTIONS ON THE STACK
13913630   14474780  Wed Nov 28 11:22:20 CST 2012   COMPRESSION OLTP; INSERT ... SELECT DOESN'T
COMPRESS SOME ROWS
13916709   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH SCN INCREASE RATE DUE TO CURSOR INVALIDATION
OF A LONG RUNNING QUERY
13917937   14474780  Wed Nov 28 11:22:20 CST 2012   INSTANCE MAY CRASH WITH ORA-7445 [KQLMBIVG()...]
WHILE INVALIDATING A TEMP TABLE
13918644   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-07445 ON RAC WITH AUDIT_SYS_OPERATIONS=TRUE
DOING CREATE TEXT INDEX PARALLEL
13923374   14474780  Wed Nov 28 11:22:20 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.3 (INCLUDES
CPU JUL2012)
13929853   14474780  Wed Nov 28 11:22:20 CST 2012   PARALLEL DDL FAILS IN 'HYBRID COLUMNAR
COMPRESSION' TABLE
13936424   14474780  Wed Nov 28 11:22:20 CST 2012   SELECT FOR UPDATE NOT RETURNING VALUES FOR COL
ADDED WITH DEF VALUE & NOT NULL
13942462   14474780  Wed Nov 28 11:22:20 CST 2012   LOADING AN HCC TABLE IN PARALLEL WITH HWM
BROKERING LEADS TO ORA-600[KCBLRL_1]
13945708   14474780  Wed Nov 28 11:22:20 CST 2012   ATTEMPTS TO DROP VIEWS IN OLD EDITIONS RESULTS IN
ORA-04063
13958038   14474780  Wed Nov 28 11:22:20 CST 2012   EXCESS SPACE USAGE DURING UPDATE
13976144   14474780  Wed Nov 28 11:22:20 CST 2012   REDUCE NON-ANT TIMEOUT TO AVOID EVICTIONS AND
REDUCE BROWNOUT
13979519   14474780  Wed Nov 28 11:22:20 CST 2012   'ROW CACHE LOCK' WAITS ON DC_USERS IN RAC
13981051   14474780  Wed Nov 28 11:22:20 CST 2012   CORE DUMP IN TBSAFL MAY BE SEEN WHILE CREATING
TABLESPACE WITH COMPRESSION
13989185   14474780  Wed Nov 28 11:22:20 CST 2012   SWITCHOVER_STATUS IS TO STANDBY EVEN WHEN
MULTIPLE SESSIONS ARE ACTIVE @PRIMARY
13997862   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600; [KSFDCHKFOBRERR1] CAN HAPPEN IF A
PROCESS DOUBLE-CLOSES A DISK
14005749   14474780  Wed Nov 28 11:22:20 CST 2012   IMPDP FAILS TO IMPORT FUNCTION NAMES (HAVING =
CHAR) ASSOCIATED WITH VPD POLICY
14008285   14474780  Wed Nov 28 11:22:20 CST 2012   CLIENT NEEDS TO OPEN DISK WITH GUID INSTEAD OF PAT
H
14013094   14474780  Wed Nov 28 11:22:20 CST 2012   PARTITION ORDER IN INDEX DEFINITION IS DIFFERENT
THAN TABLE PARTITION
14014434   14474780  Wed Nov 28 11:22:20 CST 2012   CORRUPTION ON SECUREFILES USING WLS AND JDBC WITH
MULTIPLE FLUSH; BASICFILES OK
14016187   14474780  Wed Nov 28 11:22:20 CST 2012   PARALLEL CURSOR NOT SHARED DUE TO DEFAULT
PARALLEL DEGREE MISMATCH (PX_MISMATCH)
14029050   14474780  Wed Nov 28 11:22:20 CST 2012   MMAN FAILING TO DONATE GRANULES TO SHARED POOL
DESPITE UNUSED PGA ALLOWANCE
14034244   14474780  Wed Nov 28 11:22:20 CST 2012   CORRUPTION DUE TO STALENESS REGISTRY SLICE SHARING
14038787   14474780  Wed Nov 28 11:22:20 CST 2012   CPUJUL2012 DATABASE 11.2.0.3
14040433   14474780  Wed Nov 28 11:22:20 CST 2012   CURSORS NOT SHARED DUE TO DIFFERENT CALL DURATION
14041920   14474780  Wed Nov 28 11:22:20 CST 2012   FTP OF A FILE INTO DBFS MAY GET CROPPED FILE CONTE
NT
14042380   14474780  Wed Nov 28 11:22:20 CST 2012   ERRORS ARE SEEN WHEN INSTANT CLIENT OPENS DIAUS.MS
G
14050233   14474780  Wed Nov 28 11:22:20 CST 2012   RDBMS PATCH 4 FOR 11.2.0.3 FOR OGG INTEGRATED EXTR
ACT
14052474   14474780  Wed Nov 28 11:22:20 CST 2012   QUERY INVOLVING NULLIF'S WITH CONSTANT OPERANDS
IN JOIN MAY RETURN WRONG RESULTS
14052871   14474780  Wed Nov 28 11:22:20 CST 2012   RESOURCE MANAGER CANCEL_SQL WORKING PER
CUMULATIVE PER SESSSION, NOT PER CALL
14062792   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-011-CPUJUL2012
14062793   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-012-CPUJUL2012
14062794   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-013-CPUJUL2012
14062795   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-014-CPUJUL2012
14062796   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-015-CPUJUL2012
14062797   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-016-CPUJUL2012
14063280   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-017-CPUJUL2012
14063281   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-018-CPUJUL2012
14071518   14474780  Wed Nov 28 11:22:20 CST 2012   PROBLEMS WITH OPTIMIZER CURSOR SHARING DIAGNOSTICS
14076523   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KGXRELEASE-BAD-HOLDER] FROM PROCESS WITH
NO USER SESSION
14097127   14474780  Wed Nov 28 11:22:20 CST 2012   ADG STANDBY DOES NOT HONOR CELL STORAGE KEEP
14098382   14474780  Wed Nov 28 11:22:20 CST 2012   LOG CHANGES TO SHUTDOWN SERVICES;UPDATE
ASMDEACTIVATIONOUTCOME FOR EXTERNAL DGRP
14098509   14474780  Wed Nov 28 11:22:20 CST 2012   LMON SPINNING ON KJFCRCC CAUSES EVICTION DURING ST
ARTUP
14110275   14474780  Wed Nov 28 11:22:20 CST 2012   PARSE OF QUERY WITH TABLE THAT HAD UNDERGONE ADD
COLUMN MAY RAISE INTERNAL ERROR
14114792   14474780  Wed Nov 28 11:22:20 CST 2012   EXCHANGE SUBPARTITION COMMANDS TAKING LONG TO COMP
LETE
14125317   14474780  Wed Nov 28 11:22:20 CST 2012   BUFFER ALIGNMENT ISSUE WITH FIX FOR BUG 9782075
14132953   14474780  Wed Nov 28 11:22:20 CST 2012   RDBMS; WRITE-BACK FLASH CACHE RESILVERING
14143451   14474780  Wed Nov 28 11:22:20 CST 2012   ASM; WRITE-BACK FLASH CACHE RESILVERING
14144283   14474780  Wed Nov 28 11:22:20 CST 2012   DBFS NOT USING EXPIRED FREE SPACE IN A MULTI-NODE
ENVIRONMENT
14153033   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-01115 POSSIBLE DURING SMART SCAN IF THERE IS
OFFLINE DISK IN A MIRRORED DISK
14153464   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [15265] MAY BE SEEN WHEN THE RECYCLEBIN
FEATURE IS ENABLED
14174174   14474780  Wed Nov 28 11:22:20 CST 2012   PQ SLAVE STUCK IN DIRECT PATH WRITE AFTER OSSNET T
IMEOUT
14175146   14474780  Wed Nov 28 11:22:20 CST 2012   RDBMS PATCH 5 FOR 11.2.0.3 FOR OGG INTEGRATED EXTR
ACT
14176879   14474780  Wed Nov 28 11:22:20 CST 2012   EXTENSIVE GROWTH OF SECUREFILES SEGMENTS
UNDERGOING UPDATES
14198511   14474780  Wed Nov 28 11:22:20 CST 2012   MV LOG NOT PURGED WHEN ON DEMAND AND ON COMMIT MV
EXISTS ON SAME TABLE
14207317   14474780  Wed Nov 28 11:22:20 CST 2012   ROW CACHE OBJECTS LATCH CONTENTION DUE TO CURSORS
INVLOVING VPD AND NLS MISMATCH
14215134   14474780  Wed Nov 28 11:22:20 CST 2012   UNABLE TO USE THE RECNUM COLUMN TYPE IN A SQL
EXPRESSION WITH SQL*LOADER
14218148   14474780  Wed Nov 28 11:22:20 CST 2012   IORM PLAN REPUSH BROKEN FOR MULTI-LEVEL PLANS
14237793   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-01041 FOLLOWED BY ORA-03113 WHILE COMPILING FO
RM
14275605   14474780  Wed Nov 28 11:22:20 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.4 (INCLUDES SPU
OCT2012)
14280879   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KTSIRCINFO_NUM1] FROM SEGMENT ADVISOR ON
CUBE-ORGANIZED TABLE
14287564   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [KGHSSTREAM_COPYN] WHEN EXCHANGING PARTITI
ON
14292825   14474780  Wed Nov 28 11:22:20 CST 2012   DEFAULT MEMORY PARAMETER VALUES FOR 11.2 ASM
INSTANCES LOW
14292987   14474780  Wed Nov 28 11:22:20 CST 2012   DISKMON DIED DUE TO SKGXP ASSERTION,
ORA-600[KSZSNDID3] ON ASM
14293031   14474780  Wed Nov 28 11:22:20 CST 2012   SKGZNP OSD IS NOT RETURNING PEER_DISCONNECT
14294123   14474780  Wed Nov 28 11:22:20 CST 2012   CSS FAILED TO STARTUP DUE TO GUID ISSUE AT OPEN
OSS DISK STEP
14299365   14474780  Wed Nov 28 11:22:20 CST 2012   RESYNC HITS ORA-15041 AND ORA-600 17090
14301592   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-7445 ERRORS CORRUPT BLOCKS SHIFTED BY 2 BYTES
IN BUFFER CACHE IN RECOVERY
14309390   14474780  Wed Nov 28 11:22:20 CST 2012   HIGH CPU USAGE WITH RECURSIVE STATEMENT ON FILE$
14314239   14474780  Wed Nov 28 11:22:20 CST 2012   ORA-600 [504] MAY BE SEEN IN RESILVERING IS ENABLE
D
14317360   14474780  Wed Nov 28 11:22:20 CST 2012   A SPATIAL QUERY UNDERGOING JPPD CRASHES AT QERIXGE
YKEY
14334353   14474780  Wed Nov 28 11:22:20 CST 2012   DATAPUMP; ORA 600 [KKDLINVHDLANDDEP0] DURING IMPDP
14390252   14474780  Wed Nov 28 11:22:20 CST 2012   DATABASE SECURITY PATCH UPDATE 11.2.0.3.0 - SPUOCT
2012
14409183   14474780  Wed Nov 28 11:22:20 CST 2012   SESSION HANGS ON GC BUFFER BUSY ACQUIRE
14467061   14474780  Wed Nov 28 11:22:20 CST 2012   FAILED INSTANCE RECOVERY MAY CAUSE ASM METADATA CO
RRUPTION/ORA-600[KFCRCVREAD10]
14473913   14474780  Wed Nov 28 11:22:20 CST 2012   SOURCE 11.2.0.2 TO TARGET 11.2.0.3, ISSUE OF TTC
PROTOCOL ERR WHEN USING DTYSTZ
14480674   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-019-CPUOCT2012
14480675   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-020-CPUOCT2012
14480676   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-021-CPUOCT2012
14506367   14474780  Wed Nov 28 11:22:20 CST 2012   AWR HAS INCORRECT STATS FOR PHYSICAL READS
OPTIMIZED WITH WRITE BACK FLASH
14548763   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-022-CPUOCT2012
14557588   14474780  Wed Nov 28 11:22:20 CST 2012   ORACLE_LOADER ACCESS DRIVER FAILS TO READ
MULTIPLE ORACLE_DATAPUMP DUMPFILES
14613900   14474780  Wed Nov 28 11:22:20 CST 2012   POSSIBLE CORE DUMP WHILE SCANNING FOR A CHILD FOR
SHARABLE CURSOR
14624146   14474780  Wed Nov 28 11:22:20 CST 2012   PMON MAY CRASH WHILE CLEANING UP TEMP TABLE STATE
SCN INFORMATION
14654284   14474780  Wed Nov 28 11:22:20 CST 2012   POSSIBLE MEMORY LEAK WHILE PROCESSING BINARYXML
14664355   14474780  Wed Nov 28 11:22:20 CST 2012   DB-11.2.0.3-MOLECULE-023-CPUOCT2012

------------------------------------------------------------------------------------------------------

OPatch succeeded.
...More

Status on dm01db02:/u01/app/oracle/product/11.2.0.3/dbhome_1: FAIL => System may be exposed to Exadata Critical Issue DB11


Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/product/11.2.0.3/dbhome_1
Central Inventory : /u01/app/oraInventory
from           : /u01/app/oracle/product/11.2.0.3/dbhome_1/oraInst.loc
OPatch version    : 11.2.0.3.0
OUI version       : 11.2.0.3.0
Log file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/opatch2014-04-16_11-17-07AM_1.log

Lsinventory Output file location : /u01/app/oracle/product/11.2.0.3/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2014-04-16_11-17-07AM.txt

------------------------------------------------------------------------------------------------------
Installed Top-level Products (1):

Oracle Database 11g                                                  11.2.0.3.0
There are 1 products installed in this Oracle Home.



List of Bugs fixed by Installed Patches:

Bug        Fixed by  Installed at                   Description
Patch
---        --------  ------------                   -----------

13350234   14307915  Wed Nov 28 11:23:32 CST 2012   DISKMON PATCH FOR EXADATA (DEC 2011 - 11.2.0.3.1)
13513982   14307915  Wed Nov 28 11:23:32 CST 2012   QUARTERLY DISKMON PATCH FOR EXADATA (JAN 2012 - 11
.2.0.3.2)
13688022   14307915  Wed Nov 28 11:23:32 CST 2012   DISKMON PATCH FOR EXADATA (MAR 2012 - 11.2.0.3.4)
14050993   14307915  Wed Nov 28 11:23:32 CST 2012   DISKMON PATCH FOR EXADATA (JUN 2012 - 11.2.0.3.7)
14184077   14307915  Wed Nov 28 11:23:32 CST 2012   DISKMON PATCH FOR EXADATA (JUL 2012 - 11.2.0.3.8)
14307915   14307915  Wed Nov 28 11:23:32 CST 2012   QUARTERLY DISKMON PATCH FOR EXADATA (OCT 2012 - 11
.2.0.3.11)
10114953   14275572  Wed Nov 28 11:23:15 CST 2012   HPI-SG 10205->11202 ONLY ONE HAIP UP IF 2 PRIVATE
NICS CONFIGURED BEFORE UPGRADE
10317921   14275572  Wed Nov 28 11:23:15 CST 2012   11202_GI_BUND_CRF-MEMORY ALERT SHOULD BE PROVIDED
UNDER EXTREME WORKLOAD
10418841   14275572  Wed Nov 28 11:23:15 CST 2012   LNX64-11203-CRF CHM SHOULD ALERT FOR BDB
FILESYSTEM CLOSE TO FULL
11675721   14275572  Wed Nov 28 11:23:15 CST 2012   11203-UTL DIAGCOLLECTION.PL SHOULD COLLECT
ACFS-ADVM RELATED LOGS
11772838   14275572  Wed Nov 28 11:23:15 CST 2012   DB AGENT OVERWRITE POLICY ON LOCAL_LISTENER
11836951   14275572  Wed Nov 28 11:23:15 CST 2012   ONLY 32 RLB EVENTS DEQUEUED EVERY 10 SECONDS,
EVEN IF THERE ARE MANY MORE QUEUED
12349553   14275572  Wed Nov 28 11:23:15 CST 2012   VIP ON FORMER PRIMARY NIC CAN NOT BE CLEARD WHEN
GLS NIC FAIL OVER HAPPENS
12398492   14275572  Wed Nov 28 11:23:15 CST 2012   SIHA DOES NOT SET ULIMIT FOR MEMLOCK
12538907   14275572  Wed Nov 28 11:23:15 CST 2012   ORAAGENT KEEPS EXITING AFTER APPLYING PATCH 123478
44
12594616   14275572  Wed Nov 28 11:23:15 CST 2012   AN ERROR OCCUR WHEN CHOOSE ACFS TO STORE THE
DATAFILES DURING DBCA
12639013   14275572  Wed Nov 28 11:23:15 CST 2012   POTENTIAL SPLIT AT STARTUP - LRG PROBLEM ID 556736
1
12650672   14275572  Wed Nov 28 11:23:15 CST 2012   255.255.255.255 BAD VALUE IS RECORDED IN SYSLOG
AND ORAROOTAGENT_ROOTOUT.LOG
12659561   14275572  Wed Nov 28 11:23:15 CST 2012   INSTANCE DOES NOT REGISTER SERVICES WHEN SCAN FAIL
OVERED
12680491   14275572  Wed Nov 28 11:23:15 CST 2012   STOP DEPENDENCY BETWEEN NETWORK AND VIP MUST HAVE
INTERMEDIATE MODIFYER
12709476   14275572  Wed Nov 28 11:23:15 CST 2012   CRSD ORAAGENT MEMORY LEAK AT 1.5M 1.2H ON NON-PE N
ODES
12720728   14275572  Wed Nov 28 11:23:15 CST 2012   GIPCHALOWERPROCESSNODE NO VALID INTERFACES FOUND
TO NODE
12726222   14275572  Wed Nov 28 11:23:15 CST 2012   11203 DB CREATION USING ASM...DISKGROUP ..
RESOURCES ARE NOT RUNNING ON NODES
12728585   14275572  Wed Nov 28 11:23:15 CST 2012   CRSCTL STOP CRS HANGS
12730342   14275572  Wed Nov 28 11:23:15 CST 2012   CAN'T FOUND LOGICAL CORRUPTION OF VOTEDISK ON 11.2
.0.2
12758736   14275572  Wed Nov 28 11:23:15 CST 2012   11203_WIN.X64_110713 INSTALL HANGED WHILE
REGISTERING ORAOLEDB11.DLL
12765467   14275572  Wed Nov 28 11:23:15 CST 2012   W2K3_11203 INCOMPATIBLE PERL CODE IN ROOTCRS.PL
LEADS TO MESSY OUTPUT FOR NT CMD
12771830   14275572  Wed Nov 28 11:23:15 CST 2012   ORA.ASM CRSD RESOURCE CHECK TIMED OUT -REFERENCE B
UG-12754555
12784559   14275572  Wed Nov 28 11:23:15 CST 2012   [11203-WIN64-110713]DURING DECONFIG,THE OUTPUT
'FAILED TO WRITE THE CHECKPOINT'
12791719   14275572  Wed Nov 28 11:23:15 CST 2012   USING LINK-BASED IPMP STANDBY INTERFACE'S IP IS 0.
0.0.0
12794268   14275572  Wed Nov 28 11:23:15 CST 2012   HPI-SG-11203 VIP START UP TIMEOUT WHEN RUN ROOT.SH
12829429   14275572  Wed Nov 28 11:23:15 CST 2012   11203-WIN64 ERR PRKC-1069 FAILED TO GET SUB KEYS
OF {0} WHILE CRS DEINSTALL
12829917   14275572  Wed Nov 28 11:23:15 CST 2012   WARNING DURING ADDNODE SCRIPT INVOCATION
12848480   14275572  Wed Nov 28 11:23:15 CST 2012   a b f DOS WINDOW EXIT WHILE CRS ADD NODE,PRVF-1020
9.
12849377   14275572  Wed Nov 28 11:23:15 CST 2012   11203_INST_WIN [INS-41112]THE INSTALLATION WAS
FAILED BY THE NETWORK CHECKING
12857064   14275572  Wed Nov 28 11:23:15 CST 2012   EXADA-SOL_X64-11203-UD SUNOS 5.11, HAIP STARTUP
FAILED, UPGRADING 11202 TO 11203
12867511   14275572  Wed Nov 28 11:23:15 CST 2012   ALERT IS MISSING WHEN RESOURCE RESTART-FAILOVER FA
ILS
12876314   14275572  Wed Nov 28 11:23:15 CST 2012   HPI-SG-11203 PRVF-5150 ASM DISK PATH CHECK FAILED
IN OUI PRE CHECK
12878750   14275572  Wed Nov 28 11:23:15 CST 2012   AIX-11203-CVU FOUND VALUE REPORTED BY CVU FOR
UNSATISFIED PARAMETER IS NULL
12885323   14275572  Wed Nov 28 11:23:15 CST 2012   NT OCLUMON GET MASTER FAILS TO REACH LOGGER SERVIC
E
12896850   14275572  Wed Nov 28 11:23:15 CST 2012   11203HPI 10203->11203 SIHA + DB UPGRADE, UPGRADE
SIHA ROOTUPGRADE THROW ERR
12897651   14275572  Wed Nov 28 11:23:15 CST 2012   SRGRSC TKPCWRSLG_ASM.DIF - CRS-2545
12897902   14275572  Wed Nov 28 11:23:15 CST 2012   11203_WINX64_110817 MULTICAST COMMUNICATION CHECK
FAILED
12899169   14275572  Wed Nov 28 11:23:15 CST 2012   HPI-SG-11203-UD RUN $CH-BIN-CLUVFY FROM NEW
HOME,ROOTUPGRADE.SH TERMINATE
12914824   14275572  Wed Nov 28 11:23:15 CST 2012   START CLUSTER,CSSD CAN ABORT DUE TO DISKMON
RESOURCE-AGENT TIMING ISSUES
12917897   14275572  Wed Nov 28 11:23:15 CST 2012   CLSSSCEXIT CSSD ABORTING FROM THREAD GMCLIENTLISTE
NER
12925041   14275572  Wed Nov 28 11:23:15 CST 2012   112024GIPSU OLOGGERD CORE DUMP AT 'CRFLOGDB.C
855' DURING START HAS STACK
12934171   14275572  Wed Nov 28 11:23:15 CST 2012   W2K8_11203 CVU VERIFICATION CANNOT PROCEED WITH
[CLUVFY COMP HEALTHCHECK -HTML]
12947871   14275572  Wed Nov 28 11:23:15 CST 2012   11203 WIN.X64 GI CONFIGURATION FAILED DURING
11202->11203 SIHA ASM UPG
12950823   14275572  Wed Nov 28 11:23:15 CST 2012   AIX-11203-HA-CRS SRVCTL STOP NODEAPPS WITH -R
OPTION FAIL TO STOP NETWORK RES
12959140   14275572  Wed Nov 28 11:23:15 CST 2012   VIP'S SOMETIMES DO NOT FAILOVER WHEN PRIVATE
INTERCONNECT GOES DOWN
12965049   14275572  Wed Nov 28 11:23:15 CST 2012   SOL-X64-CRF OLOGGERD WAS REPEATLY DISABLED DUE TO
DEFINED BDB SIZE REACHED
12971251   14275572  Wed Nov 28 11:23:15 CST 2012   11203_WINX64_110907 [INS-40711] CLUSTER NAME IS
BLANK (WHILE CRS UPGRADE)
12975811   14275572  Wed Nov 28 11:23:15 CST 2012   11203-WIN64 INSTALLER FAIED TO PERFORM STATUS
CHECK WHILE UPGRADE 10205 TO 11203
12990582   14275572  Wed Nov 28 11:23:15 CST 2012   AIX-11203-CVU-MSG CONFUSED SYMBOL <> IN CLUVFY
COMP HEALTHCHECK
12995950   14275572  Wed Nov 28 11:23:15 CST 2012   a b f 11107->11203 CVU CHECK NODE CONNECTIVITY FAI
LED
13000491   14275572  Wed Nov 28 11:23:15 CST 2012   RMI SSL PORT EXPOSED ON ORA.OC4J RESOURCE
13001901   14275572  Wed Nov 28 11:23:15 CST 2012   W2K3_11203 GRID INSTALLATION FAILED FOR ORA.ASM
NOT ONLINE
13001955   14275572  Wed Nov 28 11:23:15 CST 2012   11203-WIN64 ASMCA FAILED IN CONFIGURING EXISTING D
ISKGROUP
13002015   14275572  Wed Nov 28 11:23:15 CST 2012   SOL-VC-11203-CVU CSS MISSCOUNT CHECK WRONG WHEN
RUN COMP HEALTHCHECK
13011520   14275572  Wed Nov 28 11:23:15 CST 2012   [11203-SOL64-110916]UPGRADE 10205->11203 CVU POST
CHECK FAILED
13023609   14275572  Wed Nov 28 11:23:15 CST 2012   HPI_11203_CRS-CRSD MEM LEAK AT ABOUT 0.8M-1H ON
PE MASTER
13024624   14275572  Wed Nov 28 11:23:15 CST 2012   W2K8_11203 HIT ERROR [INS-20802] IN THE END OF
GRID INSTALLATION
13036424   14275572  Wed Nov 28 11:23:15 CST 2012   CHMOS HAS AN ERROR IN CALCULATING THE TOTAL
NUMBER OF OPEN FDS ON A SYSTEM
13037709   14275572  Wed Nov 28 11:23:15 CST 2012   INTERMITTENT FREE IP DETERMINATION ISSUE IN SRGSRV
13039908   14275572  Wed Nov 28 11:23:15 CST 2012   AGENT PROCESSES TAKE ABOUT 10 SECONDS TO EXIT AND
RESTART
13058611   14275572  Wed Nov 28 11:23:15 CST 2012   ROOTCRS.PL DECONFIG KEEPDG DOES NOT KEEP
DISKGROUP IN UPGRADED ENVIRONMENT
13066371   14275572  Wed Nov 28 11:23:15 CST 2012   W2K3_11203_UD UPGRADE 11201->11203 FAILED TO
CREATE ORAHOME ON ACFS
13074261   14275572  Wed Nov 28 11:23:15 CST 2012   11203-WIN64 PRKU-1058 FAILED TO RETRIEVE THE LIST
OF SERVICES DURING DEINTAL
13077654   14275572  Wed Nov 28 11:23:15 CST 2012   [11203-AIX-110901.100927]CVU CANNT GET CORRECT
NETWORK PARA FOR ERROR SCRIPT
13079948   14275572  Wed Nov 28 11:23:15 CST 2012   CVU FILES NOT BEING PICKED UP FOR 11.2.0.2.4GIPSU
13082238   14275572  Wed Nov 28 11:23:15 CST 2012   11203-WIN64 FAILED TO START THE CLUSTERWARE STACK
FROM THE LOWER VERSION
13085732   14275572  Wed Nov 28 11:23:15 CST 2012   W2K3_11203_CMP CRFMOND CORE DUMP HAPPENED SOMETIME
S
13090686   14275572  Wed Nov 28 11:23:15 CST 2012   AIX-11203-UD SERVICE FAIL TO FAILOVER AFTER DOWN
PUB NIC(11203 CRS + 10205 RAC)
13111013   14275572  Wed Nov 28 11:23:15 CST 2012   W2K8_11203 KERNEL PANIC FOR NTKRNLMP AFTER RAC
SOFTWARE INSTALLATION
13241779   14275572  Wed Nov 28 11:23:15 CST 2012   COREADM.CONF IS UPDATED IN EXECUTING CRSCTL COMMAN
D
13251796   14275572  Wed Nov 28 11:23:15 CST 2012   LNX64-12.1-EVM ORAAGENT DUMPS CORE IN
INSTCONNECTION DISCONNECT AT CLSNINSTCON
13323698   14275572  Wed Nov 28 11:23:15 CST 2012   CVUOS KERNEL PARAMETER CHECK IN GRID INFRA
INSTALLATION INCORRECT ON EXADATA
13332363   14275572  Wed Nov 28 11:23:15 CST 2012   BUG 9795321 HAS REAPPEARED IN 11.2.0.3
13334158   14275572  Wed Nov 28 11:23:15 CST 2012   REBOOT OF ONE OF THE SWITCH EVICTS INSTANCES
13339443   14275572  Wed Nov 28 11:23:15 CST 2012   ESSC CRS AGENT KILLS ASM INSTANCE DUE TO ORA-15042
13348650   14275572  Wed Nov 28 11:23:15 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.1
(INCLUDES DB PSU 11.2.0.3.1)
13355963   14275572  Wed Nov 28 11:23:15 CST 2012   NT POST-INSTALL, NODE CONNECTIVITY CHECK FAILED
ON CLUSTER NODES
13371153   14275572  Wed Nov 28 11:23:15 CST 2012   SCAN VIPS FAIL PING AFTER RELOCATE EVEN WITH NEW
ARP DRIVER (PATCH 10124639)
13396284   14275572  Wed Nov 28 11:23:15 CST 2012   11.2.0.3 GI PSU 1 HAS-CRS TRACKING BUG
13425727   14275572  Wed Nov 28 11:23:15 CST 2012   ROOTCRS.PL DOES NOT UNLOCK THE 11.2.0.3 CLONED
HOME PROPERLY
13430715   14275572  Wed Nov 28 11:23:15 CST 2012   FUJITSU-GLS-11203 ORAROOTAGENT DOESN'T RECOGNIZE
GLS ON SOLARIS SPARC
13440962   14275572  Wed Nov 28 11:23:15 CST 2012   DIFFERENT SUBNET FAILED TO CONNECT TO VIP AFTER
RESTART VIP
13460353   14275572  Wed Nov 28 11:23:15 CST 2012   REGISTRATION OF 11.2.0.3 DATABASE FAILS AGAINST
12.1 CRS STACK
13483672   14275572  Wed Nov 28 11:23:15 CST 2012   LNX64-12.1-RAC GEN0 HIT ORA-07445 [STRLEN()+16] [S
IGSEGV]
13498267   14275572  Wed Nov 28 11:23:15 CST 2012   AIX-11202-CRS HIGH CPU OVERHEAD OF AN IDLE RAC CLU
STER
13523527   14275572  Wed Nov 28 11:23:15 CST 2012   VIP DOESNT FAILOVER INTO OTHER NODE
13531373   14275572  Wed Nov 28 11:23:15 CST 2012   11.2.0.3.1GIPSU CVU CHECK FAIL FOR NETWORK
PARAMETERS EVEN THEY ARE SATISFIED
13540563   14275572  Wed Nov 28 11:23:15 CST 2012   MERGE REQUEST ON TOP OF 11.2.0.3.1PSU FOR BUGS
13425727 13440962
13550689   14275572  Wed Nov 28 11:23:15 CST 2012   TT12.1VALGRIND MLK MEMORY LEAK IN SCLS_META_CTX_IN
IT
13569812   14275572  Wed Nov 28 11:23:15 CST 2012   11.2.0.3.1GIPSU CVU FAIL TO DETERMINE IF ORACLE
HOME (ON ACFS) IS SHARED
13582411   14275572  Wed Nov 28 11:23:15 CST 2012   RAC ONE NODE SCAN_LISTENER GO OFF LINE AFTER
NETWORK HICCUP PSU4 HAS BEEN APP
13620816   14275572  Wed Nov 28 11:23:15 CST 2012   ROOTUPGRADE.SH BREAKS USER EQUIVALENCE
13652088   14275572  Wed Nov 28 11:23:15 CST 2012   EMGC OUT OF PLACE PATCHING NOT ADJUSTING
INIT.OHASD TO POINT TO NEW GI HOME
13696251   14275572  Wed Nov 28 11:23:15 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.2
(INCLUDES DB PSU 11.2.0.3.2)
13719731   14275572  Wed Nov 28 11:23:15 CST 2012   SCLSIDELADDRS() RETURNS THE WRONG RETURN CODE ON S
UCCESS
13727853   14275572  Wed Nov 28 11:23:15 CST 2012   ORACLE RESTART SIHA- OHAS IS TAKING ABOUT 11
MINUTES TO START
13776758   14275572  Wed Nov 28 11:23:15 CST 2012   GI UPGRADE 11.2.0.1 TO 11.2.0.3 ASMCA FAILED
ROOTUPGRADE.SH LAST ORA-1034
13789135   14275572  Wed Nov 28 11:23:15 CST 2012   OCLUMON REPORTS SWAPFREE 0 , SWAPTOTAL 0 AFTER
CHANGING THE SWAP-DEVICE
13806545   14275572  Wed Nov 28 11:23:15 CST 2012   CLUSTER_NAME NOT POPULATED DURING NON-ROLLING UPGR
ADE
13811209   14275572  Wed Nov 28 11:23:15 CST 2012   LNX64-11203-GIPC ONE OF THE REDUNDANT SWITCH
RESET CAUSE DB INSTANCES EVICTION
13825231   14275572  Wed Nov 28 11:23:15 CST 2012   CLSSNMREADNODEINFO SIGNALS DURING STARTUP
CLUSTERWARE WONT START
13843080   14275572  Wed Nov 28 11:23:15 CST 2012   STBH11.2.0.3 ROOTUPGRADE.SH FOR GI-CRS UPGRADE
TAKES 40-55 MINUTES
13857364   14275572  Wed Nov 28 11:23:15 CST 2012   FIX OF BUG 13791953 DOES NOT WORK
13869978   14275572  Wed Nov 28 11:23:15 CST 2012   W2K8_12.1_CSS KERNEL PANIC FOR CSS ERROR
13919095   14275572  Wed Nov 28 11:23:15 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.3
(INCLUDES DB PSU 11.2.0.3.3)
13924431   14275572  Wed Nov 28 11:23:15 CST 2012   OSYSMOND.BIN PROCESS CAUSES 100percent CPU LOAD
13947200   14275572  Wed Nov 28 11:23:15 CST 2012   DBCA DOES NOT ENABLE THE CONFIGURE DATABASE OPTION
13965075   14275572  Wed Nov 28 11:23:15 CST 2012   CRS AGENT FRAMEWORK INTERMITTENTLY DOES NOT RUN
ACTIONS IN PARALLEL
14082976   14275572  Wed Nov 28 11:23:15 CST 2012   BUG TO COORDINATE CI REGRESSION OF BUG 12709476
14275572   14275572  Wed Nov 28 11:23:15 CST 2012   GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.3.4
(INCLUDES DB PSU 11.2.0.3.4)
3522216    14474780  Wed Nov 28 11:22:21 CST 2012   WRONG PREDICATE DISPLAYING BY UTLXPLS.SQL
8316255    14474780  Wed Nov 28 11:22:21 CST 2012   SPARC T SERIES MACHINES ARE SIZED INCORRECTLY
9095696    14474780  Wed Nov 28 11:22:21 CST 2012   CF ENQUEUE USAGE IN KCRFWL() IMPACTS LGWR PERFORMA
NCE
9163477    14474780  Wed Nov 28 11:22:21 CST 2012   ERROR ORA-39726 WHILE DROPPING COLUMN ON
COMPRESSED PARTITIONED TABLE
9659614    14474780  Wed Nov 28 11:22:21 CST 2012   HUGE ORA-8103 TRACE FILES GENERATED AFTER PATCH
7519406 APPLIED
9703627    14474780  Wed Nov 28 11:22:21 CST 2012   ROOT USE OF ASMCMD PLACES ALERT.LOG IN USER DIRECT
ORY
9706792    14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KCRPDV_NOENT] IN CRASH RECOVERY WITH PARA
LLELISM
9725536    14474780  Wed Nov 28 11:22:21 CST 2012   ORA-7445 IS SEEN WHEN LOADING AN EHCC TABLE WITH
A DOMAIN INDEX
9761357    14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[QKEISEXPRRE...ED1] WHEN QUERYING DUAL
WITH PREDICATE INVOLVING ORA_ROWSN
9782075    14474780  Wed Nov 28 11:22:21 CST 2012   ASMCMD CP COMMAND SHOULD SUPPORT NAMED_PIPE
9847699    14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [17090] MAY BE SEEN WHEN A DISK GOES
OFFLINE DURING RESIZE
9858539    14474780  Wed Nov 28 11:22:21 CST 2012   DATA PUMP IMPORT FAILS TO IMPORT LOGON TRIGGER
DUE TO ORA-04072
9873405    14474780  Wed Nov 28 11:22:21 CST 2012   MV FAST REFRESH FAILS DUE TO INTERNAL ERROR AFTER
UPGRADING FROM 11201 TO 11202
9876287    14474780  Wed Nov 28 11:22:21 CST 2012   SIGNIFICANT PERFORMANCE SLOWDOWN DUE TO WAIT
EVENT PXNSQ;PQLOADINFOQUERY
9906567    14474780  Wed Nov 28 11:22:21 CST 2012   FILE CREATION CAN GET OFFLOADED TO THE EXADATA
CELL WRONGLY WHEN DISKS ARE TAKEN OFFLINE
10133521   14474780  Wed Nov 28 11:22:21 CST 2012   LOGICAL STANDBY APPLY COULD FAIL WITH
ORA-26808/26786 FOR SOME NLS_SORT VALUES
10136532   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT OVER TEMPORARY TABLE IN PARALLEL MAY
RETURN WRONG RESULTS
10214323   14474780  Wed Nov 28 11:22:21 CST 2012   LOB-BASED REPLICATION MV REFRESH USE ROW-BY-ROW PR
OCESSING
10248538   14474780  Wed Nov 28 11:22:21 CST 2012   OPTIMIZER COST MODEL NOT EXADATA-AWARE
10263668   14474780  Wed Nov 28 11:22:21 CST 2012   SELECTING CLOB SOMETIMES FAIL WITH ORA-600 [KOKEGP
INLOB1]
10287724   14474780  Wed Nov 28 11:22:21 CST 2012   STALE FILE DESCRIPTORS USED BY CLIENTS(RDBMS)
CAUSING CELLSRV CRASH WHEN CONSUMED
10297948   14474780  Wed Nov 28 11:22:21 CST 2012   FREQUENT PX MISMATCHES OCCURRING FOR PARTICULAR SQ
L
10332676   14474780  Wed Nov 28 11:22:21 CST 2012   DB KEEPS CRASHING DUE TO STALE PIN
10350832   14474780  Wed Nov 28 11:22:21 CST 2012   DML LOCK STARVATION IS SEEN IN FINISH_REDEF_TABLE
EXECUTION
10387201   14474780  Wed Nov 28 11:22:21 CST 2012   EHCC WITH CELL PASSTHRU CAUSES DOUBLE I/OS
10418524   14474780  Wed Nov 28 11:22:21 CST 2012   ANALYZE TABLE VALIDATE STRUCTURE CASCADE FAST -
SPECIAL CHARACTERS
10625145   14474780  Wed Nov 28 11:22:21 CST 2012   SWITCH_CONSUMER_GROUP_FOR_SESS DOES NOT ALLOW A
SWITCH TO CANCEL_SQL
11063191   14474780  Wed Nov 28 11:22:21 CST 2012   KGL LOCKS MAY LEAK WHEN CURSOR_SHARING WAS SET TO
A NON-DEFAULT VALUE
11071989   14474780  Wed Nov 28 11:22:21 CST 2012   VIEW INVALIDATED WHEN ADDING COLUMNS TO BASE
TABLE WITH FUNCTIONAL INDEX
11708510   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY AGAINST REMOTE PRE-11G DB USING JDBC CLIENT
WITH E2E_CONTEXT NAMESPACE MAY RESULT IN ORA-28267
11715084   14474780  Wed Nov 28 11:22:21 CST 2012   ACTIVE DUPLICATE SHOULD WORK WHEN CONNECTED TO
STANDBY AS SOURCE DB
11837095   14474780  Wed Nov 28 11:22:21 CST 2012   TIME DRIFT DETECTED APPEARS INTERMITTENTLY IN
ALERT LOG, THO' EVENT 10795 SET
11840910   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-3212 IS SEEN WHILE RUNNING THE QUERY WHEN
CONNECTED WITH SYSOPER PRIVILEGE
11841048   14474780  Wed Nov 28 11:22:21 CST 2012   WITH QUERY REWRITE ENABLED, QURIES WITH 'WITH'
CLAUSE MAY FAIL WITH INTERNAL ERROR
11855445   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH CPU UTILIZATION ON ASM LMS0 DUE TO
INEFFICIENT RESOURCE HASHING
11868640   14474780  Wed Nov 28 11:22:21 CST 2012   DB CRASH DUE TO ORA-600 [KJUSCV] OR ORA-600
[KJUCVL;!BUSY] IN PMON
11877623   14474780  Wed Nov 28 11:22:21 CST 2012   RENAMING A TRIGGER AND THEN RENAMING IT BACK TO
THE ORIGINAL NAME MAY CAUSE AN ORA-600 [17273]
11896575   14474780  Wed Nov 28 11:22:21 CST 2012   ORA ERRORS REPORTED WHEN CREATING OBJECTS WITH
SAME NAME AS EXISTING PUBLIC SYNONYMS
12312133   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN INCREMENTAL BACKUP WITH BLOCK CHANGE
TRACKING MAY CAUSE STANDBY DB CRASH
12325243   14474780  Wed Nov 28 11:22:21 CST 2012   SLOW PERFORMANCE ON EXPDP FUNCTIONAL AND BITMAP IN
DEXES
12325317   14474780  Wed Nov 28 11:22:21 CST 2012   ALTER TABLE MOVE SUBPARTITION MAY FAIL FOR
INTERVAL PARTITIONED TABLES
12326708   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULTS (WRONG TRANSACTION) WITH
MATERIALIZED TABLE FUNCTION
12328803   14474780  Wed Nov 28 11:22:21 CST 2012   BLOCKER FOR WAIT EVENT 'GC CURRENT REQUEST' NOT ID
ENTIFIED
12353494   14474780  Wed Nov 28 11:22:21 CST 2012   EXCESSIVE TRACE WRITTEN FOR LOG_ARCHIVE_TRACE=1
IN RFS TRACE FILE
12358083   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[KKQSFCS-1] DURING REWRITE OF QRY WITH
FUNCTIONAL INDEX'S VIRTUAL COLUMN
12387467   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE COULD CRASH WHEN SMART SCAN WAS
INTERRUPTED WHILE TABLESPACE IS BEING SHRUNK
12391034   14474780  Wed Nov 28 11:22:21 CST 2012   COREDUMP IS SEEN DURING RMAN BACKUP TO NFS MOUNT
12401111   14474780  Wed Nov 28 11:22:21 CST 2012   ERROR ORA-00600 [KDLIXFMCHECK] MAY BE SEEN JUST
AFTER ORA-1551 WAS THROWN
12425262   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-00600 [5400] REPORTED FOR PARALLEL INSERT ON
GLOBAL TEMP TABLES
12535346   14474780  Wed Nov 28 11:22:21 CST 2012   DML ON TABLE W/ RI AND INTERVAL PARTITIONED
PARENT TABLE MAY FAIL WITH SIGSEGV
12536287   14474780  Wed Nov 28 11:22:21 CST 2012   ODCITABLECLOSE CALLOUTS ARE NOT INVOKED IN PQ MODE
12539239   14474780  Wed Nov 28 11:22:21 CST 2012   SIGSEGV IN QSMQ_GET_SUMM_MFLAG WHILE DOING MV REFR
ESH
12556843   14474780  Wed Nov 28 11:22:21 CST 2012   IN MULTIBYTE DB, SQL PARSER SOMETIMES INCORRECTLY
REPORTS ORA-600 [QCPL.*] ERROR
12564614   14474780  Wed Nov 28 11:22:21 CST 2012   XDMG CANCELS DISK DROP WHEN CELLSRV TELLS ASM TO
REDISCOVER DISK
12582664   14474780  Wed Nov 28 11:22:21 CST 2012   DEDUPLICATION WITH SECUREFILES NOT WORKING AS EXPE
CTED
12583611   14474780  Wed Nov 28 11:22:21 CST 2012   EXCESSIVE ENQ;TX CONTENTION WITH HEAVY SECUREFILE
INSERT WORKLOAD ON RAC
12585543   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN BACKUP PERFORMANCE DROPS SIGNIFICANTLY AFTER
UPGRADE TO 11.2
12588744   14474780  Wed Nov 28 11:22:21 CST 2012   SECUREFILE WASTES STORAGE WHEN SPECIFY INITIAL EXT
ENT
12591252   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 WAS POSSIBLE DURING OPTIMIZATION OF
QUERIES USING ORDER BY WHILE REMOVING SORT USING
INDEX ACCESS
12591399   14474780  Wed Nov 28 11:22:21 CST 2012   PARTITION PRUNING FOR JOINS BETWEEN LOCAL
PARTITIONED TABLES AND REMOTE TABLES MAY FAIL
WITH INTERNAL ERRORS
12594032   14474780  Wed Nov 28 11:22:21 CST 2012   POSSIBLE MEMORY CORRUPTION WHEN USING CDC
EXTEND_WINDOW OR EXTEND_WINDOW_LIST
12596444   14474780  Wed Nov 28 11:22:21 CST 2012   CURSOR NOT SHARED WHEN CURSOR_SHARING=FORCE AND
SQL WITH CASE EXPRESSION
12612118   14474780  Wed Nov 28 11:22:21 CST 2012   CREATION OF MVIEW FOR A QUERY INVOLVING 'WITH',
'UNION ALL', 'ANSI JOIN' MIGHT DUMP CORE
12614359   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KSSDEL; BAD LIVE] MAY BE SEEN WHILE
INSERTING INTO SECUREFILE VIA JDBC
12617123   14474780  Wed Nov 28 11:22:21 CST 2012   SPLIT SUBPARTITION ON TABLE W/ CHILD
REFERENCE-PARTITIONED TABLE FAIL WITH ORA-1
12618817   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULTS WITH ABSOLUTE PARTITION-WISE JOIN
12620823   14474780  Wed Nov 28 11:22:21 CST 2012   SOL-SP64-11203;ASM INSTANCE HANG DURING CRS STACK
STARTING ON THE SECOND NODE
12621588   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-7445 [KOKSOPNHASOBJWTEMPLOB2()+39] WITH QUERY
CONTAINING LOTS OF ANSI JOINS
12625563   14474780  Wed Nov 28 11:22:21 CST 2012   STANDBY DB FAILS TO ADD DATAFILE WITH SYMBOLIC LIN
KS
12627504   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT WHERE THERE IS A JOIN BETWEEN TWO
REFERENCE PARTITIONED TABLES MAY CAUSE INTERNAL ER
ROR
12628286   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[15800] IS SEEN DUE TO INCORRECT
COMPUTATION OF KXFQR FOR PARTIION KEY
DISTRIBUTION TABLE QUEUE.
12637294   14474780  Wed Nov 28 11:22:21 CST 2012   BLOOM PARTITION PRUNING MAY CAUSE DEADLOCK ORA-60
12641849   14474780  Wed Nov 28 11:22:21 CST 2012   CUSTOMER MIGHT RECEIVE AN INTERNAL ERROR IF
CHANNEL CLEANUP FAILS AFTER ANOTHER ERROR IS SIGNA
LLED.
12646784   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KKPOFFOC] MAY BE SEEN WHILE ADDING A
COLUMN TO A TABLE WITH LOB COLUMN
12655301   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [13013] FROM MERGE WITH ADD COL OPTIMIZATI
ON
12656535   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1555 DURING DIRECT PATH READ OF SECUREFILE LOB
12658411   14474780  Wed Nov 28 11:22:21 CST 2012   SETTING RESULT CACHE TO A VALUE HIGHER THAN 1G
COULD LEAD TO INSTANCE HANG
12662040   14474780  Wed Nov 28 11:22:21 CST 2012   SECUREFILE LOB SEGMENT KEEPS GROWING IN CASE OF
PLENTY OF FREE SPACE
12672969   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY INVOLVING ORDER-BY CLAUSE DUMPS CORE IF
ORDER-BY ELIMINATION IS ENABLED
12675009   14474780  Wed Nov 28 11:22:21 CST 2012   INPUT_BYTES AND OUTPUT_BYTES COLUMN NOT ACCURATE
IN V$RMAN_BACKUP_JOB_DETAILS VIEW
12678920   14474780  Wed Nov 28 11:22:21 CST 2012   CONCURRENT SPLIT/MERGE,DROP PARTITION OPERATIONS
ON TABLE MAY FAIL WITH SIGSEGV
12685263   14474780  Wed Nov 28 11:22:21 CST 2012   NEED TO ASSERT WHEN ASM DETECTS IO BUFFER HARD
CHECK FAILURE
12693573   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH CPU W/ SPARSE IVAL PARTITIONS AND PART RANGE
ALL
12693626   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH CPU USAGE BY QUERY ON PARTITIONING KEY WITH
INTERVAL PARTITIONING
12698747   14474780  Wed Nov 28 11:22:21 CST 2012   ASM MAY HANG OR LEAKS MEMORY DUE TO MOP'S LEAK
12709059   14474780  Wed Nov 28 11:22:21 CST 2012   FIXES INTERNAL ERROR [KCBIVBR_2]
12714023   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULT OCCURS WHEN DYNAMIC SAMPLING IS DONE
12717125   14474780  Wed Nov 28 11:22:21 CST 2012   REBALANCE IS POKING EXTENT HOLES IN OFFLINE DISKS
EVEN WHEN DATA IS NOT MOVING
12718090   14474780  Wed Nov 28 11:22:21 CST 2012   LNX64-11203-RAC;DB FG RROC HIT ORA-00600[KCLCHKBLK
_3]
12723359   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY INVOLVING SUBQUERY WITH HAVING CLAUSE AND
AGGREGATES MAY LEAD TO CORE DUMP
12731940   14474780  Wed Nov 28 11:22:21 CST 2012   ANALYZE COMMAND ON TABLE WITH 'ADD COLUMN
OPTIMIZATION ENABLED' COLUMNS MAY FAIL
12734325   14474780  Wed Nov 28 11:22:21 CST 2012   PERFORMANCE ISSUE WHEN USING TIMESTAMP_TO_SCN
12748240   14474780  Wed Nov 28 11:22:21 CST 2012   Fix for Bug 12748240
12748538   14474780  Wed Nov 28 11:22:21 CST 2012   ONLINING DISKS IN ONE 11GR2 ASM DISK GROUP ABORTS
10GR2 DBS USING OTHER ASM DISK
12748795   14474780  Wed Nov 28 11:22:21 CST 2012   PARALLEL QUERY FAILS WITH ORA-600 [KKFDJOI;KKFDNPA
RT_DIM1]
12749597   14474780  Wed Nov 28 11:22:21 CST 2012   SAME TYPE IN TARGET SCHEMA GENERATES DIFFERENT
HASHCODE FROM SOURCE SCHEMA
12757532   14474780  Wed Nov 28 11:22:21 CST 2012   LOG FILE PARALLEL WRITE TAKES 300 SECONDS AFTER
SINGLE CELLSRV PROCESS DIES
12764337   14474780  Wed Nov 28 11:22:21 CST 2012   KGL ROUTINE HAS BEEN HITTING SIGSEGV WHILE
FETCHING AN OBJECT
12764658   14474780  Wed Nov 28 11:22:21 CST 2012   DBMS_STATS.GATHER_TABLE_STATS GATHERS INCORRECT
STATS FOR PARTITIONED TABLE
12766987   14474780  Wed Nov 28 11:22:21 CST 2012   INTERNAL TEST CONFIGURATION SUPPORT FOR EXADATA
12771704   14474780  Wed Nov 28 11:22:21 CST 2012   DISKMON SM QUERY DOES NOT WORK ON SOLARIS DB NODES
12772404   14474780  Wed Nov 28 11:22:21 CST 2012   SIGNIFICANT ROW CACHE OBJECTS LATCH CONTENTION
WHEN USING VPD
12778873   14474780  Wed Nov 28 11:22:21 CST 2012   COREDUMP IS SEEN IN KCLXPH WHILE QUERYING GV$POLIC
Y_HISTORY
12780098   14474780  Wed Nov 28 11:22:21 CST 2012   Fix for Bug 12780098
12780983   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-955 IS BEING HIT WHEN TRYING TO CREATE THE
INTERNALLY-GENERATED TYPE
12793917   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN CHANNEL IS TERMINATED WHILE SETTING UP BACKUP
12794025   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-12899 WHEN EXECUTING
DBMS_STATS.SET_TABLE_STATS WITH MULTI-BYTE OBJECT
NAME
12794305   14474780  Wed Nov 28 11:22:21 CST 2012   REDO SHIPMENT COULD FAIL AT THE STANDBY WITH ORA-6
00;[KRSR_PIC_COMPLETE.8]
12797420   14474780  Wed Nov 28 11:22:21 CST 2012   KGLHDGH CONTENTION ON THE DB INSTANCE HANDLE WHEN
CURSOR_SHARING IS SET TO FORCE
12797765   14474780  Wed Nov 28 11:22:21 CST 2012   SOL_SP64; AFTER ALL DISKS FAILURE, DG CAN'T BE
DISMOUNTED ON T2000-3
12829021   14474780  Wed Nov 28 11:22:21 CST 2012   COMMIT TO SWITCHOVER COULD FAIL WHEN USING THE
DATABASE FTP, HTTP OR NFS SERVERS
12831782   14474780  Wed Nov 28 11:22:21 CST 2012   ASYNC TRANSPORT PROCESS FAILS TO READ SECONDARY
MIRROR LOGFILE
12833442   14474780  Wed Nov 28 11:22:21 CST 2012   GATHERING CONCURRENT STATISTICS ON A TABLE WITH
SUB PARTITIONS IS VERY SLOW
12834027   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-00600 [KJBMPRLST;SHADOW] & [KJBRASR;PKEY] IN
A READ MOSTLY & SKIP LOCK ENV
12837280   14474780  Wed Nov 28 11:22:21 CST 2012   SHARED CURSOR MEMORY WAS LEAKING IN COMPLETE
REFRESH PROCESS
12842402   14474780  Wed Nov 28 11:22:21 CST 2012   APPLICATIONS CAN HANG ON DFS LOCK HANDLE WHEN
ACCESSING THE SAME ORDERED SEQUENCE OBJECT FROM 2
NODES IN THE CLUSTER.
12845115   14474780  Wed Nov 28 11:22:21 CST 2012   SELF DEADLOCKS ARE SEEN WHILE DROPPING MV
CONTAINER TABLE WITH SPECIAL INDEXES
12847466   14474780  Wed Nov 28 11:22:21 CST 2012   AROLTP-C; HANG SIGNATURE; 'GC CURRENT
REQUEST'<='GC BUFFER BUSY ACQUIRE'
12849688   14474780  Wed Nov 28 11:22:21 CST 2012   EXPORTING AND IMPORTING MAY CAUSE 'NEW VALUES'
CLAUSE WRONG
12861463   14474780  Wed Nov 28 11:22:21 CST 2012   RAC PERF; DEFAULT VALUE FOR
_LM_SINGLE_INST_AFFINITY_LOCK SHOULD BE FALSE
12865902   14474780  Wed Nov 28 11:22:21 CST 2012   NOWAIT LOCK REQUESTS COULD HANG
12866794   14474780  Wed Nov 28 11:22:21 CST 2012   EHCC DOES NOT SUPPORT INDEX MAINTENANCE ON DOMAIN
INDEXES FOR OCIDIRPATH
12873183   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY WITH ROWNUM IN SELECT LIST AND IN STOP
PREDICATE MAY RETURN WRONG RESULTS
12876939   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[15570] WAS POSSIBLE DURING PARALLEL
EXECUTION OF QUERIES WITH UNION ALL PUSHED
PREDICATE VIEWS ON THE RHS OF NL JOINS
12879027   14474780  Wed Nov 28 11:22:21 CST 2012   LMON PROCESS CAN GET STUCK IN THE DRM QUIESCE
STEP TRIGGERING PSEUDO RECONFIGURATION
12880299   14474780  Wed Nov 28 11:22:21 CST 2012   RAC TCP HANDLERS BLOCK IF LISTENER REGISTRATION
IS RESTRICTED TO IPC W/COST
12889054   14474780  Wed Nov 28 11:22:21 CST 2012   SNAPSHOT HANGS ON DC_OBJECTS ROW_CACHE_LOCK HELD
BY CTAS JOB
12894807   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT FOR UPDATE OVER A DB LINK ON ACTIVE
DATAGUARD STANDBY RAISES ORA-16000
12898733   14474780  Wed Nov 28 11:22:21 CST 2012   CONTROLFILE NOT CACHED IN FLASH CACHE LEADING TO
SLOW IO
12899094   14474780  Wed Nov 28 11:22:21 CST 2012   SMART SCAN WHEN EXECUTED IN SERIAL MODE MAY HAVE
A TAIL-OFF EFFECT IN SOME CASES
12899768   14474780  Wed Nov 28 11:22:21 CST 2012   PROCESSED MESSAGES REMAIN IN QUEUE CAUSING SPACE I
SSUES
12900077   14474780  Wed Nov 28 11:22:21 CST 2012   INCREASING VERSIONS COUNTS WITH BASELINE WHEN
_OPTIM_PEEK_USER_BINDS' = TRUE
12900964   14474780  Wed Nov 28 11:22:21 CST 2012   PERFORMANCE IMPROVEMENT FOR SERIAL SMART SCAN
12904429   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN DELETE ARCHIVELOG COMMAND TAKES LONG TIME
12905058   14474780  Wed Nov 28 11:22:21 CST 2012   REBOOT 2 CELL NODES, CHECKFILE FOUND CORRUPTION
BLOCK IN 3 UNDO DATAFILES
12910565   14474780  Wed Nov 28 11:22:21 CST 2012   SPAWNING MORE EMON SLAVES PROCESSES CAUSES DB
HANG ON SHUTDOWN
12912297   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [25026] WHEN INSERT INTO TEMPORARY TABLE
12913474   14474780  Wed Nov 28 11:22:21 CST 2012   DISABLED INVALID TABLE TRIGGER CAN STILL BLOCK DML
12917230   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY WITH TEMP TABLE TRANSFORMATION RUNS 5X
SLOWER WAITING FOR REMASTERING
12918738   14474780  Wed Nov 28 11:22:21 CST 2012   34708; DROPPING TABLE OF SECUREFILE LOB (CACHE)
IS VERY SLOW
12919564   14474780  Wed Nov 28 11:22:21 CST 2012   ENCOUNTERED ORA-600 [KTBESC_PLUGGED] WHILE
RUNNING APPS RTS
12922105   14474780  Wed Nov 28 11:22:21 CST 2012   PREVENT DISKMON CRASH DURING RAC SHUTDOWN
12923168   14474780  Wed Nov 28 11:22:21 CST 2012   CANNOT USE QUOTED FUNCTION NAME FOR VPD POLICY FUN
CTION
12924835   14474780  Wed Nov 28 11:22:21 CST 2012   KCFIS SHOULD RETURN CONTIGUOUS CORRUPT BLOCKS FOR
RMAN
12925089   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-4031 DURING PROCESS STARTUP SOME TIMES
ASSERTS WITH 'KSXP_RM_CHECK0'
12929644   14474780  Wed Nov 28 11:22:21 CST 2012   KCFIS TRANSLATIONS SHOULD BE MULTIPLE OF RDBMS
BLOCK SIZE
12938841   14474780  Wed Nov 28 11:22:21 CST 2012   11203_ASM_SOL_SP64;RACE BETWEEN ADD DISK AND
DISMOUNT MAY CAUSE KFGUSENUM01
12939232   14474780  Wed Nov 28 11:22:21 CST 2012   DUMPING HEADER OF TEMP FILES IN MOUNT MODE COULD
RAISE ORA-1157 AND ORA-1110
12944766   14474780  Wed Nov 28 11:22:21 CST 2012   DBFS PERFORMANCE ON EXTERNAL TABLES LOADING IS
VERY SLOW
12950644   14474780  Wed Nov 28 11:22:21 CST 2012   ASM INSTANCE CRASHES WITH ORA-07445
(KFDGLOBALOPEN) MESSAGE IN THE ASM ALERT.LOG
12950694   14474780  Wed Nov 28 11:22:21 CST 2012   UTL_RECOMP FOR SPECIFIC DATABASE EDITION
12953092   14474780  Wed Nov 28 11:22:21 CST 2012   INCORRECT RESULTS FOR QUERIES INVOLVING BLOOM
PRUNING AND CHAR COLUMNS
12959852   14474780  Wed Nov 28 11:22:21 CST 2012   INTERNAL ERROR RAISED IN BUFFER CACHE WHEN
PROCESSING A NESTED PING
12960279   14474780  Wed Nov 28 11:22:21 CST 2012   CORE DUMP IS SEEN IN STREAMS APPLY COODINATOR AS
TRANSACTION IS NOT IN THE UNASSIGNED TRANSACTION L
IST
12960455   14474780  Wed Nov 28 11:22:21 CST 2012   DB INSTANCE ABORT DUE TO ORA-600[KFFMXPGET]
12960925   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-932 ON OCISTMTEXECUTE AFTER ONLINE
REDEFINITION OF LONG TO CLOB COLUMN
12966665   14474780  Wed Nov 28 11:22:21 CST 2012   QUERIES WITH LOT OF JOINS MAY FAIL WITH INTERNAL
ERROR WHEN EVALUATION POSSIBILITY OF FULL
PARTITION WISE JOINS
12971388   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN BACKUP DOESN'T EMIT UNSTABLE WRITES VIA DNFS
12971775   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-0600 WHILE RUNNING PARALLEL DML WHILE ONLINE
INDEX IS CREATING
12974145   14474780  Wed Nov 28 11:22:21 CST 2012   CRASH IN THE EXTPROC PROCESS MAY BE SEEN WHEN
EXECUTING C CALLOUTS THAT RETURN OCINUMBER
12974860   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[QKEISEXPRREFERENCED1] SEEN WHEN
PROJECTION PUSHDOWN ENABLED ON MERGEJOIN
12976376   14474780  Wed Nov 28 11:22:21 CST 2012   MEMORY LEAK IN SHARED CURSOR LAYER; 'KKSFBC;HASH1'
12978794   14474780  Wed Nov 28 11:22:21 CST 2012   DBMS_FILE_TRANSFER FAILS THE HARD CHECKS TEST
WHEN THE SOURCE FILE CANNOT BE HARD-CHECKED AT
THE TARGET
12979199   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1466 WHEN A GLOBAL TEMPORARY TABLE IS QUERIED
FROM READ ONLY TXN
12983611   14474780  Wed Nov 28 11:22:21 CST 2012   UNDER RARE CIRCUMSTANCES ASYNC PROCESS CAN READ
THE LOG ENTRY WHILE LGWR IS MODIFYING IT.
12998795   14474780  Wed Nov 28 11:22:21 CST 2012   AROLTP-C; HANG SIGNATURE; 'GC CURRENT
REQUEST'<='GC BUFFER BUSY ACQUIRE'
13000553   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN BACKUP FAILS WITH RMAN-20999 ERROR AT
STANDBY DATABASE
13001379   14474780  Wed Nov 28 11:22:21 CST 2012   DATAPUMP TRANSPORT_TABLESPACES PRODUCES WRONG
METADATA FOR SOME TABLES
13004894   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY RETURNS WRONG RESULTS WITH A HASH JOIN IN
THE PLAN AND 10046 ENABLED
13022416   14474780  Wed Nov 28 11:22:21 CST 2012   PERFORMANCE IMPACT IN PASSTHRU MODE FOR SMART
SCAN ON EHCC TABLES
13023541   14474780  Wed Nov 28 11:22:21 CST 2012   INTERMITTENT CORE DUMP IN KNTXSLT FOR QUERIES ON
TABLE WITH MV LOG
13032258   14474780  Wed Nov 28 11:22:21 CST 2012   SMART SCAN MAY RESULT IN ORA-27618 EXTERNAL ERROR
WHEN THERE ARE LARGE NUMBER OF CONCURRENT SESSIONS
13035360   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-2303 WHEN TRYING TO CREATE A TYPE IN A CHILD
EDITION DUE TO PARENT EDITION DEPENDENCY
13035804   14474780  Wed Nov 28 11:22:21 CST 2012   CHANGE NONDESCRIPTIVE NUMBERS WHICH GIVE THE
REASON FOR PSEUDO RECONFIGURATION TO READABLE STRI
NGS
13036331   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1031 MAY BE SEEN WHILE GRANTING PRIVILEGES TO
A USER BY ANOTHER USER MULTIPLE TIMES
13040331   14474780  Wed Nov 28 11:22:21 CST 2012   MESSAGES NOT PROCESSED BY AQ TIME MANAGER
13041324   14474780  Wed Nov 28 11:22:21 CST 2012   HCC ON ZFS AND PILLAR STORAGE
13054713   14474780  Wed Nov 28 11:22:21 CST 2012   VERSION_COUNT OF KEPT STATEMENTS HAVING BINDS INCR
EASING
13059165   14474780  Wed Nov 28 11:22:21 CST 2012   EXEC OF UTLRP.SQL MAY RETURN INCORRECT COUNT FOR
'OBJECTS WITH ERRORS' RESULT
13063120   14474780  Wed Nov 28 11:22:21 CST 2012   INSERTS CAUSING HIGH DB FILE SEQUENTIAL READS
13070939   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY WITH SET OPERATION WITH A BIND VARIABLE IN
THE SELECT LIST RAISES ORA-1790 DURING DESCRIBE
ONLY EXECUTION
13079417   14474780  Wed Nov 28 11:22:21 CST 2012   EXTERNAL TABLE PREPROCESSOR SUPPORT FOR DATAPUMP
DUMP FILES
13080778   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-00942 RETURNED IN SQL ON MULTIPLE SCHEMAS DATA
BASE
13098318   14474780  Wed Nov 28 11:22:21 CST 2012   CTRL-C OR A SESSION KILL DURING DML INVOLVING
TEMP BLOCKS LEADS TO ORA-600[6856]
13099577   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1460 ERROR MAY BE SEEN IN PARALLEL QUERY
SERVERS DUE TO CURSOR SHARING ISSUE
13103913   14474780  Wed Nov 28 11:22:21 CST 2012   INSERT INTO A TABLE WITH AN UNUSABLE INDEX W/O
ANY SEGMENTS AND REBUILDING THE UNUSABLE INDEX
ONLINE IN PARALLEL RAISES INTERNAL ERROR.
13117043   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [13009] WAS RAISED FOR SELECT FOR UPDATE
INVOLVING HIERARCHIC QUERIES
13146182   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KDSGRP1] ERROR WHEN QUERYING A TABLE
WITH BITMAP INDEXES
13146719   14474780  Wed Nov 28 11:22:21 CST 2012   EVENT 10995 NEEDS TO BE SET ALWAYS IF MV DEFINING
QUERY LENGTH > 64K
13242070   14474780  Wed Nov 28 11:22:21 CST 2012   IMBALANCE IN NORMAL REDUNDANCY DISKGROUP WHILE
3RD QUORAM DISK IS IN SAME DG
13250244   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-4031 ERRORS SEEN WHEN PARAMETER
_KGHDSIDX_COUNT IS SET TO >1 DUE TO MEM LEAK
13253549   14474780  Wed Nov 28 11:22:21 CST 2012   FILE ALLOCATION FROM ONE ASM INSTANCE IS VERY SLOW
13256841   14474780  Wed Nov 28 11:22:21 CST 2012   COST BASED STAR TRANSFORMATION OF A QUERY WITH
DIMENSION TABLE COULD DUMP CORE
13257247   14474780  Wed Nov 28 11:22:21 CST 2012   AWR SNAPSHOTS COULD TAKE A LONG TIME, DUE TO AN
INSERT INTO WRH$_TEMPSTATXS USING A PROBLEMATIC PL
AN
13259364   14474780  Wed Nov 28 11:22:21 CST 2012   IN CASE OF LONG-LOB NULL SCENARIO FETCHING NULL
DATA MIGHT RAISE AN ERROR
13326736   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-959 RENAMING A TABLESPACE TO ALREADY DROPPED
TABLESPACE NAME
13328193   14474780  Wed Nov 28 11:22:21 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO THE INTEGRATED
EXTRACT COMPONENT OF ORACLE GOLDENGATE
13329145   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[KXFRGRADISTNUM3] ERROR MAY BE SEEN DUE TO
WRONG DECISION ON PARTITION LEVEL(DIMENSION) FOR
SLAVE MAPPING FOR PQ SLAVES
13332439   14474780  Wed Nov 28 11:22:21 CST 2012   UTL_RECOMP.RECOMP_PARALLEL CAN DEADLOCK IN AN
EDITIONED ENVIRONMENT
13338048   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1476 OCCURRED WHILE OUTPUTTING THE AWR REPORT
FOR STREAMS-RELATED SECTIONS
13340388   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KZAXPOPR14...] WHILE READING XML AUDIT
FILES WITH XML EXTENDED AUDITING
13340960   14474780  Wed Nov 28 11:22:21 CST 2012   MOUONT_DBFS.SH -FOUND POTENTIAL ERROR OR TIMEOUT
WHILE CHECKING STATUS
13343438   14474780  Wed Nov 28 11:22:21 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.1
13344323   14474780  Wed Nov 28 11:22:21 CST 2012   BUFFER BUSY WAIT TIMEOUT IN HIGH CONTENTION WORKLO
ADS
13345786   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[KJBMPCLO;CVT] SEEN WHEN CLOSING CLIENT
LOCK WITH NONZERO PISCN AT MASTER
13350245   14474780  Wed Nov 28 11:22:21 CST 2012   FALSE SCN CORRUPTIONS REPORTED FOR V7 BLOCKS IN 11
G
13352237   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KJCVG04] MAY BE SEEN DUE TO ENQUEUE LEAK
FOR ABORTED CHECKPOINTS
13354082   14474780  Wed Nov 28 11:22:21 CST 2012   REPLICATION FAIL TO RESUME AFTER ASM INST RESTART
ON STANDBY
13355095   14474780  Wed Nov 28 11:22:21 CST 2012   CONVENTIONAL INSERT IN PARALLEL INTO PARTITIONED
TABLE COULD CORRUPT LOCAL INDEX
13358531   14474780  Wed Nov 28 11:22:21 CST 2012   SLOWER PERFORMANCE ON MMON SLAVES ACQUIRING THE
THRESHOLD ENQUEUE
13358781   14474780  Wed Nov 28 11:22:21 CST 2012   THE FIELD DBA_HIST_SQLSTAT.CCWAIT_DELTA WAS
ALWAYS ZERO FROM 11.2 ONWARDS
13362079   14474780  Wed Nov 28 11:22:21 CST 2012   HCC SHOULD NOT BE ENABLED FOR NON ZFS/ PILLAR
STORAGE ARRAY
13364795   14474780  Wed Nov 28 11:22:21 CST 2012   TABLE SCAN ON EXADATA COULD FAIL TO LOOK FOR A
GOOD BLOCK FROM THE PHYSICAL STANDBY AFTER
FINDING A CORRUPT BLOCK
13366202   14474780  Wed Nov 28 11:22:21 CST 2012   DBNEWID DOESN'T ALLOW TARGET=/
13370330   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600[QKEISEXPRREFERENCED1] FROM QUERY W/
VIRTUAL COLUMN WITH A CONSTANT VALUE
13377816   14474780  Wed Nov 28 11:22:21 CST 2012   DON'T SEND IN DIA0 IF SOCKET CLOSED - HANDLE
FAILURE APPROPRIATELY
13384182   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [DELROW;IOT1] RAISED FOR DELETE OR
MERGE..DELETE SQL
13384397   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULT WITH STAR_TRANSFORMATION_ENABLED = TR
UE
13385346   14474780  Wed Nov 28 11:22:21 CST 2012   GCR0 TRACE FILES CONTINUOUSLY CREATED WITH
KJGCR_DELETESO MESSAGES
13388104   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1733 ERRORS WERE POSSIBLE DURING SELECT FOR
UPDATE OF CLOB COLUMNS FROM NESTED VIEWS
13395403   14474780  Wed Nov 28 11:22:21 CST 2012   LATCH 'ENQUEUE HASH CHAINS' CONTENTION ON
SECUREFILE BLOB
13397104   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE CRASH WITH ORA-600 [KJBLPKEYDRMQSCCHK;PKE
Y]
13397256   14474780  Wed Nov 28 11:22:21 CST 2012   ASM AND DISKMON MASTER HUNG AFTER A CELL WAS REBOO
TED
13399435   14474780  Wed Nov 28 11:22:21 CST 2012   KJFCDRMRCFG WAITED 249 SECS FOR LMD TO RECEIVE
ALL FTDONES, REQUESTING KILL
13419660   14474780  Wed Nov 28 11:22:21 CST 2012   UNSHARED DATAPUMP SESSION STATE THROUGH
DBMS_REDEFINITION CALLS CAUSE MEMORY LEAK
13419747   14474780  Wed Nov 28 11:22:21 CST 2012   GATHER STATS SESSION HUNG WITH WAIT EVENT 'ENQ;
KO FAST OBJECT CHECKPOINT'
13420224   14474780  Wed Nov 28 11:22:21 CST 2012   I/O ERROR DURING INSTANCE RECOVERY WHEN ONE OF
THE MIRRORS BECOMES UNAVAILABLE
13421009   14474780  Wed Nov 28 11:22:21 CST 2012   DBMS_CACHEUTIL STILL WON'T WORK WHEN
_GC_POLICY_TIME IS SET TO 0
13422949   14474780  Wed Nov 28 11:22:21 CST 2012   SELECTING COLUMNS WHICH WERE ADDED AFTER THE
TABLE WAS CREATED COULD DUMP CORE
13426605   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KGMGCHD1] SEEN IN RAC ENVIRONMENT
13429678   14474780  Wed Nov 28 11:22:21 CST 2012   UNDER RARE CIRCUMSTANCES PARALLEL OPERATIONS ON
OLTP COMPRESSED TABLES MAY CAUSE INTERNAL ERROR
13430938   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-4031 ERRORS WITH HIGH 'KTC LATCH SUBH' MEMORY
USAGE
13440068   14474780  Wed Nov 28 11:22:21 CST 2012   MEMORY LEAK OBSERVED IN DSKM_PROCESS_CMDLINE
13440516   14474780  Wed Nov 28 11:22:21 CST 2012   SKIP SCAN CAN NOT BE INTERRUPTED BY SHUTDOWN/CTRL-
C
13448206   14474780  Wed Nov 28 11:22:21 CST 2012   TOO MANY OCCURRENCES OF NOTE; ATTEMPTING VOTING
FILE REFRESH ON DISKGROUP
13454210   14474780  Wed Nov 28 11:22:21 CST 2012   UNRELEASED BUILD LOCK IN SOME ERROR CASES MAY
CAUSE HANG
13457537   14474780  Wed Nov 28 11:22:21 CST 2012   SPORADIC WRONG VALUES FROM SELECTS ON GV$ OBJECTS
ON RAC
13457582   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE CRASH DUE TO INTERNAL ERROR ORA-600
[KCLANTILOCK_8] IN LMS
13464002   14474780  Wed Nov 28 11:22:21 CST 2012   PREFETCH INVOLVING TEMP OBJECTS MAY CAUSE
INTERNAL ERROR
13466801   14474780  Wed Nov 28 11:22:21 CST 2012   CPUJAN2012 DATABASE 11.2.0.3
13467683   14474780  Wed Nov 28 11:22:21 CST 2012   JOIN OF TEMP AND PERMANENT TABLES IN RAC MIGHT
CAUSE CORRUPTION ON PERMANENT TABLES
13470240   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-7445 [QKSBGPARSELIST()] MAY BE SEEN DURING
DDL OPERATION
13471777   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-00600[4400] COULD OCCUR IN A TRANSACTION
USING MULTIPLE DATABASE LINKS
13476583   14474780  Wed Nov 28 11:22:21 CST 2012   DROPPING OF A DISK CAN CAUSE DISMOUNT OF
DISKGROUP IN OTHER ASM INSTANCES.
13477790   14474780  Wed Nov 28 11:22:21 CST 2012   QUERIES INVLOVING XMLFOREST OR XMLELEMENT SOME
TIMES DUMP CORE IN MEMORY RELATED FUNCTIONS
13478060   14474780  Wed Nov 28 11:22:21 CST 2012   BACKING UP CONTROL FILE CONCURRENTLY ON TWO
INSTANCES OF RAC GENERATES INTERNAL ERROR
13484963   14474780  Wed Nov 28 11:22:21 CST 2012   INVALID TTC BUFFER LENGTH IN CASE OF PROPAGATION
MAY RAISE ORA-3146
13492735   14474780  Wed Nov 28 11:22:21 CST 2012   DISALLOW ADDING NON-HCC DATAFILE TO HCC TABLESPACE
13495307   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT QUERY WITH ORAOLAP TABLE FUNCTION MAY FAIL
WITH INTENAL ERROR
13498646   14474780  Wed Nov 28 11:22:21 CST 2012   SQL*LOADER DIRECT PATH LOAD WITH 'SUBPARTITION
FOR' CLAUSE FAILS
13499128   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-001-CPUJAN2012
13502183   14474780  Wed Nov 28 11:22:21 CST 2012   VALID PACKAGE BODY IN CHILD EDITION MARKED AS
INVALID DURING UTL_RECOMP
13503598   14474780  Wed Nov 28 11:22:21 CST 2012   ALLOW MECHANISM FOR REJECTING HIGH SCN BASED ON
DIFFERENCE IN SCN VALUES
13505390   14474780  Wed Nov 28 11:22:21 CST 2012   REPEATED ASSERTS ARE SEEN FOR A SQL DURING
DYNAMIC SAMPLING ON AN INTERVAL PARTITIONED TABLE
13506110   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY WITH EDITIONING VIEW AND SINGLE POLICY ON
BASE TABLE COULD CRASH
13515918   14474780  Wed Nov 28 11:22:21 CST 2012   VARCHAR2 ACCEPTS MORE THAN 4000 BYTES INSERTING
FROM DBLINK
13516727   14474780  Wed Nov 28 11:22:21 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO THE INTEGRATED
EXTRACT COMPONENT OF ORACLE GOLDENGATE
13524237   14474780  Wed Nov 28 11:22:21 CST 2012   UNNEEDED TEMPORARY TABLES CREATED FOR STAR TRANSFO
RMATION
13524899   14474780  Wed Nov 28 11:22:21 CST 2012   LONG TURNAROUND TIME WAS OBSERVED WHILE EXECUTING
A QUERY DUE TO TEMP TABLES CREATION BY DB SERVER
13527323   14474780  Wed Nov 28 11:22:21 CST 2012   AWR REPORT GENERATION COULD FAIL WITH ORA-6502
WITH MULTIBYTE CHARS IN SQL TEXT
13528551   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-002-CPUJAN2012
13533487   14474780  Wed Nov 28 11:22:21 CST 2012   CLOSE CALLOUT NOT INVOKED INTERMITTENTLY FOR
PARALLEL TABLE FUNCTION QUERIES
13534412   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KCLCHKBLKDMA_3] IS SEEN AS LE BSCN IS
UPDATED WITH NEWED SCN
13544396   14474780  Wed Nov 28 11:22:21 CST 2012   INTERNAL ERROR IS SEEN IN QUERIES OR DML ON A
TABLE AFTER ALTERING CLOB COLUMN TO LONG
13548053   14474780  Wed Nov 28 11:22:21 CST 2012   UNDER HEAVY LOAD DROP TABLE STATEMENT MAY LEAD TO
ORA-00600 [12869]
13550185   14474780  Wed Nov 28 11:22:21 CST 2012   QUERIES ON V$SQLSTATS MAY CAUSE CRASH OR HANG
13553883   14474780  Wed Nov 28 11:22:21 CST 2012   WHEN THE ARCHIVE PROCESS IS UNABLE TO ARCHIVE
REDO LOG FILES, IT DOES NOT PROVIDE A STANDARD
ERROR IN THE ALERT LOG FILE
13554409   14474780  Wed Nov 28 11:22:21 CST 2012   Fix for Bug 13554409
13564720   14474780  Wed Nov 28 11:22:21 CST 2012   SEVERE PERFORMANCE DEGRADATION WITH TURNING ON FGA
.
13566938   14474780  Wed Nov 28 11:22:21 CST 2012   DML WITH BINDS ON A REFERENCE PARTITIONED TABLE
MAY RAISE ORA-600 [KCBGTCR_1]
13572659   14474780  Wed Nov 28 11:22:21 CST 2012   DBMS_REDEFINITION DISABLES FKS USED FOR REFERENCE
PARTITIONING
13575265   14474780  Wed Nov 28 11:22:21 CST 2012   PARSING ERROR IN CHECK_LOB_POLICYAUTH WHEN
USERNAME/TABLE NAME IS 30 CHARACTERS
13579992   14474780  Wed Nov 28 11:22:21 CST 2012   CREATION OF IN MEMORY TEMPORARY TABLE PRODUCES
TOO MUCH RECURSIVE SQL
13580513   14474780  Wed Nov 28 11:22:21 CST 2012   RETRY TIMEOUT OF SNAPSHOT CONTROLFILE ENQUEUE IS
NOT ONE HOUR
13584130   14474780  Wed Nov 28 11:22:21 CST 2012   COMPILING LIBRARY UNIT WITH _LOAD_WITHOUT_COMPILE
IN NON-BASE EDITION CAUSES CRASH
13588248   14474780  Wed Nov 28 11:22:21 CST 2012   SOMETIMES CORE DUMP IS SEEN IN RAC ENV WITH
SESSION POOLING, DRCP, FLASH CACHE, SERVER CACHE
AND AC ENABLED
13599864   14474780  Wed Nov 28 11:22:21 CST 2012   PERFORMANCE OF RMAN BACKUPS FROM AN EXADATA TO A
ZFSSA IS SLOW
13612575   14474780  Wed Nov 28 11:22:21 CST 2012   PROCEDURES RETURNING REFCURSOR BIND VARIABLES MAY
HIT ORA-600 [15419]
13624984   14474780  Wed Nov 28 11:22:21 CST 2012   DATAPUMP HANGS ON PACKAGE BODY COMPILATION
LIBRARY CACHE PIN
13629056   14474780  Wed Nov 28 11:22:21 CST 2012   PARALLEL INSERT AS SELECT FAILED W/ ORA-29771
13632717   14474780  Wed Nov 28 11:22:21 CST 2012   CPUAPR2012 DATABASE 11.2.0.3
13632809   14474780  Wed Nov 28 11:22:21 CST 2012   RMAN BZ2 COMPRESSION BACKUP HANGS
13642207   14474780  Wed Nov 28 11:22:21 CST 2012   ENABLE IN-MEMORY PQ OPTIMIZATIONS FOR HCC
13645917   14474780  Wed Nov 28 11:22:21 CST 2012   PMON ONLINE BLOCK RECOVERY IN LOOP COULD LEAD TO
INSTANCE HANG
13649031   14474780  Wed Nov 28 11:22:21 CST 2012   WHEN SHRINK ON PARTITIONED TABLE WHICH CONTAINS
PARTITIONS WITH DEFERRED SEGMENT MAY CAUSE ERROR
13652437   14474780  Wed Nov 28 11:22:21 CST 2012   ADDRESSES SEVERAL CRITICAL PERFORMANCE AND
CORRECTNESS ISSUES RELATED TO INTEGRATED EXTRACT
COMPONENT OF ORACLE GOLDENGATE
13657605   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KKZGBTCOLS] DURING BUILD DEFERRED REMOTE
WITH ROWID MV CREATION
13687870   14474780  Wed Nov 28 11:22:21 CST 2012   DBWR RECONNECTS TO CELLSRV UNDER HEAVY LOAD
13696023   14474780  Wed Nov 28 11:22:21 CST 2012   FIX OF BUG;12765572 CAUSE I/O PERFORMANCE DOWN
13696216   14474780  Wed Nov 28 11:22:21 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.2 (INCLUDES
CPU APR2012)
13699124   14474780  Wed Nov 28 11:22:21 CST 2012   AWR COMPARE PERIOD; SPINNING WHEN QUERYING DIFF
OF KEY INSTANCE STATS
13700577   14474780  Wed Nov 28 11:22:21 CST 2012   PARALLEL LOAD INTO HCC TABLE W/ HWM BROKERING
ENABLED MAY HIT ORA-600[KDBLDDR_2]
13705338   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULTS ON IOT SECONDARY INDEX THROUGH JOIN
13711695   14474780  Wed Nov 28 11:22:21 CST 2012   IN RARE CASES INTERNAL ERROR RAISED WHEN CHECKING
FOR CLUSTER CONFIGUARATION.
13717748   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULT WITH SIMPLE SELECT ON PARTITIONED TAB
LE
13718279   14474780  Wed Nov 28 11:22:21 CST 2012   DB INSTANCE TERMINATED DUE TO ORA-29770 WHEN
_GC_DEFER_TIME IS SET TO 1MS
13718476   14474780  Wed Nov 28 11:22:21 CST 2012   IGNORE PRED BAST TO EXCLUSIVE LOCK
13719081   14474780  Wed Nov 28 11:22:21 CST 2012   UPGRADE INVALIDATE VIEWS IS SLOW
13719292   14474780  Wed Nov 28 11:22:21 CST 2012   DB UPGRADE MAY TAKE LONGER WHEN ARCHIVELOG MODE
AND SUPPLEMENTAL LOGGING ENABLED
13720544   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULTS ON UPDATE WITH PARALLEL DML
13724193   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-01089 FROM REMOTE DATABASE, EVEN THOUGH THE
DB IS NOT SHUTTING DOWN
13725395   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH WATER MARK BROKERED LOAD INTO AN HCC TABLE
COULD LEAD TO INTERNAL ERROR
13732226   14474780  Wed Nov 28 11:22:21 CST 2012   NODE GETS EVICTED WITH REASON CODE 0X2
13737746   14474780  Wed Nov 28 11:22:21 CST 2012   BACKGROUND MEDIA RECOVERY COULD BE TERMINATED DUE
TO ORA-600[KRR_ASSEMBLE_CV_12]
13742433   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-004-CPUAPR2012
13742434   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-005-CPUAPR2012
13742435   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-006-CPUAPR2012
13742436   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-007-CPUAPR2012
13742437   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-008-CPUAPR2012
13742438   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-009-CPUAPR2012
13742464   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-003-CPUAPR2012
13743987   14474780  Wed Nov 28 11:22:21 CST 2012   ASM INSTANCE TERMINATES WITH DR CHANGE IN CPU
COUNT PARALLE_MAX_SERVERS
13767790   14474780  Wed Nov 28 11:22:21 CST 2012   EXADATA AUTOMATION MANAGER MAY NOT AUTO ONLINE
DISKS THAT ARE ADDED TO DISKGROUP WITH FORCE OPTIO
N
13769887   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KRVUATLA20] SEEN WITH SIMULATED LOG FILE
CORRUPTION
13772618   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-010-CPUAPR2012
13773133   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KTSFLMERGE-CYCLE-1] DURING INSERTS INTO
FREELIST MANAGED SEGMENT
13775960   14474780  Wed Nov 28 11:22:21 CST 2012   LATCH ENQUEUE CONTENTION SEEN IN DELETE/INSERT SF
WORKLOAD AFTER 13395403
13780816   14474780  Wed Nov 28 11:22:21 CST 2012   UTL_RECOMP LEAVES DEPENDENT MATERIALIZED VIEW INVA
LID
13784384   14474780  Wed Nov 28 11:22:21 CST 2012   NO CONSTRAINT TO BE INHERITED BY TEMP TABLE
CREATED DURING STATS COLLECTION
13786142   14474780  Wed Nov 28 11:22:21 CST 2012   DROP TRIGGER IN EDITIONING ENVIRONMENT COULD FAIL
WITH ORA-4045/ORA-4098
13786778   14474780  Wed Nov 28 11:22:21 CST 2012   WRONG RESULTS WITH USING THE INDEX_COMBINE HINT
13787482   14474780  Wed Nov 28 11:22:21 CST 2012   CDC PURGE ROUTINE INVALIDATING CUSTOM INDEXES
13790109   14474780  Wed Nov 28 11:22:21 CST 2012   REFRESH RETURN WRONG RESULTS FOR ON-COMMIT MV
WITH ROLLUP
13801740   14474780  Wed Nov 28 11:22:21 CST 2012   IMBALANCE IN NUMBER OF WORKING SETS PER DBWR ON
NUMA X2-8 10 CORES
13804294   14474780  Wed Nov 28 11:22:21 CST 2012   INTERNAL ERRORS, CORRUPTIONS, USING PIPELINED
FUNCTION WHOSE ROWS CAUSE ERRS
13811172   14474780  Wed Nov 28 11:22:21 CST 2012   DBMS_DBVERIFY MAY FAIL WITH DBV-111; OCI FAILURE
(4157) ORA-600 [KUDBVSLFW1]
13814905   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE CRASHED WITH ORA-7445 [KQLMBIVG()+711]
IN LCK0
13816397   14474780  Wed Nov 28 11:22:21 CST 2012   PST; TRIGGER TOOMANYOFFLINES WHEN DEGENERATE &
SUFFICIENT FAILGROUPS SEEN
13839641   14474780  Wed Nov 28 11:22:21 CST 2012   INCORRECT ENTRIES FOR DESCRIPTION COLUMN IN DBA_TR
IGGERS
13851078   14474780  Wed Nov 28 11:22:21 CST 2012   PQ SLAVES EXECUTING SAME STMT REFERENCING PL/SQL
FUNCTION COULD LEAD TO DEADLOCK
13863326   14474780  Wed Nov 28 11:22:21 CST 2012   UPDATE TABLE ERRORS WITH ORA-00942 EVEN THOUGH
TABLE DOES IN FACT EXIST.
13871495   14474780  Wed Nov 28 11:22:21 CST 2012   IMPROVE ASM OFFLINE HANDLING AFTER CELL FAILURE
13871547   14474780  Wed Nov 28 11:22:21 CST 2012   REDUCE DISKMON->SLAVE DISKMON NOTIFICATION
LATENCY ON CELL FAILURE
13879553   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT QUERY WITH 'FOR UPDATE', 'CONNECT BY' AND
'ORDER BY' CLAUSE MAY CAUSE INTERNAL ERROR
13880971   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-1779 FALSE DETECTION OF NON KEY-PRESERVED
TABLE IN CORRECT UPDATE STATEMENT
13882317   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH CACHE BUFFERS CHAINS LATCH CONTENTION DURING
IN-MEMORY PQ SCAN
13887875   14474780  Wed Nov 28 11:22:21 CST 2012   DEADLOCK WHILE ADDING A USER TO RESOURCE GROUP,
WHILE GATHER_STATS IS RUNNING
13901039   14474780  Wed Nov 28 11:22:21 CST 2012   LONG BUFFER BUSY WAITS WHEN LOST WRITE PROTECTION
IS ENABLED
13903046   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [4417] WHILE PERFORMING BLOCK CLEANOUTS
ON HCC COMPRESSED TABLE BLOCKS
13906496   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [15800] MAY BE SEEN WHILE CREATING THE
PARTITION TABLE
13910420   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-8103 DURING UPDATE OF BASICFILE CLOB IN ASSM
SEGMENT USING SPACE SEARCH CACH
13911821   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE TERMINATION DUE A CRASH HIT BY PMON IN
SHARED CURSORS CODE
13912192   14474780  Wed Nov 28 11:22:21 CST 2012   PQ SLAVES COULD RAISE ORA-942 FOR QUERY W/
SUBQUERY PARTITION PRUNING,TEMP TABLE
13912642   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [504] [TABLESPACE KEY CHAIN] WITH KCBI
FUNCTIONS ON THE STACK
13913630   14474780  Wed Nov 28 11:22:21 CST 2012   COMPRESSION OLTP; INSERT ... SELECT DOESN'T
COMPRESS SOME ROWS
13916709   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH SCN INCREASE RATE DUE TO CURSOR INVALIDATION
OF A LONG RUNNING QUERY
13917937   14474780  Wed Nov 28 11:22:21 CST 2012   INSTANCE MAY CRASH WITH ORA-7445 [KQLMBIVG()...]
WHILE INVALIDATING A TEMP TABLE
13918644   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-07445 ON RAC WITH AUDIT_SYS_OPERATIONS=TRUE
DOING CREATE TEXT INDEX PARALLEL
13923374   14474780  Wed Nov 28 11:22:21 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.3 (INCLUDES
CPU JUL2012)
13929853   14474780  Wed Nov 28 11:22:21 CST 2012   PARALLEL DDL FAILS IN 'HYBRID COLUMNAR
COMPRESSION' TABLE
13936424   14474780  Wed Nov 28 11:22:21 CST 2012   SELECT FOR UPDATE NOT RETURNING VALUES FOR COL
ADDED WITH DEF VALUE & NOT NULL
13942462   14474780  Wed Nov 28 11:22:21 CST 2012   LOADING AN HCC TABLE IN PARALLEL WITH HWM
BROKERING LEADS TO ORA-600[KCBLRL_1]
13945708   14474780  Wed Nov 28 11:22:21 CST 2012   ATTEMPTS TO DROP VIEWS IN OLD EDITIONS RESULTS IN
ORA-04063
13958038   14474780  Wed Nov 28 11:22:21 CST 2012   EXCESS SPACE USAGE DURING UPDATE
13976144   14474780  Wed Nov 28 11:22:21 CST 2012   REDUCE NON-ANT TIMEOUT TO AVOID EVICTIONS AND
REDUCE BROWNOUT
13979519   14474780  Wed Nov 28 11:22:21 CST 2012   'ROW CACHE LOCK' WAITS ON DC_USERS IN RAC
13981051   14474780  Wed Nov 28 11:22:21 CST 2012   CORE DUMP IN TBSAFL MAY BE SEEN WHILE CREATING
TABLESPACE WITH COMPRESSION
13989185   14474780  Wed Nov 28 11:22:21 CST 2012   SWITCHOVER_STATUS IS TO STANDBY EVEN WHEN
MULTIPLE SESSIONS ARE ACTIVE @PRIMARY
13997862   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600; [KSFDCHKFOBRERR1] CAN HAPPEN IF A
PROCESS DOUBLE-CLOSES A DISK
14005749   14474780  Wed Nov 28 11:22:21 CST 2012   IMPDP FAILS TO IMPORT FUNCTION NAMES (HAVING =
CHAR) ASSOCIATED WITH VPD POLICY
14008285   14474780  Wed Nov 28 11:22:21 CST 2012   CLIENT NEEDS TO OPEN DISK WITH GUID INSTEAD OF PAT
H
14013094   14474780  Wed Nov 28 11:22:21 CST 2012   PARTITION ORDER IN INDEX DEFINITION IS DIFFERENT
THAN TABLE PARTITION
14014434   14474780  Wed Nov 28 11:22:21 CST 2012   CORRUPTION ON SECUREFILES USING WLS AND JDBC WITH
MULTIPLE FLUSH; BASICFILES OK
14016187   14474780  Wed Nov 28 11:22:21 CST 2012   PARALLEL CURSOR NOT SHARED DUE TO DEFAULT
PARALLEL DEGREE MISMATCH (PX_MISMATCH)
14029050   14474780  Wed Nov 28 11:22:21 CST 2012   MMAN FAILING TO DONATE GRANULES TO SHARED POOL
DESPITE UNUSED PGA ALLOWANCE
14034244   14474780  Wed Nov 28 11:22:21 CST 2012   CORRUPTION DUE TO STALENESS REGISTRY SLICE SHARING
14038787   14474780  Wed Nov 28 11:22:21 CST 2012   CPUJUL2012 DATABASE 11.2.0.3
14040433   14474780  Wed Nov 28 11:22:21 CST 2012   CURSORS NOT SHARED DUE TO DIFFERENT CALL DURATION
14041920   14474780  Wed Nov 28 11:22:21 CST 2012   FTP OF A FILE INTO DBFS MAY GET CROPPED FILE CONTE
NT
14042380   14474780  Wed Nov 28 11:22:21 CST 2012   ERRORS ARE SEEN WHEN INSTANT CLIENT OPENS DIAUS.MS
G
14050233   14474780  Wed Nov 28 11:22:21 CST 2012   RDBMS PATCH 4 FOR 11.2.0.3 FOR OGG INTEGRATED EXTR
ACT
14052474   14474780  Wed Nov 28 11:22:21 CST 2012   QUERY INVOLVING NULLIF'S WITH CONSTANT OPERANDS
IN JOIN MAY RETURN WRONG RESULTS
14052871   14474780  Wed Nov 28 11:22:21 CST 2012   RESOURCE MANAGER CANCEL_SQL WORKING PER
CUMULATIVE PER SESSSION, NOT PER CALL
14062792   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-011-CPUJUL2012
14062793   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-012-CPUJUL2012
14062794   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-013-CPUJUL2012
14062795   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-014-CPUJUL2012
14062796   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-015-CPUJUL2012
14062797   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-016-CPUJUL2012
14063280   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-017-CPUJUL2012
14063281   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-018-CPUJUL2012
14071518   14474780  Wed Nov 28 11:22:21 CST 2012   PROBLEMS WITH OPTIMIZER CURSOR SHARING DIAGNOSTICS
14076523   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KGXRELEASE-BAD-HOLDER] FROM PROCESS WITH
NO USER SESSION
14097127   14474780  Wed Nov 28 11:22:21 CST 2012   ADG STANDBY DOES NOT HONOR CELL STORAGE KEEP
14098382   14474780  Wed Nov 28 11:22:21 CST 2012   LOG CHANGES TO SHUTDOWN SERVICES;UPDATE
ASMDEACTIVATIONOUTCOME FOR EXTERNAL DGRP
14098509   14474780  Wed Nov 28 11:22:21 CST 2012   LMON SPINNING ON KJFCRCC CAUSES EVICTION DURING ST
ARTUP
14110275   14474780  Wed Nov 28 11:22:21 CST 2012   PARSE OF QUERY WITH TABLE THAT HAD UNDERGONE ADD
COLUMN MAY RAISE INTERNAL ERROR
14114792   14474780  Wed Nov 28 11:22:21 CST 2012   EXCHANGE SUBPARTITION COMMANDS TAKING LONG TO COMP
LETE
14125317   14474780  Wed Nov 28 11:22:21 CST 2012   BUFFER ALIGNMENT ISSUE WITH FIX FOR BUG 9782075
14132953   14474780  Wed Nov 28 11:22:21 CST 2012   RDBMS; WRITE-BACK FLASH CACHE RESILVERING
14143451   14474780  Wed Nov 28 11:22:21 CST 2012   ASM; WRITE-BACK FLASH CACHE RESILVERING
14144283   14474780  Wed Nov 28 11:22:21 CST 2012   DBFS NOT USING EXPIRED FREE SPACE IN A MULTI-NODE
ENVIRONMENT
14153033   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-01115 POSSIBLE DURING SMART SCAN IF THERE IS
OFFLINE DISK IN A MIRRORED DISK
14153464   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [15265] MAY BE SEEN WHEN THE RECYCLEBIN
FEATURE IS ENABLED
14174174   14474780  Wed Nov 28 11:22:21 CST 2012   PQ SLAVE STUCK IN DIRECT PATH WRITE AFTER OSSNET T
IMEOUT
14175146   14474780  Wed Nov 28 11:22:21 CST 2012   RDBMS PATCH 5 FOR 11.2.0.3 FOR OGG INTEGRATED EXTR
ACT
14176879   14474780  Wed Nov 28 11:22:21 CST 2012   EXTENSIVE GROWTH OF SECUREFILES SEGMENTS
UNDERGOING UPDATES
14198511   14474780  Wed Nov 28 11:22:21 CST 2012   MV LOG NOT PURGED WHEN ON DEMAND AND ON COMMIT MV
EXISTS ON SAME TABLE
14207317   14474780  Wed Nov 28 11:22:21 CST 2012   ROW CACHE OBJECTS LATCH CONTENTION DUE TO CURSORS
INVLOVING VPD AND NLS MISMATCH
14215134   14474780  Wed Nov 28 11:22:21 CST 2012   UNABLE TO USE THE RECNUM COLUMN TYPE IN A SQL
EXPRESSION WITH SQL*LOADER
14218148   14474780  Wed Nov 28 11:22:21 CST 2012   IORM PLAN REPUSH BROKEN FOR MULTI-LEVEL PLANS
14237793   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-01041 FOLLOWED BY ORA-03113 WHILE COMPILING FO
RM
14275605   14474780  Wed Nov 28 11:22:21 CST 2012   DATABASE PATCH SET UPDATE 11.2.0.3.4 (INCLUDES SPU
OCT2012)
14280879   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KTSIRCINFO_NUM1] FROM SEGMENT ADVISOR ON
CUBE-ORGANIZED TABLE
14287564   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [KGHSSTREAM_COPYN] WHEN EXCHANGING PARTITI
ON
14292825   14474780  Wed Nov 28 11:22:21 CST 2012   DEFAULT MEMORY PARAMETER VALUES FOR 11.2 ASM
INSTANCES LOW
14292987   14474780  Wed Nov 28 11:22:21 CST 2012   DISKMON DIED DUE TO SKGXP ASSERTION,
ORA-600[KSZSNDID3] ON ASM
14293031   14474780  Wed Nov 28 11:22:21 CST 2012   SKGZNP OSD IS NOT RETURNING PEER_DISCONNECT
14294123   14474780  Wed Nov 28 11:22:21 CST 2012   CSS FAILED TO STARTUP DUE TO GUID ISSUE AT OPEN
OSS DISK STEP
14299365   14474780  Wed Nov 28 11:22:21 CST 2012   RESYNC HITS ORA-15041 AND ORA-600 17090
14301592   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-7445 ERRORS CORRUPT BLOCKS SHIFTED BY 2 BYTES
IN BUFFER CACHE IN RECOVERY
14309390   14474780  Wed Nov 28 11:22:21 CST 2012   HIGH CPU USAGE WITH RECURSIVE STATEMENT ON FILE$
14314239   14474780  Wed Nov 28 11:22:21 CST 2012   ORA-600 [504] MAY BE SEEN IN RESILVERING IS ENABLE
D
14317360   14474780  Wed Nov 28 11:22:21 CST 2012   A SPATIAL QUERY UNDERGOING JPPD CRASHES AT QERIXGE
YKEY
14334353   14474780  Wed Nov 28 11:22:21 CST 2012   DATAPUMP; ORA 600 [KKDLINVHDLANDDEP0] DURING IMPDP
14390252   14474780  Wed Nov 28 11:22:21 CST 2012   DATABASE SECURITY PATCH UPDATE 11.2.0.3.0 - SPUOCT
2012
14409183   14474780  Wed Nov 28 11:22:21 CST 2012   SESSION HANGS ON GC BUFFER BUSY ACQUIRE
14467061   14474780  Wed Nov 28 11:22:21 CST 2012   FAILED INSTANCE RECOVERY MAY CAUSE ASM METADATA CO
RRUPTION/ORA-600[KFCRCVREAD10]
14473913   14474780  Wed Nov 28 11:22:21 CST 2012   SOURCE 11.2.0.2 TO TARGET 11.2.0.3, ISSUE OF TTC
PROTOCOL ERR WHEN USING DTYSTZ
14480674   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-019-CPUOCT2012
14480675   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-020-CPUOCT2012
14480676   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-021-CPUOCT2012
14506367   14474780  Wed Nov 28 11:22:21 CST 2012   AWR HAS INCORRECT STATS FOR PHYSICAL READS
OPTIMIZED WITH WRITE BACK FLASH
14548763   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-022-CPUOCT2012
14557588   14474780  Wed Nov 28 11:22:21 CST 2012   ORACLE_LOADER ACCESS DRIVER FAILS TO READ
MULTIPLE ORACLE_DATAPUMP DUMPFILES
14613900   14474780  Wed Nov 28 11:22:21 CST 2012   POSSIBLE CORE DUMP WHILE SCANNING FOR A CHILD FOR
SHARABLE CURSOR
14624146   14474780  Wed Nov 28 11:22:21 CST 2012   PMON MAY CRASH WHILE CLEANING UP TEMP TABLE STATE
SCN INFORMATION
14654284   14474780  Wed Nov 28 11:22:21 CST 2012   POSSIBLE MEMORY LEAK WHILE PROCESSING BINARYXML
14664355   14474780  Wed Nov 28 11:22:21 CST 2012   DB-11.2.0.3-MOLECULE-023-CPUOCT2012

------------------------------------------------------------------------------------------------------

OPatch succeeded.
...More

Top

Processes parameter for ASM instance

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: This avoids issues observed when ASM hits max # of processes. For < 10 instances per node,50 X (DB instances per node + 1) For > 10 instances per node,50 * MIN (# db instances per node +1, 11) + 10 * MAX (# db instance per node - 10, 0) This new formula accommodates the consolidation case where there are a lot of instances per node.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ASM processes parameter is set to recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - PROCESSES PARAMETER FOR ASM INSTANCE



Processes parameter set on +ASM1 = 1024
Number of RDBMS instances running = 1
Recommended value for Processes parameter for +ASM1 = 100

Status on dm01db02: PASS => ASM processes parameter is set to recommended value


Processes parameter set on +ASM2 = 1024
Number of RDBMS instances running = 1
Recommended value for Processes parameter for +ASM2 = 100

Top

Check for parameter recyclebin

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: "RECYCLEBIN = ON" provides higher availability by enabling the Flashback Drop feature. "ON" is the default value and should not be changed.
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => RECYCLEBIN is set to the recommended value

MCSDB1.recyclebin = on

Status on MCSDB2: PASS => RECYCLEBIN is set to the recommended value

MCSDB2.recyclebin = on

Top

Verify celldisk configuration on flash memory devices

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server celldisks is critical for optimal performance and outage avoidance. Each storage server contains four Sun Flash Accelerator F20 PCIe cards, each with four flash modules (FMods), for a total of 16 flash memory devices. On a storage server configured according to Oracle best practices, there should be 16 celldisks on flash memory devices with a status of "normal". The impact of verifying the basic storage server celldisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the basic storage server celldisk configuration is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the basic storage server celldisk configuration on flash memory devices, execute the following command as the "celladmin" user on each storage server: cellcli -e "list celldisk where disktype=flashdisk and status=normal" \| wc -l The output should be: 16 If the output is not as expected, execute the following command as the "celladmin" user: cellcli -e "list celldisk where disktype=flashdisk and status!=normal" Perform your root cause analysis and corrective actions starting with the status key words returned. Please reference the following: The "Maintaining Flash Disks" section of "Oracle® Exadata Database Machine, Owner's Guide 11g Release 2 (11.2), E13874-24"
Links	Note: 1348736.1 - Troubleshooting guide for Sick or underperforming storage cell/Performance Issue (Doc ID 1348736.1) - Note: 1348938.1 - Troubleshooting guide for Underperforming FlashDisks (Doc ID 1348938.1) -
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => The celldisk configuration on flash memory devices matches Oracle best practices


DATA FROM DM01CEL01 FOR VERIFY CELLDISK CONFIGURATION ON FLASH MEMORY DEVICES



name:              	 FD_00_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:51+08:00
deviceName:        	 /dev/sdr
devicePartition:   	 /dev/sdr
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 6ba2320c-94d9-4553-bb70-6dc56de0afba
interleaving:      	 none
lun:               	 1_0
physicalDisk:      	 1112M07TJA
size:              	 22.875G
status:            	 normal

name:              	 FD_01_dm01cel01

comment:
creationTime:      	 2012-11-28T10:30:51+08:00
deviceName:        	 /dev/sds
devicePartition:   	 /dev/sds
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 d36984ad-d354-44af-aa21-69a600d3e8c1
interleaving:      	 none
lun:               	 1_1
physicalDisk:      	 1112M07TJ7
size:              	 22.875G
status:            	 normal

name:              	 FD_02_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:52+08:00
deviceName:        	 /dev/sdt
devicePartition:   	 /dev/sdt
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 8e3fe247-5a58-4275-9d13-8deeb4eaa445
interleaving:      	 none
lun:               	 1_2
physicalDisk:      	 1101M06DH2
size:              	 22.875G
status:            	 normal

name:              	 FD_03_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:53+08:00
deviceName:        	 /dev/sdu
devicePartition:   	 /dev/sdu
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 ae8f0339-d64a-426b-83fd-6e7c415ead37
interleaving:      	 none
lun:               	 1_3
physicalDisk:      	 1112M07TKT
size:              	 22.875G
status:            	 normal

name:              	 FD_04_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:54+08:00
deviceName:        	 /dev/sdz
devicePartition:   	 /dev/sdz
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 77b1a549-7503-46d7-9202-df42d974e047
interleaving:      	 none
lun:               	 2_0
physicalDisk:      	 1108M079YL
size:              	 22.875G
status:            	 normal

name:              	 FD_05_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:54+08:00
deviceName:        	 /dev/sdaa
devicePartition:   	 /dev/sdaa
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 dcf3a3fa-a964-46db-a311-2fd4133fe4a3
interleaving:      	 none
lun:               	 2_1
physicalDisk:      	 1108M079YM
size:              	 22.875G
status:            	 normal

name:              	 FD_06_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:55+08:00
deviceName:        	 /dev/sdab
devicePartition:   	 /dev/sdab
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 2cb65507-cb38-4024-bafd-1c18fa2c8883
interleaving:      	 none
lun:               	 2_2
physicalDisk:      	 1101M06ELW
size:              	 22.875G
status:            	 normal

name:              	 FD_07_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:56+08:00
deviceName:        	 /dev/sdac
devicePartition:   	 /dev/sdac
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 53cf8aea-ca39-467e-bc01-aebfa5bf1e95
interleaving:      	 none
lun:               	 2_3
physicalDisk:      	 1101M06E0H
size:              	 22.875G
status:            	 normal

name:              	 FD_08_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:56+08:00
deviceName:        	 /dev/sdn
devicePartition:   	 /dev/sdn
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 0b73e42f-3c1e-4be0-b466-907aa965ee57
interleaving:      	 none
lun:               	 4_0
physicalDisk:      	 1108M0797P
size:              	 22.875G
status:            	 normal

name:              	 FD_09_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:57+08:00
deviceName:        	 /dev/sdo
devicePartition:   	 /dev/sdo
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 f7a010ee-1484-4a59-a889-ff2f8744d10e
interleaving:      	 none
lun:               	 4_1
physicalDisk:      	 1108M079F7
size:              	 22.875G
status:            	 normal

name:              	 FD_10_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:58+08:00
deviceName:        	 /dev/sdp
devicePartition:   	 /dev/sdp
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 1ef54f38-daca-4886-80bd-799a3d64b992
interleaving:      	 none
lun:               	 4_2
physicalDisk:      	 1112M07V99
size:              	 22.875G
status:            	 normal

name:              	 FD_11_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:58+08:00
deviceName:        	 /dev/sdq
devicePartition:   	 /dev/sdq
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 c930daca-f3a6-487d-b447-31411229d03f
interleaving:      	 none
lun:               	 4_3
physicalDisk:      	 1112M07V9E
size:              	 22.875G
status:            	 normal

name:              	 FD_12_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:59+08:00
deviceName:        	 /dev/sdv
devicePartition:   	 /dev/sdv
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 caa97047-a8b2-4860-b2a3-bf6de14bf5ed
interleaving:      	 none
lun:               	 5_0
physicalDisk:      	 1112M07UHV
size:              	 22.875G
status:            	 normal

name:              	 FD_13_dm01cel01
comment:
creationTime:      	 2012-11-28T10:31:00+08:00
deviceName:        	 /dev/sdw
devicePartition:   	 /dev/sdw
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 fc0a5cab-8835-43b8-88a9-75c9b4d7f534
interleaving:      	 none
lun:               	 5_1
physicalDisk:      	 1112M07UHU
size:              	 22.875G
status:            	 normal

name:              	 FD_14_dm01cel01
comment:
creationTime:      	 2012-11-28T10:31:01+08:00
deviceName:        	 /dev/sdx
devicePartition:   	 /dev/sdx
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 7edf4977-71e0-4274-b4f0-40f08aa38755
interleaving:      	 none
lun:               	 5_2
physicalDisk:      	 1105M06PYV
size:              	 22.875G
status:            	 normal

name:              	 FD_15_dm01cel01
comment:
creationTime:      	 2012-11-28T10:31:01+08:00
deviceName:        	 /dev/sdy
devicePartition:   	 /dev/sdy
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 b726f2b9-5e9e-4968-ab08-28efe79ea679
interleaving:      	 none
lun:               	 5_3
physicalDisk:      	 1112M07UFV
size:              	 22.875G
status:            	 normal




DATA FROM DM01CEL02 FOR VERIFY CELLDISK CONFIGURATION ON FLASH MEMORY DEVICES



name:              	 FD_00_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:51+08:00
deviceName:        	 /dev/sdr
devicePartition:   	 /dev/sdr
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 22819b6e-e16d-4864-8005-0a79618eff79
interleaving:      	 none
lun:               	 1_0
physicalDisk:      	 1112M07X5W
size:              	 22.875G
status:            	 normal

name:              	 FD_01_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:52+08:00
deviceName:        	 /dev/sds
devicePartition:   	 /dev/sds
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 a75bdf1c-4b84-4093-8a86-8e1bf8735922
interleaving:      	 none
lun:               	 1_1
physicalDisk:      	 1112M07U00
size:              	 22.875G
status:            	 normal

name:              	 FD_02_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:53+08:00
deviceName:        	 /dev/sdt
devicePartition:   	 /dev/sdt
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 955d55fb-e387-4285-bd41-e39dd6bc03e3
interleaving:      	 none
lun:               	 1_2
physicalDisk:      	 1112M07X6Q
size:              	 22.875G
status:            	 normal

name:              	 FD_03_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:53+08:00
deviceName:        	 /dev/sdu
devicePartition:   	 /dev/sdu
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 3c1738d6-5bc8-42f3-84a4-c3f8ec5666f4
interleaving:      	 none
lun:               	 1_3
physicalDisk:      	 1112M07X5X
size:              	 22.875G
status:            	 normal

name:              	 FD_04_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:54+08:00
deviceName:        	 /dev/sdz
devicePartition:   	 /dev/sdz
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 6284a092-0a6c-47d1-ba77-d1eb3c9423ad
interleaving:      	 none
lun:               	 2_0
physicalDisk:      	 1112M07U03
size:              	 22.875G
status:            	 normal

name:              	 FD_05_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:55+08:00
deviceName:        	 /dev/sdaa
devicePartition:   	 /dev/sdaa
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 a5bcdd7a-b8b0-4ae0-8a4e-ca3cf0d6b18d
interleaving:      	 none
lun:               	 2_1
physicalDisk:      	 1101M06EA9
size:              	 22.875G
status:            	 normal

name:              	 FD_06_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:55+08:00
deviceName:        	 /dev/sdab
devicePartition:   	 /dev/sdab
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 0e4b6ab0-838d-4983-b90c-0370e5e8dad2
interleaving:      	 none
lun:               	 2_2
physicalDisk:      	 1112M07U01
size:              	 22.875G
status:            	 normal

name:              	 FD_07_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:56+08:00
deviceName:        	 /dev/sdac
devicePartition:   	 /dev/sdac
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 24326ad1-d4aa-43e9-a56d-ad798138c616
interleaving:      	 none
lun:               	 2_3
physicalDisk:      	 1112M07U02
size:              	 22.875G
status:            	 normal

name:              	 FD_08_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:57+08:00
deviceName:        	 /dev/sdn
devicePartition:   	 /dev/sdn
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 c7db0545-2c0c-4744-8744-d6ea6b09c25b
interleaving:      	 none
lun:               	 4_0
physicalDisk:      	 1101M06DV2
size:              	 22.875G
status:            	 normal

name:              	 FD_09_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:58+08:00
deviceName:        	 /dev/sdo
devicePartition:   	 /dev/sdo
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 cd52cf2e-9dfa-4879-a979-f0ab187f1f80
interleaving:      	 none
lun:               	 4_1
physicalDisk:      	 1101M06DV3
size:              	 22.875G
status:            	 normal

name:              	 FD_10_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:58+08:00
deviceName:        	 /dev/sdp
devicePartition:   	 /dev/sdp
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 74b12341-0e5a-4e07-bd19-18de3ffcafcb
interleaving:      	 none
lun:               	 4_2
physicalDisk:      	 1101M06DYH
size:              	 22.875G
status:            	 normal

name:              	 FD_11_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:59+08:00
deviceName:        	 /dev/sdq
devicePartition:   	 /dev/sdq
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 f67902b3-8e28-401f-8c14-c361d4bf6bad
interleaving:      	 none
lun:               	 4_3
physicalDisk:      	 1101M06E6C
size:              	 22.875G
status:            	 normal

name:              	 FD_12_dm01cel02
comment:
creationTime:      	 2012-11-28T10:31:00+08:00
deviceName:        	 /dev/sdv
devicePartition:   	 /dev/sdv
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 6547b6c0-5273-4f59-a52d-0333e31ee42a
interleaving:      	 none
lun:               	 5_0
physicalDisk:      	 1101M06DQL
size:              	 22.875G
status:            	 normal

name:              	 FD_13_dm01cel02
comment:
creationTime:      	 2012-11-28T10:31:00+08:00
deviceName:        	 /dev/sdw
devicePartition:   	 /dev/sdw
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 d1a95442-c781-4236-847f-6fdbe17c9e61
interleaving:      	 none
lun:               	 5_1
physicalDisk:      	 1112M07WW8
size:              	 22.875G
status:            	 normal

name:              	 FD_14_dm01cel02
comment:
creationTime:      	 2012-11-28T10:31:01+08:00
deviceName:        	 /dev/sdx
devicePartition:   	 /dev/sdx
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 69e8a57c-bfb0-40c7-945f-4af531f73cb1
interleaving:      	 none
lun:               	 5_2
physicalDisk:      	 1101M06E6A
size:              	 22.875G
status:            	 normal

name:              	 FD_15_dm01cel02
comment:
creationTime:      	 2012-11-28T10:31:02+08:00
deviceName:        	 /dev/sdy
devicePartition:   	 /dev/sdy
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 db8fac88-71fd-4656-833b-2fe4963e31d9
interleaving:      	 none
lun:               	 5_3
physicalDisk:      	 1101M06DQM
size:              	 22.875G
status:            	 normal




DATA FROM DM01CEL03 FOR VERIFY CELLDISK CONFIGURATION ON FLASH MEMORY DEVICES



name:              	 FD_00_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:51+08:00
deviceName:        	 /dev/sdr
devicePartition:   	 /dev/sdr
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 75854a9d-43eb-4813-87cc-7105d7ec9dc6
interleaving:      	 none
lun:               	 1_0
physicalDisk:      	 1101M06EM1
size:              	 22.875G
status:            	 normal

name:              	 FD_01_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:52+08:00
deviceName:        	 /dev/sds
devicePartition:   	 /dev/sds
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 306fcb05-b08c-4e63-a280-deb6e40d020d
interleaving:      	 none
lun:               	 1_1
physicalDisk:      	 1101M06EM0
size:              	 22.875G
status:            	 normal

name:              	 FD_02_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:52+08:00
deviceName:        	 /dev/sdt
devicePartition:   	 /dev/sdt
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 e4cdb280-5898-463d-b2b3-ac92895c9553
interleaving:      	 none
lun:               	 1_2
physicalDisk:      	 1112M07V1T
size:              	 22.875G
status:            	 normal

name:              	 FD_03_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:53+08:00
deviceName:        	 /dev/sdu
devicePartition:   	 /dev/sdu
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 0a3fbc1b-766a-4ed0-86c5-505ff446b220
interleaving:      	 none
lun:               	 1_3
physicalDisk:      	 1112M07V1M
size:              	 22.875G
status:            	 normal

name:              	 FD_04_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:54+08:00
deviceName:        	 /dev/sdz
devicePartition:   	 /dev/sdz
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 53b770c9-5873-4d3d-8e83-240ac9b03e7f
interleaving:      	 none
lun:               	 2_0
physicalDisk:      	 1108M0796D
size:              	 22.875G
status:            	 normal

name:              	 FD_05_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:54+08:00
deviceName:        	 /dev/sdaa
devicePartition:   	 /dev/sdaa
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 c61396b1-e6f3-4591-a0e7-6e48c78c0bf6
interleaving:      	 none
lun:               	 2_1
physicalDisk:      	 1108M0795P
size:              	 22.875G
status:            	 normal

name:              	 FD_06_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:55+08:00
deviceName:        	 /dev/sdab
devicePartition:   	 /dev/sdab
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 caf9e8df-d860-4085-bc15-29ed514114a2
interleaving:      	 none
lun:               	 2_2
physicalDisk:      	 1108M0795N
size:              	 22.875G
status:            	 normal

name:              	 FD_07_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:56+08:00
deviceName:        	 /dev/sdac
devicePartition:   	 /dev/sdac
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 5aec34cd-189c-44ad-b362-50b5e8b511eb
interleaving:      	 none
lun:               	 2_3
physicalDisk:      	 1112M07UNC
size:              	 22.875G
status:            	 normal

name:              	 FD_08_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:57+08:00
deviceName:        	 /dev/sdn
devicePartition:   	 /dev/sdn
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 d12b2ffe-c9d0-4372-860e-f8eb47a69004
interleaving:      	 none
lun:               	 4_0
physicalDisk:      	 1112M0829D
size:              	 22.875G
status:            	 normal

name:              	 FD_09_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:57+08:00
deviceName:        	 /dev/sdo
devicePartition:   	 /dev/sdo
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 b0864ac8-dc87-4c03-8197-abd4b887aa00
interleaving:      	 none
lun:               	 4_1
physicalDisk:      	 1112M07YUR
size:              	 22.875G
status:            	 normal

name:              	 FD_10_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:58+08:00
deviceName:        	 /dev/sdp
devicePartition:   	 /dev/sdp
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 ae0eecbd-7c9a-493b-a06b-57bebf8fe17c
interleaving:      	 none
lun:               	 4_2
physicalDisk:      	 1112M07V67
size:              	 22.875G
status:            	 normal

name:              	 FD_11_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:59+08:00
deviceName:        	 /dev/sdq
devicePartition:   	 /dev/sdq
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 4540435c-caa0-4e29-b7c8-06ad39ebfca1
interleaving:      	 none
lun:               	 4_3
physicalDisk:      	 1112M0829E
size:              	 22.875G
status:            	 normal

name:              	 FD_12_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:59+08:00
deviceName:        	 /dev/sdv
devicePartition:   	 /dev/sdv
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 acd1215e-37ef-4348-96c3-a81538741f8c
interleaving:      	 none
lun:               	 5_0
physicalDisk:      	 1101M06EP1
size:              	 22.875G
status:            	 normal

name:              	 FD_13_dm01cel03
comment:
creationTime:      	 2012-11-28T10:31:00+08:00
deviceName:        	 /dev/sdw
devicePartition:   	 /dev/sdw
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 97d3a6f7-7286-4541-abc7-c8657617a271
interleaving:      	 none
lun:               	 5_1
physicalDisk:      	 1101M06EP0
size:              	 22.875G
status:            	 normal

name:              	 FD_14_dm01cel03
comment:
creationTime:      	 2012-11-28T10:31:01+08:00
deviceName:        	 /dev/sdx
devicePartition:   	 /dev/sdx
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 f2ce3a64-29db-4cbf-9bb8-8b71074019f1
interleaving:      	 none
lun:               	 5_2
physicalDisk:      	 1144M0AG24
size:              	 22.875G
status:            	 normal

name:              	 FD_15_dm01cel03
comment:
creationTime:      	 2012-11-28T10:31:02+08:00
deviceName:        	 /dev/sdy
devicePartition:   	 /dev/sdy
diskType:          	 FlashDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 047c7584-4237-498b-a87c-76775141c182
interleaving:      	 none
lun:               	 5_3
physicalDisk:      	 1144M0AG2T
size:              	 22.875G
status:            	 normal




...More

Top

Verify griddisk count matches across all storage servers where a given prefix name exists

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server griddisks is critical for optimal performance and outage avoidance. The impact of verifying the basic storage server griddisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the storage server griddisk configuration as designed is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the storage server griddisk count matches across all storage server where a given prefix name exists, execute the following command as the "root" userid on the database server from which the onecommand script was executed during initial deployment: for GD_PREFIX in `cellcli -e "list griddisk attributes name" \| cut -d" " -f2 \| gawk -F "_CD_" '{print $1}' \| sort -u`;do GD_PREFIX_RESULT=`cellcli -e list griddisk where name like \'$GD_PREFIX\_.\' \| wc -l \| cut -d" " -f2 \| sort -u \| wc -l`;if [ $GD_PREFIX_RESULT = 1 ]; then echo -e "$GD_PREFIX: SUCCESS";else echo -e $GD_PREFIX: FAILURE" cellcli -e list griddisk where name like \'$GD_PREFIX\_.\' \| wc -l";fi;done The output should be similar to: DATA_SLCC16: SUCCESS DBFS_DG: SUCCESS RECO_SLCC16: SUCCESS If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. NOTE: On a storage server configured according to Oracle best practices, the total number of griddisks per storage server for a given prefix name (e.g: DATA) should match across all storage servers where the given prefix name exists. NOTE: Not all storage servers are required to have all prefix names in use. This is possible where for security reasons a customer has segregated the storage servers, is using a data lifecycle management methodology, or an Oracle Storage Expansion Rack is in use. For example, when an Oracle Storage Expansion Rack is in use for data lifecycle management, those storage servers will likely have griddisks with unique names that differ from the griddisk names used on the storage servers that contain real time data, yet all griddisks are visible to the same cluster.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => The griddisk count matches across all storage servers where a given prefix name exists


DATA FROM DM01CEL01 FOR VERIFY GRIDDISK COUNT MATCHES ACROSS ALL STORAGE SERVERS WHERE A GIVEN PREFIX NAME EXISTS




DATA_DM01_CD_00_dm01cel01	 active
DATA_DM01_CD_01_dm01cel01	 active
DATA_DM01_CD_02_dm01cel01	 not present
DATA_DM01_CD_03_dm01cel01	 active
DATA_DM01_CD_04_dm01cel01	 active
DATA_DM01_CD_05_dm01cel01	 active
DATA_DM01_CD_06_dm01cel01	 active
DATA_DM01_CD_07_dm01cel01	 active
DATA_DM01_CD_08_dm01cel01	 active
DATA_DM01_CD_09_dm01cel01	 active
DATA_DM01_CD_10_dm01cel01	 active
DATA_DM01_CD_11_dm01cel01	 active
DBFS_DG_CD_02_dm01cel01	 not present
DBFS_DG_CD_03_dm01cel01	 active
DBFS_DG_CD_04_dm01cel01	 active

DBFS_DG_CD_05_dm01cel01	 active
DBFS_DG_CD_06_dm01cel01	 active
DBFS_DG_CD_07_dm01cel01	 active
DBFS_DG_CD_08_dm01cel01	 active
DBFS_DG_CD_09_dm01cel01	 active
DBFS_DG_CD_10_dm01cel01	 active
DBFS_DG_CD_11_dm01cel01	 active
RECO_DM01_CD_00_dm01cel01	 active
RECO_DM01_CD_01_dm01cel01	 active
RECO_DM01_CD_02_dm01cel01	 not present
RECO_DM01_CD_03_dm01cel01	 active
RECO_DM01_CD_04_dm01cel01	 active
RECO_DM01_CD_05_dm01cel01	 active
RECO_DM01_CD_06_dm01cel01	 active
RECO_DM01_CD_07_dm01cel01	 active
RECO_DM01_CD_08_dm01cel01	 active
RECO_DM01_CD_09_dm01cel01	 active
RECO_DM01_CD_10_dm01cel01	 active
RECO_DM01_CD_11_dm01cel01	 active




DATA FROM DM01CEL02 FOR VERIFY GRIDDISK COUNT MATCHES ACROSS ALL STORAGE SERVERS WHERE A GIVEN PREFIX NAME EXISTS




DATA_DM01_CD_00_dm01cel02	 active
DATA_DM01_CD_01_dm01cel02	 active
DATA_DM01_CD_02_dm01cel02	 active
DATA_DM01_CD_03_dm01cel02	 active
DATA_DM01_CD_04_dm01cel02	 active
DATA_DM01_CD_05_dm01cel02	 active
DATA_DM01_CD_06_dm01cel02	 active
DATA_DM01_CD_07_dm01cel02	 active
DATA_DM01_CD_08_dm01cel02	 active
DATA_DM01_CD_09_dm01cel02	 active
DATA_DM01_CD_10_dm01cel02	 active
DATA_DM01_CD_11_dm01cel02	 active
DBFS_DG_CD_02_dm01cel02	 active
DBFS_DG_CD_03_dm01cel02	 active
DBFS_DG_CD_04_dm01cel02	 active
DBFS_DG_CD_05_dm01cel02	 active
DBFS_DG_CD_06_dm01cel02	 active
DBFS_DG_CD_07_dm01cel02	 active
DBFS_DG_CD_08_dm01cel02	 active
DBFS_DG_CD_09_dm01cel02	 active
DBFS_DG_CD_10_dm01cel02	 active
DBFS_DG_CD_11_dm01cel02	 active
RECO_DM01_CD_00_dm01cel02	 active
RECO_DM01_CD_01_dm01cel02	 active
RECO_DM01_CD_02_dm01cel02	 active
RECO_DM01_CD_03_dm01cel02	 active
RECO_DM01_CD_04_dm01cel02	 active
RECO_DM01_CD_05_dm01cel02	 active
RECO_DM01_CD_06_dm01cel02	 active
RECO_DM01_CD_07_dm01cel02	 active
RECO_DM01_CD_08_dm01cel02	 active
RECO_DM01_CD_09_dm01cel02	 active
RECO_DM01_CD_10_dm01cel02	 active
RECO_DM01_CD_11_dm01cel02	 active




DATA FROM DM01CEL03 FOR VERIFY GRIDDISK COUNT MATCHES ACROSS ALL STORAGE SERVERS WHERE A GIVEN PREFIX NAME EXISTS




DATA_DM01_CD_00_dm01cel03	 active
DATA_DM01_CD_01_dm01cel03	 active
DATA_DM01_CD_02_dm01cel03	 active
DATA_DM01_CD_03_dm01cel03	 active
DATA_DM01_CD_04_dm01cel03	 active
DATA_DM01_CD_05_dm01cel03	 active
DATA_DM01_CD_06_dm01cel03	 active
DATA_DM01_CD_07_dm01cel03	 active
DATA_DM01_CD_08_dm01cel03	 active
DATA_DM01_CD_09_dm01cel03	 active
DATA_DM01_CD_10_dm01cel03	 active
DATA_DM01_CD_11_dm01cel03	 active
DBFS_DG_CD_02_dm01cel03	 active
DBFS_DG_CD_03_dm01cel03	 active
DBFS_DG_CD_04_dm01cel03	 active
DBFS_DG_CD_05_dm01cel03	 active
DBFS_DG_CD_06_dm01cel03	 active
DBFS_DG_CD_07_dm01cel03	 active
DBFS_DG_CD_08_dm01cel03	 active
DBFS_DG_CD_09_dm01cel03	 active
DBFS_DG_CD_10_dm01cel03	 active
DBFS_DG_CD_11_dm01cel03	 active
RECO_DM01_CD_00_dm01cel03	 active
RECO_DM01_CD_01_dm01cel03	 active
RECO_DM01_CD_02_dm01cel03	 active
RECO_DM01_CD_03_dm01cel03	 active
RECO_DM01_CD_04_dm01cel03	 active
RECO_DM01_CD_05_dm01cel03	 active
RECO_DM01_CD_06_dm01cel03	 active
RECO_DM01_CD_07_dm01cel03	 active
RECO_DM01_CD_08_dm01cel03	 active
RECO_DM01_CD_09_dm01cel03	 active
RECO_DM01_CD_10_dm01cel03	 active
RECO_DM01_CD_11_dm01cel03	 active




...More

Top

Verify total number of griddisks with a given prefix name is evenly divisible of celldisks

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server griddisks is critical for optimal performance and outage avoidance. The impact of verifying the storage server griddisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the storage server griddisk configuration as designed is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the total number of griddisks with a given prefix name is evenly divisible by the number of celldisks, execute the following command as the "celladmin" user on each storage server: CELLDISK_COUNT=`cellcli -e "list celldisk where disktype=harddisk" \| wc -l`; for GD_SHORT_NAME in `cellcli -e "list griddisk attributes name" \| awk -F "_CD_" '{print $1}' \| sort -u \| egrep -v "DBFS\|SYSTEM"`; do export GD_COUNT=`cellcli -e "list griddisk where name like '$GD_SHORT_NAME.'" \| wc -l`; if [ `expr $GD_COUNT % $CELLDISK_COUNT` = 0 ]; then echo -e "$GD_SHORT_NAME: SUCCESS" else echo -e "$GD_SHORT_NAME: FAILURE:"; cellcli -e "list griddisk attributes name where name like '$GD_SHORT_NAME\_.'"; fi; done; The output should be similar to: DATA_SLCC16: SUCCESS RECO_SLCC16: SUCCESS If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. NOTE: On a storage server configured according to Oracle best practices, the total number of all griddisks with a given name prefix (e.g: DATA) should be evenly divisible by the number of celldisks.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => The total number of griddisks with a given prefix name is evenly divisible by the number of celldisks


DATA FROM DM01CEL01 FOR VERIFY TOTAL NUMBER OF GRIDDISKS WITH A GIVEN PREFIX NAME IS EVENLY DIVISIBLE OF CELLDISKS




DATA_DM01:  SUCCESS
RECO_DM01:  SUCCESS




DATA FROM DM01CEL02 FOR VERIFY TOTAL NUMBER OF GRIDDISKS WITH A GIVEN PREFIX NAME IS EVENLY DIVISIBLE OF CELLDISKS




DATA_DM01:  SUCCESS
RECO_DM01:  SUCCESS





DATA FROM DM01CEL03 FOR VERIFY TOTAL NUMBER OF GRIDDISKS WITH A GIVEN PREFIX NAME IS EVENLY DIVISIBLE OF CELLDISKS




DATA_DM01:  SUCCESS
RECO_DM01:  SUCCESS




...More

Top

Verify griddisk ASM status

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server griddisks is critical for optimal performance and outage avoidance. The impact of verifying the storage server griddisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the storage server griddisk configuration as designed is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the storage server griddisk ASM status, execute the following command as the "celladmin" user on each storage server: ASM_STAT_RESLT=`cellcli -e "list griddisk attributes name,status, asmmodestatus,asmdeactivationoutcome" \| egrep -v ".\.\.\" \| wc -l`; if [ $ASM_STAT_RESLT = 0 ] then echo -e "\nSUCCESS\n" else echo -e "\nFAILURE:"; cellcli -e "list griddisk attributes name,status, asmmodestatus,asmdeactivationoutcome" \| egrep -v ".\.\.\"; echo -e "\n"; fi; The output should be: SUCCESS If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. NOTE: On a storage server configured according to Oracle best practices, all griddisks should have "status" of "active", "asmmodestatus" of "online" and "asmdeactivationoutcome" of "yes".
Needs attention on	dm01cel01
Passed on	dm01cel03, dm01cel02

Status on dm01cel01: FAIL => The griddisk ASM status should match specification


DATA FROM DM01CEL01 FOR VERIFY GRIDDISK ASM STATUS



DATA_DM01_CD_02_dm01cel01	 not present	 DROPPED	 Yes
DBFS_DG_CD_02_dm01cel01  	 not present	 DROPPED	 Yes
RECO_DM01_CD_02_dm01cel01	 not present	 DROPPED	 Yes

Status on dm01cel03, dm01cel02: PASS


DATA FROM DM01CEL02 FOR VERIFY GRIDDISK ASM STATUS



DATA_DM01_CD_00_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_01_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_02_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_03_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_04_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_05_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_06_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_07_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_08_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_09_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_10_dm01cel02	 active	 ONLINE	 Yes
DATA_DM01_CD_11_dm01cel02	 active	 ONLINE	 Yes
DBFS_DG_CD_02_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_03_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_04_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_05_dm01cel02  	 active	 ONLINE	 Yes

DBFS_DG_CD_06_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_07_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_08_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_09_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_10_dm01cel02  	 active	 ONLINE	 Yes
DBFS_DG_CD_11_dm01cel02  	 active	 ONLINE	 Yes
RECO_DM01_CD_00_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_01_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_02_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_03_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_04_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_05_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_06_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_07_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_08_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_09_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_10_dm01cel02	 active	 ONLINE	 Yes
RECO_DM01_CD_11_dm01cel02	 active	 ONLINE	 Yes




DATA FROM DM01CEL03 FOR VERIFY GRIDDISK ASM STATUS



DATA_DM01_CD_00_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_01_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_02_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_03_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_04_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_05_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_06_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_07_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_08_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_09_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_10_dm01cel03	 active	 ONLINE	 Yes
DATA_DM01_CD_11_dm01cel03	 active	 ONLINE	 Yes
DBFS_DG_CD_02_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_03_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_04_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_05_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_06_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_07_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_08_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_09_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_10_dm01cel03  	 active	 ONLINE	 Yes
DBFS_DG_CD_11_dm01cel03  	 active	 ONLINE	 Yes
RECO_DM01_CD_00_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_01_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_02_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_03_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_04_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_05_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_06_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_07_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_08_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_09_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_10_dm01cel03	 active	 ONLINE	 Yes
RECO_DM01_CD_11_dm01cel03	 active	 ONLINE	 Yes




...More

Top

Verify celldisk configuration on disk drives

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server celldisks is critical for optimal performance and outage avoidance. The impact of verifying the basic storage server celldisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the basic storage server celldisk configuration is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the basic storage server celldisk configuration on disk drives, execute the following command as the "celladmin" user on each storage server: cellcli -e "list celldisk where disktype=harddisk and status=normal" \| wc -l The output should be: 12 If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. NOTE: On a storage server configured according to Oracle best practices, there should be 12 celldisks on disk drives with a status of "normal".
Needs attention on	dm01cel01
Passed on	dm01cel03, dm01cel02

Status on dm01cel01: FAIL => The celldisk configuration on disk drives should match Oracle best practices


DATA FROM DM01CEL01 FOR VERIFY CELLDISK CONFIGURATION ON DISK DRIVES



name:              	 CD_00_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:40+08:00
deviceName:        	 /dev/sda
devicePartition:   	 /dev/sda3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 5e35f429-e6b8-422a-bde4-2705c82fe9bc
interleaving:      	 none
lun:               	 0_0
physicalDisk:      	 L45WSN
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal


name:              	 CD_01_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:44+08:00
deviceName:        	 /dev/sdb
devicePartition:   	 /dev/sdb3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 0fcd88af-4565-4a11-a3bc-06dcf1abfafa
interleaving:      	 none
lun:               	 0_1
physicalDisk:      	 L45TF8
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal

name:              	 CD_03_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:45+08:00
deviceName:        	 /dev/sdd
devicePartition:   	 /dev/sdd
diskType:          	 HardDisk
errorCount:        	 1
freeSpace:         	 0
id:                	 c8f50c15-8fbc-48ad-b4fb-c5c4e65d3fa9
interleaving:      	 none
lun:               	 0_3
physicalDisk:      	 L45SBG
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_04_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sde
devicePartition:   	 /dev/sde
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 01159ec8-47ae-449e-8828-9486083fb585
interleaving:      	 none
lun:               	 0_4
physicalDisk:      	 L45G1G
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_05_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sdf
devicePartition:   	 /dev/sdf
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 3950c739-3112-451e-8b48-2da15e747b19
interleaving:      	 none
lun:               	 0_5
physicalDisk:      	 L45T31
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_06_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:47+08:00
deviceName:        	 /dev/sdg
devicePartition:   	 /dev/sdg
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 51ef3d73-97fd-46b1-9433-d9d21a0f8a9d
interleaving:      	 none
lun:               	 0_6
physicalDisk:      	 L468GC
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_07_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:48+08:00
deviceName:        	 /dev/sdh
devicePartition:   	 /dev/sdh
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 57ca1bd6-d8a5-4769-a318-886b2e5948ee
interleaving:      	 none
lun:               	 0_7
physicalDisk:      	 L45WLA
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_08_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:48+08:00
deviceName:        	 /dev/sdi
devicePartition:   	 /dev/sdi
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 110309b0-e56d-4e93-9ac7-020848d9dfa4
interleaving:      	 none
lun:               	 0_8
physicalDisk:      	 L468RK
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_09_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdj
devicePartition:   	 /dev/sdj
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 47f57615-0e41-4868-bdcc-e990dd2a06a9
interleaving:      	 none
lun:               	 0_9
physicalDisk:      	 L46A1G
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_10_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdk
devicePartition:   	 /dev/sdk
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 236c5b48-fde6-4904-840b-1f7a1b7c3cda
interleaving:      	 none
lun:               	 0_10
physicalDisk:      	 L45ES8
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_11_dm01cel01
comment:
creationTime:      	 2012-11-28T10:30:50+08:00
deviceName:        	 /dev/sdl
devicePartition:   	 /dev/sdl
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 227ad49d-1159-4d30-aa8b-53cd957b19e2
interleaving:      	 none
lun:               	 0_11
physicalDisk:      	 L45RNA
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal




...More

Status on dm01cel03, dm01cel02: PASS


DATA FROM DM01CEL02 FOR VERIFY CELLDISK CONFIGURATION ON DISK DRIVES



name:              	 CD_00_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:41+08:00
deviceName:        	 /dev/sda
devicePartition:   	 /dev/sda3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 6901754a-39ff-4d2a-8777-d5a1ac70f914
interleaving:      	 none
lun:               	 0_0
physicalDisk:      	 L45T67
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal


name:              	 CD_01_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:45+08:00
deviceName:        	 /dev/sdb
devicePartition:   	 /dev/sdb3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 62a6a866-d3b4-49a1-a969-1d9d47ab4391
interleaving:      	 none
lun:               	 0_1
physicalDisk:      	 L39XQ0
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal

name:              	 CD_02_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:45+08:00
deviceName:        	 /dev/sdc
devicePartition:   	 /dev/sdc
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 fce82175-db23-4457-b6f1-3f85a49a61b5
interleaving:      	 none
lun:               	 0_2
physicalDisk:      	 L45WPM
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_03_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sdd
devicePartition:   	 /dev/sdd
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 1ece0370-f278-4d10-968b-866878d89ae8
interleaving:      	 none
lun:               	 0_3
physicalDisk:      	 L45F1X
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_04_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sde
devicePartition:   	 /dev/sde
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 1bb44196-833a-4e0f-8dbf-f4d1bfc9dda4
interleaving:      	 none
lun:               	 0_4
physicalDisk:      	 L45ERT
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_05_dm01cel02
comment:
creationTime:      	 2013-05-24T18:20:44+08:00
deviceName:        	 /dev/sdl
devicePartition:   	 /dev/sdl
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 23d9ebad-8d3e-4be0-bfda-c518f9ee2677
interleaving:      	 none
lun:               	 0_5
physicalDisk:      	 L32QX0
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_06_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:48+08:00
deviceName:        	 /dev/sdf
devicePartition:   	 /dev/sdf
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 e8d759f3-e816-4422-884e-d1a562f78f96
interleaving:      	 none
lun:               	 0_6
physicalDisk:      	 L46AGT
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_07_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:48+08:00
deviceName:        	 /dev/sdg
devicePartition:   	 /dev/sdg
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 37a99edc-93c3-423f-92e1-6aee65f47da2
interleaving:      	 none
lun:               	 0_7
physicalDisk:      	 L45WQQ
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_08_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdh
devicePartition:   	 /dev/sdh
diskType:          	 HardDisk
errorCount:        	 1
freeSpace:         	 0
id:                	 c8aeb87e-cfa3-4cfa-8087-29b490c57c84
interleaving:      	 none
lun:               	 0_8
physicalDisk:      	 L45G00
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_09_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdi
devicePartition:   	 /dev/sdi
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 34aa6de4-d642-493f-bf8b-a0613b2be35d
interleaving:      	 none
lun:               	 0_9
physicalDisk:      	 L3HSH2
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_10_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:50+08:00
deviceName:        	 /dev/sdj
devicePartition:   	 /dev/sdj
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 609edace-8b0d-4f4b-aa8b-e08cf2c155e7
interleaving:      	 none
lun:               	 0_10
physicalDisk:      	 L45TFW
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_11_dm01cel02
comment:
creationTime:      	 2012-11-28T10:30:51+08:00
deviceName:        	 /dev/sdk
devicePartition:   	 /dev/sdk
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 084aef7a-8222-4678-9c84-3d0ee52dc01b
interleaving:      	 none
lun:               	 0_11
physicalDisk:      	 L45RWF
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal




DATA FROM DM01CEL03 FOR VERIFY CELLDISK CONFIGURATION ON DISK DRIVES



name:              	 CD_00_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:41+08:00
deviceName:        	 /dev/sda
devicePartition:   	 /dev/sda3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 e8ea9daf-d38c-43f7-ad61-17899fb2f51f
interleaving:      	 none
lun:               	 0_0
physicalDisk:      	 L3V1QA
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal

name:              	 CD_01_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:44+08:00
deviceName:        	 /dev/sdb
devicePartition:   	 /dev/sdb3
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 98d600db-887d-4b88-a2bf-432e902171dc
interleaving:      	 none
lun:               	 0_1
physicalDisk:      	 L45ET0
raidLevel:         	 0
size:              	 1832.59375G
status:            	 normal

name:              	 CD_02_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:45+08:00
deviceName:        	 /dev/sdc
devicePartition:   	 /dev/sdc
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 1ef671b8-de75-4fab-b981-e3e795302076
interleaving:      	 none
lun:               	 0_2
physicalDisk:      	 L45RYM
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_03_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sdd
devicePartition:   	 /dev/sdd
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 61930bc2-268a-40f1-828e-311e2c05050a
interleaving:      	 none
lun:               	 0_3
physicalDisk:      	 L45BNE
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_04_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:46+08:00
deviceName:        	 /dev/sde
devicePartition:   	 /dev/sde
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 5c2f9904-052d-4772-b59f-a790546ca004
interleaving:      	 none
lun:               	 0_4
physicalDisk:      	 L46AAN
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_05_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:47+08:00
deviceName:        	 /dev/sdf
devicePartition:   	 /dev/sdf
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 2a9b49c2-981e-418a-842e-39918a58900f
interleaving:      	 none
lun:               	 0_5
physicalDisk:      	 L45WC1
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_06_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:47+08:00
deviceName:        	 /dev/sdg
devicePartition:   	 /dev/sdg
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 99efa242-e49e-41eb-83ce-e62248b0c4a5
interleaving:      	 none
lun:               	 0_6
physicalDisk:      	 L45RNP
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_07_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:48+08:00
deviceName:        	 /dev/sdh
devicePartition:   	 /dev/sdh
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 9294f089-b646-49b8-b392-498f6d62ec66
interleaving:      	 none
lun:               	 0_7
physicalDisk:      	 L45SP5
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_08_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdi
devicePartition:   	 /dev/sdi
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 d4661a58-da83-481e-8410-8d4613b9e56a
interleaving:      	 none
lun:               	 0_8
physicalDisk:      	 L46889
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_09_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:49+08:00
deviceName:        	 /dev/sdj
devicePartition:   	 /dev/sdj
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 f21a3d5e-1d9b-4d4c-8839-d3bb97e82e22
interleaving:      	 none
lun:               	 0_9
physicalDisk:      	 L45SDT
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_10_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:50+08:00
deviceName:        	 /dev/sdk
devicePartition:   	 /dev/sdk
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 4abc6ab9-61d1-4b0a-8998-bcc99cd58c0c
interleaving:      	 none
lun:               	 0_10
physicalDisk:      	 L45SNB
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal

name:              	 CD_11_dm01cel03
comment:
creationTime:      	 2012-11-28T10:30:50+08:00
deviceName:        	 /dev/sdl
devicePartition:   	 /dev/sdl
diskType:          	 HardDisk
errorCount:        	 0
freeSpace:         	 0
id:                	 ccc45ecd-5faf-4987-9d9a-851766380116
interleaving:      	 none
lun:               	 0_11
physicalDisk:      	 L45ESG
raidLevel:         	 0
size:              	 1861.703125G
status:            	 normal




...More

Top

Verify total size of all griddisks fully utilizes celldisk capacity

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server griddisks is critical for optimal performance and outage avoidance. The impact of verifying the storage server griddisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the storage server griddisk configuration as designed is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify the storage server griddisk configuration fully utilizes celldisk capacity, execute the following command as the "celladmin" user on each storage server: echo `cellcli -e "list griddisk attributes size" \| awk '{ SUM += $1} END { print SUM}'` `cellcli -e "list celldisk attributes size where disktype=harddisk" \| awk '{ SUM += $1} END { print SUM}'` \| awk '{ printf("%f\n", ($1/$2)*100) }' The output returned will be similar to: 99.991561 If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. NOTE: On a storage server configured according to Oracle best practices, the total size of all configured griddisks will be greater than 99.5% of the total of celldisks configured on disk drives.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => The total size of all griddisks fully utilizes celldisk capacity


DATA FROM DM01CEL01 FOR VERIFY TOTAL SIZE OF ALL GRIDDISKS FULLY UTILIZES CELLDISK CAPACITY



Cell Disks Size = 22281.7
Grid Disks Size = 22282.2




DATA FROM DM01CEL02 FOR VERIFY TOTAL SIZE OF ALL GRIDDISKS FULLY UTILIZES CELLDISK CAPACITY



Cell Disks Size = 22281.7
Grid Disks Size = 22282.2





DATA FROM DM01CEL03 FOR VERIFY TOTAL SIZE OF ALL GRIDDISKS FULLY UTILIZES CELLDISK CAPACITY



Cell Disks Size = 22281.7
Grid Disks Size = 22282.2




...More

Top

Check for parameter asm_power_limit

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for Database Machine V2, X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Default ASM_POWER_LIMIT value is 1 for an Exadata quarter rack, 2 for all other rack sizes. The Exadata default is chosen to mitigate application performance impact during ASM rebalance. Please evaluate application performance impact before using a higher ASM_POWER_LIMIT.
Needs attention on	-
Passed on	+ASM1, +ASM2

Status on +ASM1: PASS => ASM parameter ASM_POWER_LIMIT is set to the default value.

+ASM1.asm_power_limit = 1

Status on +ASM2: PASS => ASM parameter ASM_POWER_LIMIT is set to the default value.

+ASM2.asm_power_limit = 1

Top

Verify average ping times to DNS nameserver

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Secure Shell (SSH) remote login procedures require communication between the remote target device and the DNS nameserver. Verifying that the ping times between Exadata storage servers, database servers, and InfiniBand switches are minimal improves remote SSH login times. The impact of verifying minimal ping times to the DNS server is minimal. Because the effort required to minimize ping times will vary by configuration and root cause, the impact cannot be estimated here. Risk: If ping times between remote SSH targets and the active DNS server become too long, delays in remote login operations and/or timeouts in applications may be observed. Action / Repair: To verify the ping times between the active DNS server and Exadata database servers, enter the following command as the "root" userid on each database server: HOST_NAME=`hostname`; DNS_SERVER=`nslookup $HOST_NAME \| head -1 \| cut -d: -f2 \| sed -e 's/^[ \t]*//'`; echo -e "Active DNS Server IP:\t\t$DNS_SERVER"; echo -n -e "Average for 10 pings in ms:\t"; ping -c10 $DNS_SERVER \| grep -E ^64\| cut -d"=" -f 4 \| cut -d" " -f 1 \| awk '{ SUM += $1} END { print SUM/10}' The output should be similar to the following: Active DNS Server IP: 130.35.249.52 Average for 10 pings in ms: 1.794 As with any network response measurement, the response time should be "minimal". If the reported average ping response times are not "minimal", and especially if the environment is experiencing long SSH login times or application timeouts, investigate the condition and take corrective action.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => DNS Server ping time is in acceptable range


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY AVERAGE PING TIMES TO DNS NAMESERVER



Active DNS Server IP:		10.187.4.86
Average for 10 pings in ms:	0.1506

Status on dm01db02: PASS => DNS Server ping time is in acceptable range


Active DNS Server IP:		10.187.4.86
Average for 10 pings in ms:	0.1839

Top

Verify average ping times to DNS nameserver

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Secure Shell (SSH) remote login procedures require communication between the remote target device and the DNS nameserver. Verifying that the ping times between Exadata storage servers, database servers, and InfiniBand switches are minimal improves remote SSH login times. The impact of verifying minimal ping times to the DNS server is minimal. Because the effort required to minimize ping times will vary by configuration and root cause, the impact cannot be estimated here. Risk: If ping times between remote SSH targets and the active DNS server become too long, delays in remote login operations and/or timeouts in applications may be observed. Action / Repair: To verify the ping times between the active DNS server and Exadata database servers, enter the following command as the "root" userid on each database server: HOST_NAME=`hostname`; DNS_SERVER=`nslookup $HOST_NAME \| head -1 \| cut -d: -f2 \| sed -e 's/^[ \t]*//'`; echo -e "Active DNS Server IP:\t\t$DNS_SERVER"; echo -n -e "Average for 10 pings in ms:\t"; ping -c10 $DNS_SERVER \| grep -E ^64\| cut -d"=" -f 4 \| cut -d" " -f 1 \| awk '{ SUM += $1} END { print SUM/10}' The output should be similar to the following: Active DNS Server IP: 130.35.249.52 Average for 10 pings in ms: 1.794 As with any network response measurement, the response time should be "minimal". If the reported average ping response times are not "minimal", and especially if the environment is experiencing long SSH login times or application timeouts, investigate the condition and take corrective action.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => DNS Server ping time is in acceptable range


DATA FROM DM01CEL01 FOR VERIFY AVERAGE PING TIMES TO DNS NAMESERVER



Active DNS Server IP:		10.187.4.86
Average for 10 pings in ms:	0.2088




DATA FROM DM01CEL02 FOR VERIFY AVERAGE PING TIMES TO DNS NAMESERVER



Active DNS Server IP:		10.187.4.86
Average for 10 pings in ms:	0.3





DATA FROM DM01CEL03 FOR VERIFY AVERAGE PING TIMES TO DNS NAMESERVER



Active DNS Server IP:		10.187.4.86
Average for 10 pings in ms:	0.2149




...More

Top

Verify Database Server Disk Controller Configuration

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: For X2-2, there are 4 disk drives in a database server controlled by an LSI MegaRAID SAS 9261-8i disk controller. The disks are configured RAID-5 with 3 disks in the RAID set and 1 disk as a hot spare. There is 1 virtual drive created across the RAID set. Verifying the status of the database server RAID devices helps to avoid a possible performance impact, or an outage. The impact of validating the RAID devices is minimal. The impact of corrective actions will vary depending on the specific issue uncovered, and may range from simple reconfiguration to an outage. Risk: Not verifying the RAID devices increases the chance of a performance degradation or an outage. Action / Repair: To verify the database server disk controller configuration, use the following command: /opt/MegaRAID/MegaCli/MegaCli64 AdpAllInfo -aALL \| grep "Device Present" -A 8 For X2-2, the output will be similar to: Device Present ================ Virtual Drives : 1 Degraded : 0 Offline : 0 Physical Devices : 5 Disks : 4 Critical Disks : 0 Failed Disks : 0 The expected output is 1 virtual drive, none degraded or offline, 5 physical devices (controller + 4 disks), 4 disks, and no critical or failed disks.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database Server Disk Controller Configuration meets recommendation


DATA FROM DM01DB01 FOR VERIFY DATABASE SERVER DISK CONTROLLER CONFIGURATION



Device Present
================
Virtual Drives    : 1
Degraded        : 0
Offline         : 0
Physical Devices  : 5
Disks           : 4
Critical Disks  : 0
Failed Disks    : 0

Status on dm01db02: PASS => Database Server Disk Controller Configuration meets recommendation


DATA FROM DM01DB02 FOR VERIFY DATABASE SERVER DISK CONTROLLER CONFIGURATION



Device Present
================
Virtual Drives    : 1
Degraded        : 0
Offline         : 0
Physical Devices  : 5
Disks           : 4
Critical Disks  : 0
Failed Disks    : 0

Top

Verify Database Server Physical Drive Configuration

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: For X2-2, there are 4 disk drives in a database server controlled by an LSI MegaRAID SAS 9261-8i disk controller. The disks are configured RAID-5 with 3 disks in the RAID set and 1 disk as a hot spare. There is 1 virtual drive created across the RAID set. Verifying the status of the database server RAID devices helps to avoid a possible performance impact, or an outage. For X2-8, there are 8 disk drives in a database server controlled by an LSI MegaRAID SAS 9261-8i disk controller. The disks are configured RAID-5 with 7 disks in the RAID set and 1 disk as a hot spare. There is 1 virtual drive created across the RAID set. Verifying the status of the database server RAID devices helps to avoid a possible performance impact, or an outage. The impact of validating the physical drives is minimal. The impact of corrective actions will vary depending on the specific issue uncovered, and may range from simple reconfiguration to an outage. Risk: Not verifying the physical drives increases the chance of a performance degradation or an outage. Action / Repair: To verify the database server physical drive configuration, use the following command: /opt/MegaRAID/MegaCli/MegaCli64 PDList -aALL \| grep "Firmware state" The output for X2-2 will be similar to: Firmware state: Online, Spun Up Firmware state: Online, Spun Up Firmware state: Online, Spun Up Firmware state: Hotspare, Spun down There should be three lines of output showing a state of "Online, Spun Up", and one line showing a state of "Hotspare, Spun down". The ordering of the output lines is not significant and may vary based upon a given database server's physical drive replacement history. NOTE: Modified 03/21/12 Occasionally in normal operation, the "Hotspare" physical drive may be brought to a state of "Online, Spun Up". Thirty minutes (default) after the operation that brought the drive to "Online, Spun Up" has completed, the drive should spin down due to the powersaving feature. There is no harm for the drive to be "Online, Spun Up" if there are no other errors reported in the disk drive configuration checks. For additional information, please reference My Oracle Support note "Exadata: Hot Spares Not Spinning Down (Doc ID 1403613.1)"
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: FAIL => Database Server Physical Drive Configuration does not meet recommendation


DATA FROM DM01DB01 FOR VERIFY DATABASE SERVER PHYSICAL DRIVE CONFIGURATION



Firmware state: Hotspare, Spun Up
Firmware state: Online, Spun Up
Firmware state: Online, Spun Up
Firmware state: Online, Spun Up

Status on dm01db02: FAIL => Database Server Physical Drive Configuration does not meet recommendation


DATA FROM DM01DB02 FOR VERIFY DATABASE SERVER PHYSICAL DRIVE CONFIGURATION



Firmware state: Hotspare, Spun Up
Firmware state: Online, Spun Up
Firmware state: Online, Spun Up
Firmware state: Online, Spun Up

Top

Check for parameter memory_max_target

Success Factor	LINUX DATA COLLECTIONS AND AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Setting MEMORY_MAX_TARGET to 0 disables MEMORY_MAX_TARGET for the ASM instance NOTE: The proper way to implement the memory related parameters is as follows. This is important as it works around an issue where memory_target remains set despite setting it to 0. * alter system set sga_target=1250M sid='' scope=spfile; alter system set pga_aggregate_target=400M sid='' scope=spfile; alter system set memory_target=0 sid='' scope=spfile; alter system set memory_max_target=0 sid='' scope=spfile; alter system reset memory_max_target sid='*' scope=spfile;
Links	Note: 1373255.1 - 11.2.0.1/11.2.0.2 to 11.2.0.3 Database Upgrade on Exadata Database Machine -
Needs attention on	-
Passed on	+ASM1, +ASM2

Status on +ASM1: PASS => ASM parameter MEMORY_MAX_TARGET is set according to recommended value

+ASM1.memory_max_target = 0

Status on +ASM2: PASS => ASM parameter MEMORY_MAX_TARGET is set according to recommended value

+ASM2.memory_max_target = 0

Top

Check for parameter pga_aggregate_target

Success Factor	LINUX DATA COLLECTIONS AND AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: This disables memory_target for the ASM instance and setting PGA_AGGREGATE_TARGET to 400M provides the ASM instance sufficient PGA memory NOTE: The proper way to implement the memory related parameters is as follows. This is important as it works around an issue where memory_target remains set despite setting it to 0. * alter system set sga_target=1250M sid='' scope=spfile; alter system set pga_aggregate_target=400M sid='' scope=spfile; alter system set memory_target=0 sid='' scope=spfile; alter system set memory_max_target=0 sid='' scope=spfile; alter system reset memory_max_target sid='*' scope=spfile;
Links	Note: 1373255.1 - 11.2.0.1/11.2.0.2 to 11.2.0.3 Database Upgrade on Exadata Database Machine -
Needs attention on	-
Passed on	+ASM1, +ASM2

Status on +ASM1: PASS => ASM parameter PGA_AGGREGATE_TARGET is set according to recommended value

+ASM1.pga_aggregate_target = 419430400

Status on +ASM2: PASS => ASM parameter PGA_AGGREGATE_TARGET is set according to recommended value

+ASM2.pga_aggregate_target = 419430400

Top

Check for parameter memory_target

Success Factor	LINUX DATA COLLECTIONS AND AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: This disables memory_target for the ASM instance. NOTE: The proper way to implement the memory related parameters is as follows. This is important as it works around an issue where memory_target remains set despite setting it to 0. * alter system set sga_target=1250M sid='' scope=spfile; alter system set pga_aggregate_target=400M sid='' scope=spfile; alter system set memory_target=0 sid='' scope=spfile; alter system set memory_max_target=0 sid='' scope=spfile; alter system reset memory_max_target sid='*' scope=spfile;
Links	Note: 1373255.1 - 11.2.0.1/11.2.0.2 to 11.2.0.3 Database Upgrade on Exadata Database Machine -
Needs attention on	-
Passed on	+ASM1, +ASM2

Status on +ASM1: PASS => ASM parameter MEMORY_TARGET is set according to recommended value

+ASM1.memory_target = 0

Status on +ASM2: PASS => ASM parameter MEMORY_TARGET is set according to recommended value

+ASM2.memory_target = 0

Top

Check for parameter sga_target

Success Factor	LINUX DATA COLLECTIONS AND AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: This disables memory_target for the ASM instance and setting SGA_TARGET to 1250M provides the ASM instance sufficient SGA memory. NOTE: The proper way to implement the memory related parameters is as follows. This is important as it works around an issue where memory_target remains set despite setting it to 0. * alter system set sga_target=1250M sid='' scope=spfile; alter system set pga_aggregate_target=400M sid='' scope=spfile; alter system set memory_target=0 sid='' scope=spfile; alter system set memory_max_target=0 sid='' scope=spfile; alter system reset memory_max_target sid='*' scope=spfile;
Links	Note: 1373255.1 - 11.2.0.1/11.2.0.2 to 11.2.0.3 Database Upgrade on Exadata Database Machine -
Needs attention on	-
Passed on	+ASM1, +ASM2

Status on +ASM1: PASS => ASM parameter SGA_TARGET is set according to recommended value.

+ASM1.sga_target = 1325400064

Status on +ASM2: PASS => ASM parameter SGA_TARGET is set according to recommended value.

+ASM2.sga_target = 1325400064

Top

Check for parameter fast_start_mttr_target

Success Factor	COMPUTER FAILURE PREVENTION BEST PRACTICES
Recommendation	The deployment default for fast_start_mttr_target is 60. To optimize run time performance for write/redo generation intensive workloads, increase fast_start_mttr_target to 300. This will reduce checkpoint writes from DBWR processes, making more room for LGWR IO. The trade-off is that instance recovery will run longer, so if instance recovery is more important than performance, then keep fast_start_mttr_target low. Also keep in mind that an application with inadequately sized redo logs will likley not see an affect from this change due to frequent log switches. Considerations for a direct writes in a data warehouse type of application: Even though direct operations aren't using the buffer cache, fast_start_mttr_target is very effective at controlling crash recovery time because it ensures adequate checkpointing for the few buffers that are resident (ex: undo segment headers). fast_start_mttr_target should be set to the desired RTO (Recovery Time Objective) while still maintaing performance SLAs.
Links	Oracle® Database High Availability Best Practices 11g Release 2 (11.2)
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => fast_start_mttr_target has been changed from default

MCSDB1.fast_start_mttr_target = 300

Status on MCSDB2: PASS => fast_start_mttr_target has been changed from default

MCSDB2.fast_start_mttr_target = 300

Top

Oracle net services configuration to ship redo

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	Optimize network throughput following the best practices described in section 8.2.2 in the HA Best Practice guide:
Links	Assess Performance with Proposed Network Configuration
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: FAIL => Oracle Net service name to ship redo to the standby is not configured properly


DATA FROM DM01DB01 - MCSDB DATABASE - ORACLE NET SERVICES CONFIGURATION TO SHIP REDO




TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 16-APR-2014 11:16:01

Copyright (c) 1997, 2011, Oracle.  All rights reserved.

Used parameter files:

TNS-03505: Failed to resolve name

Status on dm01db02: FAIL => Oracle Net service name to ship redo to the standby is not configured properly



TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 16-APR-2014 11:21:40

Copyright (c) 1997, 2011, Oracle.  All rights reserved.

Used parameter files:

TNS-03505: Failed to resolve name

Top

Redo transport protocol

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	The ARCH redo transport mode has been deprecated and will be desupported in a future release. Oracle recommends that you switch to the ASYNC transport mode if you are currently using the ARCH transport mode. The ASYNC transport mode is superior to the ARCH transport mode in all respects, and is the new default transport mode.
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Remote destination not is using either ASYNC or SYNC transport for redo transport


DATA FOR MCSDB FOR REDO TRANSPORT PROTOCOL

Top

Check for parameter undo_retention

Success Factor	LOGICAL CORRUPTION PREVENTION BEST PRACTICES
Recommendation	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)
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter UNDO_RETENTION is not null

MCSDB1.undo_retention = 900

Status on MCSDB2: PASS => Database parameter UNDO_RETENTION is not null

MCSDB2.undo_retention = 900

Top

Verify all "BIGFILE" tablespaces have non-default "MAXBYTES" values set

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: "MAXBYTES" is the SQL attribute that expresses the "MAXSIZE" value that is used in the DDL command to set "AUTOEXTEND" to "ON". By default, for a bigfile tablespace, the value is "3.5184E+13", or "35184372064256". The benefit of having "MAXBYTES" set at a non-default value for "BIGFILE" tablespaces is that a runaway operation or heavy simultaneous use (e.g., temp tablespace) cannot take up all the space in a diskgroup. The impact of verifying that "MAXBYTES" is set to a non-default value is minimal. The impact of setting the "MAXSIZE" attribute to a non-default value "varies depending upon if it is done during database creation, file addition to a tablespace, or added to an existing file. Risk The risk of running out of space in a diskgroup varies by application and cannot be quantified here. A diskgroup running out of space may impact the entire database as well as ASM operations (e.g., rebalance operations). Action / Repair: To obtain a list of file numbers and bigfile tablespaces that have the "MAXBYTES" attribute at the default value, enter the following sqlplus command logged into the database as sysdba: select file_id, a.tablespace_name, autoextensible, maxbytes from (select file_id, tablespace_name, autoextensible, maxbytes from dba_data_files where autoextensible='YES' and maxbytes = 35184372064256) a, (select tablespace_name from dba_tablespaces where bigfile='YES') b where a.tablespace_name = b.tablespace_name union select file_id,a.tablespace_name, autoextensible, maxbytes from (select file_id, tablespace_name, autoextensible, maxbytes from dba_temp_files where autoextensible='YES' and maxbytes = 35184372064256) a, (select tablespace_name from dba_tablespaces where bigfile='YES') b where a.tablespace_name = b.tablespace_name; The output should be:no rows returned If you see output similar to: FILE_ID TABLESPACE_NAME AUT MAXBYTES ---------- ------------------------------ --- ---------- 1 TEMP YES 3.5184E+13 3 UNDOTBS1 YES 3.5184E+13 4 UNDOTBS2 YES 3.5184E+13 Investigate and correct the condition.
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => All bigfile tablespaces have non-default maxbytes values set


DATA FOR MCSDB FOR VERIFY ALL "BIGFILE" TABLESPACES HAVE NON-DEFAULT "MAXBYTES" VALUES SET




If no rows returned means query did not return any row and SQL check passed

Top

Verify InfiniBand subnet manager is running on an InfiniBand switch

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The Impact of verifying that the InfiniBand switch software is running on an InfiniBand switch is minimal. To move the InfiniBand subnet manager requires stopping the subnet manager on the incorrect InfiniBand fabric node and verifying that it failed over to an InfiniBand switch. Risk: If the InfiniBand subnet manager is not running on an InfiniBand switch, the InfiniBand fabric may crash during certain fabric management transitions. Action / Repair: To verify the InfiniBand subnet manager is located on an InfiniBand switch, execute the following command as the "root" userid on a database server: export SUBNET_MGR_GID=`sminfo \| cut -d" " -f7 \| cut -c3-16`;export SUBNET_MGR_LOC="OTHER";for IB_NODE_GID in `ibswitches \| cut -c14-27`; do if [ $SUBNET_MGR_GID = $IB_NODE_GID ]; then export SUBNET_MGR_LOC="IB_SWITCH"; fi; done; echo $SUBNET_MGR_LOC; The output should be similar to: IB_SWITCH If the output is not "IB_SWITCH", investigate and correct the condition. NOTE: For additional guidance on configuring the InfiniBand subnet manager, please see the "Setting the Subnet Manager Master on Exadata Database Machine Full Rack and Exadata Database Machine Half Rack" section of the "Oracle® Exadata Database Machine Owner's Guide, 11g Release 2 (11.2), E13874-17".
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => subnet manager is running on an InfiniBand switch


DATA FROM DM01DB01 FOR VERIFY INFINIBAND SUBNET MANAGER IS RUNNING ON AN INFINIBAND SWITCH



Subnet manager GUID=2128e8af6da0a0 and switches GUID are 2128e8b08ea0a0 2128e8af6da0a0

Top

LOG_FILE_NAME_CONVERT

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	As part of a switchover, the standby database must clear the online redo log files on the standby database before opening as a primary database. The time needed to complete the I/O can significantly increase the overall switchover time. By setting theLOG_FILE_NAME_CONVERT parameter, the standby database can pre-create the online redo logs the first time the MRP process is started. You can also pre-create empty online redo logs by issuing the SQL*Plus ALTER DATABASE CLEAR LOGFILE statement on the standby database. See section of 8.4.1 of the HA Best Practice guide for further information.
Links	Oracle Data Guard Role Transition Best Practices
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => Database parameter LOG_FILE_NAME_CONVERT or DB_CREATE_ONLINE_LOG_DEST_1 is not null


DATA FOR MCSDB FOR LOG_FILE_NAME_CONVERT




log_file_name_convert


db_create_online_log_dest_1
+DATA_DM01

Top

Clusterware status

Success Factor	CLIENT FAILOVER OPERATIONAL BEST PRACTICES
Recommendation	Oracle clusterware is required for complete client failover integration. Please consult the following whitepaper for further information
Links	Client Failover Best Practices for Highly Available Oracle Databases: Oracle Database 11g Release 2
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Clusterware is running


DATA FROM DM01DB01 - MCSDB DATABASE - CLUSTERWARE STATUS



--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA_DM01.dg
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.DBFS_DG.dg
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.LISTENER.lsnr
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.RECO_DM01.dg
ONLINE  ONLINE       dm01db01

ONLINE  ONLINE       dm01db02
ora.asm
ONLINE  ONLINE       dm01db01                 Started
ONLINE  ONLINE       dm01db02                 Started
ora.gsd
OFFLINE OFFLINE      dm01db01
OFFLINE OFFLINE      dm01db02
ora.net1.network
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.ons
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1        ONLINE  ONLINE       dm01db02
ora.LISTENER_SCAN2.lsnr
1        ONLINE  ONLINE       dm01db01
ora.LISTENER_SCAN3.lsnr
1        ONLINE  ONLINE       dm01db01
ora.cvu
1        ONLINE  ONLINE       dm01db01
ora.dm01db01.vip
1        ONLINE  ONLINE       dm01db01
ora.dm01db02.vip
1        ONLINE  ONLINE       dm01db02
ora.mcsdb.db
1        ONLINE  ONLINE       dm01db01                 Open
2        ONLINE  ONLINE       dm01db02                 Open
ora.oc4j
1        ONLINE  ONLINE       dm01db01
ora.scan1.vip
1        ONLINE  ONLINE       dm01db02
ora.scan2.vip
1        ONLINE  ONLINE       dm01db01
ora.scan3.vip
1        ONLINE  ONLINE       dm01db01
...More

Status on dm01db02: PASS => Clusterware is running


--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA_DM01.dg
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.DBFS_DG.dg
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.LISTENER.lsnr
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.RECO_DM01.dg
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.asm
ONLINE  ONLINE       dm01db01                 Started
ONLINE  ONLINE       dm01db02                 Started

ora.gsd
OFFLINE OFFLINE      dm01db01
OFFLINE OFFLINE      dm01db02
ora.net1.network
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
ora.ons
ONLINE  ONLINE       dm01db01
ONLINE  ONLINE       dm01db02
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.LISTENER_SCAN1.lsnr
1        ONLINE  ONLINE       dm01db02
ora.LISTENER_SCAN2.lsnr
1        ONLINE  ONLINE       dm01db01
ora.LISTENER_SCAN3.lsnr
1        ONLINE  ONLINE       dm01db01
ora.cvu
1        ONLINE  ONLINE       dm01db01
ora.dm01db01.vip
1        ONLINE  ONLINE       dm01db01
ora.dm01db02.vip
1        ONLINE  ONLINE       dm01db02
ora.mcsdb.db
1        ONLINE  ONLINE       dm01db01                 Open
2        ONLINE  ONLINE       dm01db02                 Open
ora.oc4j
1        ONLINE  ONLINE       dm01db01
ora.scan1.vip
1        ONLINE  ONLINE       dm01db02
ora.scan2.vip
1        ONLINE  ONLINE       dm01db01
ora.scan3.vip
1        ONLINE  ONLINE       dm01db01
...More

Top

Logical standby unsupported datatypes

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	You can use a transient logical standby database to perform a rolling database upgrade using your current physical standby database by temporarily converting it to a logical standby database. Use a transient logical standby when your configuration only has a physical standby database. To determine data types that exist in your database that are not supported for logical standby refer to appendix C of the Data Guard Concepts and Admin guide:
Links	Determine Support for Data Types and Storage Attributes for Tables
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: WARNING => Logical standby unsupported datatypes found


DATA FOR MCSDB FOR LOGICAL STANDBY UNSUPPORTED DATATYPES




DEV5_SOAINFRA                  AQ$_IP_QTAB_I
DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_H
DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_G
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_I
DEV6_BIPLATFORM                SDCLEANUPLIST2
DEV1_SOAINFRA                  AQ$_IP_QTAB_I
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_G
DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_G
GIS                            MAP_STATION_POI
DEV1_SOAINFRA                  AQ$_IP_QTAB_S
DEV1_SOAINFRA                  AQ$_IP_QTAB_H
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_T
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_I

DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_T

DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_I
DEV1_SOAINFRA                  B2B_BAM_QTAB
DEVBITEST_BIPLATFORM           SDCLEANUPLIST2
DEV5_SOAINFRA                  AQ$_IP_QTAB_G
DEV5_SOAINFRA                  EDN_OAOO_DELIVERY_TABLE
GIS                            POI_BASEINFO
DEV1_SOAINFRA                  AQ$_IP_QTAB_G
DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_H
DEV6_BIPLATFORM                SDCLEANUPLIST1
GIS                            OS_BASE_INFO_BAK
GIS                            COM_STAFF_PRE
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_H

GIS                            MAP_POI_SD
DEV5_SOAINFRA                  IP_QTAB
DEV5_SOAINFRA                  AQ$_IP_QTAB_H
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_S
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_H
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_G
GIS                            MAP_COUNTY_AREA
DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_S
GIS                            MAP_DEPOT_POI
DEV5_SOAINFRA                  AQ$_IP_QTAB_S
DEV5_SOAINFRA                  EDN_EVENT_QUEUE_TABLE
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_T
DEV5_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_L

GIS                            MAP_SHOP_POI
DEV1_SOAINFRA                  EDN_EVENT_QUEUE_TABLE
GIS                            MAP_EASYJOY_POI
DEV5_SOAINFRA                  AQ$_IP_QTAB_T
DEV5_SOAINFRA                  AQ$_IP_QTAB_L
DEV5_SOAINFRA                  B2B_BAM_QTAB
GIS                            OS_BASE_INFO
DEV1_SOAINFRA                  IP_QTAB
DEV1_SOAINFRA                  AQ$_IP_QTAB_L
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_S
DEV1_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_L
DEV1_SOAINFRA                  EDN_OAOO_DELIVERY_TABLE
DEVBITEST_BIPLATFORM           SDCLEANUPLIST1

DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_S
DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_T
DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_L
DEV5_SOAINFRA                  AQ$_EDN_EVENT_QUEUE_TABLE_I
GIS                            MAP_CITY_AREA
DEV1_SOAINFRA                  AQ$_IP_QTAB_T
DEV1_SOAINFRA                  AQ$_EDN_OAOO_DELIVERY_TABLE_L
GIS                            MAP_ROAD_INFO
...More

Top

Standby recovery mode

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	Use real-time apply so that redo data is applied to the standby database as soon as it is received. See section of 8.3.8 of the HA Best Practice guide for further information.
Links	Use Data Guard Redo Apply Best Practices
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Standby is not running in MANAGED REAL TIME APPLY mode


DATA FOR MCSDB FOR STANDBY RECOVERY MODE

Top

Standby redolog status on primary

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	You should configure standby redo logs on both sites for improved availability and performance. To determine the recommended number of standby redo logs, use the following formula: (maximum # of logfile groups +1) * maximum # of threads
Links	Use Standby Redo Logs and Configure Size Appropriately
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Standby redo logs are not configured on both sites


DATA FOR MCSDB FOR STANDBY REDOLOG STATUS ON PRIMARY

Top

Dataguard broker confugration

Success Factor	CLIENT FAILOVER OPERATIONAL BEST PRACTICES
Recommendation	Data Guard broker is required for complete client failover integration. Please consult the following whitepaper for further information
Links	Client Failover Best Practices for Highly Available Oracle Databases: Oracle Database 11g Release 2
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: FAIL => Dataguard broker configuration does not exist


DATA FROM DM01DB01 - MCSDB DATABASE - DATAGUARD BROKER CONFUGRATION



DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production

Copyright (c) 2000, 2009, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.
Error:
ORA-16525: the Data Guard broker is not yet available

Configuration details cannot be determined by DGMGRL

Status on dm01db02: FAIL => Dataguard broker configuration does not exist


DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production

Copyright (c) 2000, 2009, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.
Error:
ORA-16525: the Data Guard broker is not yet available

Configuration details cannot be determined by DGMGRL

Top

High redundancy diskgroups

Success Factor	STORAGE FAILURES PREVENTION BEST PRACTICES
Recommendation	Choose Oracle Automatic Storage Management (ASM) high redundancy for DATA and RECO disk groups for best tolerance from data and storage failures. ASM high redundancy is the ideal recommendation for business critical databases
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => At least one high redundancy diskgroup configured


DATA FOR MCSDB FOR HIGH REDUNDANCY DISKGROUPS




DATA_DM01                      HIGH
DBFS_DG                        NORMAL
RECO_DM01                      NORMAL

Top

Physical standby status

Success Factor	DATABASE/CLUSTER/SITE FAILURE PREVENTION BEST PRACTICES
Recommendation	Oracle Data Guard is a high availability and disaster-recovery solution that provides very fast automatic failover (referred to as fast-start failover) in database failures, node failures, corruption, and media failures. Furthermore, the standby databases can be used for read-only access and subsequently for reader farms, for reporting, for backups and for testing and development. For zero data loss protection and fastest recovery time, deploy a local Data Guard standby database with Data Guard Fast-Start Failover. For protection against outages impacting both the primary and the local standby, deploy a second Data Guard standby database at a remote location.
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Physical standby status is not valid


DATA FOR MCSDB FOR PHYSICAL STANDBY STATUS

Top

Flashback database on primary

Success Factor	LOGICAL CORRUPTION PREVENTION BEST PRACTICES
Recommendation	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)
Links	HA Best Practices guide - 5.1.4 Enable Flashback Database
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Flashback is not configured


DATA FOR MCSDB FOR FLASHBACK DATABASE ON PRIMARY




primary_flashback = NO

Top

Database init paramter DB_BLOCK_CHECKING on standby

Success Factor	DATA CORRUPTION PREVENTION BEST PRACTICES
Recommendation	Critical Benefit / Impact: Intially db_block_checking is set to off due to potential performance impact. Performance testing is particularly important given that overhead is incurred on every block change. Block checking typically causes 1% to 10% overhead, but for update and insert intensive applications (such as Redo Apply at a standby database) the overhead can be much higher. OLTP compressed tables also require additional checks that can result in higher overhead depending on the frequency of updates to those tables. Workload specific testing is required to assess whether the performance overhead is acceptable. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Based on performance testing results set the primary or standby database to either medium or full depending on the impact. If performance concerns prevent setting DB_BLOCK_CHECKING to either FULL or MEDIUM at a primary database, then it becomes even more important to enable this at the standby database. This protects the standby database from logical corruption that would be undetected at the primary database. For higher data corruption detection and prevention, enable this setting but performance impacts vary per workload. Evaluate performance impact.
Links	Note: 1302539.1 - Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration - Protect Against Data Corruption
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: WARNING => Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.


DATA FROM DM01DB01 - MCSDB DATABASE - DATABASE INIT PARAMTER DB_BLOCK_CHECKING ON STANDBY



DB_BLOCK_CHECKING = FALSE

Status on dm01db02: WARNING => Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.


DB_BLOCK_CHECKING = FALSE

Top

Scan storage server alerthistory for open alerts

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Needs attention on	dm01cel03, dm01cel02, dm01cel01
Passed on	-

Status on dm01cel03, dm01cel02, dm01cel01: FAIL => one or storage server has open critical alerts.


DATA FROM DM01CEL01 FOR SCAN STORAGE SERVER ALERTHISTORY FOR OPEN ALERTS



6_1 	 2012-11-28T10:33:05+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_2 	 2013-01-16T15:41:00+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_3 	 2013-01-17T15:40:56+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_4 	 2013-02-21T15:48:57+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_5 	 2013-02-22T15:48:58+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_6 	 2013-05-23T15:49:12+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_7 	 2013-05-24T15:49:13+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_8 	 2013-08-26T15:51:01+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf Checking DNS server on 10.187.0.206                                                              : FAILED DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_9 	 2013-08-27T15:50:46+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_10	 2014-03-08T15:55:33+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_11	 2014-03-11T15:55:29+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_12	 2014-03-30T15:57:11+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf Checking DNS server on 10.187.0.206                                                              : FAILED DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_13	 2014-03-31T15:56:56+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
8_1 	 2012-12-03T12:38:31+08:00	 "File system "/" is 80% full, which is above the 80% threshold. Accelerated space reclamation has started.  This alert will be cleared when file system "/" becomes less than 75% full. Top three directories ordered by total space usage are as follows: /opt        : 3.68G /usr        : 2.4G /root        : 1.55G"
60_1	 2013-12-06T18:39:58+08:00	 "Data hard disk entered predictive failure status.  Status        : WARNING - PREDICTIVE FAILURE  Manufacturer  : SEAGATE  Model Number  : ST32000SSSUN2.0T  Size          : 2.0TB  Serial Number : 1108L45RD9  Firmware      : 061A  Slot Number   : 2  Cell Disk     : CD_02_dm01cel01  Grid Disk     : RECO_DM01_CD_02_dm01cel01, DATA_DM01_CD_02_dm01cel01, DBFS_DG_CD_02_dm01cel01"
60_2	 2013-12-06T19:13:08+08:00	 "Data hard disk failed.  Status        : CRITICAL  Manufacturer  : SEAGATE  Model Number  : ST32000SSSUN2.0T  Size          : 2.0T  Serial Number : 1108L45RD9  Firmware      : 061A  Slot Number   : 2  Cell Disk     : CD_02_dm01cel01  Grid Disk     : RECO_DM01_CD_02_dm01cel01, DATA_DM01_CD_02_dm01cel01, DBFS_DG_CD_02_dm01cel01"

61_1	 2013-12-06T19:13:05+08:00	 "Disk drive 0_2 is in WriteThrough caching mode. Write Performance on this drive will be affected. Please contact Oracle Support"




DATA FROM DM01CEL02 FOR SCAN STORAGE SERVER ALERTHISTORY FOR OPEN ALERTS



7_1  	 2012-11-28T10:33:05+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_2  	 2012-12-14T13:03:13+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_3  	 2012-12-15T13:03:09+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_4  	 2013-01-18T13:03:32+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_5  	 2013-01-19T13:03:29+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_6  	 2013-04-27T13:10:40+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_7  	 2013-04-28T13:10:40+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_8  	 2013-07-16T18:23:40+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_9  	 2013-07-17T18:23:44+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_10 	 2014-03-08T18:25:54+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_11 	 2014-03-11T18:25:49+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_12 	 2014-03-25T18:26:11+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_13 	 2014-03-26T18:26:06+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_14 	 2014-04-13T18:26:07+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
7_15 	 2014-04-14T18:26:07+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
79_1 	 2013-05-24T18:18:10+08:00	 "File system "/" is 80% full, which is above the 80% threshold. Accelerated space reclamation has started.  This alert will be cleared when file system "/" becomes less than 75% full. Top three directories ordered by total space usage are as follows: /opt        : 3.59G /usr        : 2.4G /root        : 1.55G"
129  	 2014-02-08T17:35:09+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
130  	 2014-02-08T17:40:39+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
131  	 2014-02-10T10:21:43+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
132  	 2014-02-14T15:06:01+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
133_1	 2014-03-25T03:46:50+08:00	 "The critical threshold for the following metric has been crossed. Metric Name        : CL_TEMP  Metric Description : Temperature (Celsius) of the server, provided by the BMC  Object Name        : dm01cel02  Current Value      : 33.0 C  Threshold Value    : 32.0 C  "
135_1	 2014-03-25T16:27:44+08:00	 "A generic component is suspected of causing a fault.  Component Name : /SYS  Fault class    : fault.chassis.env.temp.over-fail  Fault message  : http://www.sun.com/msg/SPX86-8000-6P"
136_1	 2014-03-27T16:01:51+08:00	 "The critical threshold for the following metric has been crossed. Metric Name        : CL_TEMP  Metric Description : Temperature (Celsius) of the server, provided by the BMC  Object Name        : dm01cel02  Current Value      : 33.0 C  Threshold Value    : 32.0 C  "
139_1	 2014-03-28T09:10:23+08:00	 "A generic component is suspected of causing a fault.  Component Name : /SYS  Fault class    : fault.chassis.env.temp.over-fail  Fault message  : http://www.sun.com/msg/SPX86-8000-6P"




DATA FROM DM01CEL03 FOR SCAN STORAGE SERVER ALERTHISTORY FOR OPEN ALERTS



6_1  	 2012-11-28T10:33:24+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_2  	 2012-12-14T13:02:57+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_3  	 2012-12-15T13:02:52+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_4  	 2013-01-18T13:03:03+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_5  	 2013-01-19T13:02:58+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_6  	 2013-04-27T13:11:47+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.187.4.86                                                               : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_7  	 2013-04-28T13:11:47+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_8  	 2014-03-08T13:16:56+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Checking NTP server on 10.6.2.171                                                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
6_9  	 2014-03-12T13:16:49+08:00	 "Cell configuration check discovered the following problems:   Check Exadata configuration via ipconf utility Verifying of Exadata configuration file /opt/oracle.cellos/cell.conf DNS server 10.187.0.206 exists only in Exadata configuration file                                : FAILED Error. Overall status of verification of Exadata configuration file: FAILED [INFO] The ipconf check may generate a failure for temporary inability to reach NTP or DNS server. You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] You may ignore this alert, if the NTP or DNS servers are valid and available. [INFO] As root user run /usr/local/bin/ipconf -verify -semantic to verify consistent network configurations."
50_1 	 2013-06-25T08:00:31+08:00	 "File system "/" is 80% full, which is above the 80% threshold. Accelerated space reclamation has started.  This alert will be cleared when file system "/" becomes less than 75% full. Top three directories ordered by total space usage are as follows: /opt        : 3.71G /usr        : 2.4G /root        : 1.55G"
105  	 2014-02-08T17:35:18+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
106  	 2014-02-10T10:21:39+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
107  	 2014-02-14T15:06:14+08:00	 "RS-7445 [Serv CELLSRV hang detected] [It will be restarted] [] [] [] [] [] [] [] [] [] []"
108_1	 2014-03-25T05:16:04+08:00	 "The critical threshold for the following metric has been crossed. Metric Name        : CL_TEMP  Metric Description : Temperature (Celsius) of the server, provided by the BMC  Object Name        : dm01cel03  Current Value      : 32.4 C  Threshold Value    : 32.0 C  "
110_1	 2014-03-25T16:29:28+08:00	 "A generic component is suspected of causing a fault.  Component Name : /SYS  Fault class    : fault.chassis.env.temp.over-fail  Fault message  : http://www.sun.com/msg/SPX86-8000-6P"
111_1	 2014-03-27T16:11:19+08:00	 "The critical threshold for the following metric has been crossed. Metric Name        : CL_TEMP  Metric Description : Temperature (Celsius) of the server, provided by the BMC  Object Name        : dm01cel03  Current Value      : 33.0 C  Threshold Value    : 32.0 C  "
113_1	 2014-03-28T06:25:40+08:00	 "A generic component is suspected of causing a fault.  Component Name : /SYS  Fault class    : fault.chassis.env.temp.over-fail  Fault message  : http://www.sun.com/msg/SPX86-8000-6P"




...More

Top

Verify Exadata Smart Flash Log is Created

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: When created, Exadata Smart Flash Log uses 512MB of flash memory per storage server by default to help minimize redo log write latency. The impact of verifying that Exadata Smart Flash Log is created is minimal. Risk: Without Exadata Smart Flash Log, the LGWR process may be delayed causing longer "log file parallel write" and "log file sync" waits. Action / Repair: To verify that Exadata Smart Flash Log is created, execute the following cellcli command as the "celladmin" user on each storage server: list flashlog attributes size,status The output should be similar to: 512M normal If the output is not as shown, Exadata Smart Flash Log may not be created, or there may be a hardware issue, or there may be a configuration issue. Investigate and correct the condition. Because they share the same storage server physical flash memory, there is a space usage relationship between Exadata Smart Flash Log and Exadata Smart Flash Cache. Exadata Smart Flash Log should be created before Exadata Smart Flash Cache, because the default configuration for Exadata Smart Flash Cache will use all available storage server flash memory. If Exadata Smart Flash Cache already exists, a subsequent attempt to create Exadata Smart Flash Log will fail because all the available storage server flash memory is in use. To create Exadata Smart Flash Log when Exadata Smart Flash Cache is not created, execute the following cellcli command as the "celladmin" user: create flashlog all To create Exadata Smart Flash Log when Exadata Smart Flash Cache is already enabled, at the default sizings for both, enter the following "cellcli" commands as the "celladmin" user: drop flashcache create flashlog all create flashcache all NOTE: Exadata Smart Flash Log is created by default with Exadata Storage Server Software version 11.2.2.4.0 and above. NOTE: Exadata Smart Flash Log will be used by Oracle software 11.2.0.2 Bundle Patch 9 (or higher) or 11.2.0.3.0. The recommended Oracle software version levels are 11.2.0.2 Bundle Patch 11 (or higher) or 11.2.0.3 Bundle Patch 1 (or higher). NOTE: The default Exadata Smart Flash Log size of 512MB is the recommended value. NOTE: See also "Configure Storage Server Flash Memory as Exadata Smart Flash Cache"
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Smart flash log is created on all storage server


DATA FROM DM01CEL01 FOR VERIFY EXADATA SMART FLASH LOG IS CREATED



name:              	 dm01cel01_FLASHLOG
cellDisk:          	 FD_08_dm01cel01,FD_06_dm01cel01,FD_09_dm01cel01,FD_12_dm01cel01,FD_02_dm01cel01,FD_01_dm01cel01,FD_04_dm01cel01,FD_14_dm01cel01,FD_05_dm01cel01,FD_13_dm01cel01,FD_10_dm01cel01,FD_00_dm01cel01,FD_07_dm01cel01,FD_15_dm01cel01,FD_11_dm01cel01,FD_03_dm01cel01
creationTime:      	 2012-11-28T10:31:16+08:00
degradedCelldisks:
effectiveSize:     	 512M
efficiency:        	 100.0
id:                	 463e749c-cdbf-469d-abad-283c3eb39f0b
size:              	 512M
status:            	 normal




DATA FROM DM01CEL02 FOR VERIFY EXADATA SMART FLASH LOG IS CREATED




name:              	 dm01cel02_FLASHLOG
cellDisk:          	 FD_13_dm01cel02,FD_09_dm01cel02,FD_10_dm01cel02,FD_11_dm01cel02,FD_00_dm01cel02,FD_15_dm01cel02,FD_04_dm01cel02,FD_07_dm01cel02,FD_12_dm01cel02,FD_03_dm01cel02,FD_01_dm01cel02,FD_02_dm01cel02,FD_06_dm01cel02,FD_05_dm01cel02,FD_08_dm01cel02,FD_14_dm01cel02
creationTime:      	 2012-11-28T10:31:16+08:00
degradedCelldisks:
effectiveSize:     	 512M
efficiency:        	 100.0
id:                	 26e04e86-9d21-477c-88f2-1862950ba2c8
size:              	 512M
status:            	 normal




DATA FROM DM01CEL03 FOR VERIFY EXADATA SMART FLASH LOG IS CREATED



name:              	 dm01cel03_FLASHLOG
cellDisk:          	 FD_13_dm01cel03,FD_10_dm01cel03,FD_04_dm01cel03,FD_12_dm01cel03,FD_09_dm01cel03,FD_03_dm01cel03,FD_14_dm01cel03,FD_07_dm01cel03,FD_08_dm01cel03,FD_06_dm01cel03,FD_00_dm01cel03,FD_15_dm01cel03,FD_05_dm01cel03,FD_01_dm01cel03,FD_11_dm01cel03,FD_02_dm01cel03
creationTime:      	 2012-11-28T10:31:16+08:00
degradedCelldisks:
effectiveSize:     	 512M
efficiency:        	 100.0
id:                	 82b94d5e-ac01-40a0-8667-4abfabd671dc
size:              	 512M
status:            	 normal




...More

Top

Verify Exadata Smart Flash Cache is created

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: For the vast majority of situations, maximum performance is achieved by configuring the storage server flash memory as cache, allowing the Exadata software to determine the content of the cache. The impact of configuring storage server flash memory as cache at initial deployment is minimal. If there are already grid disks configured in the flash memory, consideration must be given as to the relocation of the data when converting the flash memory back to cache. Risk: Not configuring the storage server flash memory as cache may result in a degradation of overall performance. Action / Repair: To confirm all storage server flash memory is configured as smart flash cache, execute the command shown below: cellcli -e "list flashcache detail" \| grep size The output will be similar to: size: 364.75G Starting with Exadata software version 11.2.2.4, for an environment deployed according to Oracle standards, with the storage server "flashlog" feature in use at the default size of 512M, the size of the storage server "flashcache" is expected to be 364.75G. If the size is less than that, some of the storage server flash memory may be configured as grid disks, or there may be a hardware issue, or there may be a configuration issue. Investigate and correct the condition. To create Exadata Smart Flash Cache, execute the following cellcli command as the "celladmin" user: create flashcache all NOTE: For Exadata Software version 11.2.2.3 or lower, or Exadata Software version 11.2.2.4.0 or higher where a decision was made not to create Exadata Smart Flash Log, the size of the storage server "flashcache" is expected to be 365.25G. NOTE: See also "Verify Exadata Smart Flash Log is Created".
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Storage Server Flash Memory is configured as Exadata Smart Flash Cache


DATA FROM DM01CEL01 FOR VERIFY EXADATA SMART FLASH CACHE IS CREATED




NOTE: Look for size or size:

name:              	 dm01cel01_FLASHCACHE
cellDisk:          	 FD_07_dm01cel01,FD_13_dm01cel01,FD_09_dm01cel01,FD_05_dm01cel01,FD_10_dm01cel01,FD_00_dm01cel01,FD_04_dm01cel01,FD_14_dm01cel01,FD_11_dm01cel01,FD_08_dm01cel01,FD_15_dm01cel01,FD_06_dm01cel01,FD_02_dm01cel01,FD_01_dm01cel01,FD_03_dm01cel01,FD_12_dm01cel01
creationTime:      	 2012-11-28T10:31:41+08:00
degradedCelldisks:
effectiveCacheSize:	 364.75G
id:                	 71c5504c-606e-4142-a5ef-e195dca88900
size:              	 364.75G
status:            	 normal




DATA FROM DM01CEL02 FOR VERIFY EXADATA SMART FLASH CACHE IS CREATED





NOTE: Look for size or size:

name:              	 dm01cel02_FLASHCACHE
cellDisk:          	 FD_02_dm01cel02,FD_07_dm01cel02,FD_12_dm01cel02,FD_04_dm01cel02,FD_13_dm01cel02,FD_10_dm01cel02,FD_09_dm01cel02,FD_06_dm01cel02,FD_15_dm01cel02,FD_14_dm01cel02,FD_05_dm01cel02,FD_01_dm01cel02,FD_00_dm01cel02,FD_03_dm01cel02,FD_08_dm01cel02,FD_11_dm01cel02
creationTime:      	 2012-11-28T10:31:41+08:00
degradedCelldisks:
effectiveCacheSize:	 364.75G
id:                	 274e3864-e4c3-4e74-b13a-e3a4ebfb1a08
size:              	 364.75G
status:            	 normal




DATA FROM DM01CEL03 FOR VERIFY EXADATA SMART FLASH CACHE IS CREATED




NOTE: Look for size or size:

name:              	 dm01cel03_FLASHCACHE
cellDisk:          	 FD_04_dm01cel03,FD_06_dm01cel03,FD_15_dm01cel03,FD_05_dm01cel03,FD_09_dm01cel03,FD_00_dm01cel03,FD_10_dm01cel03,FD_12_dm01cel03,FD_03_dm01cel03,FD_11_dm01cel03,FD_08_dm01cel03,FD_14_dm01cel03,FD_13_dm01cel03,FD_01_dm01cel03,FD_07_dm01cel03,FD_02_dm01cel03
creationTime:      	 2012-11-28T10:31:41+08:00
degradedCelldisks:
effectiveCacheSize:	 364.75G
id:                	 1be0d930-bd64-462b-86ed-f042a4e5d53f
size:              	 364.75G
status:            	 normal




...More

Top

Verify PCI bridge is configured for generation II on storage servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The storage server PCI bridges (19:0.0 and 27:0.0) should be configured for generation II for maximum performance. There is minimal impact to verify the PCI Bridges configuration. Risk: If the PCI bridges are not configured for generation II, performance will be sub-optimal. Action / Repair: To verify the current PCI bridges configuration, execute the following command as the root userid on all storage servers: for BUS_NUM in 19:0.0 27:0.0; do echo $BUS_NUM `lspci -xxx -s $BUS_NUM \| grep ^50 \| cut -d" " -f4`; done The output should be similar to: 19:0.0 82 27:0.0 82 If any of the storage server PCI bridges do not return "82", there are three possible corrective actions: If the value returned is "81" you may upgrade to Exadata storage server software version 11.2.2.4.0 or greater, or refer to MOS note1351559.1. If neither the value "81" nor "82" is returned, contact oracle support for further assistance. NOTE: PCI Bridge generation I will return the value "81".
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Peripheral component interconnect (PCI) bridge is configured for generation II on all storage servers


DATA FROM DM01CEL01 FOR VERIFY PCI BRIDGE IS CONFIGURED FOR GENERATION II ON STORAGE SERVERS



19:0.0 82
27:0.0 82




DATA FROM DM01CEL02 FOR VERIFY PCI BRIDGE IS CONFIGURED FOR GENERATION II ON STORAGE SERVERS



19:0.0 82
27:0.0 82





DATA FROM DM01CEL03 FOR VERIFY PCI BRIDGE IS CONFIGURED FOR GENERATION II ON STORAGE SERVERS



19:0.0 82
27:0.0 82




...More

Top

Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: When using multiple InfiniBand interfaces for the private cluster interconnect, there are specific ARP settings required for Real Application Clusters (RAC) to work correctly. The impact of verifying the ARP configuration is minimal. Correcting a configuration requires editing "/etc/sysctl.conf" and restarting the interface(s). Risk: Incorrect ARP configurations for multiple InfiniBand interfaces used as the private cluster interconnect may prevent RAC from starting, or result in dropped packets and inconsistent RAC operation. Action / Repair: To verify the InfiniBand interface ARP settings for a database server, use the following command as the "root" userid: grep -E "rp_filter\|accept_local" /etc/sysctl.conf \| grep -v max For an X2-8, the output will be similar to: net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 0 net.ipv4.conf.bondib0.rp_filter = 0 net.ipv4.conf.bondib1.rp_filter = 0 net.ipv4.conf.bondib2.rp_filter = 0 net.ipv4.conf.bondib3.rp_filter = 0 net.ipv4.conf.all.accept_local = 1 net.ipv4.conf.bondib0.accept_local = 1 net.ipv4.conf.bondib1.accept_local = 1 net.ipv4.conf.bondib2.accept_local = 1 net.ipv4.conf.bondib3.accept_local = 1 For an X2-2(4170) or X2-2, the output will be similar to: net.ipv4.conf.default.rp_filter = 1 If the output is not as shown, edit the "/etc/sysctl.conf" file and restart the relevant interface(s). NOTE: A customer may have additonal settings in the "/etc/sysctl.conf" file depending upon their specific requirements. NOTE: These settings do not contradict MOS note 1286796.1. The note uses two active IB interfaces in a non-bonded configuration in it's example. An X2-2(4170) or X2-2 uses the active/passive bonded "bondib0" interface as the private cluster interconnect, which does not qualify as "multiple private interconnects", so the ARP configuration is left at the defaults. For an X2-8, rp_filter is turned off because multiple active/passive bonded InfiniBand interfaces are used for the private cluster interconnect and it is possible to receive packets on one interface that will be replied to from another interface.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Address Resolution Protocol (ARP) is configured properly on database server.


DATA FROM DM01DB01 FOR VERIFY INFINIBAND ADDRESS RESOLUTION PROTOCOL (ARP) CONFIGURATION ON DATABASE SERVERS



net.ipv4.conf.default.rp_filter = 1

Status on dm01db02: PASS => Address Resolution Protocol (ARP) is configured properly on database server.


DATA FROM DM01DB02 FOR VERIFY INFINIBAND ADDRESS RESOLUTION PROTOCOL (ARP) CONFIGURATION ON DATABASE SERVERS



net.ipv4.conf.default.rp_filter = 1

Top

Database init parameter DB_BLOCK_CHECKING

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Intially db_block_checking is set to off due to potential performance impact. Performance testing is particularly important given that overhead is incurred on every block change. Block checking typically causes 1% to 10% overhead, but for update and insert intensive applications (such as Redo Apply at a standby database) the overhead can be much higher. OLTP compressed tables also require additional checks that can result in higher overhead depending on the frequency of updates to those tables. Workload specific testing is required to assess whether the performance overhead is acceptable. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Based on performance testing results set the primary or standby database to either medium or full depending on the impact. If performance concerns prevent setting DB_BLOCK_CHECKING to either FULL or MEDIUM at a primary database, then it becomes even more important to enable this at the standby database. This protects the standby database from logical corruption that would be undetected at the primary database. For higher data corruption detection and prevention, enable this setting but performance impacts vary per workload.Evaluate performance impact.
Links	Note: 1302539.1 - Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration - Protect Against Data Corruption
Needs attention on	dm01db01, dm01db02
Passed on	-

Status on dm01db01: WARNING => Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.


DATA FROM DM01DB01 - MCSDB DATABASE - DATABASE INIT PARAMETER DB_BLOCK_CHECKING



DB_BLOCK_CHECKING = FALSE

Status on dm01db02: WARNING => Database parameter DB_BLOCK_CHECKING is NOT set to the recommended value.


DB_BLOCK_CHECKING = FALSE

Top

Verify there are no griddisks configured on flash memory devices

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The definition and maintenance of storage server griddisks is critical for optimal performance and outage avoidance. The impact of verifying the storage server griddisk configuration is minimal. Correcting any abnormalities is dependent upon the reason for the anomaly, so the impact cannot be estimated here. Risk: If the storage server griddisk configuration is not verified, poor performance or unexpected outages may occur. Action / Repair: To verify there are no storage server griddisks configured on flash memory devices, execute the following command as the "celladmin" user on each storage server: cellcli -e "list griddisk where disktype=flashdisk" \| wc -l The output should be:0 If the output is not as expected, investigate the condition and take corrective action based upon the root cause of the unexpected result. Experience has shown that the Oracle recommended Best Practice of using all available flash device space for Smart Flash Log and Smart Flash Cache provides the highest overall performance benefit with lowest maintenance overhead for an Oracle Exadata Database Machine. In some very rare cases for certain highly write-intensive applications, there may be some performance benefit to configuring grid disks onto the flash devices for datafile writes only. Flash grid disks should never be configured for redo which is addressed with the Smart Flash Log feature implemented in release 11.2.2.4 and higher. The space available to Smart Flash Cache and Smart Flash Log is reduced by the amount of space allocated to the grid disks deployed on flash devices. The usable space in the flash grid disk group is either half or one-third of the space allocated for grid disks on flash devices, depending on whether the flash grid disks are configured with ASM normal or high redundancy. If after thorough performance and recovery testing, a customer chooses to deploy grid disks on flash devices, it would be a supported, but not Best Practice, configuration.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => There are no griddisks configured on flash memory devices


DATA FROM DM01CEL01 FOR VERIFY THERE ARE NO GRIDDISKS CONFIGURED ON FLASH MEMORY DEVICES



name:              	 DATA_DM01_CD_00_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_00_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_00_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 01f726cc-700b-485a-9eaa-694eb0849b2a
offset:            	 32M
size:              	 1562G
status:            	 active


name:              	 DATA_DM01_CD_01_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_01_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_01_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 a2f82f99-eeef-427a-92f9-b8cdbdf71885
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_02_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_02_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 19c9916a-164c-42d3-bf8f-1c48e7687948
offset:            	 32M
size:              	 1562G
status:            	 not present

name:              	 DATA_DM01_CD_03_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_03_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 1
id:                	 e984f6af-f9dc-47a2-adb7-77bbf0477611
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_04_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_04_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 149ede0e-a368-4bba-aec3-84bb52ce7269
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_05_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_05_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6010159f-8f35-4cff-b926-6c135e084f06
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_06_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_06_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 9fe322c1-1b80-4594-bed5-db29eb9368dc
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_07_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_07_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:54+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 386b4e95-ecb8-4bef-92eb-cb3320eaf862
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_08_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_08_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:55+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 5a337742-98e6-4773-a613-90ee61572fd9
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_09_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_09_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:55+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 0ab29976-250d-4b5f-b2ae-cfb2469931c9
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_10_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_10_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:55+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 55942c6e-dc96-4aaf-b746-9c0b12c2a39e
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_11_dm01cel01
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_11_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:55+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 3b3c73e8-e439-4542-85fb-0889411e97ea
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DBFS_DG_CD_02_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_02_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:13+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 bd3b06ea-f3ac-4881-ab54-966bfeafb9a5
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 not present

name:              	 DBFS_DG_CD_03_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_03_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:14+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 a8db61ee-2f21-4efe-ade9-63d8a55c722d
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_04_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_04_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:16+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 13c9aa6b-bd65-4c59-abce-c1d94790ed69
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_05_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_05_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:17+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 7c92933e-bc02-4e84-b338-c08564cbc416
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_06_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_06_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:18+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 9eeca7c0-eda9-4d53-9bd9-21a19410e534
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_07_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_07_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:19+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 847da5d5-d2dd-432e-9fae-de7552b632c3
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_08_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_08_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:20+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 5e062bd3-b4c5-4a21-8547-53ab1329622c
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_09_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_09_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:21+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 f57617b7-ccfc-46cf-9284-5703d48bd0b7
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_10_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_10_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:22+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b4155f70-68eb-4e40-b57d-ea33a379dd19
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_11_dm01cel01
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_11_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel01
comment:
creationTime:      	 2012-11-28T10:33:23+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 ff2e1ce3-34cd-4d0b-a178-076e27ffdacd
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 RECO_DM01_CD_00_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_00_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_00_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 3abb259c-71ce-4ed1-9d95-05c35bddd79a
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_01_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_01_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_01_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 c89aabc2-846f-4e42-beca-a6b5a14b1c1c
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_02_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_02_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_02_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 31
id:                	 742506e9-8e37-4cd2-a673-d86854ee20fd
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 not present

name:              	 RECO_DM01_CD_03_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_03_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_03_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 d0d21fcd-e3bf-47e5-8967-6fd6fa0c28bb
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_04_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_04_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_04_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 616b12bc-c7f6-4df6-ab2f-2ccfc258db66
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_05_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_05_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_05_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e4baa13d-5177-441c-bc8e-3669d681b881
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_06_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_06_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_06_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 56fb36b6-f6a1-44c4-8f21-a7cabc05bb3b
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_07_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_07_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_07_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 102d6461-2efc-470a-a17a-4548b7bcc252
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_08_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_08_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_08_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:00+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 23915b36-fe24-4a0c-9fcd-63dce7c43e8b
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_09_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_09_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_09_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:01+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 f1a1bee8-f5de-4760-ba20-4b79b2fa4819
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_10_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_10_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_10_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:01+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 92b42de2-0c4c-4e1e-be2e-d2ad44a6a54d
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_11_dm01cel01
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_11_DM01CEL01
asmFailGroupName:  	 DM01CEL01
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_11_dm01cel01
comment:
creationTime:      	 2012-11-28T10:34:01+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 205f92c0-d89c-4d4e-8de3-9adc27120fcc
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active




DATA FROM DM01CEL02 FOR VERIFY THERE ARE NO GRIDDISKS CONFIGURED ON FLASH MEMORY DEVICES



name:              	 DATA_DM01_CD_00_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_00_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_00_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 1cc4dc6b-fc57-4ca6-a436-6e0fe47f3718
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_01_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_01_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_01_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 f00c4b5c-1539-4e94-bb76-e26646852fd9
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_02_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_02_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 171dd7e4-efee-4324-93ac-2c42e6d78771
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_03_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_03_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 1c92d7fa-68f6-407a-ade1-67ce8922695b
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_04_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_04_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b27f779f-beee-4511-bf27-f67ef12ffc1e
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_05_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_05_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel02
comment:
creationTime:      	 2013-05-24T18:24:10+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6db2ca7c-5792-401d-91cf-63722ba95a1a
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_06_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_06_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 865b488a-a187-45be-b2ea-2d3c63da72ef
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_07_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_07_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e2ed58ab-b31d-4ee4-82d9-fec9677255bf
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_08_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_08_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 1
id:                	 b565f8bb-1b2f-4b08-88a7-0479224bf433
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_09_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_09_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 32a49418-ca9b-4a32-ad9a-e046688723f1
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_10_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_10_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 cbacfa50-72ed-48e8-be9b-c5eb82f41339
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_11_dm01cel02
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_11_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:57+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 101393cb-2d18-436a-a473-433febfa66b6
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DBFS_DG_CD_02_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_02_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:25+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6a321802-5e6c-46db-9052-9e0c6735cb6a
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_03_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_03_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:26+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 1223a79b-8807-406a-b484-730f2d633d33
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_04_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_04_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:27+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 27cf32cf-badc-4f5b-b6a3-5a08c5e2cf63
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_05_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_05_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel02
comment:
creationTime:      	 2013-05-24T18:27:36+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 722c36e0-0c6d-451e-a2e1-22ef16b5a502
offset:            	 1562.046875G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_06_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_06_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:29+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e91f9e24-19d6-4fd7-9e9c-f36272a70a62
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_07_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_07_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:30+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 bf45c05e-b1a9-44b0-ac68-b2e24b8e5e01
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_08_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_08_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:31+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 77e9530d-8c83-41dd-80ac-cbb51af5c8ee
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_09_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_09_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:32+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 642bd2dd-0d0a-41ac-aa01-a9bb50e1f437
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_10_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_10_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:34+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 298782b4-53d9-4036-9516-28397e197d42
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_11_dm01cel02
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_11_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel02
comment:
creationTime:      	 2012-11-28T10:33:35+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 8274e762-f478-4132-bba6-e95015e90909
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 RECO_DM01_CD_00_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_00_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_00_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 9cd29129-b20f-4430-a81e-4ed0bc530445
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_01_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_01_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_01_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e102f1ad-fb87-4eb7-b76e-9c4e92125759
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_02_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_02_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_02_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 19202e21-b4bf-455e-aced-1ec0e788e3f4
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_03_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_03_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_03_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 a875839e-09f0-495d-bc22-303df77d1133
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_04_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_04_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_04_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b7e306de-170d-48ee-b56f-98eb70b1b2bd
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_05_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_05_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel02
comment:
creationTime:      	 2013-05-24T18:28:56+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 d3995b4e-e504-481f-8d04-2791110c2b1b
offset:            	 1591.15625G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_06_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_06_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_06_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6f43dd7b-0c14-4cbd-bf70-d60277a846ca
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_07_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_07_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_07_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 9823d35b-3600-4c4a-99be-50d397acf482
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_08_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_08_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_08_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6f74d3c7-2ecf-4eea-a77e-276ace517974
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_09_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_09_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_09_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 3dbeb04b-220d-4686-b541-bf6dc7b41d24
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_10_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_10_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_10_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 a10f32e6-149f-43af-ae40-5159d85d5b60
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_11_dm01cel02
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_11_DM01CEL02
asmFailGroupName:  	 DM01CEL02
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_11_dm01cel02
comment:
creationTime:      	 2012-11-28T10:34:02+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 57fea8cf-ee2d-4f6c-bf9e-c998b6088a1c
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active




DATA FROM DM01CEL03 FOR VERIFY THERE ARE NO GRIDDISKS CONFIGURED ON FLASH MEMORY DEVICES



name:              	 DATA_DM01_CD_00_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_00_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_00_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b6a667d8-9b06-4720-859f-b674f41834a2
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_01_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_01_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_01_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b804b321-6d3d-4d73-86f6-466ddacfb213
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_02_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_02_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6148e63b-e867-4cfc-95ef-6f0a2185a663
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_03_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_03_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 bd8e1666-b6b3-42b0-bf82-bdfd67790990
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_04_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_04_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 44b38d14-61c0-4b98-b5c5-03d0dfb910d6
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_05_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_05_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:58+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e9bf953f-9cc8-4c3f-81f3-903e64384f08
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_06_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_06_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 149ffee0-60e5-46fd-a7aa-9403ad547343
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_07_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_07_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 dd1c159a-3151-4b78-afea-fc970c2107cd
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_08_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_08_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 9a30b19f-4281-4d27-a9fd-c56a18542838
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_09_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_09_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 0c5650e0-aa96-4ca6-b54e-0e2aa13a98aa
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_10_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_10_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 74d73c1b-21a5-4a62-b2db-f800c90371bf
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DATA_DM01_CD_11_dm01cel03
asmDiskgroupName:  	 DATA_DM01
asmDiskName:       	 DATA_DM01_CD_11_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:59+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 af066de4-43b0-440c-bb32-4563e19fb7ca
offset:            	 32M
size:              	 1562G
status:            	 active

name:              	 DBFS_DG_CD_02_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_02_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_02_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:36+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 7fc040bc-8d1d-4ce8-bd6c-b851590700dc
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_03_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_03_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_03_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:37+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 250b3781-b60f-474a-b240-a7e5c2866fe3
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_04_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_04_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_04_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:38+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 502d1816-581a-4a56-ae8d-6dff90bcf34c
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_05_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_05_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_05_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:39+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 737b3dcf-22d8-4b3b-9158-457d8ed8654d
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_06_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_06_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_06_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:40+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 5271b6f0-a0c9-4a71-8efb-e897bd22c300
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_07_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_07_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_07_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:42+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 ad368f1d-c6cc-4cf5-9d50-c714a62d9e8f
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_08_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_08_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_08_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:43+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 83d693ae-933f-4c3f-8467-b40c29dd9bb5
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_09_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_09_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_09_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:44+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 c5b8cd32-b768-4c24-9612-3e4e731ef1f9
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_10_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_10_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_10_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:45+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 b2c89542-fd0b-4c18-8e24-ff13a4428b55
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 DBFS_DG_CD_11_dm01cel03
asmDiskgroupName:  	 DBFS_DG
asmDiskName:       	 DBFS_DG_CD_11_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 default
cellDisk:          	 CD_11_dm01cel03
comment:
creationTime:      	 2012-11-28T10:33:46+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 4c508a3e-c5cb-41fc-87ff-e7cff663fb4c
offset:            	 1832.59375G
size:              	 29.109375G
status:            	 active

name:              	 RECO_DM01_CD_00_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_00_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_00_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 56bcb1ab-6ff5-4f5f-9eca-a376c15a45d1
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_01_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_01_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_01_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 118a3c66-4a6e-4e99-ac6b-bcd3973015e1
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_02_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_02_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_02_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 e75f7e91-6f81-489c-85bc-05d058f3d48a
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_03_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_03_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_03_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 5f7d37ab-38b3-4aff-ae38-db8399ec590a
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_04_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_04_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_04_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 6870911c-c252-4f69-97b5-3dcd33e59da8
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_05_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_05_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_05_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 fc23cf84-3745-473a-9710-72ded9fa3cb6
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_06_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_06_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_06_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 682534a7-bce6-4b18-85fb-35a8a32ae85a
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_07_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_07_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_07_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 2505effc-449e-4c78-80ec-8abf6d85d7fa
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_08_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_08_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_08_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 ebbf0771-00f3-4c9c-a548-99e982c31e41
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_09_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_09_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_09_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 ec81b522-63da-4b90-a4ae-e2bfa65b86b5
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_10_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_10_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_10_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 316facb0-3201-4ef9-a75e-4ce5be9cfba3
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active

name:              	 RECO_DM01_CD_11_dm01cel03
asmDiskgroupName:  	 RECO_DM01
asmDiskName:       	 RECO_DM01_CD_11_DM01CEL03
asmFailGroupName:  	 DM01CEL03
availableTo:
cachingPolicy:     	 none
cellDisk:          	 CD_11_dm01cel03
comment:
creationTime:      	 2012-11-28T10:34:03+08:00
diskType:          	 HardDisk
errorCount:        	 0
id:                	 262fd20a-e7de-4c5c-ab7c-8d1b401577b1
offset:            	 1562.046875G
size:              	 270.546875G
status:            	 active




...More

Top

Verify ASM griddisk,diskgroup and Failure group mapping

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: To detect and repair improper configuration on a system Risk: If a single storage server is improperly configured to contain grid disks for a disk group that reside in more than one failure group, then it is possible for the disk group to be taken offline, causing the database to crash, if that single storage server is taken offline (e.g. for planned maintenance) or fails. Action / Repair: Please download the checkDiskFGMapping.sh script from MOS note 1351036.1 referenced below , copy it to the database server(s) on which exachk will be executed at /opt/oracle.cellos/ location and run checkDiskFGMapping.sh manually to make sure that all grid disks are mapped to the correct ASM diskgroup and failure group. Subsequently with checkDiskFGMapping.sh on the database server(s) where exachk will be executed, exachk will call checkDiskFGMapping.sh to check the mapping so that it doesn't need to be run manually again. Please follow the instructions in MOS note 1351036.1 for executing checkDiskFGMapping.sh and how to interpret its output. NOTE: exachk will not run the script in repair mode, only check mode. It is up to the customer to schedule the repair, if needed, during a maintenance window as part of a standard change control process.
Links	Note: 1351036.1 - Validate and Fix Proper ASM Failure Group Configuration on Oracle Exadata Database Machine -
Needs attention on	dm01db01
Passed on	-

Top

Verify storage server metric CD_IO_ST_RQ

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	One or more storage servers have been found that may have a conventional or flash disk with a performance problem. Please contact Oracle Support for further diagnostic assistance.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => No Storage Server conventional or flash disks have a performance problem


DATA FROM DM01CEL01 FOR VERIFY STORAGE SERVER METRIC CD_IO_ST_RQ









DATA FROM DM01CEL02 FOR VERIFY STORAGE SERVER METRIC CD_IO_ST_RQ










DATA FROM DM01CEL03 FOR VERIFY STORAGE SERVER METRIC CD_IO_ST_RQ









...More

Top

Verify Platform Configuration and Initialization Parameters for Consolidation

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	when more than one RDBMS instances are running on database server, Please review the following MOS Note for consolidation best practices.
Links	Note: 1274318.1 - Oracle Sun Database Machine X2-2 Setup/Configuration Best Practices (Doc ID 1274318.1) -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Only one non-ASM instance discovered


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY PLATFORM CONFIGURATION AND INITIALIZATION PARAMETERS FOR CONSOLIDATION



oracle   26335     1  0 Feb08 ?        00:47:46 ora_pmon_MCSDB1

Status on dm01db02: PASS => Only one non-ASM instance discovered


oracle    9353     1  0 Feb08 ?        00:48:45 ora_pmon_MCSDB2

Top

High Redundancy Redolog files

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Ensure the db_create_online_log_dest_n is configured for a high redundancy diskgroup A high redundancy diskgroup optimizes availability. If a high redundancy disk group is available, use the first high ASM redundancy disk group for all your Online Redo Logs or Standby Redo Logs. Use only one log member to minimize performance impact. If a high redundancy disk group is not available, multiplex redo log members across DATA and RECO ASM disk groups for additional protection.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database parameter Db_create_online_log_dest_n is set to recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - HIGH REDUNDANCY REDOLOG FILES



High redundancy disk groups = 	  1
Number of redo log groups with more than 1 member = 	     0
Number of diskgroup where redo log members are multiplexed = 		       1

Status on dm01db02: PASS => Database parameter Db_create_online_log_dest_n is set to recommended value


High redundancy disk groups = 	  1
Number of redo log groups with more than 1 member = 	     0
Number of diskgroup where redo log members are multiplexed = 		       1

Top

log_archive_dest_n

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Ensure if log_archive_dest_n location attribute specification is set to USE_DB_RECOVERY_FILE_DEST similar to *.log_archive_dest_1= 'LOCATION=USE_DB_RECOVERY_FILE_DEST' Do NOT set to a specific diskgroup since fast recovery area auto space management is ignored unless "USE_DB_FILE_RECOVERY_DEST" is explicitly used. This is not the same as setting it to the equivalent diskgroup name from db_recovery_file_dest parameter
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database parameters log_archive_dest_n with Location attribute are all set to recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - LOG_ARCHIVE_DEST_N

Status on dm01db02: PASS => Database parameters log_archive_dest_n with Location attribute are all set to recommended value

Top

compatible

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Set database parameter COMPATIBLE to current RDBMS version in use out to the fourth digit (ex: 11.2.0.2).
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database parameter COMPATIBLE is set to recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - COMPATIBLE



instance_vesion = 11.2.0.3.0 and compatible = 11.2.0.3.0

Status on dm01db02: PASS => Database parameter COMPATIBLE is set to recommended value


instance_vesion = 11.2.0.3.0 and compatible = 11.2.0.3.0

Top

Verify InfiniBand Cable Connection Quality on storage servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: InfiniBand cables require proper connections for optimal efficiency. Verifying the InfiniBand cable connection quality helps to ensure that the InfiniBand network operates at optimal efficiency. There is minimal impact to verify InfiniBand cable connection quality. Risk: InfiniBand cables that are not properly connected may negotiate to a lower speed, work intermittently, or fail. Action / Repair: Execute the following command on all database and storage servers: for ib_cable in `ls /sys/class/net \| grep ^ib`; do printf "$ib_cable: "; cat /sys/class/net/$ib_cable/carrier; done The output should look similar to: ib0: 1 ib1: 1 If anything other than "1" is reported, investigate that cable connection. NOTE: Storage servers should report 2 connections. X2-2(4170) and X2-2 database servers should report 2 connections. X2-8 database servers should report 8 connections.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => All InfiniBand network cables are connected on all Storage Servers


DATA FROM DM01CEL01 FOR VERIFY INFINIBAND CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/ib0/carrier = 1
/sys/class/net/ib1/carrier = 1




DATA FROM DM01CEL02 FOR VERIFY INFINIBAND CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/ib0/carrier = 1
/sys/class/net/ib1/carrier = 1





DATA FROM DM01CEL03 FOR VERIFY INFINIBAND CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/ib0/carrier = 1
/sys/class/net/ib1/carrier = 1




...More

Top

Verify Ethernet Cable Connection Quality

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Ethernet cables require proper connections for optimal efficiency. Verifying the Ethernet cable connection quality helps to ensure that the Ethernet network operates at optimal efficiency. There is minimal impact to verify Ethernet cable connection quality. Risk: Ethernet cables that are not properly connected may negotiate to a lower speed, work intermittently, or fail. Action / Repair: Execute the following command as the root userid on all database and storage servers: for cable in `ls /sys/class/net \| grep ^eth`; do printf "$cable: "; cat /sys/class/net/$cable/carrier; done The output should look similar to: eth0: 1 eth1: cat: /sys/class/net/eth1/carrier: Invalid argument eth2: cat: /sys/class/net/eth2/carrier: Invalid argument eth3: cat: /sys/class/net/eth3/carrier: Invalid argument eth4: 1 eth5: 1 "Invalid argument" usually indicates the device has not been configured and is not in use. If a device reports "0", investigate that cable connection. NOTE: Within machine types, the output of this command will vary by customer depending on how the customer chooses to configure the available ethernet cards.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => All Ethernet network cables are connected


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY ETHERNET CABLE CONNECTION QUALITY



/sys/class/net/eth0/carrier = 1
/sys/class/net/eth1/carrier = 1
/sys/class/net/eth2/carrier = 1
/sys/class/net/eth3/carrier =
/sys/class/net/eth4/carrier =
/sys/class/net/eth5/carrier =

Status on dm01db02: PASS => All Ethernet network cables are connected


/sys/class/net/eth0/carrier = 1
/sys/class/net/eth1/carrier = 1
/sys/class/net/eth2/carrier = 1
/sys/class/net/eth3/carrier =
/sys/class/net/eth4/carrier =
/sys/class/net/eth5/carrier =

Top

Verify Ethernet Cable Connection Quality on storage servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Ethernet cables require proper connections for optimal efficiency. Verifying the Ethernet cable connection quality helps to ensure that the Ethernet network operates at optimal efficiency. There is minimal impact to verify Ethernet cable connection quality. Risk: Ethernet cables that are not properly connected may negotiate to a lower speed, work intermittently, or fail. Action / Repair: Execute the following command as the root userid on all database and storage servers: for cable in `ls /sys/class/net \| grep ^eth`; do printf "$cable: "; cat /sys/class/net/$cable/carrier; done The output should look similar to: eth0: 1 eth1: cat: /sys/class/net/eth1/carrier: Invalid argument eth2: cat: /sys/class/net/eth2/carrier: Invalid argument eth3: cat: /sys/class/net/eth3/carrier: Invalid argument eth4: 1 eth5: 1 "Invalid argument" usually indicates the device has not been configured and is not in use. If a device reports "0", investigate that cable connection. NOTE: Within machine types, the output of this command will vary by customer depending on how the customer chooses to configure the available ethernet cards.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => All Ethernet network cables are connected on all Storage Servers


DATA FROM DM01CEL01 FOR VERIFY ETHERNET CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/eth0/carrier = 1
/sys/class/net/eth1/carrier =
/sys/class/net/eth2/carrier =
/sys/class/net/eth3/carrier =




DATA FROM DM01CEL02 FOR VERIFY ETHERNET CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/eth0/carrier = 1
/sys/class/net/eth1/carrier =
/sys/class/net/eth2/carrier =
/sys/class/net/eth3/carrier =





DATA FROM DM01CEL03 FOR VERIFY ETHERNET CABLE CONNECTION QUALITY ON STORAGE SERVERS



/sys/class/net/eth0/carrier = 1
/sys/class/net/eth1/carrier =
/sys/class/net/eth2/carrier =
/sys/class/net/eth3/carrier =




...More

Top

Verify InfiniBand Cable Connection Quality

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: InfiniBand cables require proper connections for optimal efficiency. Verifying the InfiniBand cable connection quality helps to ensure that the InfiniBand network operates at optimal efficiency. There is minimal impact to verify InfiniBand cable connection quality. Risk: InfiniBand cables that are not properly connected may negotiate to a lower speed, work intermittently, or fail. Action / Repair: Execute the following command on all database and storage servers: for ib_cable in `ls /sys/class/net \| grep ^ib`; do printf "$ib_cable: "; cat /sys/class/net/$ib_cable/carrier; done The output should look similar to: ib0: 1 ib1: 1 If anything other than "1" is reported, investigate that cable connection. NOTE: Storage servers should report 2 connections. X2-2(4170) and X2-2 database servers should report 2 connections. X2-8 database servers should report 8 connections.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => All InfiniBand network cables are connected


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY INFINIBAND CABLE CONNECTION QUALITY



/sys/class/net/ib0/carrier = 1
/sys/class/net/ib1/carrier = 1

Status on dm01db02: PASS => All InfiniBand network cables are connected


/sys/class/net/ib0/carrier = 1
/sys/class/net/ib1/carrier = 1

Top

db_recovery_file_dest_size

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Ensure db_recovery_file_dest_size <= 90% of the Recovery Area diskgroup TOTAL_MB size
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database parameter db_recovery_file_dest_size is set to recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - DB_RECOVERY_FILE_DEST_SIZE



90% of RECO_DM01 Total Space = 			 8522GB
db_recovery_file_dest_size= 			 2048GB

Status on dm01db02: PASS => Database parameter db_recovery_file_dest_size is set to recommended value


90% of RECO_DM01 Total Space = 			 8522GB
db_recovery_file_dest_size= 			 2048GB

Top

Recovery and Create File Destinations

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: In order to maximize recoverability and availability ensure that DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST are located in separate ASM diskgroups
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST are in different diskgroups


DATA FROM DM01DB01 - MCSDB DATABASE - RECOVERY AND CREATE FILE DESTINATIONS



db_recovery_file_dest = +RECO_DM01
db_create_file_dest = NONE SPECIFIED

Status on dm01db02: PASS => Database DB_CREATE_FILE_DEST and DB_RECOVERY_FILE_DEST are in different diskgroups


db_recovery_file_dest = +RECO_DM01
db_create_file_dest = NONE SPECIFIED

Top

cluster_interconnects

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Database parameter CLUSTER_INTERCONNECTS should be a colon delimited string of the IP addresses returned from sbin/ifconfig for each cluster_interconnect interface returned by oifcfg. In the case of X2-2 it is expected that there would only be one interface and therefore one IP address. This is used to avoid the Clusterware HAIP address; For an X2-8, the 4 IP addresses should be colon delimited
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database parameter CLUSTER_INTERCONNECTS is set to the recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - CLUSTER_INTERCONNECTS




Cluster Interconnect Value from instance = 192.168.10.1

Network card name and IP from oifcfg
bondib0 = 192.168.10.1

Status on dm01db02: PASS => Database parameter CLUSTER_INTERCONNECTS is set to the recommended value



Cluster Interconnect Value from instance = 192.168.10.2

Network card name and IP from oifcfg
bondib0 = 192.168.10.2

Top

cluster_interconnects

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain ASM initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these ASM initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are specific to the ASM instances. Unless otherwise specified, the value is for both X2-2 and X2-8 Database Machines. The impact of setting these parameters is minimal. Risk: If the ASM initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: ASM parameter CLUSTER_INTERCONNECTS should be a colon delimited string of the IP addresses returned from sbin/ifconfig for each cluster_interconnect interface returned by oifcfg. In the case of X2-2 it is expected that there would only be one interface and therefore one IP address. This is used to avoid the Clusterware HAIP address; For an X2-8, the 4 IP addresses should be colon delimited
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ASM parameter CLUSTER_INTERCONNECTS is set to the recommended value


DATA FROM DM01DB01 - MCSDB DATABASE - CLUSTER_INTERCONNECTS




Cluster Interconnect Value from instance = 192.168.10.1

Network card name and IP from oifcfg
bondib0 = 192.168.10.1

Status on dm01db02: PASS => ASM parameter CLUSTER_INTERCONNECTS is set to the recommended value



Cluster Interconnect Value from instance = 192.168.10.2

Network card name and IP from oifcfg
bondib0 = 192.168.10.2

Top

Check for parameter parallel_execution_message_size

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: PARALLEL_EXECUTION_MESSAGE_SIZE = 16384 Improves Parallel Query performance
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter PARALLEL_EXECUTION_MESSAGE_SIZE is set to recommended value

MCSDB1.parallel_execution_message_size = 16384

Status on MCSDB2: PASS => Database parameter PARALLEL_EXECUTION_MESSAGE_SIZE is set to recommended value

MCSDB2.parallel_execution_message_size = 16384

Top

Check for parameter sql92_security

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: SQL92_SECURITY = TRUE is a security optimization
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter SQL92_SECURITY is set to recommended value

MCSDB1.sql92_security = TRUE

Status on MCSDB2: PASS => Database parameter SQL92_SECURITY is set to recommended value

MCSDB2.sql92_security = TRUE

Top

Check for parameter use_large_pages

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Memory savings and reduce paging and swapping. Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: USE_LARGE_PAGES = ONLY ensures the entire SGA is stored in hugepage for Linux based systems only. Prequisites: Operating system hugepages setting need to be correctly configured and need to be adjusted when another instance is added or dropped or whenever sga sizes change. See referenced MOS Notes to configure HugePages.
Links	Note: 401749.1 - Shell Script to Calculate Values Recommended Linux HugePages / HugeTLB - Note: 361323.1 - HugePages on Linux: What It Is... and What It Is Not... -
Needs attention on	MCSDB1, MCSDB2
Passed on	-

Status on MCSDB1: FAIL => Database parameter USE_LARGE_PAGES is NOT set to recommended value

MCSDB1.use_large_pages = TRUE

Status on MCSDB2: FAIL => Database parameter USE_LARGE_PAGES is NOT set to recommended value

MCSDB2.use_large_pages = TRUE

Top

Check for parameter open_cursors

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: OPEN_CURSORS >= 300. Initial deployment database uses 1000
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter OPEN_CURSORS is set to recommended value

MCSDB1.open_cursors = 3000

Status on MCSDB2: PASS => Database parameter OPEN_CURSORS is set to recommended value

MCSDB2.open_cursors = 3000

Top

Check for parameter os_authent_prefix

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: OS_AUTHENT_PREFIX = is a security optimization (ie., null string)
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter OS_AUTHENT_PREFIX is set to recommended value

MCSDB1.os_authent_prefix =

Status on MCSDB2: PASS => Database parameter OS_AUTHENT_PREFIX is set to recommended value

MCSDB2.os_authent_prefix =

Top

Check for parameter parallel_threads_per_cpu

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: PARALLEL_THREADS_PER_CPU = 1 properly accounts for hyper threading
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter PARALLEL_THREADS_PER_CPU is set to recommended value

MCSDB1.parallel_threads_per_cpu = 1

Status on MCSDB2: PASS => Database parameter PARALLEL_THREADS_PER_CPU is set to recommended value

MCSDB2.parallel_threads_per_cpu = 1

Top

Check for parameter _enable_NUMA_support

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: _ENABLE_NUMA_SUPPORT = FALSE Enable NUMA support on Oracle Database Machine X2-8 only
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter _ENABLE_NUMA_SUPPORT is set to recommended value

_enable_NUMA_support = FALSE

Status on MCSDB2: PASS => Database parameter _ENABLE_NUMA_SUPPORT is set to recommended value

_enable_NUMA_support = FALSE

Top

Check for parameter parallel_adaptive_multi_user

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Performance impact: PQ degree will be reduced for some queries especially with concurrent workloads. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: set PARALLEL_ADAPTIVE_MULTI_USER to FALSE.
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter PARALLEL_ADAPTIVE_MULTI_USER is set to recommended value

MCSDB1.parallel_adaptive_multi_user = FALSE

Status on MCSDB2: PASS => Database parameter PARALLEL_ADAPTIVE_MULTI_USER is set to recommended value

MCSDB2.parallel_adaptive_multi_user = FALSE

Top

Check for parameter _file_size_increase_increment

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: _file_size_increase_increment = 2044M (2143289344 bytes) ensures adequately sized RMAN backup allocations
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter _file_size_increase_increment is set to the recommended value

_file_size_increase_increment = 2044M

Status on MCSDB2: PASS => Database parameter _file_size_increase_increment is set to the recommended value

_file_size_increase_increment = 2044M

Top

Check for parameter global_names

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: GLOBAL_NAMES = TRUE is a security optimization
Needs attention on	MCSDB1, MCSDB2
Passed on	-

Status on MCSDB1: FAIL => Database parameter GLOBAL_NAMES is NOT set to recommended value

MCSDB1.global_names = FALSE

Status on MCSDB2: FAIL => Database parameter GLOBAL_NAMES is NOT set to recommended value

MCSDB2.global_names = FALSE

Top

Check for parameter db_lost_write_protect

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: This is important for data block lost write detection and repair. Enable for primary and standby databases. Refer to MOS 1265884.1 and 1302539.1. Refer to section on how to address ORA-752 on the standby database
Links	Note: 1265884.1 - Resolving ORA-752 or ORA-600 [3020] During Standby Recovery - Note: 1302539.1 - Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration - Protect Against Data Corruption
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter DB_LOST_WRITE_PROTECT is set to recommended value

MCSDB1.db_lost_write_protect = typical

Status on MCSDB2: PASS => Database parameter DB_LOST_WRITE_PROTECT is set to recommended value

MCSDB2.db_lost_write_protect = typical

Top

Check for parameter log_buffer

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Database LOG_BUFFER parameter value of at least 134217728 (128M) ensures adequate buffer space for new LGWR transport.
Needs attention on	-
Passed on	MCSDB1, MCSDB2

Status on MCSDB1: PASS => Database parameter LOG_BUFFER is set to recommended value

MCSDB1.log_buffer = 134217728

Status on MCSDB2: PASS => Database parameter LOG_BUFFER is set to recommended value

MCSDB2.log_buffer = 134217728

Top

Verify Disk Cache Policy on database server

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: "Disk Cache Policy" is set to "Disabled" by default and should not be changed because the cache created by setting "Disk Cache Policy" to "Enabled" is not battery backed. The impact of verifying that "Disk Cache Policy" is set to "Disabled" is minimal. The impact of suddenly losing power with "Disk Cache Policy" set to anything other than "Disabled" will vary according to each specific case, and cannot be estimated here. Risk: If the "Disk Cache Policy" is not "Disabled", there is a risk of data loss in the event of a sudden power loss because the cache created by "Disk Cache Policy" is not backed up by a battery. Action / Repair: To verify that "Disk Cache Policy" is set to "Disabled" on all servers, use the following command as the "root" userid on the first database server in the cluster: dcli -g /opt/oracle.SupportTools/onecommand/all_group -l root /opt/MegaRAID/MegaCli/MegaCli64 -LdPdInfo -aALL \| grep -i 'Disk Cache Policy' The output will be similar to: randomdb01: Disk Cache Policy : Disabled randomdb01: Disk Cache Policy : Disabled randomdb01: Disk Cache Policy : Disabled randomcel03: Disk Cache Policy : Disabled randomcel03: Disk Cache Policy : Disabled randomcel03: Disk Cache Policy : Disabled randomcel03: Disk Cache Policy : Disabled randomcel03: Disk Cache Policy : Disabled If any of the results are other than "Disabled", identify the LUN in question and reset the "Disk Cache Policy" to "Disabled" using the following command (where Lx= the lun in question, for example: L2): MegaCli64 -LDSetProp -DisDskCache -Lx -a0 Note: The "Disk Cache Policy" is completely separate from the disk controller caching mode of "WriteBack". Do not confuse the two. The cache created by "WriteBack" cache mode is battery-backed, the cache created by "Disk Cache Policy" is not!
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Disk cache policy is set to Disabled on database server


DATA FROM DM01DB01 FOR VERIFY DISK CACHE POLICY ON DATABASE SERVER



Disk Cache Policy   : Disabled
Slot Number: 1
Slot Number: 2
Slot Number: 3

Status on dm01db02: PASS => Disk cache policy is set to Disabled on database server


DATA FROM DM01DB02 FOR VERIFY DISK CACHE POLICY ON DATABASE SERVER



Disk Cache Policy   : Disabled
Slot Number: 1
Slot Number: 2
Slot Number: 3

Top

Verify Disk Cache Policy on Storage Server

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: "Disk Cache Policy" is set to "Disabled" by default and should not be changed because the cache created by setting "Disk Cache Policy" to "Enabled" is not battery backed. The impact of verifying that "Disk Cache Policy" is set to "Disabled" is minimal. The impact of suddenly losing power with "Disk Cache Policy" set to anything other than "Disabled" will vary according to each specific case, and cannot be estimated here. Risk: If the "Disk Cache Policy" is not "Disabled", there is a risk of data loss in the event of a sudden power loss because the cache created by "Disk Cache Policy" is not backed up by a battery. Action / Repair: To verify that "Disk Cache Policy" is set to "Disabled" on all servers, use the following command as the "root" userid on the first database server in the cluster: Note : -The slot number is included in the output for assistance in identifying disk drives. dcli -g /opt/oracle.SupportTools/onecommand/all_group -l root /opt/MegaRAID/MegaCli/MegaCli64 -LdPdInfo -aALL \|egrep -i 'Disk Cache Policy\|slot number'
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Disk cache policy is set to Disabled on all storage server


DATA FROM DM01CEL01 FOR VERIFY DISK CACHE POLICY ON STORAGE SERVER



Disk Cache Policy   : Disabled
Slot Number: 0
Disk Cache Policy   : Disabled
Slot Number: 1
Disk Cache Policy   : Disabled
Slot Number: 3
Disk Cache Policy   : Disabled
Slot Number: 4
Disk Cache Policy   : Disabled
Slot Number: 5
Disk Cache Policy   : Disabled
Slot Number: 6
Disk Cache Policy   : Disabled
Slot Number: 7
Disk Cache Policy   : Disabled
Slot Number: 8

Disk Cache Policy   : Disabled
Slot Number: 9
Disk Cache Policy   : Disabled
Slot Number: 10
Disk Cache Policy   : Disabled
Slot Number: 11




DATA FROM DM01CEL02 FOR VERIFY DISK CACHE POLICY ON STORAGE SERVER



Disk Cache Policy   : Disabled
Slot Number: 0
Disk Cache Policy   : Disabled
Slot Number: 1
Disk Cache Policy   : Disabled
Slot Number: 2
Disk Cache Policy   : Disabled
Slot Number: 3
Disk Cache Policy   : Disabled
Slot Number: 4
Disk Cache Policy   : Disabled
Slot Number: 6
Disk Cache Policy   : Disabled
Slot Number: 7
Disk Cache Policy   : Disabled
Slot Number: 8
Disk Cache Policy   : Disabled
Slot Number: 9
Disk Cache Policy   : Disabled
Slot Number: 10
Disk Cache Policy   : Disabled
Slot Number: 11
Disk Cache Policy   : Disabled
Slot Number: 5




DATA FROM DM01CEL03 FOR VERIFY DISK CACHE POLICY ON STORAGE SERVER



Disk Cache Policy   : Disabled
Slot Number: 0
Disk Cache Policy   : Disabled
Slot Number: 1
Disk Cache Policy   : Disabled
Slot Number: 2
Disk Cache Policy   : Disabled
Slot Number: 3
Disk Cache Policy   : Disabled
Slot Number: 4
Disk Cache Policy   : Disabled
Slot Number: 5
Disk Cache Policy   : Disabled
Slot Number: 6
Disk Cache Policy   : Disabled
Slot Number: 7
Disk Cache Policy   : Disabled
Slot Number: 8
Disk Cache Policy   : Disabled
Slot Number: 9
Disk Cache Policy   : Disabled
Slot Number: 10
Disk Cache Policy   : Disabled
Slot Number: 11




...More

Top

Minimum exadata version required for ASR

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Minimum version is 11.2.1.3.1 for ASR support Risk: Automated SR's will not be filed for failures detected on the DBM Action / Repair: Upgrade to 11.2.1.3.1 or higher to get this functionality
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Exadata software version supports Automatic Service Request functionality


DATA FROM DM01DB01 FOR MINIMUM EXADATA VERSION REQUIRED FOR ASR




Kernel version: 2.6.32-400.1.1.el5uek #1 SMP Mon Jun 25 20:25:08 EDT 2012 x86_64
Image version: 11.2.3.2.0.120713
Image activated: 2012-11-28 09:53:22 +0800
Image status: success
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

Status on dm01db02: PASS => Exadata software version supports Automatic Service Request functionality


DATA FROM DM01DB02 FOR MINIMUM EXADATA VERSION REQUIRED FOR ASR




Kernel version: 2.6.32-400.1.1.el5uek #1 SMP Mon Jun 25 20:25:08 EDT 2012 x86_64
Image version: 11.2.3.2.0.120713
Image activated: 2012-11-28 09:53:21 +0800
Image status: success
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

Top

Verify Electronic Storage Module (ESM) Lifetime is within Specification

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The Flash 20 card supports ESM lifetime to enable proactive replacement before failure. The impact of verifying that the ESM lifetime is within specification is minimal. Replacing an ESM requires a scheduled outage. Risk: Failure of the ESM will put the Flash 20 card in WriteThrough mode which has a high impact on performance. Action / Repair: Top verify the ESM lifetime value, use the following command on the storage servers: for RISER in RISER1/PCIE1 RISER1/PCIE4 RISER2/PCIE2 RISER2/PCIE5; do ipmitool sunoem cli "show /SYS/MB/$RISER/F20CARD/UPTIME"; done \| grep value -A4 The output will be similar to: value = 3382.350 Hours upper_nonrecov_threshold = 17500.000 Hours upper_critical_threshold = 17200.000 Hours upper_noncritical_threshold = 16800.000 Hours lower_noncritical_threshold = N/A -- If the "value" reported exceeds the "upper_noncritical_threshold" reported, schedule a replacement of the relevant ESM. NOTE: There is a bug in ILOM firmware version 3.0.9.19.a which may report "Invalid target..." for "RISER1/PCIE4". If that happens, consult your site records to verify the age the ESM Module. NOTE: For Aura II (F20 M2) cards, the CPLD reports the End of Life indication on the F20 M2 cards, so the thresholds for UPTIME sensor are not needed. The threshold values are replaced with "N/A". The ILOM will fault the system when it's time to replace the F20 M2's ESM. Beginning with 2.1.3, exachk does not execute this check on F20 M2 cards. Beginning with 2.1.5, exachk posts a message in the html report detail that the card is an F20M2 model and the check is not applicable.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Electronic Storage Module (ESM) Lifetime is within specification for all flash cards on all storage servers


DATA FROM DM01CEL01 FOR VERIFY ELECTRONIC STORAGE MODULE (ESM) LIFETIME IS WITHIN SPECIFICATION



/SYS/MB/RISER1/PCIE1/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER1/PCIE4/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE2/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE5/F20CARD is an F20M2 model and this esm lifetime check does not apply.





DATA FROM DM01CEL02 FOR VERIFY ELECTRONIC STORAGE MODULE (ESM) LIFETIME IS WITHIN SPECIFICATION




/SYS/MB/RISER1/PCIE1/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER1/PCIE4/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE2/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE5/F20CARD is an F20M2 model and this esm lifetime check does not apply.





DATA FROM DM01CEL03 FOR VERIFY ELECTRONIC STORAGE MODULE (ESM) LIFETIME IS WITHIN SPECIFICATION



/SYS/MB/RISER1/PCIE1/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER1/PCIE4/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE2/F20CARD is an F20M2 model and this esm lifetime check does not apply.

/SYS/MB/RISER2/PCIE5/F20CARD is an F20M2 model and this esm lifetime check does not apply.





...More

Top

Data network is separate from management network on storage server

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical, 03/02/11 Benefit / Impact: It is a requirement that the management network be on a different non-overlapping sub-net than the InfiniBand network and the client access network. This is necessary for better network security, better client access bandwidths, and for Auto Service Request (ASR) to work correctly. The management network comprises of the eth0 network interface in the database and storage severs, the ILOM network interfaces of the database and storage servers, and the Ethernet management interfaces of the InfiniBand switches and PDUs. Risk: Having the management network on the same subnet as the client access network will reduce network security, potentially restrict the client access bandwidth to/from the Database Machine to a single 1GbE link, and will prevent ASR from working correctly. Action / Repair: To verify that the management network interface (eth0) is on a separate network from other network interfaces, execute the following command as the "root" userid on both storage and database servers: grep -i network /etc/sysconfig/network-scripts/ifcfg* \| cut -f5 -d"/" \| grep -v "#" The output will be similar to: ifcfg-bondeth0:NETWORK=10.204.77.0 ifcfg-bondib0:NETWORK=192.168.76.0 ifcfg-eth0:NETWORK=10.204.78.0 ifcfg-lo:NETWORK=127.0.0.0 The expected result is that the network values are different. If they are not, investigate and correct the condition.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Management network is separate from data network on all storage servers


DATA FROM DM01CEL01 FOR DATA NETWORK IS SEPARATE FROM MANAGEMENT NETWORK ON STORAGE SERVER



ifcfg-bondib0:NETWORK=192.168.8.0
ifcfg-eth0:NETWORK=10.187.5.0




DATA FROM DM01CEL02 FOR DATA NETWORK IS SEPARATE FROM MANAGEMENT NETWORK ON STORAGE SERVER



ifcfg-bondib0:NETWORK=192.168.8.0
ifcfg-eth0:NETWORK=10.187.5.0





DATA FROM DM01CEL03 FOR DATA NETWORK IS SEPARATE FROM MANAGEMENT NETWORK ON STORAGE SERVER



ifcfg-bondib0:NETWORK=192.168.8.0
ifcfg-eth0:NETWORK=10.187.5.0




...More

Top

Ambient Temperature

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Maintaining environmental temperature conditions within design specification for an Oracle Exadata Database Machine helps to achieve maximum efficiency and targeted component service lifetimes. The impact of verifying the ambient temperature range is minimal. The impact of correcting reported ambient temperatures outside of design specification range will vary depending upon the cause of the environmental conditions. Risk: Temperatures outside the design specification range affect all components within the chassis of an Oracle Exadata Database Machine, possibly manifesting performance problems and shortened service lifetimes. Action / Repair: To verify the ambient temperature range of all servers, execute the following command as the root userid on the first database server in the cluster: if [ `cat /opt/oracle.SupportTools/onecommand/cell_group \| egrep "01$\|02$\|03$" \| wc -l` = 0 ] then echo "SKIPPED: This cluster does not access the first three storage servers. Ambient temperature check skipped."; else export SS_LIST=`awk '{OFS=","; ORS=""}{ print $0 "," }' /opt/oracle.SupportTools/onecommand/cell_group \| cut -d"," -f 1-3` export AVG_TEMP=`dcli -c $SS_LIST -l root 'ipmitool sunoem cli "show /SYS/T_AMB" \| grep value' \| cut -d" " -f 4 \| awk '{ SUM += $1} END { printf "%.0f",SUM/3}'`; if [ $AVG_TEMP -ge 5 -a $AVG_TEMP -le 32 ] then echo "SUCCESS: Average ambient temperature is within range of 5 to 32 degrees Centigrade: $AVG_TEMP"; else echo -e "FAILURE: Average ambient temperature is outside range of 5 to 32 degrees Centigrade: $AVG_TEMP"; fi; fi The output should be similar to: SUCCESS: Average ambient temperature is within range of 5 to 32 degrees Centigrade: 27 If the "SUCCESS" message is not returned, there are two possibilities: 1) The "SKIPPED" message indicates that the cluster in which this command was executed does not have access in cell_group to the first 3 storage servers in the physical rack. This could occur because the physical rack is logically or physically divided into multiple clusters. The corrective action is to execute the command in the cluster on the physical rack that has access to the first three storage servers in cell_group. 2) The "FAILURE" message indicates that the average ambient temperature of the first three storage servers in the physical rack was outside the permitted range of 5C to 32C. The corrective action is to investigate and correct the environmental conditions. NOTE: Since there is no one sensor in the physical rack for overall ambient temperature of the data center air, this check reads the ambient temperature from the first three storage servers in the physical rack (deployed according to Oracle standards) which are closest to the air flow from the raised floor tiles and averages the result. The averaging is in case there might be a sensor reading incorrectly.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Ambient temperature is within the recommended range.


DATA FROM DM01CEL01 FOR AMBIENT TEMPERATURE



value = 25.000 degree C




DATA FROM DM01CEL02 FOR AMBIENT TEMPERATURE



value = 26.000 degree C




DATA FROM DM01CEL03 FOR AMBIENT TEMPERATURE




value = 25.000 degree C




...More

Top

Verify Oracle ASM instance use RDS Protocol over InfiniBand Network.

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: RDS protocol provides superior performance for Oracle RAC communication because it does not require additional memory buffering operations when moving data from process memory to the network interface for RAC inter-node communication. There is minimal impact to verify that RDS protocol is in use. If it is not, implementing it will require a relink of the Oracle software, which requires an outage. Risk: If the Oracle RAC databases do not use RDS protocol over the InfiniBand network, RAC inter-node communication will be sub-optimal. Action / Repair: Perform the following steps on the database servers: 1. Verify an Oracle RAC database is using the RDS protocol over the InfiniBand Network by checking all alert logs on all nodes: Cluster communication is configured to use the following interface(s) for this instance 192.168.20.21 cluster interconnect IPC version:Oracle RDS/IP (generic) 1. If it is not running RDS, relink the Oracle binary via the following: * (as oracle) Shutdown any process using the Oracle binary * (as root) GRID_HOME/crs/install/rootcrs.pl -unlock only required if relinking in the Grid Infrastructure home * (as oracle) cd $ORACLE_HOME/rdbms/lib * (as oracle) make -f ins_rdbms.mk ipc_rds ioracle * (as root) GRID_HOME/crs/install/rootcrs.pl -patch only required if relinking in the Grid Infrastructure home Note: Avoid using the relink all command due to various issues. Use the make commands as seen above when relinking oracle binaries. Note: The dcli utility can be used to double check that all nodes are configured consistently with respect to the skgxp libraries in use. An example command to perform this check is dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l oracle md5sum ${ORACLE_HOME}/lib/libskgxp11.so
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Oracle ASM Communication is using RDS protocol on Infiniband Network


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY ORACLE ASM INSTANCE USE RDS PROTOCOL OVER INFINIBAND NETWORK.



rds

Status on dm01db02: PASS => Oracle ASM Communication is using RDS protocol on Infiniband Network

rds

Top

Verify database server disk controllers use writeback cache

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Database servers use an internal RAID controller with a battery-backed cache to host local filesystems. For maximum performance when writing I/O to local disks, the battery-backed cache should be in "WriteBack" mode. The impact of configuring the battery-backed cache in "WriteBack" mode is minimal. Risk: Not configuring the battery-backed cache in "WriteBack" mode will result in degraded performance when writing I/O to the local database server disks. Action / Repair: To verify that the disk controller battery-backed cache is in "WriteBack" mode, run the following set of commands as the "root" userid on all database servers: unset TMP_CMD; unset TMP_RSLT; if [ -x /opt/MegaRAID/MegaCli/MegaCli64 ] then #Linux export TMP_CMD=/opt/MegaRAID/MegaCli/MegaCli64 else #Solaris export TMP_CMD=/opt/MegaRAID/MegaCli fi; TMP_RSLT=`$TMP_CMD -CfgDsply -a0 \| grep -i writethrough \| wc -l`; if [ $TMP_RSLT = 0 ] then echo -e "\nSUCCESS\n" else echo -e "\nFAILURE:"; $TMP_CMD -CfgDsply -a0 \| grep -i writethrough; echo -e "\n"; fi; The output should be: SUCCESS If the battery-backed cache is not in "WriteBack" mode, run these commands on the effected server to place the battery-backed cache into "WriteBack" mode: if [ -x /opt/MegaRAID/MegaCli/MegaCli64 ] then #Linux export TMP_CMD=/opt/MegaRAID/MegaCli/MegaCli64 else #Solaris export TMP_CMD=/opt/MegaRAID/MegaCli fi $TMP_CMD -LDSetProp WB -Lall -a0 $TMP_CMD -LDSetProp NoCachedBadBBU -Lall -a0 $TMP_CMD -LDSetProp NORA -Lall -a0 $TMP_CMD -LDSetProp Direct -Lall -a0 NOTE: No settings should be modified on Exadata storage cells. The mode described above applies only to database servers in an Exadata database machine.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database server disk controllers use writeback cache


DATA FROM DM01DB01 FOR VERIFY DATABASE SERVER DISK CONTROLLERS USE WRITEBACK CACHE



Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU

Status on dm01db02: PASS => Database server disk controllers use writeback cache


DATA FROM DM01DB02 FOR VERIFY DATABASE SERVER DISK CONTROLLERS USE WRITEBACK CACHE



Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU

Top

Infiniband Switch counters on all switchs

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Verifying that there are no high, persistent InfiniBand network error counters helps to maintain the InfiniBand network at peak efficiency. The impact of verifying there are no InfiniBand network errors is minimal. Risk: Without verifying the InfiniBand network error counters, there is a risk that a component will degrade the InfiniBand network performance, yet may not be sending an alert or error condition. Action / Repair: Use the command shown below on one of the database or storage servers: # ibqueryerrors.pl -rR -s RcvSwRelayErrors,XmtDiscards,XmtWait There should be no errors reported. The InfiniBand counters are cumulative and the errors may have occurred at any time in the past. If there are errors, it is recommended to clear the InfiniBand counters with ibclearcounters, let the system run for a few minutes under load, and then re-execute the ibquerryerrors command. Any links reporting persistent errors (especially RcvErrors or SymbolErrors) may indicate a bad/loose cable or port. Some counters (e.g RcvErrors, SymbolErrors) can increment when nodes are rebooted. Small values for these counters which are less than the "LinkDowned" counter are generally not a problem. The "LinkDowned" counter indicates the number of times the port has gone down (usually for valid reasons, e.g reboot) and is not usually an error indicator by itself. If there are persistent, high InfiniBand network error counters, investigate and correct the condition.
Needs attention on	dm01db01
Passed on	-

Status on dm01db01: FAIL => InfiniBand network error counters are non-zero


DATA FROM DM01DB01 FOR INFINIBAND SWITCH COUNTERS ON ALL SWITCHS



Suppressing: RcvSwRelayErrors XmtDiscards XmtWait
Errors for 0x2128e8b08ea0a0 "SUN DCS 36P QDR dm01sw-ib3.mcsdb.com"
GUID 0x2128e8b08ea0a0 port 7: [RcvErrors == 1]
Link info:      2   7[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x0021280001cf4886      8    2[  ] "SUN DCS 36P QDR dm01sw-ib3.mcsdb.com" ( )
Errors for 0x2128e8af6da0a0 "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com"
GUID 0x2128e8af6da0a0 port 7: [RcvErrors == 1]
Link info:      1   7[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x0021280001cf4886      7    1[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 10: [RcvErrors == 1]
Link info:      1  10[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x0021280001cf4862      3    1[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 13: [LinkDowned == 1]
Link info:      1  13[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   14[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 14: [LinkDowned == 1]
Link info:      1  14[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   13[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 15: [LinkDowned == 1]
Link info:      1  15[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   16[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 16: [LinkDowned == 1]

Link info:      1  16[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   15[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 17: [LinkDowned == 1]
Link info:      1  17[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   18[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 18: [LinkDowned == 1]
Link info:      1  18[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   17[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
GUID 0x2128e8af6da0a0 port 31: [LinkDowned == 1]
Link info:      1  31[  ] ==( 4X 10.0 Gbps Active/  LinkUp)==>  0x002128e8b08ea0a0      2   31[  ] "SUN DCS 36P QDR dm01sw-ib2.mcsdb.com" ( )
...More

Top

Verify InfiniBand Fabric Topology (verify-topology)

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Verifying that the InfiniBand network is configured with the correct topology for an Oracle Exadata Database Machine helps to ensure that the InfiniBand network operates at maximum efficiency. Risk: An incorrect InfiniBand topology will cause the InfiniBand network to operate at degraded efficiency, intermittently, or fail to operate. Action / Repair: Execute the verify-topology command as shown below: # /opt/oracle.SupportTools/ibdiagtools/verify-topology -t fattree [ DB Machine InfiniBand Cabling Topology Verification Tool ] Is every external switch connected to every internal switch..........[SUCCESS] Are any external switches connected to each other....................[SUCCESS] Are any hosts connected to spine switch..............................[SUCCESS] Check if all hosts have 2 CAs to different switches..................[SUCCESS] Leaf switch check: cardinality and even distribution.................[SUCCESS] Check if each rack has an valid internal ring........................[SUCCESS]If anything other than "SUCCESS" is reported, investigate and correct the condition.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => Verify-topology executes without any errors or warning


DATA FROM DM01DB01 FOR VERIFY INFINIBAND FABRIC TOPOLOGY (VERIFY-TOPOLOGY)




[ DB Machine Infiniband Cabling Topology Verification Tool ]
[Version IBD VER 2.c ]

--------------- Quarter Rack Exadata V2 Cabling Check---------

Check if all hosts have 2 CAs to different switches..................[SUCCESS]
Leaf switch check: cardinality and even distribution.................[SUCCESS]
Check if each rack has an valid internal ring........................[SUCCESS]

Top

Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Database Server]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: The Oracle Exadata Database Machine is tightly integrated, and verifying the hardware and firmware before the Oracle Exadata Database Machine is placed into or returned to production status can avoid problems related to the hardware or firmware modifications. The impact for these verification steps is minimal. Risk: If the hardware and firmware are not validated, inconsistencies between database and storage servers can lead to problems and outages. Action / Repair: Verify the hardware and firmware configuration by executing the /opt/oracle.cellos/CheckHWnFWProfile script as the root userid as shown below: # /opt/oracle.cellos/CheckHWnFWProfile [SUCCESS] The hardware and firmware profile matches one of the supported profile If any result other than "SUCCESS" is returned, investigate and correct the condition. NOTE: CheckHWnFWProfile is also executed at each boot of the storage and database servers.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Hardware and firmware profile check is successful. [Database Server]


DATA FROM DM01DB01 FOR VERIFY HARDWARE AND FIRMWARE ON DATABASE AND STORAGE SERVERS (CHECKHWNFWPROFILE) [DATABASE SERVER]



[40;1;32m[SUCCESS][0m The hardware and firmware profile matches one of the supported profiles

Status on dm01db02: PASS => Hardware and firmware profile check is successful. [Database Server]


DATA FROM DM01DB02 FOR VERIFY HARDWARE AND FIRMWARE ON DATABASE AND STORAGE SERVERS (CHECKHWNFWPROFILE) [DATABASE SERVER]



[40;1;32m[SUCCESS][0m The hardware and firmware profile matches one of the supported profiles

Top

Verify Software on Storage Servers (CheckSWProfile.sh)

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Verifying the software configuration after initial deployment, upgrades, or patching and before the Oracle Exadata Database Machine is placed into or returned to production status can avoid problems related to the software modifications. The overhead for these verification steps is minimal. Risk: If the software is not validated, inconsistencies between database and storage servers can lead to problems and outages. Action / Repair: Verify the storage server software configuration with the /opt/oracle.SupportTools/CheckSWProfile.sh script, as shown in the following example: [root@node1 oracle.SupportTools]# ./CheckSWProfile.sh -c [INFO] SUCCESS: Meets requirements of operating platform and installed software for [INFO] below listed releases and patches of Exadata and of corresponding Database. [INFO] Check does NOT verify correctness of configuration for installed software. [The_ExadataAndDatabaseReleases] Exadata: 11.2.2.1.0 OracleDatabase: 11.2.0.2+Patches
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Software profile check is successful on all storage servers.


DATA FROM DM01CEL01 FOR VERIFY SOFTWARE ON STORAGE SERVERS (CHECKSWPROFILE.SH)




[INFO] [1;32mSUCCESS[0m: Meets requirements of operating platform and InfiniBand software.
[INFO] Check does NOT verify correctness of configuration for installed software.





DATA FROM DM01CEL02 FOR VERIFY SOFTWARE ON STORAGE SERVERS (CHECKSWPROFILE.SH)




[INFO] [1;32mSUCCESS[0m: Meets requirements of operating platform and InfiniBand software.
[INFO] Check does NOT verify correctness of configuration for installed software.






DATA FROM DM01CEL03 FOR VERIFY SOFTWARE ON STORAGE SERVERS (CHECKSWPROFILE.SH)




[INFO] [1;32mSUCCESS[0m: Meets requirements of operating platform and InfiniBand software.
[INFO] Check does NOT verify correctness of configuration for installed software.





...More

Top

Verify Hardware and Firmware on Database and Storage Servers (CheckHWnFWProfile) [Storage Server]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: The Oracle Exadata Database Machine is tightly integrated, and verifying the hardware and firmware before the Oracle Exadata Database Machine is placed into or returned to production status can avoid problems related to the hardware or firmware modifications. The impact for these verification steps is minimal. Risk: If the hardware and firmware are not validated, inconsistencies between database and storage servers can lead to problems and outages. Action / Repair: Verify the hardware and firmware configuration by executing the /opt/oracle.cellos/CheckHWnFWProfile script as the root userid as shown below: # /opt/oracle.cellos/CheckHWnFWProfile [SUCCESS] The hardware and firmware profile matches one of the supported profile If any result other than "SUCCESS" is returned, investigate and correct the condition. NOTE: CheckHWnFWProfile is also executed at each boot of the storage and database servers.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => Hardware and firmware profile check is successful on all storage servers.


DATA FROM DM01CEL01 FOR VERIFY HARDWARE AND FIRMWARE ON DATABASE AND STORAGE SERVERS (CHECKHWNFWPROFILE) [STORAGE SERVER]



[40;1;32m[SUCCESS][0m The hardware and firmware profile matches one of the supported profiles




DATA FROM DM01CEL02 FOR VERIFY HARDWARE AND FIRMWARE ON DATABASE AND STORAGE SERVERS (CHECKHWNFWPROFILE) [STORAGE SERVER]



[40;1;32m[SUCCESS][0m The hardware and firmware profile matches one of the supported profiles




DATA FROM DM01CEL03 FOR VERIFY HARDWARE AND FIRMWARE ON DATABASE AND STORAGE SERVERS (CHECKHWNFWPROFILE) [STORAGE SERVER]




[40;1;32m[SUCCESS][0m The hardware and firmware profile matches one of the supported profiles




...More

Top

Local listener set to node VIP

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The LOCAL_LISTENER parameter should be set to the node VIP. If you need fully qualified domain names, ensure that LOCAL_LISTENER is set to the fully qualified domain name (node-vip.mycompany.com). By default a local listener is created during cluster configuration that runs out of the grid infrastructure home and listens on the specified port(default is 1521) of the node VIP.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Local listener init parameter is set to local node VIP


DATA FROM DM01DB01 - MCSDB DATABASE - LOCAL LISTENER SET TO NODE VIP



Local Listener= (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.187.4.92)(PORT=1521)))) VIP Names=dm0101-vip VIP IPs=10.187.4.92

Status on dm01db02: PASS => Local listener init parameter is set to local node VIP


Local Listener= (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.187.4.93)(PORT=1521)))) VIP Names=dm0102-vip VIP IPs=10.187.4.93

Top

Voting disk status

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Stability, Availability Risk: Cluster instability Action / Repair: Voting disks that are not online would indicate a problem with the clusterware and should be investigated as soon as possible. All voting disks are expected to be ONLINE. Use the following command to list the status of the voting disks $CRS_HOME/bin/crsctl query css votedisk\|sed 's/^ //g'\|grep ^[0-9] The output should look similar to the following, one row were voting disk, all disks should indicate ONLINE 1. ONLINE 192c8f030e5a4fb3bf77e43ad3b8479a (o/192.168.10.102/DBFS_DG_CD_02_sclcgcel01) [DBFS_DG] 2. ONLINE 2612d8a72d194fa4bf3ddff928351c41 (o/192.168.10.104/DBFS_DG_CD_02_sclcgcel03) [DBFS_DG] 3. ONLINE 1d3cceb9daeb4f0bbf23ee0218209f4c (o/192.168.10.103/DBFS_DG_CD_02_sclcgcel02) [DBFS_DG]
Needs attention on	dm01db01
Passed on	-

Status on dm01db01: WARNING => All voting disks are not online


DATA FROM DM01DB01 - MCSDB DATABASE - VOTING DISK STATUS



##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
1. OFFLINE  2a642ed3cc384febbf1f14ee69ab1523 (o/192.168.10.5/DBFS_DG_CD_02_dm01cel03) [DBFS_DG]
2. ONLINE   403c030ed70c4f91bf758a919f42e695 (o/192.168.10.4/DBFS_DG_CD_02_dm01cel02) [DBFS_DG]
3. ONLINE   5e4c17f237424fcfbf7edbd2cc0379ae (o/192.168.10.3/DBFS_DG_CD_03_dm01cel01) [DBFS_DG]
Located 3 voting disk(s).

Top

Non-autoextensible data and temp files

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The benefit of having "AUTOEXTEND" on is that applications may avoid out of space errors. The impact of verifying that the "AUTOEXTEND" attribute is "ON" is minimal. The impact of setting "AUTOEXTEND" to "ON" varies depending upon if it is done during database creation, file addition to a tablespace, or added to an existing file. Risk The risk of running out of space in either the tablespace or diskgroup varies by application and cannot be quantified here. A tablespace that runs out of space will interfere with an application, and a diskgroup running out of space could impact the entire database as well as ASM operations (e.g., rebalance operations). Action / Repair: To obtain a list of tablespaces that are not set to "AUTOEXTEND", enter the following sqlplus command logged into the database as sysdba: select file_id, file_name, tablespace_name from dba_data_files where autoextensible <>'YES' union select file_id, file_name, tablespace_name from dba_temp_files where autoextensible <> 'YES'; The output should be: no rows selected If any rows are returned, investigate and correct the condition. NOTE: Configuring "AUTOEXTEND" to "ON" requires comparing space utilization growth projections at the tablespace level to space available in the diskgroups to permit the expected projected growth while retaining sufficient storage space in reserve to account for ASM rebalance operations that occur either as a result of planned operations or component failure. The resulting growth targets are implemented with the "MAXSIZE" attribute that should always be used in conjunction with the "AUTOEXTEND" attribute. The "MAXSIZE" settings should allow for projected growth while minimizing the prospect of depleting a disk group. The "MAXSIZE" settings will vary by customer and a blanket recommendation cannot be given here. NOTE: When configuring a file for "AUTOEXTEND" to "ON", the size specified for the "NEXT" attribute should cover all disks in the diskgroup to optimize balance. For example, with a 4MB AU size and 168 disks, the size of the "NEXT" attribute should be a multiple of 672M (4*168).
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: FAIL => Some data or temp files are not autoextensible


DATA FOR MCSDB FOR NON-AUTOEXTENSIBLE DATA AND TEMP FILES




+DATA_DM01/mcsdb/datafile/dev1_oim.447.802540729
+DATA_DM01/mcsdb/datafile/dev5_apm.391.801068887
+DATA_DM01/mcsdb/datafile/dev5_brsadata.381.801068881
+DATA_DM01/mcsdb/datafile/dev5_brsaindx.369.801068877
+DATA_DM01/mcsdb/datafile/dev5_ias_iau.393.801068887
+DATA_DM01/mcsdb/datafile/dev5_ias_oif.417.801068897
+DATA_DM01/mcsdb/datafile/dev5_ias_orasdpm.416.801068897
+DATA_DM01/mcsdb/datafile/dev5_mds.419.801068897
+DATA_DM01/mcsdb/datafile/dev5_oam.418.801068897
+DATA_DM01/mcsdb/datafile/dev5_oim.413.801068895
+DATA_DM01/mcsdb/datafile/dev5_oim_lob.387.801068885
+DATA_DM01/mcsdb/datafile/dev5_soainfra.374.801068879
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data.384.801068883

+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_apr.371.801068877

+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_aug.386.801068883
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_dec.377.801068881
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_feb.388.801068885
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_jan.402.801068891
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_jul.410.801068893
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_jun.408.801068893
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_mar.409.801068893
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_may.405.801068891
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_nov.385.801068883
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_oct.376.801068879
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_data_sep.394.801068887
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_entone_idx.390.801068885

+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_entx_mp_idx.375.801068879
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_eoneprf_idx.379.801068881
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_et_us_mp_idx.372.801068877
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_indx.395.801068887
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_mo_lg_idx.400.801068889
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_mon_idx.389.801068885
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_nd_hs_idx.373.801068879
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_nd_idx.406.801068891
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_pl_lg_idx.398.801068889
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_ps_lg_idx.397.801068889
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_qa_data.399.801068889
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_qa_ht_data.382.801068883
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_rl_lg_idx.378.801068881

+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_sess_idx.414.801068895
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_tx_dt_idx.407.801068893
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_tx_lg_idx.401.801068891
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_udv_mp_idx.370.801068877
+DATA_DM01/mcsdb/datafile/dev5_tbs_oaam_us_nd_idx.411.801068895
+DATA_DM01/mcsdb/datafile/dev6_biplatform.426.801069449
+DATA_DM01/mcsdb/datafile/dev6_ias_activity.424.801069449
+DATA_DM01/mcsdb/datafile/dev6_ias_discuss.427.801069451
+DATA_DM01/mcsdb/datafile/dev6_ias_portlet.425.801069449
+DATA_DM01/mcsdb/datafile/dev6_ias_webcenter.421.801069447
+DATA_DM01/mcsdb/datafile/dev6_mds.423.801069449
+DATA_DM01/mcsdb/datafile/olts_attrstore.380.801068881
+DATA_DM01/mcsdb/datafile/olts_battrstore.368.801068877

+DATA_DM01/mcsdb/datafile/olts_ct_store.415.801068895
+DATA_DM01/mcsdb/datafile/olts_default.366.801068875
+DATA_DM01/mcsdb/datafile/olts_svrmgstore.412.801068895
+DATA_DM01/mcsdb/datafile/sysaux.265.800704881
+DATA_DM01/mcsdb/datafile/system.266.800704875
+DATA_DM01/mcsdb/datafile/system01.dbf
+DATA_DM01/mcsdb/datafile/system02.dbf
+DATA_DM01/mcsdb/datafile/undotbs1.258.800704885
+DATA_DM01/mcsdb/datafile/undotbs2.264.800704897
+DATA_DM01/mcsdb/datafile/users.263.800704903
+DATA_DM01/mcsdb/gis_datafiles/gis_data01.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_data_idx01.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_data_idx02.dbf

+DATA_DM01/mcsdb/gis_datafiles/gis_data_idx03.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_data_idx04.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_data_idx05.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_gps_his_data01.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_gps_his_data02.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_gps_his_data03.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_gps_his_data04.dbf
+DATA_DM01/mcsdb/gis_datafiles/gis_gps_his_data05.dbf
+DATA_DM01/mcsdb/gis_datafiles/mapinfo01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw04.dbf

+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw05.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw06.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw07.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw08.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw09.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsdw10.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods04.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods05.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods06.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods07.dbf

+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods08.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods09.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsods10.dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsstg01dbf
+DATA_DM01/mcsdb/mcs_datafiles/idx_mcsstg02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsapp01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsapp02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsapp03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw04.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw05.dbf

+DATA_DM01/mcsdb/mcs_datafiles/mcsdw06.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw07.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw08.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw09.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw10.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw11.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw12.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw13.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw14.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw15.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw16.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw17.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw18.dbf

+DATA_DM01/mcsdb/mcs_datafiles/mcsdw19.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsdw20.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcserp01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcshty_data01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcshty_data02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods04.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods05.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods06.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods07.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods08.dbf

+DATA_DM01/mcsdb/mcs_datafiles/mcsods09.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods10.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods11.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods12.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods13.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods14.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods15.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods16.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods17.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods18.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods19.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsods20.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg01.dbf

+DATA_DM01/mcsdb/mcs_datafiles/mcsstg02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg04.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg05.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg06.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg07.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg08.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg09.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg10.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg11.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg12dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg13dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcsstg14.dbf

+DATA_DM01/mcsdb/mcs_datafiles/mcsstg15.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcszemn01.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcszemn02.dbf
+DATA_DM01/mcsdb/mcs_datafiles/mcszemn03.dbf
+DATA_DM01/mcsdb/mcs_datafiles/portal01.dbf
+DATA_DM01/mcsdb/midware_datafiles/all_idx01.dbf
+DATA_DM01/mcsdb/midware_datafiles/all_idx02.dbf
+DATA_DM01/mcsdb/midware_datafiles/all_idx03.dbf
+DATA_DM01/mcsdb/midware_datafiles/all_idx04.dbf
+DATA_DM01/mcsdb/midware_datafiles/etl_monitor01.dbf
+DATA_DM01/mcsdb/midware_datafiles/info_base01.dbf
+DATA_DM01/mcsdb/midware_datafiles/info_data01.dbf
+DATA_DM01/mcsdb/midware_datafiles/info_data02.dbf

+DATA_DM01/mcsdb/midware_datafiles/osbdb.dbf
+DATA_DM01/mcsdb/tempfile/dev1172_ias_temp.471.822651787
+DATA_DM01/mcsdb/tempfile/dev117_ias_temp.464.816802505
+DATA_DM01/mcsdb/tempfile/dev1_ias_temp.444.802540727
+DATA_DM01/mcsdb/tempfile/dev52_ias_temp.404.815310015
+DATA_DM01/mcsdb/tempfile/dev53_ias_temp.276.815426683
+DATA_DM01/mcsdb/tempfile/dev5_apm_temp.383.801068883
+DATA_DM01/mcsdb/tempfile/dev5_brsatemp.403.801068891
+DATA_DM01/mcsdb/tempfile/dev5_ias_temp.420.801068899
+DATA_DM01/mcsdb/tempfile/dev5_oam_temp.396.801068889
+DATA_DM01/mcsdb/tempfile/dev5_oim_temp.392.801068887
+DATA_DM01/mcsdb/tempfile/dev5_tbs_oaam_temp.367.801068875
+DATA_DM01/mcsdb/tempfile/dev6_ias_temp.422.801069447

+DATA_DM01/mcsdb/tempfile/devbitest_ias_temp.453.814114575
+DATA_DM01/mcsdb/tyyw_datafiles/tyyw01.dbf
+DATA_DM01/mcsdb/tyyw_datafiles/tyyw02.dbf
+DATA_DM01/mcsdb/tyyw_datafiles/tyyw03.dbf
+DATA_DM01/mcsdb/ywy_datafiles/dep01.dbf
+DATA_DM01/mcsdb/ywy_datafiles/dep02.dbf
+DATA_DM01/mcsdb/ywy_datafiles/dep03.dbf
+DATA_DM01/mcsdb/ywy_datafiles/dep04.dbf
+DATA_DM01/mcsdb/ywy_datafiles/dep05.dbf
+DATA_DM01/mcsdb/ywy_datafiles/sdywy01.dbf
+DATA_DM01/mcsdb/ywy_datafiles/sdywy02.dbf
+DATA_DM01/mcsdb/ywy_datafiles/sdywy03.dbf
...More

Top

ohasd/orarootagent_root Log File Ownership

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Supportability, diagnostics Risk: If for any reason the ownership of certain clusterware related log files is changed incorrectly it could result in important diagnostics not being available when needed by Support. These logs are rotated periodically to keep them from growing unmanageably large and if the ownership of the files is incorrect when it is time to rotate the logs that operation could fail and while that doesn't effect the operation of the clusterware itself it would effect the logging and therefore problem diagnostics. Action / Repair: It is wise to verify that the ownership of the following files is root:root: $ls -l $GRID_HOME/log/`hostname`/crsd/* $ls -l $GRID_HOME/log/`hostname`/ohasd/* $ls -l $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* $ls -l $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/* If any of those files' ownership is NOT root:root then you should change the ownership of the files individually as follows (as root): # chown root:root $GRID_HOME/log/`hostname`/crsd/* # chown root:root $GRID_HOME/log/`hostname`/ohasd/* # chown root:root $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* # chown root:root $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/*
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ohasd/orarootagent_root Log Ownership is Correct (root root)


DATA FROM DM01DB01 - MCSDB DATABASE - OHASD/ORAROOTAGENT_ROOT LOG FILE OWNERSHIP



total 108408
-rw-r--r-- 1 root root 10594175 Apr 15 19:26 orarootagent_root.l01
-rw-r--r-- 1 root root 10594162 Apr 14 09:00 orarootagent_root.l02
-rw-r--r-- 1 root root 10594176 Apr 12 22:33 orarootagent_root.l03
-rw-r--r-- 1 root root 10594278 Apr 11 12:07 orarootagent_root.l04
-rw-r--r-- 1 root root 10594207 Apr 10 01:39 orarootagent_root.l05
-rw-r--r-- 1 root root 10594252 Apr  8 15:11 orarootagent_root.l06
-rw-r--r-- 1 root root 10594219 Apr  7 04:45 orarootagent_root.l07
-rw-r--r-- 1 root root 10594237 Apr  5 18:18 orarootagent_root.l08
-rw-r--r-- 1 root root 10594181 Apr  4 07:50 orarootagent_root.l09
-rw-r--r-- 1 root root 10594197 Apr  2 21:23 orarootagent_root.l10
-rw-r--r-- 1 root root  4864965 Apr 16 11:15 orarootagent_root.log
-rw-r--r-- 1 root root        0 Nov 28  2012 orarootagent_rootOUT.log
-rw-r--r-- 1 root root        6 Feb  8 20:12 orarootagent_root.pid

Status on dm01db02: PASS => ohasd/orarootagent_root Log Ownership is Correct (root root)


total 105496
-rw-r--r-- 1 root root 10594087 Apr 16 05:08 orarootagent_root.l01
-rw-r--r-- 1 root root 10593994 Apr 14 18:20 orarootagent_root.l02
-rw-r--r-- 1 root root 10594035 Apr 13 07:33 orarootagent_root.l03
-rw-r--r-- 1 root root 10594080 Apr 11 20:46 orarootagent_root.l04
-rw-r--r-- 1 root root 10594063 Apr 10 09:59 orarootagent_root.l05
-rw-r--r-- 1 root root 10594129 Apr  8 23:12 orarootagent_root.l06
-rw-r--r-- 1 root root 10594094 Apr  7 12:24 orarootagent_root.l07
-rw-r--r-- 1 root root 10594104 Apr  6 01:38 orarootagent_root.l08
-rw-r--r-- 1 root root 10594122 Apr  4 14:51 orarootagent_root.l09
-rw-r--r-- 1 root root 10594078 Apr  3 04:04 orarootagent_root.l10
-rw-r--r-- 1 root root  1889469 Apr 16 11:20 orarootagent_root.log
-rw-r--r-- 1 root root        0 Nov 28  2012 orarootagent_rootOUT.log
-rw-r--r-- 1 root root        5 Feb  8 20:40 orarootagent_root.pid

Top

Remote listener set to scan name

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	For Oracle Database 11g Release 2, the REMOTE_LISTENER parameter should be set to the SCAN. This allows the instances to register with the SCAN Listeners to provide information on what services are being provided by the instance, the current load, and a recommendation on how many incoming connections should be directed to the instance.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Remote listener is set to SCAN name


DATA FROM DM01DB01 - MCSDB DATABASE - REMOTE LISTENER SET TO SCAN NAME



remote listener name=dm01-scan scan name= dm01-scan

Status on dm01db02: PASS => Remote listener is set to SCAN name


remote listener name=dm01-scan scan name= dm01-scan

Top

NTP with correct setting

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Cluster stability Risk: Cluster instability due to time synchronization issues Action / Repair: Make sure machine clocks are synchronized on all nodes to the same NTP source. Implement NTP (Network Time Protocol) on all nodes. Prevents evictions and helps to facilitate problem diagnosis. Also use the -x option (ie. ntpd -x, xntp -x) if available to prevent time from moving backwards in large amounts. This slewing will help reduce time changes into multiple small changes, such that they will not impact the CRS. Enterprise Linux: see /etc/sysconfig/ntpd; Solaris: set "slewalways yes" and "disable pll" in /etc/inet/ntp.conf. Like:- # Drop root to id 'ntp:ntp' by default. OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid" # Set to 'yes' to sync hw clock after successful ntpdate SYNC_HWCLOCK=no # Additional options for ntpdate NTPDATE_OPTIONS="" The Time servers operate in a pyramid structure where the top of the NTP stack is usually an external time source (such as GPS Clock). This then trickles down through the Network Switch stack to the connected server. This NTP stack acts as the NTP Server and ensuring that all the RAC Nodes are acting as clients to this server in a slewing method will keep time changes to a minute amount. Changes in global time to account for atomic accuracy's over Earth rotational wobble , will thus be accounted for with minimal effect. This is sometimes referred to as the " Leap Second " " epoch ", (between UTC 12/31/2008 23:59.59 and 01/01/2009 00:00.00 has the one second inserted). RFC "NTP Slewing for RAC" has been created successfully. CCB ID 462
Links	Note: 759143.1 - NTP leap second event causing Oracle Clusterware node reboot -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NTP is running with correct setting


DATA FROM DM01DB01 - MCSDB DATABASE - NTP WITH CORRECT SETTING



ntp       5477     1  0 Feb08 ?        00:05:56 ntpd -u ntp:ntp -p /var/run/ntpd.pid -x

Status on dm01db02: PASS => NTP is running with correct setting


ntp       5462     1  0 Feb08 ?        00:05:50 ntpd -u ntp:ntp -p /var/run/ntpd.pid -x

Top

Non-routable network for interconnect

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Interconnect should be configured on non-routable private LAN. Interconnect IP should not be accessible outside LAN
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Interconnect is configured on non-routable network addresses


DATA FROM DM01DB01 - MCSDB DATABASE - NON-ROUTABLE NETWORK FOR INTERCONNECT



bondib0  192.168.8.0  global  cluster_interconnect

Status on dm01db02: PASS => Interconnect is configured on non-routable network addresses


bondib0  192.168.8.0  global  cluster_interconnect

Top

IDGEN$ sequence cache size

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Sequence contention (SQ enqueue) can occur if SYS.IDGEN1$ sequence is not cached to 1000. This condition can lead to performance issues in RAC. 1000 is the default starting in version 11.2.0.1.
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => SYS.IDGEN1$ sequence cache size >= 1,000


DATA FOR MCSDB FOR IDGEN$ SEQUENCE CACHE SIZE




idgen1$.cache_size = 1000

Top

OSWatcher status on storage servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	It is considered a best practice to run OSWatcher proactively on compute nodes as well on Exadata storage server to capture first failure diagnostics.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => OSWatcher is running on all storage servers


DATA FROM DM01CEL01 FOR OSWATCHER STATUS ON STORAGE SERVERS




NOTE: No output would indicate OSWatcher not running

root     15556     1  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3
root     16301 15556  0 11:00 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_cellsrvstat.sh
root     24275 24273  0 11:05 ?        00:00:00 grep -i osw
root     26519 15556  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcherFM.sh 168 3
root     26539 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_vmstat.sh
root     26540 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_mpstat.sh
root     26541 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_netstat.sh
root     26542 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_iostat.sh
root     26543 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_diskstats.sh
root     26548 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_top.sh
root     26559 15556  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh
root     26579 26559  0 04:02 ?        00:00:04 /bin/bash /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh HighFreq





DATA FROM DM01CEL02 FOR OSWATCHER STATUS ON STORAGE SERVERS




NOTE: No output would indicate OSWatcher not running

root      3540 30806  0 11:00 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_cellsrvstat.sh
root     12902 30806  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcherFM.sh 168 3
root     12922 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_vmstat.sh
root     12923 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_mpstat.sh
root     12924 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_netstat.sh
root     12925 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_iostat.sh
root     12927 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_diskstats.sh
root     12931 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_top.sh
root     12944 30806  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh
root     12963 12944  0 04:02 ?        00:00:04 /bin/bash /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh HighFreq
root     14352 14350  0 11:08 ?        00:00:00 grep -i osw
root     30806     1  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3




DATA FROM DM01CEL03 FOR OSWATCHER STATUS ON STORAGE SERVERS




NOTE: No output would indicate OSWatcher not running

root      6031     1  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3
root     10790  6031  0 11:00 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_cellsrvstat.sh
root     21039  6031  0 04:02 ?        00:00:04 /bin/ksh ./OSWatcherFM.sh 168 3
root     21090  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_vmstat.sh
root     21091  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_mpstat.sh
root     21092  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_netstat.sh
root     21093  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_iostat.sh
root     21095  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_diskstats.sh
root     21099  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_top.sh
root     21112  6031  0 04:02 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh
root     21133 21112  0 04:02 ?        00:00:04 /bin/bash /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh HighFreq
root     26485 26483  0 11:11 ?        00:00:00 grep -i osw




...More

Top

Automatic segment storage management

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Starting with Oracle 9i Auto Segment Space Management (ASSM) can be used by specifying the SEGMENT SPACE MANAGEMENT clause, set to AUTO in the CREATE TABLESPACE statement. Implementing the ASSM feature allows Oracle to use bitmaps to manage the free space within segments. The bitmap describes the status of each data block within a segment, with respect to the amount of space in the block available for inserting rows. The current status of the space available in a data block is reflected in the bitmap allowing for Oracle to manage free space automatically with ASSM. ASSM tablespaces automate freelist management and remove the requirement/ability to specify PCTUSED, FREELISTS, and FREELIST GROUPS storage parameters for individual tables and indexes created in these tablespaces.
Needs attention on	MCSDB
Passed on	-

Status on MCSDB: WARNING => Some tablespaces are not using Automatic segment storage management.


DATA FOR MCSDB FOR AUTOMATIC SEGMENT STORAGE MANAGEMENT




OLTS_BATTRSTORE
OLTS_SVRMGSTORE

Top

crsd Log File Ownership

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Supportability, diagnostics Risk: If for any reason the ownership of certain clusterware related log files is changed incorrectly it could result in important diagnostics not being available when needed by Support. These logs are rotated periodically to keep them from growing unmanageably large and if the ownership of the files is incorrect when it is time to rotate the logs that operation could fail and while that doesn't effect the operation of the clusterware itself it would effect the logging and therefore problem diagnostics. Action / Repair: It is wise to verify that the ownership of the following files is root:root: $ls -l $GRID_HOME/log/`hostname`/crsd/* $ls -l $GRID_HOME/log/`hostname`/ohasd/* $ls -l $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* $ls -l $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/* If any of those files' ownership is NOT root:root then you should change the ownership of the files individually as follows (as root): # chown root:root $GRID_HOME/log/`hostname`/crsd/* # chown root:root $GRID_HOME/log/`hostname`/ohasd/* # chown root:root $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* # chown root:root $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/*
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => crsd Log Ownership is Correct (root root)


DATA FROM DM01DB01 - MCSDB DATABASE - CRSD LOG FILE OWNERSHIP



total 106308
-rw-r--r-- 1 root root 10575713 Apr 15 23:48 crsd.l01
-rw-r--r-- 1 root root 10575446 Apr 14 05:05 crsd.l02
-rw-r--r-- 1 root root 10575401 Apr 12 10:20 crsd.l03
-rw-r--r-- 1 root root 10575472 Apr 10 15:46 crsd.l04
-rw-r--r-- 1 root root 10575587 Apr  8 21:03 crsd.l05
-rw-r--r-- 1 root root 10575186 Apr  7 02:44 crsd.l06
-rw-r--r-- 1 root root 10575315 Apr  5 08:24 crsd.l07
-rw-r--r-- 1 root root 10575544 Apr  3 13:40 crsd.l08
-rw-r--r-- 1 root root 10575475 Apr  1 19:03 crsd.l09
-rw-r--r-- 1 root root 10575395 Mar 31 00:15 crsd.l10
-rw-r--r-- 1 root root  2920707 Apr 16 11:14 crsd.log
-rw-r--r-- 1 root root     4119 Feb  8 20:12 crsdOUT.log

Status on dm01db02: PASS => crsd Log Ownership is Correct (root root)


total 107284
-rw-r--r-- 1 root root 10586297 Apr  7 19:54 crsd.l01
-rw-r--r-- 1 root root 10585922 Mar 15 12:55 crsd.l02
-rw-r--r-- 1 root root 10536518 Feb 20 09:16 crsd.l03
-rw-r--r-- 1 root root 10569543 Feb  7 11:01 crsd.l04
-rw-r--r-- 1 root root 10569623 Feb  4 02:18 crsd.l05
-rw-r--r-- 1 root root 10569637 Jan 31 16:38 crsd.l06
-rw-r--r-- 1 root root 10570177 Jan 28 06:28 crsd.l07
-rw-r--r-- 1 root root 10569960 Jan 24 20:16 crsd.l08
-rw-r--r-- 1 root root 10569814 Jan 21 10:09 crsd.l09
-rw-r--r-- 1 root root 10569840 Jan 17 23:54 crsd.l10
-rw-r--r-- 1 root root  3963099 Apr 16 11:20 crsd.log
-rw-r--r-- 1 root root     4906 Feb  8 20:40 crsdOUT.log

Top

OSWatcher status

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Improved first failure diagnostics if run proactively Risk: Degraded ability to provide first failure diagnostics in case of problems Action / Repair: Operating System Watcher (OSW) is a collection of UNIX shell scripts intended to collect and archive operating system and network metrics to aid diagnosing performance issues. OSW is designed to run continuously and to write the metrics to ASCII files which are saved to an archive directory. The amount of archived data saved and frequency of collection are based on user parameters set when starting OSW.
Links	Note: 301137.1 - OS Watcher User Guide -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => OSWatcher is running


DATA FROM DM01DB01 - MCSDB DATABASE - OSWATCHER STATUS



root     13687     1  0 04:05 ?        00:00:02 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3
root     13852 13687  0 04:06 ?        00:00:02 /bin/ksh ./OSWatcherFM.sh 168 3
root     13874 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_vmstat.sh
root     13875 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_mpstat.sh
root     13876 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_netstat.sh
root     13877 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_iostat.sh
root     13878 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_diskstats.sh
root     13879 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_top.sh
root     13888 13687  0 04:06 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh
root     13902 13888  0 04:06 ?        00:00:15 /bin/bash /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh HighFreq

Status on dm01db02: PASS => OSWatcher is running


root     14369     1  0 04:05 ?        00:00:02 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3
root     14498 14369  0 04:05 ?        00:00:02 /bin/ksh ./OSWatcherFM.sh 168 3
root     14530 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_vmstat.sh
root     14531 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_mpstat.sh
root     14532 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_netstat.sh
root     14533 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_iostat.sh
root     14534 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_diskstats.sh
root     14536 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq ./Exadata_top.sh
root     14544 14369  0 04:05 ?        00:00:00 /bin/ksh ./oswsub.sh HighFreq /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh
root     14556 14544  0 04:05 ?        00:00:15 /bin/bash /opt/oracle.oswatcher/osw/ExadataRdsInfo.sh HighFreq

Top

No CRS HOME env variable

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Avoid unexpected results running various Oracle utilities Risk: Setting this variable can cause problems for various Oracle components, and it is never necessary for CRS programs because they all have wrapper scripts. Action / Repair: Unset ORA_CRS_HOME in the execution environment. If a variable is needed for automation purposes or convenience then use a different variable name (eg., GI_HOME, etc.)
Links	Note: 1312225.1 - Things to Consider Before Upgrading to 11.2.0.2 Grid Infrastructure -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ORA_CRS_HOME environment variable is not set


DATA FROM DM01DB01 - MCSDB DATABASE - NO CRS HOME ENV VARIABLE



SUDOCMD=/usr/bin/sudo
HOSTNAME=dm01db01.mcsdb.com
SHELL=/bin/bash
TERM=xterm
HISTSIZE=1000
CRS_HOME=/u01/app/11.2.0.3/grid
ORACLE_UNQNAME=MCSDB
USER=oracle
LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0.3/dbhome_1/jdk/lib:/u01/app/oracle/product/11.2.0.3/dbhome_1/lib:/u01/app/11.2.0.3/grid/lib
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
ORACLE_SID=MCSDB1
ORACLE_BASE=/u01/app/oracle
MAIL=/var/spool/mail/oracle
PATH=/u01/app/oracle/product/11.2.0.3/dbhome_1/bin:/u01/app/oracle/product/11.2.0.3/dbhome_1/jdk/bin:/u01/app/oracle/product/11.2.0.3/dbhome_1/bin:/u01/app/oracle/product/11.2.0.3/dbhome_1/jdk/bin:/usr/local/bin:/bin:/usr/bin:.:/u01/app/oracle/product/11.2.0.3/dbhome_1/bin
INPUTRC=/etc/inputrc
PWD=/opt/oracle.SupportTools/exachk

JAVA_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1/jdk
CRS=/u01/app/11.2.0.3/grid
LANG=en_US.UTF-8
SHLVL=3
HOME=/home/oracle
LOGNAME=oracle
LESSOPEN=|/usr/bin/lesspipe.sh %s
ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
G_BROKEN_FILENAMES=1
_=/bin/env
...More

Status on dm01db02: PASS => ORA_CRS_HOME environment variable is not set


SHELL=/bin/bash
CRS_HOME=/u01/app/11.2.0.3/grid
SSH_CLIENT=10.187.5.2 52273 22
USER=oracle
LD_LIBRARY_PATH=:/u01/app/oracle/product/11.2.0.3/dbhome_1/lib:/u01/app/11.2.0.3/grid/lib
LS_COLORS=
ORACLE_SID=MCSDB2
ORACLE_BASE=/u01/app/oracle
PATH=/u01/app/oracle/product/11.2.0.3/dbhome_1/bin:/usr/local/bin:/bin:/usr/bin
MAIL=/var/mail/oracle
PWD=/home/oracle
LANG=en_US.UTF-8
HOME=/home/oracle
SHLVL=2
LOGNAME=oracle
SSH_CONNECTION=10.187.5.2 52273 10.187.5.3 22
LESSOPEN=|/usr/bin/lesspipe.sh %s
ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1
G_BROKEN_FILENAMES=1
_=/bin/env

Top

GC block lost

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Optimal global cache performance Risk: The RDBMS reports global cache lost block statistics ("gc cr block lost" and/or "gc current block lost") which could indicate a negative impact on interconnect performance and global cache processing. Action / Repair: The vast majority of escalations attributed to RDBMS global cache lost blocks can be directly related to faulty or misconfigured interconnects. GC lost blocks diagnostics guide serves as a starting point for evaluating common (and sometimes obvious) causes.
Links	Note: 563566.1 - gc lost blocks diagnostics -
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => GC blocks lost is not occurring


DATA FOR MCSDB FOR GC BLOCK LOST




No of GC lost block in last 24 hours = 0

Top

NIC Bonding Mode interconnect

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Optimal interconnect performance Risk: Even though the mode 3 option is available for the Linux bonding driver, testing has proven that it duplicates all UDP packets and transmits them on every path. This increases CPU overhead for processing data from the interconnect thereby making the interconnect less efficient. Mode 3 is not needed for fault tolerance as other modes are available for that purpose and which do not duplicate the packets. While there have been some enhancements to more effectively deal with duplicate packets it still is not a good idea to generate a large number of duplicate packets that are just going to be thrown away and which imposes additional overhead on the interconnect and CPUs. If you must use mode 3 bonding then you should at least have the patches for the two bugs mentioned. A couple of relevant bugs: Bug 7238620 - ORA-600 [2032] REDISCOVERY INFORMATION: If you are using a RAC IPC module over an unreliable protocol, like ipc_g link targets, and your network is duplicating packets at a high rate, you may have hit this bug. WORKAROUND: Ensure network is not duplicating any packets. Bug 9081436 - GC CR REQUEST WAIT CAUSING SESSIONS TO WAIT This bug is a side effect of the fix for BUG 7238620 which allowed an invalid/corrupt packet to make it through to higher layers in Oracle code, instead of it being discarded and re-requested. The fact that the bad packet was not discarded and re-request a new one is a result of the new code where we are attempting to ignore duplicate packets. But that is now fixed, so what should happen now is that Oracle will still discard duplicate packets, but will also still be on the lookout for any bad/corrupt packets, and if any are received they should be thrown away and re-requested, instead of allowing these bad packets through, to potentially corrupt or overwrite other buffers in memory. Action / Repair: Use a different NIC bonding mode, usually mode 1 (Active/Passive)
Links	Note: 730796.1 - Potential Disadvantages Using Broadcast Mode 3 For Bonded Devices -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NIC bonding mode is not set to Broadcast(3) for cluster interconnect


DATA FROM DM01DB01 - MCSDB DATABASE - NIC BONDING MODE INTERCONNECT



Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup) (fail_over_mac active)
Primary Slave: None
Currently Active Slave: ib0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 5000
Down Delay (ms): 5000

Slave Interface: ib0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 80:00:00:48:fe:80
Slave queue ID: 0


Slave Interface: ib1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 80:00:00:49:fe:80
Slave queue ID: 0
...More

Status on dm01db02: PASS => NIC bonding mode is not set to Broadcast(3) for cluster interconnect


Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup) (fail_over_mac active)
Primary Slave: None
Currently Active Slave: ib0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 5000
Down Delay (ms): 5000

Slave Interface: ib0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 80:00:00:48:fe:80
Slave queue ID: 0

Slave Interface: ib1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 80:00:00:49:fe:80

Slave queue ID: 0
...More

Top

AUDSES$ sequence cache size

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Application scalability Risk: Problems have been reported with AUDSES$, ORA_TQ_BASE$ and IDGEN1$, which are all internal sequences, if the cache size is too small (eg., login storms or very high concurrency) and can manifest as waits in "rowcache" for "dc_sequences" which is a rowcache type for sequences. Action / Repair: Increase AUDSES$ and ORA_TQ_BASE$ to 10,000 Increase IDGEN1$ to a value of 1000 See referenced Notes.
Links	Note: 268476.1 - LOB Performance Guideline - Note: 432508.1 - High SQ Enqueue Contention with LOBs or Advanced Replication - Note: 561414.1 - Transactional Sequences in Applications in a RAC environment -
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => SYS.AUDSES$ sequence cache size >= 10,000


DATA FOR MCSDB FOR AUDSES$ SEQUENCE CACHE SIZE




audses$.cache_size = 10000

Top

SELinux status

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Exadata standards Risk: Deviation from standard deployment, potential unforeseen problems. Action / Repair: When Exadata Database Machine is initially deployed SELinux is configured in "permissive" mode. Customers should only deviate from this configuration if directed to do so by Oracle Support. Consult Oracle Support about correcting the configuration.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => SELinux is not being Enforced.


DATA FROM DM01DB01 - MCSDB DATABASE - SELINUX STATUS



Disabled

Status on dm01db02: PASS => SELinux is not being Enforced.


Disabled

Top

crsd/orarootagent_root Log File Ownership

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Supportability, diagnostics Risk: If for any reason the ownership of certain clusterware related log files is changed incorrectly it could result in important diagnostics not being available when needed by Support. These logs are rotated periodically to keep them from growing unmanageably large and if the ownership of the files is incorrect when it is time to rotate the logs that operation could fail and while that doesn't effect the operation of the clusterware itself it would effect the logging and therefore problem diagnostics. Action / Repair: It is wise to verify that the ownership of the following files is root:root: $ls -l $GRID_HOME/log/`hostname`/crsd/* $ls -l $GRID_HOME/log/`hostname`/ohasd/* $ls -l $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* $ls -l $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/* If any of those files' ownership is NOT root:root then you should change the ownership of the files individually as follows (as root): # chown root:root $GRID_HOME/log/`hostname`/crsd/* # chown root:root $GRID_HOME/log/`hostname`/ohasd/* # chown root:root $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* # chown root:root $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/*
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => crsd/orarootagent_root Log Ownership is Correct (root root)


DATA FROM DM01DB01 - MCSDB DATABASE - CRSD/ORAROOTAGENT_ROOT LOG FILE OWNERSHIP



total 109248
-rw-r--r-- 1 root root 10572528 Mar 28 10:54 orarootagent_root.l01
-rw-r--r-- 1 root root 10525003 Feb 23 12:34 orarootagent_root.l02
-rw-r--r-- 1 root root 10572171 Jan 22 17:24 orarootagent_root.l03
-rw-r--r-- 1 root root 10572279 Dec 22 01:23 orarootagent_root.l04
-rw-r--r-- 1 root root 10572246 Nov 19 13:03 orarootagent_root.l05
-rw-r--r-- 1 root root 10572174 Oct 18 08:49 orarootagent_root.l06
-rw-r--r-- 1 root root 10572955 Sep 16  2013 orarootagent_root.l07
-rw-r--r-- 1 root root 10491452 Aug 14  2013 orarootagent_root.l08
-rw-r--r-- 1 root root 10560602 Jul 12  2013 orarootagent_root.l09
-rw-r--r-- 1 root root 10517359 Jun 10  2013 orarootagent_root.l10
-rw-r--r-- 1 root root  6130017 Apr 16 11:14 orarootagent_root.log
-rw-r--r-- 1 root root        0 Nov 28  2012 orarootagent_rootOUT.log
-rw-r--r-- 1 root root        6 Feb  8 20:13 orarootagent_root.pid

Status on dm01db02: PASS => crsd/orarootagent_root Log Ownership is Correct (root root)


total 107120
-rw-r--r-- 1 root root 10572802 Apr  4 09:02 orarootagent_root.l01
-rw-r--r-- 1 root root 10545310 Mar  3 04:09 orarootagent_root.l02
-rw-r--r-- 1 root root 10572300 Jan 29 14:40 orarootagent_root.l03
-rw-r--r-- 1 root root 10572408 Dec 27 10:20 orarootagent_root.l04
-rw-r--r-- 1 root root 10572378 Nov 24 06:58 orarootagent_root.l05
-rw-r--r-- 1 root root 10572372 Oct 21 23:50 orarootagent_root.l06
-rw-r--r-- 1 root root 10572950 Sep 18  2013 orarootagent_root.l07
-rw-r--r-- 1 root root 10496762 Aug 16  2013 orarootagent_root.l08
-rw-r--r-- 1 root root 10572712 Jul 14  2013 orarootagent_root.l09
-rw-r--r-- 1 root root 10521468 Jun 11  2013 orarootagent_root.l10
-rw-r--r-- 1 root root  3916231 Apr 16 11:19 orarootagent_root.log
-rw-r--r-- 1 root root        0 Nov 28  2012 orarootagent_rootOUT.log
-rw-r--r-- 1 root root        5 Feb  8 20:40 orarootagent_root.pid

Top

oradism executable ownership

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Changes scheduling priority of LMS and other background processes to realtime scheduling class to maximize the ability of key processes to be able to be scheduled on the CPU at times of high CPU utilization Risk: The oradism executable should be owned by root and the owner s-bit should be set, eg. -rwsr-x---, where the s is the setuid bit (s-bit) for root in this case. If the LMS process is not running at the proper scheduling priority it can lead to instance evictions due to IPC send timeouts or ORA-29740 errors. oradism must be owned by root and it's s-bit set in order to be able to change the scheduling priority. If oradism ownership is not root and the owner s-bit is not set then something must have gone wrong in the installation process or the ownership or the permission was otherwise changed. Action / Repair: Please check with Oracle Support to determine the best course to take for your platform to correct the problem.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => $ORACLE_HOME/bin/oradism ownership is root


DATA FROM DM01DB01 - MCSDB DATABASE - ORADISM EXECUTABLE OWNERSHIP



-rwsr-x--- 1 root oinstall 71758 Sep 17  2011 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oradism

Status on dm01db02: PASS => $ORACLE_HOME/bin/oradism ownership is root


-rwsr-x--- 1 root oinstall 71758 Nov 28  2012 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oradism

Top

Interconnect NIC bonding config.

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Interconnect network interface redundancy, increased node availability Risk: Lack of NIC bonding for the interconnect network interface can result in a single point of failure for cluster nodes thereby causing the potential for database instance and cluster node availaibility issues. Action / Repair: Oracle highly recommends to configure redundant network for the interconnect using NIC BONDING.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NIC bonding is configured for interconnect


DATA FROM DM01DB01 - MCSDB DATABASE - INTERCONNECT NIC BONDING CONFIG.



bondib0  192.168.8.0  global  cluster_interconnect

Status on dm01db02: PASS => NIC bonding is configured for interconnect


bondib0  192.168.8.0  global  cluster_interconnect

Top

oradism executable permission

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The oradism executable is invoked after database startup to change the scheduling priority of LMS and other database background processes to the realtime scheduling class in order to maximize the ability of these key processes to be scheduled on the CPU in a timely way at times of high CPU utilization. Risk: The oradism executable should be owned by root and the owner s-bit should be set, eg. -rwsr-x---, where the s is the setuid bit (s-bit) for root in this case. If the LMS process is not running at the proper scheduling priority it can lead to instance evictions due to IPC send timeouts or ORA-29740 errors. oradism must be owned by root and it's s-bit set in order to be able to change the scheduling priority. If oradism ownership is not root and the owner s-bit is not set then something must have gone wrong in the installation process or the ownership or the permission was otherwise changed. Action / Repair: Please check with Oracle Support to determine the best course to take for your platform to correct the problem.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => $ORACLE_HOME/bin/oradism setuid bit is set


DATA FROM DM01DB01 - MCSDB DATABASE - ORADISM EXECUTABLE PERMISSION



-rwsr-x--- 1 root oinstall 71758 Sep 17  2011 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oradism

Status on dm01db02: PASS => $ORACLE_HOME/bin/oradism setuid bit is set


-rwsr-x--- 1 root oinstall 71758 Nov 28  2012 /u01/app/oracle/product/11.2.0.3/dbhome_1/bin/oradism

Top

ohasd Log File Ownership

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Supportability, diagnostics Risk: If for any reason the ownership of certain clusterware related log files is changed incorrectly it could result in important diagnostics not being available when needed by Support. These logs are rotated periodically to keep them from growing unmanageably large and if the ownership of the files is incorrect when it is time to rotate the logs that operation could fail and while that doesn't effect the operation of the clusterware itself it would effect the logging and therefore problem diagnostics. Action / Repair: It is wise to verify that the ownership of the following files is root:root: $ls -l $GRID_HOME/log/`hostname`/crsd/* $ls -l $GRID_HOME/log/`hostname`/ohasd/* $ls -l $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* $ls -l $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/* If any of those files' ownership is NOT root:root then you should change the ownership of the files individually as follows (as root): # chown root:root $GRID_HOME/log/`hostname`/crsd/* # chown root:root $GRID_HOME/log/`hostname`/ohasd/* # chown root:root $GRID_HOME/log/`hostname`/agent/crsd/orarootagent_root/* # chown root:root $GRID_HOME/log/`hostname`/agent/ohasd/orarootagent_root/*
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ohasd Log Ownership is Correct (root root)


DATA FROM DM01DB01 - MCSDB DATABASE - OHASD LOG FILE OWNERSHIP



total 108132
-rw-r--r-- 1 root root 10577866 Apr 14 17:25 ohasd.l01
-rw-r--r-- 1 root root 10577707 Apr 10 19:59 ohasd.l02
-rw-r--r-- 1 root root 10577670 Apr  6 22:37 ohasd.l03
-rw-r--r-- 1 root root 10577866 Apr  3 01:15 ohasd.l04
-rw-r--r-- 1 root root 10578394 Mar 30 03:48 ohasd.l05
-rw-r--r-- 1 root root 10577876 Mar 26 05:57 ohasd.l06
-rw-r--r-- 1 root root 10577956 Mar 22 08:32 ohasd.l07
-rw-r--r-- 1 root root 10578163 Mar 18 11:03 ohasd.l08
-rw-r--r-- 1 root root 10578016 Mar 14 13:32 ohasd.l09
-rw-r--r-- 1 root root 10578027 Mar 10 15:54 ohasd.l10
-rw-r--r-- 1 root root  4744544 Apr 16 11:13 ohasd.log
-rw-r--r-- 1 root root     3720 Feb  8 20:12 ohasdOUT.log

Status on dm01db02: PASS => ohasd Log Ownership is Correct (root root)


total 107524
-rw-r--r-- 1 root root 10578869 Apr 14 12:19 ohasd.l01
-rw-r--r-- 1 root root 10578936 Apr  9 11:33 ohasd.l02
-rw-r--r-- 1 root root 10578581 Apr  4 10:32 ohasd.l03
-rw-r--r-- 1 root root 10578607 Mar 30 10:01 ohasd.l04
-rw-r--r-- 1 root root 10578885 Mar 25 09:35 ohasd.l05
-rw-r--r-- 1 root root 10578796 Mar 20 08:54 ohasd.l06
-rw-r--r-- 1 root root 10579078 Mar 15 08:11 ohasd.l07
-rw-r--r-- 1 root root 10579057 Mar 10 06:57 ohasd.l08
-rw-r--r-- 1 root root 10578728 Mar  5 05:59 ohasd.l09
-rw-r--r-- 1 root root 10579056 Feb 28 05:11 ohasd.l10
-rw-r--r-- 1 root root  4132524 Apr 16 11:19 ohasd.log
-rw-r--r-- 1 root root     2232 Feb  8 20:39 ohasdOUT.log

Top

VIP NIC bonding config.

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Public network interface (VIP) redundancy, increased application availability Risk: Lack of NIC bonding for the public network interface can result in a single point of failure for VIPs thereby causing the potential for application availaibility issues. Action / Repair: Oracle highly recommends to configure redundant network for VIPs using NIC BONDING.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NIC bonding is configured for public network (VIP)


DATA FROM DM01DB01 - MCSDB DATABASE - VIP NIC BONDING CONFIG.



bondeth0  Link encap:Ethernet  HWaddr 00:21:28:E7:98:DF
inet addr:10.187.4.90  Bcast:10.187.4.255  Mask:255.255.255.0
inet6 addr: fe80::221:28ff:fee7:98df/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:8257391698 errors:0 dropped:0 overruns:0 frame:0
TX packets:9581043446 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2074115133099 (1.8 TiB)  TX bytes:5842294339942 (5.3 TiB)

Status on dm01db02: PASS => NIC bonding is configured for public network (VIP)


bondeth0  Link encap:Ethernet  HWaddr 00:21:28:E7:C0:A5
inet addr:10.187.4.91  Bcast:10.187.4.255  Mask:255.255.255.0
inet6 addr: fe80::221:28ff:fee7:c0a5/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:7443677732 errors:0 dropped:0 overruns:0 frame:0
TX packets:8714433867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1911704716665 (1.7 TiB)  TX bytes:5486788385307 (4.9 TiB)

Top

User Open File Limit

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Please consult Oracle Database Installation Guide for Linux Configure Oracle Installation Owner Shell Limits
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Open files limit (ulimit -n) for current user is set to recommended value >= 65536 or unlimited


DATA FROM DM01DB01 - MCSDB DATABASE - USER OPEN FILE LIMIT



core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 773848
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65536
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 131072
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Status on dm01db02: PASS => Open files limit (ulimit -n) for current user is set to recommended value >= 65536 or unlimited


core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 773848
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65536
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 131072
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Top

NIC Bonding Mode Public

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NIC bonding mode is not set to Broadcast(3) for public network


DATA FROM DM01DB01 - MCSDB DATABASE - NIC BONDING MODE PUBLIC




NOTE: Look for Bonding Mode:

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 5000
Down Delay (ms): 5000

Slave Interface: eth1
MII Status: up
Link Failure Count: 0

Permanent HW addr: 00:21:28:e7:98:df
Slave queue ID: 0

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:21:28:e7:98:e0
Slave queue ID: 0
...More

Status on dm01db02: PASS => NIC bonding mode is not set to Broadcast(3) for public network



NOTE: Look for Bonding Mode:

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 5000
Down Delay (ms): 5000

Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:21:28:e7:c0:a5
Slave queue ID: 0

Slave Interface: eth2

MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:21:28:e7:c0:a6
Slave queue ID: 0
...More

Top

GI shell limits hard stack

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The hard stack shell limit for the Oracle Grid Infrastructure software install owner as defined in /etc/security/limits.conf should be >= 10240. What's being checked here is the /etc/security/limits.conf file as documented in 11gR2 Grid Infrastructure Installation Guide, section 2.15.3 Setting Resource Limits for the Oracle Software Installation Users. If the /etc/security/limits.conf file is not configured as described in the documentation then to check the hard stack configuration while logged into the software owner account (eg. grid). $ ulimit -Hs 10240 As long as the hard stack limit is 10240 or above then the configuration should be ok.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard stack for GI is configured according to recommendation


DATA FROM DM01DB01 FOR CRS USER LIMITS CONFIGURATION



Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            1572864              unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             773848               773848               processes
Max open files            65536                65536                files
Max locked memory         unlimited            unlimited            bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       773848               773848               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0

Max realtime timeout      unlimited            unlimited            us
...More

Status on dm01db02: PASS => Shell limit hard stack for GI is configured according to recommendation


DATA FROM DM01DB02 FOR CRS USER LIMITS CONFIGURATION



Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            1572864              unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             773848               773848               processes
Max open files            65536                65536                files
Max locked memory         unlimited            unlimited            bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       773848               773848               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0

Max realtime timeout      unlimited            unlimited            us
...More

Top

DB shell limits soft nproc

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The soft nproc shell limit for the Oracle DB software install owner as defined in /etc/security/limits.conf should be >= 2047.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit soft nproc for DB is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - DB SHELL LIMITS SOFT NPROC



oracle soft nproc 131072

Status on dm01db02: PASS => Shell limit soft nproc for DB is configured according to recommendation


oracle soft nproc 131072

Top

DB shell limits hard stack

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Documented value is the /etc/security/limits.conf file as documented in 11gR2 Grid Infrastructure Installation Guide, section 2.15.3 Setting Resource Limits for the Oracle Software Installation Users. If the /etc/security/limits.conf file is not configured as described in the documentation then log in to the system as the database software owner (eg., oracle) and check the hard stack configuration as described below. Risk: The hard stack shell limit for the Oracle DB software install owner as defined in /etc/security/limits.conf should be >= 10240. As long as the hard stack limit is 10240 or above then the configuration should be ok. Action / Repair: Change DB software install owner hard stack shell limit $ ulimit -Hs 10240
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard stack for DB is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - DB SHELL LIMITS HARD STACK



oracle hard stack unlimited

Status on dm01db02: PASS => Shell limit hard stack for DB is configured according to recommendation


oracle hard stack unlimited

Top

DB shell limits hard nofile

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Documented value, cluster stability The hard nofile shell limit for the Oracle DB software install owner as defined in /etc/security/limits.conf should be >= 65536. Risk: Resource starvation (file descriptors) leading to node instability Action / Repair: Change DB software install owner hard nofile shell limit
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard nofile for DB is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - DB SHELL LIMITS HARD NOFILE



oracle hard nofile 65536

Status on dm01db02: PASS => Shell limit hard nofile for DB is configured according to recommendation


oracle hard nofile 65536

Top

DB shell limits soft nofile

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Documented value, cluster stability The soft nofile shell limit for the Oracle DB software install owner as defined in /etc/security/limits.conf should be >= 1024. Risk: Resource starvation leading to node instability Action / Repair: Change DB software install owner soft nofile shell limit
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit soft nofile for DB is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - DB SHELL LIMITS SOFT NOFILE



oracle soft nofile 65536

Status on dm01db02: PASS => Shell limit soft nofile for DB is configured according to recommendation


oracle soft nofile 65536

Top

DB shell limits hard nproc

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Documented value, cluster stability The hard nproc shell limit for the Oracle DB software install owner as defined in /etc/security/limits.conf should be >= 16384. Risk: Resource starvation (processes) leading to node instability Action / Repair: Change DB software install owner hard nproc shell limit
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard nproc for DB is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - DB SHELL LIMITS HARD NPROC



oracle hard nproc 131072

Status on dm01db02: PASS => Shell limit hard nproc for DB is configured according to recommendation


oracle hard nproc 131072

Top

GI shell limits hard nproc

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The hard nproc shell limit for the Oracle GI software install owner as defined in /etc/security/limits.conf should be >= 16384.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard nproc for GI is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - GI SHELL LIMITS HARD NPROC






oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072

grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock       unlimited
grid     hard    memlock       unlimited


...More

Status on dm01db02: PASS => Shell limit hard nproc for GI is configured according to recommendation





oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072
grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock      unlimited
grid     hard    memlock      unlimited



...More

Top

GI shell limits hard nofile

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The hard nofile shell limit for the Oracle GI software install owner as defined in /etc/security/limits.conf should be >= 65536.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit hard nofile for GI is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - GI SHELL LIMITS HARD NOFILE






oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072

grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock       unlimited
grid     hard    memlock       unlimited


...More

Status on dm01db02: PASS => Shell limit hard nofile for GI is configured according to recommendation





oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072
grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock      unlimited
grid     hard    memlock      unlimited



...More

Top

GI shell limits soft nproc

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The soft nproc shell limit for the Oracle GI software install owner as defined in /etc/security/limits.conf should be >= 2047.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit soft nproc for GI is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - GI SHELL LIMITS SOFT NPROC






oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072

grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock       unlimited
grid     hard    memlock       unlimited


...More

Status on dm01db02: PASS => Shell limit soft nproc for GI is configured according to recommendation





oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072
grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock      unlimited
grid     hard    memlock      unlimited



...More

Top

GI shell limits soft nofile

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The soft nofile shell limit for the Oracle GI software install owner as defined in /etc/security/limits.conf should be >= 1024.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Shell limit soft nofile for GI is configured according to recommendation


DATA FROM DM01DB01 - MCSDB DATABASE - GI SHELL LIMITS SOFT NOFILE






oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072

grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock       unlimited
grid     hard    memlock       unlimited


...More

Status on dm01db02: PASS => Shell limit soft nofile for GI is configured according to recommendation





oracle     soft    core       unlimited
oracle     hard    core       unlimited
oracle     soft    nproc       131072
oracle     hard    nproc       131072
oracle     soft    nofile       65536
oracle     hard    nofile       65536
oracle     soft    memlock      unlimited
oracle     hard    memlock      unlimited

grid     soft    core       unlimited
grid     hard    core       unlimited
grid     soft    nproc       131072
grid     hard    nproc       131072
grid     soft    nofile       65536
grid     hard    nofile       65536
grid     soft    memlock      unlimited
grid     hard    memlock      unlimited



...More

Top

Verify Data Network is Separate from Management Network

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical, 03/02/11 Benefit / Impact: It is a requirement that the management network be on a different non-overlapping sub-net than the InfiniBand network and the client access network. This is necessary for better network security, better client access bandwidths, and for Auto Service Request (ASR) to work correctly. The management network comprises of the eth0 network interface in the database and storage severs, the ILOM network interfaces of the database and storage servers, and the Ethernet management interfaces of the InfiniBand switches and PDUs. Risk: Having the management network on the same subnet as the client access network will reduce network security, potentially restrict the client access bandwidth to/from the Database Machine to a single 1GbE link, and will prevent ASR from working correctly. Action / Repair: To verify that the management network interface (eth0) is on a separate network from other network interfaces, execute the following command as the "root" userid on both storage and database servers: grep -i network /etc/sysconfig/network-scripts/ifcfg* \| cut -f5 -d"/" \| grep -v "#" The output will be similar to: ifcfg-bondeth0:NETWORK=10.204.77.0 ifcfg-bondib0:NETWORK=192.168.76.0 ifcfg-eth0:NETWORK=10.204.78.0 ifcfg-lo:NETWORK=127.0.0.0 The expected result is that the network values are different. If they are not, investigate and correct the condition.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Management network is separate from data network


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY DATA NETWORK IS SEPARATE FROM MANAGEMENT NETWORK



ifcfg-bondeth0:NETWORK=10.187.4.0
ifcfg-bondib0:NETWORK=192.168.8.0
ifcfg-eth0:NETWORK=10.187.5.0

Status on dm01db02: PASS => Management network is separate from data network


ifcfg-bondeth0:NETWORK=10.187.4.0
ifcfg-bondib0:NETWORK=192.168.8.0
ifcfg-eth0:NETWORK=10.187.5.0

Top

Verify RAID Controller Battery Temperature [Storage Server]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Maintaining proper temperature ranges maximizes RAID controller battery life. The impact of verifying RAID controller battery temperature is minimal. Risk: A reported temperature of 60C or higher causes the battery to suspend charging until the temperature drops and shortens the service life of the battery, causing it to fail prematurely and put the RAID controller into WriteThrough mode which significantly impacts write I/O performance. Action / Repair: To verify the RAID controller battery temperature, execute the following command on all servers: /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -a0 \| grep BatteryType; /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -a0 \| grep -i temper The output will be similar to: BatteryType: iBBU08 Temperature: 38 C Temperature : OK Over Temperature : No If the battery temperature is equal to or greater than 55C, investigate and correct the environmental conditions. NOTE: Replace Battery Module after 3 Year service life assuming the battery temperature has not exceeded 55C. If the temperature has exceeded 55C (battery temp shall not exceed 60C), replace the battery every 2 years.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => RAID controller battery temperature is normal [Storage Server]


DATA FROM DM01CEL01 FOR VERIFY RAID CONTROLLER BATTERY TEMPERATURE [STORAGE SERVER]



Temperature: 39 C
Temperature                             : OK
Over Temperature        : No




DATA FROM DM01CEL02 FOR VERIFY RAID CONTROLLER BATTERY TEMPERATURE [STORAGE SERVER]



Temperature: 38 C
Temperature                             : OK
Over Temperature        : No





DATA FROM DM01CEL03 FOR VERIFY RAID CONTROLLER BATTERY TEMPERATURE [STORAGE SERVER]



Temperature: 40 C
Temperature                             : OK
Over Temperature        : No




...More

Top

Verify RAID Controller Battery Temperature [Database Server]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Maintaining proper temperature ranges maximizes RAID controller battery life. The impact of verifying RAID controller battery temperature is minimal. Risk: A reported temperature of 60C or higher causes the battery to suspend charging until the temperature drops and shortens the service life of the battery, causing it to fail prematurely and put the RAID controller into WriteThrough mode which significantly impacts write I/O performance. Action / Repair: To verify the RAID controller battery temperature, execute the following command on all servers: /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -a0 \| grep BatteryType; /opt/MegaRAID/MegaCli/MegaCli64 -AdpBbuCmd -a0 \| grep -i temper The output will be similar to: BatteryType: iBBU08 Temperature: 38 C Temperature : OK Over Temperature : No If the battery temperature is equal to or greater than 55C, investigate and correct the environmental conditions. NOTE: Replace Battery Module after 3 Year service life assuming the battery temperature has not exceeded 55C. If the temperature has exceeded 55C (battery temp shall not exceed 60C), replace the battery every 2 years.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => RAID controller battery temperature is normal [Database Server]


DATA FROM DM01DB01 FOR VERIFY RAID CONTROLLER BATTERY TEMPERATURE [DATABASE SERVER]



Temperature: 41 C
Temperature                             : OK
Over Temperature        : No

Status on dm01db02: PASS => RAID controller battery temperature is normal [Database Server]


DATA FROM DM01DB02 FOR VERIFY RAID CONTROLLER BATTERY TEMPERATURE [DATABASE SERVER]



Temperature: 38 C
Temperature                             : OK
Over Temperature        : No

Top

Manage ASM Audit File Directory Growth with cron

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The audit file destination directories for an ASM instance can grow to contain a very large number of files if they are not regularly maintained. Use the Linux cron(8) utility and the find(1) command to manage the number of files in the audit file destination directories. The impact of using cron(8) and find(1) to manage the number of files in the audit file destination directories is minimal. Risk: Having a very large number of files can cause the file system to run out of free disk space or inodes, or can cause Oracle to run very slowly due to file system directory scaling limits, which can have the appearance that the ASM instance is hanging on startup. Action / Repair: Refer to MOS Note 1298957.1.
Links	Note: 1298957.1 - Manage Audit File Directory Growth with cron -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ASM Audit file destination file count <= 100,000


DATA FROM DM01DB01 - MCSDB DATABASE - MANAGE ASM AUDIT FILE DIRECTORY GROWTH WITH CRON



Number of audit files at /u01/app/11.2.0.3/grid/rdbms/audit = 139

Status on dm01db02: PASS => ASM Audit file destination file count <= 100,000


Number of audit files at /u01/app/11.2.0.3/grid/rdbms/audit = 38

Top

Verify Database Server Virtual Drive Configuration

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: For X2-2, there are 4 disk drives in a database server controlled by an LSI MegaRAID SAS 9261-8i disk controller. The disks are configured RAID-5 with 3 disks in the RAID set and 1 disk as a hot spare. There is 1 virtual drive created across the RAID set. Verifying the status of the database server RAID devices helps to avoid a possible performance impact, or an outage. For X2-8, there are 8 disk drives in a database server controlled by an LSI MegaRAID SAS 9261-8i disk controller. The disks are configured RAID-5 with 7 disks in the RAID set and 1 disk as a hot spare. There is 1 virtual drive created across the RAID set. Verifying the status of the database server RAID devices helps to avoid a possible performance impact, or an outage. The impact of validating the virtual drives is minimal. The impact of corrective actions will vary depending on the specific issue uncovered, and may range from simple reconfiguration to an outage. Risk: Not verifying the virtual drives increases the chance of a performance degradation or an outage. Action / Repair: To verify the database server virtual drive configuration, use the following command: /opt/MegaRAID/MegaCli/MegaCli64 CfgDsply -aALL \| grep "Virtual Drive:";/opt/MegaRAID/MegaCli/MegaCli64 CfgDsply -aALL \| grep "Number Of Drives";/opt/MegaRAID/MegaCli/MegaCli64 CfgDsply -aALL \| grep "^State" For X2-2 the output should be similar to: Virtual Drive: 0 (Target Id: 0) Number Of Drives : 3 State : Optimal The expected result is that the virtual device has 3 drives and a state of optimal. NOTE: The virtual device number reported may vary depending upon configuration and version levels. NOTE: If a bare metal restore procedure is performed on a database server without using the "dualboot=no" configuration, that database server may be left with three virtual devices for X2-2 and 7 for X2-8. Please see My Oracle Support note 1323309.1 for additional information and correction instructions.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database Server Virtual Drive Configuration meets recommendation


DATA FROM DM01DB01 FOR VERIFY DATABASE SERVER VIRTUAL DRIVE CONFIGURATION



Virtual Drive: 1 (Target Id: 1)
State               : Optimal
Number Of Drives    : 3

Status on dm01db02: PASS => Database Server Virtual Drive Configuration meets recommendation


DATA FROM DM01DB02 FOR VERIFY DATABASE SERVER VIRTUAL DRIVE CONFIGURATION



Virtual Drive: 1 (Target Id: 1)
State               : Optimal
Number Of Drives    : 3

Top

DBM FailGroups

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	There should be one failgroup per diskgroup for each Database Machine cell. So for instance, assuming 3 cells and two diskgroups, each diskgroup should have 3 failgroups, one on each cell. SQL> select distinct group_number,failgroup from v$asm_disk; GROUP_NUMBER FAILGROUP ------------ ------------------------------ 1 DSCBAS01S 1 DSCBAS02S 1 DSCBAS03S 2 DSCBAS01S 2 DSCBAS02S 2 DSCBAS03S 6 rows selected.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => Correct number of FailGroups per ASM DiskGroup are configured


DATA FROM DM01DB01 - MCSDB DATABASE - DBM FAILGROUPS




Disk group DATA_DM01 has 3 failgroups
Disk group DBFS_DG has 3 failgroups
Disk group RECO_DM01 has 3 failgroups

Top

Exadata storage server system model number

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => All Exadata storage server meet system model number requirement


DATA FROM DM01CEL01 FOR EXADATA STORAGE SERVER SYSTEM MODEL NUMBER




NOTE: Look for system_descritpion =

Connected. Use ^D to exit.
-> show /SP system_description

/SP
Properties:
system_description = SUN FIRE X4270 M2 SERVER, ILOM v3.0.16.10.d, r74499


-> Session closed
Disconnected





DATA FROM DM01CEL02 FOR EXADATA STORAGE SERVER SYSTEM MODEL NUMBER




NOTE: Look for system_descritpion =

Connected. Use ^D to exit.
-> show /SP system_description

/SP
Properties:
system_description = SUN FIRE X4270 M2 SERVER, ILOM v3.0.16.10.d, r74499


-> Session closed
Disconnected




DATA FROM DM01CEL03 FOR EXADATA STORAGE SERVER SYSTEM MODEL NUMBER




NOTE: Look for system_descritpion =

Connected. Use ^D to exit.
-> show /SP system_description

/SP
Properties:
system_description = SUN FIRE X4270 M2 SERVER, ILOM v3.0.16.10.d, r74499


-> Session closed
Disconnected




...More

Top

Database server system model number

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => System model number is correct


DATA FROM DM01DB01 FOR EXADATA SYSTEM MODEL NUMBER




NOTE: Look for system_description =

Connected. Use ^D to exit.
-> show /SP system_description

/SP
Properties:
system_description = SUN FIRE X4170 M2 SERVER, ILOM v3.0.16.10.d, r74499


-> Session closed
Disconnected

Status on dm01db02: PASS => System model number is correct


DATA FROM DM01DB02 FOR EXADATA SYSTEM MODEL NUMBER




NOTE: Look for system_description =

Connected. Use ^D to exit.
-> show /SP system_description

/SP
Properties:
system_description = SUN FIRE X4170 M2 SERVER, ILOM v3.0.16.10.d, r74499


-> Session closed
Disconnected

Top

Number of Mounts before a File System check

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	A filesystem will be checked (fsck) after a specified number of times it is mounted, typically at reboot time. This maximum number of mounts before a check can be determined via the tune2fs -l command (look for Maximum mount count) and is -1 by default on the database servers of the database machine, meaning no fsck will be run. If you would like to change this maximum, it can be done with the tune2fs -c command.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Number of Mounts before a File System check is set to -1 for system disk


DATA FROM DM01DB01 FOR NUMBER OF MOUNTS BEFORE A FILE SYSTEM CHECK




NOTE: Look for Maximum mount count

tune2fs 1.39 (29-May-2006)
Filesystem volume name:   BOOT
Last mounted on:          <not available>
Filesystem UUID:          d8d92dff-d116-403a-8476-9cb0cce12bd4
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal resize_inode dir_index filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              32128
Block count:              128488

Reserved block count:     6424
Free blocks:              97461
Free inodes:              32089
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2008
Inode blocks per group:   251
Filesystem created:       Tue Nov 27 10:42:25 2012
Last mount time:          Sat Feb  8 19:10:54 2014
Last write time:          Sat Feb  8 19:10:54 2014
Mount count:              25
Maximum mount count:      -1
Last checked:             Tue Nov 27 10:42:25 2012
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:		  128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      c18c01b2-49a7-403a-b4be-90a608146db2
Journal backup:           inode blocks
...More

Status on dm01db02: PASS => Number of Mounts before a File System check is set to -1 for system disk


DATA FROM DM01DB02 FOR NUMBER OF MOUNTS BEFORE A FILE SYSTEM CHECK




NOTE: Look for Maximum mount count

tune2fs 1.39 (29-May-2006)
Filesystem volume name:   BOOT
Last mounted on:          <not available>
Filesystem UUID:          6ab16708-dba7-43ae-8629-e05ce8cfce1a
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal resize_inode dir_index filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              32128
Block count:              128488

Reserved block count:     6424
Free blocks:              97471
Free inodes:              32089
First block:              1
Block size:               1024
Fragment size:            1024
Reserved GDT blocks:      256
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2008
Inode blocks per group:   251
Filesystem created:       Tue Nov 27 10:44:33 2012
Last mount time:          Sat Feb  8 20:38:29 2014
Last write time:          Sat Feb  8 20:38:29 2014
Mount count:              17
Maximum mount count:      -1
Last checked:             Tue Nov 27 10:44:33 2012
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:		  128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      9bee6516-c917-4d77-9b41-de33ab323e96
Journal backup:           inode blocks
...More

Top

Free space in root file system

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Best Practice, proactive problem avoidance Risk: root filesystem has less than 10% free space remaining. action should be taken to free up space in order to avoid potential problems from lack of space in the root filesystem. Action / Repair: Free up space in the root filesystem
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Free space in root(/) filesystem meets or exceeds recommendation.


DATA FROM DM01DB01 - MCSDB DATABASE - FREE SPACE IN ROOT FILE SYSTEM



Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VGExaDb-LVDbSys1
30G   17G   12G  59% /

Status on dm01db02: PASS => Free space in root(/) filesystem meets or exceeds recommendation.


Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VGExaDb-LVDbSys1
30G  9.5G   19G  34% /

Top

Exadata storage server root filesystem free space

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	root filesystem has less than 10% free space remaining on one ore more storage servers. action should be taken to free up space.
Needs attention on	dm01cel03, dm01cel02, dm01cel01
Passed on	-

Status on dm01cel03, dm01cel02, dm01cel01: WARNING => Free space in root(/) filesystem is less than recommended on one or more storage servers.


DATA FROM DM01CEL01 FOR EXADATA STORAGE SERVER ROOT FILESYSTEM FREE SPACE



Filesystem            Size  Used Avail Use% Mounted on
/dev/md6              9.9G  8.8G  593M  94% /




DATA FROM DM01CEL02 FOR EXADATA STORAGE SERVER ROOT FILESYSTEM FREE SPACE



Filesystem            Size  Used Avail Use% Mounted on
/dev/md6              9.9G  8.5G  884M  91% /





DATA FROM DM01CEL03 FOR EXADATA STORAGE SERVER ROOT FILESYSTEM FREE SPACE



Filesystem            Size  Used Avail Use% Mounted on
/dev/md6              9.9G  8.5G  946M  91% /




...More

Top

Verify Oracle RAC Databases use RDS Protocol over InfiniBand Network.

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The RDS protocol over InfiniBand provides superior performance because it avoids additional memory buffering operations when moving data from process memory to the network interface for IO operations. This includes both IO operations between the Oracle instance and the storage servers, as well as instance to instance block transfers via Cache Fusion. There is minimal impact to verify that the RDS protocol is in use. Implementing the RDS protocol over InfiniBand requires an outage to relink the Oracle software. Risk: If the Oracle RAC databases do not use RDS protocol over the InfiniBand network, IO operations will be sub-optimal. Action / Repair: To verify the RDS protocol is in use by a given Oracle instance, set the ORACLE_HOME and LD_LIBRARY_PATH variables properly for the instance and execute the following command as the oracle userid on each database server where the instance is running: $ORACLE_HOME/bin/skgxpinfo The output should be: rds Note: For Oracle software versions below 11.2.0.2, the skgxpinfo command is not present. For 11.2.0.1, you can copy over skgxpinfo to the proper path in your 11.2.0.1 environment from an available 11.2.0.2 environment and execute it against the 11.2.0.1 database home(s) using the provided command. Note: An alternative check (regardless of Oracle software version) is to scan each instance's alert log (must contain a startup sequence!) for the following line: Cluster communication is configured to use the following interface(s) for this instance 192.168.20.21 cluster interconnect IPC version:Oracle RDS/IP (generic) If the instance is not using the RDS protocol over InfiniBand, relink the Oracle binary using the following commands (with variables properly defined for each home being linked): (as oracle) Shutdown any processes using the Oracle binary If and only if relinking the grid infrastructure home, then (as root) GRID_HOME/crs/install/rootcrs.pl -unlock (as oracle) cd $ORACLE_HOME/rdbms/lib (as oracle) make -f ins_rdbms.mk ipc_rds ioracle If and only if relinking the Grid Infrastructure home, then (as root) GRID_HOME/crs/install/rootcrs.pl -patch Note: Avoid using the relink all command due to various issues. Use the make commands provided.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Oracle RAC Communication is using RDS protocol on Infiniband Network


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY ORACLE RAC DATABASES USE RDS PROTOCOL OVER INFINIBAND NETWORK.



rds

Status on dm01db02: PASS => Oracle RAC Communication is using RDS protocol on Infiniband Network

rds

Top

Verify Oracle RAC Databases use RDS Protocol over InfiniBand Network. [Database Home]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: RDS protocol provides superior performance for Oracle RAC communication because it does not require additional memory buffering operations when moving data from process memory to the network interface for RAC inter-node communication. There is minimal impact to verify that RDS protocol is in use. If it is not, implementing it will require a relink of the Oracle software, which requires an outage. Risk: If the Oracle RAC databases do not use RDS protocol over the InfiniBand network, RAC inter-node communication will be sub-optimal. Action / Repair: Perform the following steps on the database servers: 1. Verify an Oracle RAC database is using the RDS protocol over the InfiniBand Network by checking all alert logs on all nodes: Cluster communication is configured to use the following interface(s) for this instance 192.168.20.21 cluster interconnect IPC version:Oracle RDS/IP (generic) 1. If it is not running RDS, relink the Oracle binary via the following: * (as oracle) Shutdown any process using the Oracle binary * (as root) GRID_HOME/crs/install/rootcrs.pl -unlock only required if relinking in the Grid Infrastructure home * (as oracle) cd $ORACLE_HOME/rdbms/lib * (as oracle) make -f ins_rdbms.mk ipc_rds ioracle * (as root) GRID_HOME/crs/install/rootcrs.pl -patch only required if relinking in the Grid Infrastructure home Note: Avoid using the relink all command due to various issues. Use the make commands as seen above when relinking oracle binaries. Note: The dcli utility can be used to double check that all nodes are configured consistently with respect to the skgxp libraries in use. An example command to perform this check is dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l oracle md5sum ${ORACLE_HOME}/lib/libskgxp11.so
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database Home is properly linked with RDS library


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY ORACLE RAC DATABASES USE RDS PROTOCOL OVER INFINIBAND NETWORK. [DATABASE HOME]




NOTE: md5sum of RDS protocol libraries should match for Database to properly use RDS protocol for Infiniband

352f95d3be1aed7796f11e7cfa45699d  /u01/app/oracle/product/11.2.0.3/dbhome_1/lib/libskgxp11.so
352f95d3be1aed7796f11e7cfa45699d  /u01/app/oracle/product/11.2.0.3/dbhome_1/lib/libskgxpr.so

Status on dm01db02: PASS => Database Home is properly linked with RDS library



NOTE: md5sum of RDS protocol libraries should match for Database to properly use RDS protocol for Infiniband

352f95d3be1aed7796f11e7cfa45699d  /u01/app/oracle/product/11.2.0.3/dbhome_1/lib/libskgxp11.so
352f95d3be1aed7796f11e7cfa45699d  /u01/app/oracle/product/11.2.0.3/dbhome_1/lib/libskgxpr.so

Top

Verify InfiniBand is the Private Network for Oracle Clusterware Communication

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The InfiniBand network in an Oracle Exadata Database Machine provides superior performance and throughput characteristics that allow Oracle Clusterware to operate at optimal efficiency. The overhead for these verification steps is minimal. Risk: If the InfiniBand network is not used for Oracle Clusterware communication, performance will be sub-optimal. Action / Repair: The InfiniBand network is preconfigured on the storage servers. Perform the following on the database servers: Verify the InfiniBand network is the private network used for Oracle Clusterware communication with the following command: $GI_HOME/bin/oifcfg getif -type cluster_interconnect For X2-2 the output should be similar to: bondib0 192.168.8.0 global cluster_interconnect For X2-8 the output should be similar to: bondib0 192.168.8.0 global cluster_interconnect bondib1 192.168.8.0 global cluster_interconnect bondib2 192.168.8.0 global cluster_interconnect bondib3 192.168.8.0 global cluster_interconnect If the InfiniBand network is not the private network used for Oracle Clusterware communication, configure it following the instructions in MOS note 1073502.1, "How to Modify Private Network Interface in 11.2 Grid Infrastructure". NOTE: It is important to ensure that your public interface is properly marked as public and not private. This can be checked with the oifcfg getif command. If it is inadvertantly marked private, you can get errors such as "OS system dependent operation:bind failed with status" and "OS failure message: Cannot assign requested address". It can be corrected with a command like oifcfg setif -global eth0/:public
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => InfiniBand is the Private Network for Oracle Clusterware Communication


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY INFINIBAND IS THE PRIVATE NETWORK FOR ORACLE CLUSTERWARE COMMUNICATION



bondib0 = InfiniBand

Status on dm01db02: PASS => InfiniBand is the Private Network for Oracle Clusterware Communication


bondib0 = InfiniBand

Top

Verify storage server disk controllers use writeback cache

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Database servers use an internal RAID controller with a battery-backed cache to host local filesystems. For maximum performance when writing I/O to local disks, the battery-backed cache should be in "WriteBack" mode. The impact of configuring the battery-backed cache in "WriteBack" mode is minimal. Risk: Not configuring the battery-backed cache in "WriteBack" mode will result in degraded performance when writing I/O to the local database server disks. Action / Repair: To verify that the database server disk controller battery-backed cache is in "WriteBack" mode, run the following command: # /opt/MegaRAID/MegaCli/MegaCli64 -CfgDsply -a0 \| grep -i writethrough # There should be no output returned. If the battery-backed cache is not in "WriteBack" mode, run these commands on the database server to place the battery-backed cache into "WriteBack" mode: /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp WB -Lall -a0 /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp NoCachedBadBBU -Lall -a0 /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp NORA -Lall -a0 /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp Direct -Lall -a0 NOTE: No settings should be modified on Exadata storage cells. The mode described above applies only to database servers in an Exadata database machine.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => All storage server disk controllers use writeback cache


DATA FROM DM01CEL01 FOR VERIFY STORAGE SERVER DISK CONTROLLERS USE WRITEBACK CACHE



Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU




DATA FROM DM01CEL02 FOR VERIFY STORAGE SERVER DISK CONTROLLERS USE WRITEBACK CACHE




Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU




DATA FROM DM01CEL03 FOR VERIFY STORAGE SERVER DISK CONTROLLERS USE WRITEBACK CACHE



Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU




...More

Top

Configure Storage Server alerts to be sent via email

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Oracle Exadata Storage Servers can send various levels of alerts and clear messages via email or snmp, or both. Sending these messages via email at a minimum helps to ensure that a problem is detected and corrected. There is little impact to storage server operation to send these messages via email. Risk: If the storage servers are not configured to send alerts and clear messages via email at a minimum, there is an increased risk of a problem not being detected in a timely manner. Action / Repair: Configure a storage server to send email alerts using the following cellcli command (tailored to your environment): ALTER CELL smtpServer='mailserver.maildomain.com', - smtpFromAddr='firstname.lastname@maildomain.com', - smtpToAddr='firstname.lastname@maildomain.com', - smtpFrom='Exadata cell', - smtpPort='', - smtpUseSSL='TRUE', - notificationPolicy='critical,warning,clear', - notificationMethod='mail'; Use the following cellcli command to validate the email configuration by sending a test email: alter cell validate mail; NOTE: The recommended best practice to monitor an Oracle Exadata Database Machine is with Oracle Enterprise Manager (OEM) and the suite of OEM plugins developed for the Oracle Exadata Database Machine. Please reference My Oracle Support (MOS) note 1110675.1 for details.
Needs attention on	dm01cel03, dm01cel02, dm01cel01
Passed on	-

Status on dm01cel03, dm01cel02, dm01cel01: FAIL => Storage Server alerts are not configured to be sent via email


DATA FROM DM01CEL01 FOR CONFIGURE STORAGE SERVER ALERTS TO BE SENT VIA EMAIL







DATA FROM DM01CEL02 FOR CONFIGURE STORAGE SERVER ALERTS TO BE SENT VIA EMAIL







DATA FROM DM01CEL03 FOR CONFIGURE STORAGE SERVER ALERTS TO BE SENT VIA EMAIL








...More

Top

Exadata celldisk predictive failures

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Any disks in predictive failure status should be attended to immediately.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => No celldisks have status of predictive failure


DATA FROM DM01CEL01 FOR EXADATA CELLDISK PREDICTIVE FAILURES




NOTE: Celldisk Name, Status, Size Attributes

CD_00_dm01cel01	 normal     	 1832.59375G
CD_01_dm01cel01	 normal     	 1832.59375G
CD_02_dm01cel01	 not present	 1861.703125G
CD_03_dm01cel01	 normal     	 1861.703125G
CD_04_dm01cel01	 normal     	 1861.703125G
CD_05_dm01cel01	 normal     	 1861.703125G
CD_06_dm01cel01	 normal     	 1861.703125G
CD_07_dm01cel01	 normal     	 1861.703125G
CD_08_dm01cel01	 normal     	 1861.703125G
CD_09_dm01cel01	 normal     	 1861.703125G
CD_10_dm01cel01	 normal     	 1861.703125G
CD_11_dm01cel01	 normal     	 1861.703125G
FD_00_dm01cel01	 normal     	 22.875G

FD_01_dm01cel01	 normal     	 22.875G
FD_02_dm01cel01	 normal     	 22.875G
FD_03_dm01cel01	 normal     	 22.875G
FD_04_dm01cel01	 normal     	 22.875G
FD_05_dm01cel01	 normal     	 22.875G
FD_06_dm01cel01	 normal     	 22.875G
FD_07_dm01cel01	 normal     	 22.875G
FD_08_dm01cel01	 normal     	 22.875G
FD_09_dm01cel01	 normal     	 22.875G
FD_10_dm01cel01	 normal     	 22.875G
FD_11_dm01cel01	 normal     	 22.875G
FD_12_dm01cel01	 normal     	 22.875G
FD_13_dm01cel01	 normal     	 22.875G
FD_14_dm01cel01	 normal     	 22.875G
FD_15_dm01cel01	 normal     	 22.875G




DATA FROM DM01CEL02 FOR EXADATA CELLDISK PREDICTIVE FAILURES




NOTE: Celldisk Name, Status, Size Attributes

CD_00_dm01cel02	 normal	 1832.59375G
CD_01_dm01cel02	 normal	 1832.59375G
CD_02_dm01cel02	 normal	 1861.703125G
CD_03_dm01cel02	 normal	 1861.703125G
CD_04_dm01cel02	 normal	 1861.703125G
CD_05_dm01cel02	 normal	 1861.703125G
CD_06_dm01cel02	 normal	 1861.703125G
CD_07_dm01cel02	 normal	 1861.703125G
CD_08_dm01cel02	 normal	 1861.703125G
CD_09_dm01cel02	 normal	 1861.703125G
CD_10_dm01cel02	 normal	 1861.703125G
CD_11_dm01cel02	 normal	 1861.703125G
FD_00_dm01cel02	 normal	 22.875G
FD_01_dm01cel02	 normal	 22.875G
FD_02_dm01cel02	 normal	 22.875G
FD_03_dm01cel02	 normal	 22.875G
FD_04_dm01cel02	 normal	 22.875G
FD_05_dm01cel02	 normal	 22.875G
FD_06_dm01cel02	 normal	 22.875G
FD_07_dm01cel02	 normal	 22.875G
FD_08_dm01cel02	 normal	 22.875G
FD_09_dm01cel02	 normal	 22.875G
FD_10_dm01cel02	 normal	 22.875G
FD_11_dm01cel02	 normal	 22.875G
FD_12_dm01cel02	 normal	 22.875G
FD_13_dm01cel02	 normal	 22.875G
FD_14_dm01cel02	 normal	 22.875G
FD_15_dm01cel02	 normal	 22.875G




DATA FROM DM01CEL03 FOR EXADATA CELLDISK PREDICTIVE FAILURES




NOTE: Celldisk Name, Status, Size Attributes

CD_00_dm01cel03	 normal	 1832.59375G
CD_01_dm01cel03	 normal	 1832.59375G
CD_02_dm01cel03	 normal	 1861.703125G
CD_03_dm01cel03	 normal	 1861.703125G
CD_04_dm01cel03	 normal	 1861.703125G
CD_05_dm01cel03	 normal	 1861.703125G
CD_06_dm01cel03	 normal	 1861.703125G
CD_07_dm01cel03	 normal	 1861.703125G
CD_08_dm01cel03	 normal	 1861.703125G
CD_09_dm01cel03	 normal	 1861.703125G
CD_10_dm01cel03	 normal	 1861.703125G
CD_11_dm01cel03	 normal	 1861.703125G
FD_00_dm01cel03	 normal	 22.875G
FD_01_dm01cel03	 normal	 22.875G
FD_02_dm01cel03	 normal	 22.875G
FD_03_dm01cel03	 normal	 22.875G
FD_04_dm01cel03	 normal	 22.875G
FD_05_dm01cel03	 normal	 22.875G
FD_06_dm01cel03	 normal	 22.875G
FD_07_dm01cel03	 normal	 22.875G
FD_08_dm01cel03	 normal	 22.875G
FD_09_dm01cel03	 normal	 22.875G
FD_10_dm01cel03	 normal	 22.875G
FD_11_dm01cel03	 normal	 22.875G
FD_12_dm01cel03	 normal	 22.875G
FD_13_dm01cel03	 normal	 22.875G
FD_14_dm01cel03	 normal	 22.875G
FD_15_dm01cel03	 normal	 22.875G




...More

Top

RAID controller version on storage servers

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	RAID controller version should match on all storage cells. use following command to find out the RAID controller version on storage cell. /opt/MegaRAID/MegaCli/MegaCli64 -AdpAllInfo -a0 \| grep 'FW Package Build' \|awk -F: '{print $2}'
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => RAID controller version matches on all storage servers


DATA FROM DM01CEL01 FOR RAID CONTROLLER VERSION ON STORAGE SERVERS




NOTE: Look for FW Package Build


Adapter #0

==============================================================================
Versions
================
Product Name    : LSI MegaRAID SAS 9261-8i
Serial No       : SV10914745
FW Package Build: 12.12.0-0079

Mfg. Data
================
Mfg. Date       : 03/02/11

Rework Date     : 00/00/00
Revision No     : 16B
Battery FRU     : N/A

Image Versions in Flash:
================
FW Version         : 2.120.203-1440
BIOS Version       : 3.24.00_4.12.05.00_0x05090000
Preboot CLI Version: 04.04-019:#%00008
WebBIOS Version    : 6.0-46-e_41-Rel
NVDATA Version     : 2.09.03-0027
Boot Block Version : 2.02.00.00-0000
BOOT Version       : 09.250.01.219

Pending Images in Flash
================
None

PCI Info
================
Controller Id	: 0000
Vendor Id       : 1000
Device Id       : 0079
SubVendorId     : 1000
SubDeviceId     : 9263

Host Interface  : PCIE

ChipRevision    : B4

Number of Frontend Port: 0
Device Interface  : PCIE

Number of Backend Port: 8
Port  :  Address
0        508002000000007f
1        0000000000000000
2        0000000000000000
3        0000000000000000
4        0000000000000000
5        0000000000000000
6        0000000000000000
7        0000000000000000

HW Configuration
================
SAS Address      : 500605b0030f2800
BBU              : Present
Alarm            : Present
NVRAM            : Present
Serial Debugger  : Present
Memory           : Present
Flash            : Present
Memory Size      : 512MB
TPM              : Absent
On board Expander: Absent
Upgrade Key      : Absent
Temperature sensor for ROC    : Absent
Temperature sensor for controller    : Absent


Settings
================
Current Time                     : 10:59:54 4/16, 2014
Predictive Fail Poll Interval    : 300sec
Interrupt Throttle Active Count  : 16
Interrupt Throttle Completion    : 50us
Rebuild Rate                     : 30%
PR Rate                          : 30%
BGI Rate                         : 30%
Check Consistency Rate           : 30%
Reconstruction Rate              : 30%
Cache Flush Interval             : 4s
Max Drives to Spinup at One Time : 4
Delay Among Spinup Groups        : 2s
Physical Drive Coercion Mode     : 1GB
Cluster Mode                     : Disabled
Alarm                            : Disabled
Auto Rebuild                     : Enabled
Battery Warning                  : Enabled
Ecc Bucket Size                  : 15
Ecc Bucket Leak Rate             : 1440 Minutes
Restore HotSpare on Insertion    : Enabled
Expose Enclosure Devices         : Enabled
Maintain PD Fail History         : Disabled
Host Request Reordering          : Enabled
Auto Detect BackPlane Enabled    : SGPIO/i2c SEP
Load Balance Mode                : Auto
Use FDE Only                     : Yes
Security Key Assigned            : No
Security Key Failed              : No
Security Key Not Backedup        : No
Default LD PowerSave Policy      : Controller Defined
Maximum number of direct attached drives to spin up in 1 min : 120
Auto Enhanced Import             : No
Any Offline VD Cache Preserved   : No
Allow Boot with Preserved Cache  : No
Disable Online Controller Reset  : No
PFK in NVRAM                     : No
Use disk activity for locate     : No
POST delay			 : 90 seconds

Capabilities
================
RAID Level Supported             : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span
Supported Drives                 : SAS, SATA

Allowed Mixing:

Mix in Enclosure Allowed
Mix of SAS/SATA of HDD type in VD Allowed
Mix of SAS/SATA of SSD type in VD Allowed

Status
================
ECC Bucket Count                 : 0

Limitations
================
Max Arms Per VD          : 32
Max Spans Per VD         : 8
Max Arrays               : 128
Max Number of VDs        : 64
Max Parallel Commands    : 1008
Max SGE Count            : 80
Max Data Transfer Size   : 8192 sectors
Max Strips PerIO         : 42
Max LD per array         : 16
Min Strip Size           : 8 KB
Max Strip Size           : 1.0 MB
Max Configurable CacheCade Size: 0 GB
Current Size of CacheCade      : 0 GB
Current Size of FW Cache       : 399 MB

Device Present
================
Virtual Drives    : 11
Degraded        : 0
Offline         : 0
Physical Devices  : 14
Disks           : 12
Critical Disks  : 1
Failed Disks    : 0

Supported Adapter Operations
================
Rebuild Rate                    : Yes
CC Rate                         : Yes
BGI Rate                        : Yes
Reconstruct Rate                : Yes
Patrol Read Rate                : Yes
Alarm Control                   : Yes
Cluster Support                 : No
BBU                             : Yes
Spanning                        : Yes
Dedicated Hot Spare             : Yes
Revertible Hot Spares           : Yes
Foreign Config Import           : Yes
Self Diagnostic                 : Yes
Allow Mixed Redundancy on Array : No
Global Hot Spares               : Yes
Deny SCSI Passthrough           : No
Deny SMP Passthrough            : No
Deny STP Passthrough            : No
Support Security                : No
Snapshot Enabled                : No
Support the OCE without adding drives : Yes
Support PFK                     : Yes
Support PI                      : No
Support Boot Time PFK Change    : Yes
Disable Online PFK Change       : No
PFK TrailTime Remaining         : 0 days 0 hours
Support Shield State            : No
Block SSD Write Disk Cache Change: No

Supported VD Operations
================
Read Policy          : Yes
Write Policy         : Yes
IO Policy            : Yes
Access Policy        : Yes
Disk Cache Policy    : Yes
Reconstruction       : Yes
Deny Locate          : No
Deny CC              : No
Allow Ctrl Encryption: No
Enable LDBBM         : No
Support Breakmirror  : No
Power Savings        : No

Supported PD Operations
================
Force Online                            : Yes
Force Offline                           : Yes
Force Rebuild                           : Yes
Deny Force Failed                       : No
Deny Force Good/Bad                     : No
Deny Missing Replace                    : No
Deny Clear                              : No
Deny Locate                             : No
Support Temperature                     : Yes
Disable Copyback                        : No
Enable JBOD                             : No
Enable Copyback on SMART                : Yes
Enable Copyback to SSD on SMART Error   : Yes
Enable SSD Patrol Read                  : No
PR Correct Unconfigured Areas           : Yes
Enable Spin Down of UnConfigured Drives : Yes
Disable Spin Down of hot spares         : No
Spin Down time                          : 30
T10 Power State                         : No
Error Counters
================
Memory Correctable Errors   : 0
Memory Uncorrectable Errors : 0

Cluster Information
================
Cluster Permitted     : No
Cluster Active        : No

Default Settings
================
Phy Polarity                     : 0
Phy PolaritySplit                : 0
Background Rate                  : 30
Strip Size                       : 64kB
Flush Time                       : 4 seconds
Write Policy                     : WB
Read Policy                      : None
Cache When BBU Bad               : Disabled
Cached IO                        : Yes
SMART Mode                       : Mode 6
Alarm Disable                    : No
Coercion Mode                    : 1GB
ZCR Config                       : Unknown
Dirty LED Shows Drive Activity   : No
BIOS Continue on Error           : No
Spin Down Mode                   : None
Allowed Device Type              : SAS/SATA Mix
Allow Mix in Enclosure           : Yes
Allow HDD SAS/SATA Mix in VD     : Yes
Allow SSD SAS/SATA Mix in VD     : Yes
Allow HDD/SSD Mix in VD          : No
Allow SATA in Cluster            : No
Max Chained Enclosures           : 16
Disable Ctrl-R                   : Yes
Enable Web BIOS                  : Yes
Direct PD Mapping                : No
BIOS Enumerate VDs               : Yes
Restore Hot Spare on Insertion   : Yes
Expose Enclosure Devices         : Yes
Maintain PD Fail History         : Yes
Disable Puncturing               : No
Zero Based Enclosure Enumeration : Yes
PreBoot CLI Enabled              : Yes
LED Show Drive Activity          : No
Cluster Disable                  : Yes
SAS Disable                      : No
Auto Detect BackPlane Enable     : SGPIO/i2c SEP
Use FDE Only                     : Yes
Enable Led Header                : Yes
Delay during POST                : 0
EnableCrashDump                  : No
Disable Online Controller Reset  : No
EnableLDBBM                      : No
Un-Certified Hard Disk Drives    : Allow
Treat Single span R1E as R10     : No
Max LD per array                 : 16
Power Saving option              : Don't Auto spin down Configured Drives
Max power savings option is  not allowed for LDs. Only T10 power conditions are to be used.
Default spin down time in minutes: 30
Enable JBOD                      : No
TTY Log In Flash                 : No
Auto Enhanced Import             : No
BreakMirror RAID Support         : No
Disable Join Mirror              : No
Enable Shield State              : No
Time taken to detect CME         : 60s

Exit Code: 0x00




DATA FROM DM01CEL02 FOR RAID CONTROLLER VERSION ON STORAGE SERVERS




NOTE: Look for FW Package Build


Adapter #0

==============================================================================
Versions
================
Product Name    : LSI MegaRAID SAS 9261-8i
Serial No       : SV11001625
FW Package Build: 12.12.0-0079

Mfg. Data
================
Mfg. Date       : 03/01/11
Rework Date     : 00/00/00
Revision No     : 16B
Battery FRU     : N/A

Image Versions in Flash:
================
FW Version         : 2.120.203-1440
BIOS Version       : 3.24.00_4.12.05.00_0x05090000
Preboot CLI Version: 04.04-019:#%00008
WebBIOS Version    : 6.0-46-e_41-Rel
NVDATA Version     : 2.09.03-0027
Boot Block Version : 2.02.00.00-0000
BOOT Version       : 09.250.01.219

Pending Images in Flash
================
None

PCI Info
================
Controller Id	: 0000
Vendor Id       : 1000
Device Id       : 0079
SubVendorId     : 1000
SubDeviceId     : 9263

Host Interface  : PCIE

ChipRevision    : B4

Number of Frontend Port: 0
Device Interface  : PCIE

Number of Backend Port: 8
Port  :  Address
0        508002000000007f
1        0000000000000000
2        0000000000000000
3        0000000000000000
4        0000000000000000
5        0000000000000000
6        0000000000000000
7        0000000000000000

HW Configuration
================
SAS Address      : 500605b0030fb610
BBU              : Present
Alarm            : Present
NVRAM            : Present
Serial Debugger  : Present
Memory           : Present
Flash            : Present
Memory Size      : 512MB
TPM              : Absent
On board Expander: Absent
Upgrade Key      : Absent
Temperature sensor for ROC    : Absent
Temperature sensor for controller    : Absent


Settings
================
Current Time                     : 11:5:50 4/16, 2014
Predictive Fail Poll Interval    : 300sec
Interrupt Throttle Active Count  : 16
Interrupt Throttle Completion    : 50us
Rebuild Rate                     : 30%
PR Rate                          : 30%
BGI Rate                         : 30%
Check Consistency Rate           : 30%
Reconstruction Rate              : 30%
Cache Flush Interval             : 4s
Max Drives to Spinup at One Time : 4
Delay Among Spinup Groups        : 2s
Physical Drive Coercion Mode     : 1GB
Cluster Mode                     : Disabled
Alarm                            : Disabled
Auto Rebuild                     : Enabled
Battery Warning                  : Enabled
Ecc Bucket Size                  : 15
Ecc Bucket Leak Rate             : 1440 Minutes
Restore HotSpare on Insertion    : Enabled
Expose Enclosure Devices         : Enabled
Maintain PD Fail History         : Disabled
Host Request Reordering          : Enabled
Auto Detect BackPlane Enabled    : SGPIO/i2c SEP
Load Balance Mode                : Auto
Use FDE Only                     : Yes
Security Key Assigned            : No
Security Key Failed              : No
Security Key Not Backedup        : No
Default LD PowerSave Policy      : Controller Defined
Maximum number of direct attached drives to spin up in 1 min : 120
Auto Enhanced Import             : No
Any Offline VD Cache Preserved   : No
Allow Boot with Preserved Cache  : No
Disable Online Controller Reset  : No
PFK in NVRAM                     : No
Use disk activity for locate     : No
POST delay			 : 90 seconds

Capabilities
================
RAID Level Supported             : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span
Supported Drives                 : SAS, SATA

Allowed Mixing:

Mix in Enclosure Allowed
Mix of SAS/SATA of HDD type in VD Allowed
Mix of SAS/SATA of SSD type in VD Allowed

Status
================
ECC Bucket Count                 : 0

Limitations
================
Max Arms Per VD          : 32
Max Spans Per VD         : 8
Max Arrays               : 128
Max Number of VDs        : 64
Max Parallel Commands    : 1008
Max SGE Count            : 80
Max Data Transfer Size   : 8192 sectors
Max Strips PerIO         : 42
Max LD per array         : 16
Min Strip Size           : 8 KB
Max Strip Size           : 1.0 MB
Max Configurable CacheCade Size: 0 GB
Current Size of CacheCade      : 0 GB
Current Size of FW Cache       : 399 MB

Device Present
================
Virtual Drives    : 12
Degraded        : 0
Offline         : 0
Physical Devices  : 14
Disks           : 12
Critical Disks  : 0
Failed Disks    : 0

Supported Adapter Operations
================
Rebuild Rate                    : Yes
CC Rate                         : Yes
BGI Rate                        : Yes
Reconstruct Rate                : Yes
Patrol Read Rate                : Yes
Alarm Control                   : Yes
Cluster Support                 : No
BBU                             : Yes
Spanning                        : Yes
Dedicated Hot Spare             : Yes
Revertible Hot Spares           : Yes
Foreign Config Import           : Yes
Self Diagnostic                 : Yes
Allow Mixed Redundancy on Array : No
Global Hot Spares               : Yes
Deny SCSI Passthrough           : No
Deny SMP Passthrough            : No
Deny STP Passthrough            : No
Support Security                : No
Snapshot Enabled                : No
Support the OCE without adding drives : Yes
Support PFK                     : Yes
Support PI                      : No
Support Boot Time PFK Change    : Yes
Disable Online PFK Change       : No
PFK TrailTime Remaining         : 0 days 0 hours
Support Shield State            : No
Block SSD Write Disk Cache Change: No

Supported VD Operations
================
Read Policy          : Yes
Write Policy         : Yes
IO Policy            : Yes
Access Policy        : Yes
Disk Cache Policy    : Yes
Reconstruction       : Yes
Deny Locate          : No
Deny CC              : No
Allow Ctrl Encryption: No
Enable LDBBM         : No
Support Breakmirror  : No
Power Savings        : No

Supported PD Operations
================
Force Online                            : Yes
Force Offline                           : Yes
Force Rebuild                           : Yes
Deny Force Failed                       : No
Deny Force Good/Bad                     : No
Deny Missing Replace                    : No
Deny Clear                              : No
Deny Locate                             : No
Support Temperature                     : Yes
Disable Copyback                        : No
Enable JBOD                             : No
Enable Copyback on SMART                : Yes
Enable Copyback to SSD on SMART Error   : Yes
Enable SSD Patrol Read                  : No
PR Correct Unconfigured Areas           : Yes
Enable Spin Down of UnConfigured Drives : Yes
Disable Spin Down of hot spares         : No
Spin Down time                          : 30
T10 Power State                         : No
Error Counters
================
Memory Correctable Errors   : 0
Memory Uncorrectable Errors : 0

Cluster Information
================
Cluster Permitted     : No
Cluster Active        : No

Default Settings
================
Phy Polarity                     : 0
Phy PolaritySplit                : 0
Background Rate                  : 30
Strip Size                       : 64kB
Flush Time                       : 4 seconds
Write Policy                     : WB
Read Policy                      : None
Cache When BBU Bad               : Disabled
Cached IO                        : Yes
SMART Mode                       : Mode 6
Alarm Disable                    : No
Coercion Mode                    : 1GB
ZCR Config                       : Unknown
Dirty LED Shows Drive Activity   : No
BIOS Continue on Error           : No
Spin Down Mode                   : None
Allowed Device Type              : SAS/SATA Mix
Allow Mix in Enclosure           : Yes
Allow HDD SAS/SATA Mix in VD     : Yes
Allow SSD SAS/SATA Mix in VD     : Yes
Allow HDD/SSD Mix in VD          : No
Allow SATA in Cluster            : No
Max Chained Enclosures           : 16
Disable Ctrl-R                   : Yes
Enable Web BIOS                  : Yes
Direct PD Mapping                : No
BIOS Enumerate VDs               : Yes
Restore Hot Spare on Insertion   : Yes
Expose Enclosure Devices         : Yes
Maintain PD Fail History         : Yes
Disable Puncturing               : No
Zero Based Enclosure Enumeration : Yes
PreBoot CLI Enabled              : Yes
LED Show Drive Activity          : No
Cluster Disable                  : Yes
SAS Disable                      : No
Auto Detect BackPlane Enable     : SGPIO/i2c SEP
Use FDE Only                     : Yes
Enable Led Header                : Yes
Delay during POST                : 0
EnableCrashDump                  : No
Disable Online Controller Reset  : No
EnableLDBBM                      : No
Un-Certified Hard Disk Drives    : Allow
Treat Single span R1E as R10     : No
Max LD per array                 : 16
Power Saving option              : Don't Auto spin down Configured Drives
Max power savings option is  not allowed for LDs. Only T10 power conditions are to be used.
Default spin down time in minutes: 30
Enable JBOD                      : No
TTY Log In Flash                 : No
Auto Enhanced Import             : No
BreakMirror RAID Support         : No
Disable Join Mirror              : No
Enable Shield State              : No
Time taken to detect CME         : 60s

Exit Code: 0x00




DATA FROM DM01CEL03 FOR RAID CONTROLLER VERSION ON STORAGE SERVERS




NOTE: Look for FW Package Build


Adapter #0

==============================================================================
Versions
================
Product Name    : LSI MegaRAID SAS 9261-8i
Serial No       : SV11006711
FW Package Build: 12.12.0-0079

Mfg. Data
================
Mfg. Date       : 03/02/11
Rework Date     : 00/00/00
Revision No     : 16B
Battery FRU     : N/A

Image Versions in Flash:
================
FW Version         : 2.120.203-1440
BIOS Version       : 3.24.00_4.12.05.00_0x05090000
Preboot CLI Version: 04.04-019:#%00008
WebBIOS Version    : 6.0-46-e_41-Rel
NVDATA Version     : 2.09.03-0027
Boot Block Version : 2.02.00.00-0000
BOOT Version       : 09.250.01.219

Pending Images in Flash
================
None

PCI Info
================
Controller Id	: 0000
Vendor Id       : 1000
Device Id       : 0079
SubVendorId     : 1000
SubDeviceId     : 9263

Host Interface  : PCIE

ChipRevision    : B4

Number of Frontend Port: 0
Device Interface  : PCIE

Number of Backend Port: 8
Port  :  Address
0        508002000000007f
1        0000000000000000
2        0000000000000000
3        0000000000000000
4        0000000000000000
5        0000000000000000
6        0000000000000000
7        0000000000000000

HW Configuration
================
SAS Address      : 500605b00310ad90
BBU              : Present
Alarm            : Present
NVRAM            : Present
Serial Debugger  : Present
Memory           : Present
Flash            : Present
Memory Size      : 512MB
TPM              : Absent
On board Expander: Absent
Upgrade Key      : Absent
Temperature sensor for ROC    : Absent
Temperature sensor for controller    : Absent


Settings
================
Current Time                     : 11:8:0 4/16, 2014
Predictive Fail Poll Interval    : 300sec
Interrupt Throttle Active Count  : 16
Interrupt Throttle Completion    : 50us
Rebuild Rate                     : 30%
PR Rate                          : 30%
BGI Rate                         : 30%
Check Consistency Rate           : 30%
Reconstruction Rate              : 30%
Cache Flush Interval             : 4s
Max Drives to Spinup at One Time : 4
Delay Among Spinup Groups        : 2s
Physical Drive Coercion Mode     : 1GB
Cluster Mode                     : Disabled
Alarm                            : Disabled
Auto Rebuild                     : Enabled
Battery Warning                  : Enabled
Ecc Bucket Size                  : 15
Ecc Bucket Leak Rate             : 1440 Minutes
Restore HotSpare on Insertion    : Enabled
Expose Enclosure Devices         : Enabled
Maintain PD Fail History         : Disabled
Host Request Reordering          : Enabled
Auto Detect BackPlane Enabled    : SGPIO/i2c SEP
Load Balance Mode                : Auto
Use FDE Only                     : Yes
Security Key Assigned            : No
Security Key Failed              : No
Security Key Not Backedup        : No
Default LD PowerSave Policy      : Controller Defined
Maximum number of direct attached drives to spin up in 1 min : 120
Auto Enhanced Import             : No
Any Offline VD Cache Preserved   : No
Allow Boot with Preserved Cache  : No
Disable Online Controller Reset  : No
PFK in NVRAM                     : No
Use disk activity for locate     : No
POST delay			 : 90 seconds

Capabilities
================
RAID Level Supported             : RAID0, RAID1, RAID5, RAID6, RAID00, RAID10, RAID50, RAID60, PRL 11, PRL 11 with spanning, SRL 3 supported, PRL11-RLQ0 DDF layout with no span, PRL11-RLQ0 DDF layout with span
Supported Drives                 : SAS, SATA

Allowed Mixing:

Mix in Enclosure Allowed
Mix of SAS/SATA of HDD type in VD Allowed
Mix of SAS/SATA of SSD type in VD Allowed

Status
================
ECC Bucket Count                 : 0

Limitations
================
Max Arms Per VD          : 32
Max Spans Per VD         : 8
Max Arrays               : 128
Max Number of VDs        : 64
Max Parallel Commands    : 1008
Max SGE Count            : 80
Max Data Transfer Size   : 8192 sectors
Max Strips PerIO         : 42
Max LD per array         : 16
Min Strip Size           : 8 KB
Max Strip Size           : 1.0 MB
Max Configurable CacheCade Size: 0 GB
Current Size of CacheCade      : 0 GB
Current Size of FW Cache       : 399 MB

Device Present
================
Virtual Drives    : 12
Degraded        : 0
Offline         : 0
Physical Devices  : 14
Disks           : 12
Critical Disks  : 0
Failed Disks    : 0

Supported Adapter Operations
================
Rebuild Rate                    : Yes
CC Rate                         : Yes
BGI Rate                        : Yes
Reconstruct Rate                : Yes
Patrol Read Rate                : Yes
Alarm Control                   : Yes
Cluster Support                 : No
BBU                             : Yes
Spanning                        : Yes
Dedicated Hot Spare             : Yes
Revertible Hot Spares           : Yes
Foreign Config Import           : Yes
Self Diagnostic                 : Yes
Allow Mixed Redundancy on Array : No
Global Hot Spares               : Yes
Deny SCSI Passthrough           : No
Deny SMP Passthrough            : No
Deny STP Passthrough            : No
Support Security                : No
Snapshot Enabled                : No
Support the OCE without adding drives : Yes
Support PFK                     : Yes
Support PI                      : No
Support Boot Time PFK Change    : Yes
Disable Online PFK Change       : No
PFK TrailTime Remaining         : 0 days 0 hours
Support Shield State            : No
Block SSD Write Disk Cache Change: No

Supported VD Operations
================
Read Policy          : Yes
Write Policy         : Yes
IO Policy            : Yes
Access Policy        : Yes
Disk Cache Policy    : Yes
Reconstruction       : Yes
Deny Locate          : No
Deny CC              : No
Allow Ctrl Encryption: No
Enable LDBBM         : No
Support Breakmirror  : No
Power Savings        : No

Supported PD Operations
================
Force Online                            : Yes
Force Offline                           : Yes
Force Rebuild                           : Yes
Deny Force Failed                       : No
Deny Force Good/Bad                     : No
Deny Missing Replace                    : No
Deny Clear                              : No
Deny Locate                             : No
Support Temperature                     : Yes
Disable Copyback                        : No
Enable JBOD                             : No
Enable Copyback on SMART                : Yes
Enable Copyback to SSD on SMART Error   : Yes
Enable SSD Patrol Read                  : No
PR Correct Unconfigured Areas           : Yes
Enable Spin Down of UnConfigured Drives : Yes
Disable Spin Down of hot spares         : No
Spin Down time                          : 30
T10 Power State                         : No
Error Counters
================
Memory Correctable Errors   : 0
Memory Uncorrectable Errors : 0

Cluster Information
================
Cluster Permitted     : No
Cluster Active        : No

Default Settings
================
Phy Polarity                     : 0
Phy PolaritySplit                : 0
Background Rate                  : 30
Strip Size                       : 64kB
Flush Time                       : 4 seconds
Write Policy                     : WB
Read Policy                      : None
Cache When BBU Bad               : Disabled
Cached IO                        : Yes
SMART Mode                       : Mode 6
Alarm Disable                    : No
Coercion Mode                    : 1GB
ZCR Config                       : Unknown
Dirty LED Shows Drive Activity   : No
BIOS Continue on Error           : No
Spin Down Mode                   : None
Allowed Device Type              : SAS/SATA Mix
Allow Mix in Enclosure           : Yes
Allow HDD SAS/SATA Mix in VD     : Yes
Allow SSD SAS/SATA Mix in VD     : Yes
Allow HDD/SSD Mix in VD          : No
Allow SATA in Cluster            : No
Max Chained Enclosures           : 16
Disable Ctrl-R                   : Yes
Enable Web BIOS                  : Yes
Direct PD Mapping                : No
BIOS Enumerate VDs               : Yes
Restore Hot Spare on Insertion   : Yes
Expose Enclosure Devices         : Yes
Maintain PD Fail History         : Yes
Disable Puncturing               : No
Zero Based Enclosure Enumeration : Yes
PreBoot CLI Enabled              : Yes
LED Show Drive Activity          : No
Cluster Disable                  : Yes
SAS Disable                      : No
Auto Detect BackPlane Enable     : SGPIO/i2c SEP
Use FDE Only                     : Yes
Enable Led Header                : Yes
Delay during POST                : 0
EnableCrashDump                  : No
Disable Online Controller Reset  : No
EnableLDBBM                      : No
Un-Certified Hard Disk Drives    : Allow
Treat Single span R1E as R10     : No
Max LD per array                 : 16
Power Saving option              : Don't Auto spin down Configured Drives
Max power savings option is  not allowed for LDs. Only T10 power conditions are to be used.
Default spin down time in minutes: 30
Enable JBOD                      : No
TTY Log In Flash                 : No
Auto Enhanced Import             : No
BreakMirror RAID Support         : No
Disable Join Mirror              : No
Enable Shield State              : No
Time taken to detect CME         : 60s

Exit Code: 0x00




...More

Top

RDBMS Version

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	The RBMS version for X2-2 is expected to be 11.2.0.2 or higher.
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => RDBMS Version is 11.2.0.2 or higher as expected


DATA FOR MCSDB FOR RDBMS VERSION




RDBMS Version = 11.2.0.3.0

Top

Locally managed tablespaces

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	In order to reduce contention to the data dictionary, rollback data, and reduce the amount of generated redo, locally managed tablespaces should be used rather than dictionary managed tablespaces.
Needs attention on	-
Passed on	MCSDB

Status on MCSDB: PASS => All tablespaces are locally manged tablespace


DATA FOR MCSDB FOR LOCALLY MANAGED TABLESPACES




SYSTEM                         LOCAL
SYSAUX                         LOCAL
UNDOTBS1                       LOCAL
TEMP                           LOCAL
UNDOTBS2                       LOCAL
USERS                          LOCAL
MCSDW                          LOCAL
MCSODS                         LOCAL
IDX_MCSODS                     LOCAL
IDX_MCSDW                      LOCAL
MCSSTG                         LOCAL
MCSAPP                         LOCAL
INFO_BASE                      LOCAL

INFO_DATA                      LOCAL

GIS_DATA                       LOCAL
GIS_GPS_HIS_DATA               LOCAL
DEP                            LOCAL
TYYW                           LOCAL
OLTS_DEFAULT                   LOCAL
DEV5_TBS_OAAM_TEMP             LOCAL
OLTS_BATTRSTORE                LOCAL
DEV5_BRSAINDX                  LOCAL
DEV5_TBS_OAAM_UDV_MP_IDX       LOCAL
DEV5_TBS_OAAM_DATA_APR         LOCAL
DEV5_TBS_OAAM_ET_US_MP_IDX     LOCAL
DEV5_TBS_OAAM_ND_HS_IDX        LOCAL

DEV5_SOAINFRA                  LOCAL
DEV5_TBS_OAAM_ENTX_MP_IDX      LOCAL
DEV5_TBS_OAAM_DATA_OCT         LOCAL
DEV5_TBS_OAAM_DATA_DEC         LOCAL
DEV5_TBS_OAAM_RL_LG_IDX        LOCAL
DEV5_TBS_OAAM_EONEPRF_IDX      LOCAL
OLTS_ATTRSTORE                 LOCAL
DEV5_BRSADATA                  LOCAL
DEV5_TBS_OAAM_QA_HT_DATA       LOCAL
DEV5_APM_TEMP                  LOCAL
DEV5_TBS_OAAM_DATA             LOCAL
DEV5_TBS_OAAM_DATA_NOV         LOCAL
DEV5_TBS_OAAM_DATA_AUG         LOCAL

DEV5_OIM_LOB                   LOCAL
DEV5_TBS_OAAM_DATA_FEB         LOCAL
DEV5_TBS_OAAM_MON_IDX          LOCAL
DEV5_TBS_OAAM_ENTONE_IDX       LOCAL
DEV5_APM                       LOCAL
DEV5_OIM_TEMP                  LOCAL
DEV5_IAS_IAU                   LOCAL
DEV5_TBS_OAAM_DATA_SEP         LOCAL
DEV5_TBS_OAAM_INDX             LOCAL
DEV5_OAM_TEMP                  LOCAL
DEV5_TBS_OAAM_PS_LG_IDX        LOCAL
DEV5_TBS_OAAM_PL_LG_IDX        LOCAL
DEV5_TBS_OAAM_QA_DATA          LOCAL

DEV5_TBS_OAAM_MO_LG_IDX        LOCAL
DEV5_TBS_OAAM_TX_LG_IDX        LOCAL
DEV5_TBS_OAAM_DATA_JAN         LOCAL
DEV5_BRSATEMP                  LOCAL
DEV5_TBS_OAAM_DATA_MAY         LOCAL
DEV5_TBS_OAAM_ND_IDX           LOCAL
DEV5_TBS_OAAM_TX_DT_IDX        LOCAL
DEV5_TBS_OAAM_DATA_JUN         LOCAL
DEV5_TBS_OAAM_DATA_MAR         LOCAL
DEV5_TBS_OAAM_DATA_JUL         LOCAL
DEV5_TBS_OAAM_US_ND_IDX        LOCAL
OLTS_SVRMGSTORE                LOCAL
DEV5_OIM                       LOCAL

DEV5_TBS_OAAM_SESS_IDX         LOCAL
OLTS_CT_STORE                  LOCAL
DEV5_IAS_ORASDPM               LOCAL
DEV5_IAS_OIF                   LOCAL
DEV5_OAM                       LOCAL
DEV5_MDS                       LOCAL
DEV5_IAS_TEMP                  LOCAL
DEV6_IAS_WEBCENTER             LOCAL
DEV6_IAS_TEMP                  LOCAL
DEV6_MDS                       LOCAL
DEV6_IAS_ACTIVITY              LOCAL
DEV6_IAS_PORTLET               LOCAL
DEV6_BIPLATFORM                LOCAL

DEV6_IAS_DISCUSS               LOCAL
OSBDB                          LOCAL
MAPINFO                        LOCAL
GIS_DATA_IDX                   LOCAL
PORTAL                         LOCAL
SDYWY                          LOCAL
DEV55_OIM_LOB                  LOCAL
DEV55_OIM                      LOCAL
DEV1_IAS_ORASDPM               LOCAL
DEV1_IAS_TEMP                  LOCAL
DEV1_MDS                       LOCAL
DEV1_OIM_LOB                   LOCAL
DEV1_OIM                       LOCAL

DEV1_OIM_TEMP                  LOCAL
DEV1_SOAINFRA                  LOCAL
ALL_IDX                        LOCAL
ETL_MONITOR                    LOCAL
DEV52_IAS_TEMP                 LOCAL
MCSERP                         LOCAL
DEVBITEST_IAS_TEMP             LOCAL
DEVBITEST_BIPLATFORM           LOCAL
DEVBITEST_MDS                  LOCAL
DEV52_OAM_TEMP                 LOCAL
DEV52_OAM                      LOCAL
DEV52_IAS_IAU                  LOCAL
DEV53_OAM_TEMP                 LOCAL

DEV53_IAS_TEMP                 LOCAL
DEV53_IAS_IAU                  LOCAL
DEV53_OAM                      LOCAL
MCSZEMN                        LOCAL
DEV117_OAM_TEMP                LOCAL
DEV117_IAS_IAU                 LOCAL
DEV117_IAS_TEMP                LOCAL
DEV117_OAM                     LOCAL
DEV1172_IAS_TEMP               LOCAL
DEV1172_OAM_TEMP               LOCAL
DEV1172_IAS_IAU                LOCAL
DEV1172_OAM                    LOCAL
IDX_MCSSTG                     LOCAL

MCSHTY_DATA                    LOCAL
...More

Top

ASM Version

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The components in the I/O stack are tightly integrated in Exadata. You must use the proper versions of software both on the storage servers and the database servers. There is minimal impact to verify the ASM version. Risk: If the ASM version is not correct, the database(s) will not be able to communicate with the storage servers via ASM. Action / Repair: Verify the Oracle ASM software is version 11.2.0.2 or higher If it is not, correct the condition.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => ASM Version is 11.2.0.2 or higher as expected


DATA FROM DM01DB01 - MCSDB DATABASE - ASM VERSION



asm instance version = 11.2.0.3.0

Status on dm01db02: PASS => ASM Version is 11.2.0.2 or higher as expected


asm instance version = 11.2.0.3.0

Top

Turn NUMA Off [Operating System]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Database servers in Oracle Exadata Database Machine by default are booted with operating system NUMA support enabled. Commands that manipulate large files without using direct I/O on ext3 file systems will cause low memory conditions on the NUMA node (Xeon 5500 processor) currently running the process. By turning NUMA off, a potential local node low memory condition and subsequent performance drop is avoided. The impact of turning NUMA off is minimal. Risk: Once local node memory is depleted, system performance as a whole will be severely impacted. Action / Repair: Follow the instructions in the referenced MOS Note to turn NUMA off in the kernel for database serverss
Links	Note: 1053332.1 - Disable NUMA on database servers to improve performance of Linux file system utilities -
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => NUMA is OFF at operating system level.


DATA FROM DM01DB01 - MCSDB DATABASE - TURN NUMA OFF [OPERATING SYSTEM]




NOTE: Look for numa=off

root=LABEL=DBSYS ro bootarea=dbsys loglevel=7 panic=60 debug rhgb numa=off console=ttyS0,115200n8 console=tty1 crashkernel=128M@64M audit=1 processor.max_cstate=1 nomce
available: 1 nodes (0)
node 0 size: 98295 MB
node 0 free: 6919 MB
No distance information available.

Status on dm01db02: PASS => NUMA is OFF at operating system level.



NOTE: Look for numa=off

root=LABEL=DBSYS ro bootarea=dbsys loglevel=7 panic=60 debug rhgb numa=off console=ttyS0,115200n8 console=tty1 crashkernel=128M@64M audit=1 processor.max_cstate=1 nomce
available: 1 nodes (0)
node 0 size: 98295 MB
node 0 free: 9796 MB
No distance information available.

Top

Verify database server InfiniBand network MTU size is 65520

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Setting the database server InfiniBand network Maximum Transmission Unit (MTU) to 65520 ensures a high transfer rate to external devices that are using TCP/IP over IB such as Media Servers / Data Mules or NFS Servers. There is no impact to verifying the InfiniBand network MTU size. Changing the database server InfiniBand network MTU size requires a reboot. Risk: If the InfiniBand network MTU size is not set to 65520, performance when communicating with devices that use TCP/IP over InfiniBand will be sub-optimal. Action / Repair: To verify the database server InfiniBand network MTU size is 65520, use the following command: for ib_intrfce in `ifconfig \| grep ib \| grep -v ":1" \| cut -c1-7`; do printf "$ib_intrfce: "; ifconfig $ib_intrfce \| grep MTU \| cut -c49-58; done For X2-2, the output will be similar to: bondib0: MTU:65520 ib0: MTU:65520 ib1: MTU:65520 For X2-8, the output will be similar to: bondib0: MTU:65520 bondib1: MTU:65520 bondib2: MTU:65520 bondib3: MTU:65520 ib0: MTU:65520 ib1: MTU:65520 ib2: MTU:65520 ib3: MTU:65520 ib4: MTU:65520 ib5: MTU:65520 ib6: MTU:65520 ib7: MTU:65520 The expected output is that MTU size is 65520. If the MTU size is not 65520, correct it using the following steps: 1) Edit the appropriate files (for example, /etc/sysconfig/network-scripts/ifcfg-bondib0, /etc/sysconfig/network-scripts/ifcfg-ib0, and /etc/sysconfig/network-scripts/ifcfg-ib1 for the bondib0 interface) and add an entry for MTU=65520. For example: MTU=65520 2) Reboot the database server and verify the InfiniBand network MTU size is 65520. NOTE: The InfiniBand? fabric must be in "connected" mode before MTU size can be set. NOTE: Devices that communicate with the database server using TCP/IP over InfiniBand should also be configured with an MTU size of 65520. Both the device and the database server must use the same MTU setting to send transmission units of that size. NOTE: The MTU Size for the IB Interfaces on the Exadata Cells should be left unchanged at 1500 because the communication between the DB Nodes and the Exadata Cells uses RDS and not IP protocols.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database Server InfiniBand network MTU size is 65520


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY DATABASE SERVER INFINIBAND NETWORK MTU SIZE IS 65520




NOTE: Look for MTU:

bondib0   Link encap:InfiniBand  HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
inet addr:192.168.10.1  Bcast:192.168.11.255  Mask:255.255.252.0
inet6 addr: fe80::221:2800:1cf:4887/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1

Status on dm01db02: PASS => Database Server InfiniBand network MTU size is 65520



NOTE: Look for MTU:

bondib0   Link encap:InfiniBand  HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
inet addr:192.168.10.2  Bcast:192.168.11.255  Mask:255.255.252.0
inet6 addr: fe80::221:2800:1cf:4863/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:65520  Metric:1

Top

Verify Oracle RAC Databases use RDS Protocol over InfiniBand Network. [Cluster Home]

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: RDS protocol provides superior performance for Oracle RAC communication because it does not require additional memory buffering operations when moving data from process memory to the network interface for RAC inter-node communication. There is minimal impact to verify that RDS protocol is in use. If it is not, implementing it will require a relink of the Oracle software, which requires an outage. Risk: If the Oracle RAC databases do not use RDS protocol over the InfiniBand network, RAC inter-node communication will be sub-optimal. Action / Repair: Perform the following steps on the database servers: 1. Verify an Oracle RAC database is using the RDS protocol over the InfiniBand Network by checking all alert logs on all nodes: Cluster communication is configured to use the following interface(s) for this instance 192.168.20.21 cluster interconnect IPC version:Oracle RDS/IP (generic) 1. If it is not running RDS, relink the Oracle binary via the following: * (as oracle) Shutdown any process using the Oracle binary * (as root) GRID_HOME/crs/install/rootcrs.pl -unlock only required if relinking in the Grid Infrastructure home * (as oracle) cd $ORACLE_HOME/rdbms/lib * (as oracle) make -f ins_rdbms.mk ipc_rds ioracle * (as root) GRID_HOME/crs/install/rootcrs.pl -patch only required if relinking in the Grid Infrastructure home Note: Avoid using the relink all command due to various issues. Use the make commands as seen above when relinking oracle binaries. Note: The dcli utility can be used to double check that all nodes are configured consistently with respect to the skgxp libraries in use. An example command to perform this check is dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l oracle md5sum ${ORACLE_HOME}/lib/libskgxp11.so
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Clusterware Home is properly linked with RDS library


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY ORACLE RAC DATABASES USE RDS PROTOCOL OVER INFINIBAND NETWORK. [CLUSTER HOME]




NOTE: md5sum should match for Clusterware to properly use RDS Protocol for Infiniband

352f95d3be1aed7796f11e7cfa45699d  /u01/app/11.2.0.3/grid/lib/libskgxp11.so
352f95d3be1aed7796f11e7cfa45699d  /u01/app/11.2.0.3/grid/lib/libskgxpr.so

Status on dm01db02: PASS => Clusterware Home is properly linked with RDS library



NOTE: md5sum should match for Clusterware to properly use RDS Protocol for Infiniband

352f95d3be1aed7796f11e7cfa45699d  /u01/app/11.2.0.3/grid/lib/libskgxp11.so
352f95d3be1aed7796f11e7cfa45699d  /u01/app/11.2.0.3/grid/lib/libskgxpr.so

Top

Verify Cluster Synchronization Services (CSS) misscount = 60

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: By default in 11.2, the CSS misscount is 30 for new Oracle Clusterware Repository (OCR) installations built at install time (not a previous OCR that has been upgraded to 11.2), however onecommand sets misscount to 60 at deployment time. 60 is a conservative setting and the current recommended default for Database Machine. For mission critical applications that require lower brownouts after a database node failure, 30 may be used. Misscount should not be set lower than 30 seconds. The impact of setting CSS misscount to 60 is minimal. Risk: Setting misscount lower than 60 creates a higher risk that an unexpected temporary stall (ex: caused by component failure or performance degredation) results in a node eviction. Action / Repair: To verify that the CSS misscount is set to 60, execute the following command as the "root" userid on a database server, substituting your environment specific path for : /bin/crsctl get css misscount The output will be similar to: CRS-4678: Successful get misscount 60 for Cluster Synchronization Services The expected output is that the CSS misscount is set to 60. If it is not, set it executing the following command as the "root" userid on a database server (takes effect on all nodes in a cluster without an Oracle Clusterware restart), substituting your environment specific path for : /bin/crsctl set css misscount 60 The output will be similar to: CRS-4684: Successful set of parameter misscount to 60 for Cluster Synchronization Services NOTE: Prior to 11.2, the CSS diagwait parameter was set to aid in debugging by ensuring log files had timely information. In 11.2, this parameter is no longer required and should not be set.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => CSS misscount is set to the recommended value of 60


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY CLUSTER SYNCHRONIZATION SERVICES (CSS) MISSCOUNT = 60



CRS-4678: Successful get misscount 60 for Cluster Synchronization Services.

Top

Check for parameter _lm_rcvr_hang_allow_time

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Database initialization parameter _lm_rcvr_hang_allow_time = 140 protects from corner case timeouts lower in the stack and prevents instance evictions
Needs attention on	MCSDB1, MCSDB2
Passed on	-

Status on MCSDB1: FAIL => Database parameter _lm_rcvr_hang_allow_time is NOT set to the recommended value

_lm_rcvr_hang_allow_time = 70

Status on MCSDB2: FAIL => Database parameter _lm_rcvr_hang_allow_time is NOT set to the recommended value

_lm_rcvr_hang_allow_time = 70

Top

Check for parameter _kill_diagnostics_timeout

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: Database initialization parameter _kill_diagnostics_timeout = 140 protects from corner case timeouts lower in the stack and prevents instance evictions
Needs attention on	MCSDB1, MCSDB2
Passed on	-

Status on MCSDB1: FAIL => Database parameter _kill_diagnostics_timeout is not set to recommended value

_kill_diagnostics_timeout = 60

Status on MCSDB2: FAIL => Database parameter _kill_diagnostics_timeout is not set to recommended value

_kill_diagnostics_timeout = 60

Top

Verify There Are No Storage Server Memory (ECC) Errors

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Memory modules that have corrected Memory Errors (ECC) can show degraded performance, IPMI driver timeouts, and BMC error messages in /var/log/messages file. Correcting the condition restores optimal performance. The impact of checking for memory ECC errors is slight. Correction will likely require a firmware upgrade and reboot, or hardware repair downtime. Risk: If not corrected, the faulty memory will lead to performance degradation and other errors. Action / Repair: To check for memory ECC errors, run the following command as the root userid on the storage server: # ipmitool sel list \| grep ECC \| cut -f1 -d : \| sort -u If any errors are reported, take the following actions in order: 1. Upgrade to the latest BIOS as it addresses a potential cause. 2. Reseat the DIMM. 3. Open an SR for hardware replacement.
Needs attention on	-
Passed on	dm01cel03, dm01cel02, dm01cel01

Status on dm01cel03, dm01cel02, dm01cel01: PASS => No Storage Server Memory (ECC) Errors found.


DATA FROM DM01CEL01 FOR VERIFY THERE ARE NO STORAGE SERVER MEMORY (ECC) ERRORS




NOTE: No output means no errors were found






DATA FROM DM01CEL02 FOR VERIFY THERE ARE NO STORAGE SERVER MEMORY (ECC) ERRORS




NOTE: No output means no errors were found







DATA FROM DM01CEL03 FOR VERIFY THERE ARE NO STORAGE SERVER MEMORY (ECC) ERRORS




NOTE: No output means no errors were found






...More

Top

Check for parameter db_block_checksum

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: Experience and testing has shown that certain database initialization parameters should be set at specific values. These are the best practice values set at deployment time. By setting these database initialization parameters as recommended, known problems may be avoided and performance maximized. The parameters are common to all database instances. The impact of setting these parameters is minimal. The performance related settings provide guidance to maintain highest stability without sacrificing performance. Changing the default performance settings can be done after careful performance evaluation and clear understanding of the performance impact. Risk: If the database initialization parameters are not set as recommended, a variety of issues may be encountered, depending upon which initialization parameter is not set as recommended, and the actual set value. Action / Repair: DB_BLOCK_CHECKSUM = FULL aids in block corruption detection. Enable for primary and standby databases
Links	Note: 1302539.1 - Best Practices for Corruption Detection, Prevention, and Automatic Repair - in a Data Guard Configuration - Protect Against Data Corruption
Needs attention on	MCSDB1, MCSDB2
Passed on	-

Status on MCSDB1: FAIL => Database parameter DB_BLOCK_CHECKSUM is NOT set to recommended value

MCSDB1.db_block_checksum = typical

Status on MCSDB2: FAIL => Database parameter DB_BLOCK_CHECKSUM is NOT set to recommended value

MCSDB2.db_block_checksum = typical

Top

Verify the database server InfiniBand network is in "connected" mode.

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: Having the database server InfiniBand network in "connected" mode increases performance when communicating with devices that use TCP/IP over InfiniBand. There is no impact to verifying the InfiniBand network mode. Change the InfiniBand network mode requires a reboot. NOTE: Devices that communicate with the database server using TCP/IP over InfiniBand should also be configured in "connected" mode. Both the device and the database server must be in "connected" mode to achieve the performance benefit. Risk: If the database server InfiniBand network is not in "connected" mode, the performance of devices using TCP/IP over InfiniBand to communicate with the database server will be sub-optimal. Action / Repair: To verify that the database server InfiniBand network is in "connnected" mode, use the following command: # grep [a-z] /sys/class/net/ib*/mode /sys/class/net/ib0/mode:connected /sys/class/net/ib1/mode:connected The expected output is that both ib0 and ib1 report "connected" in the output. If it is not, correct it using the following steps: 1) Edit the /etc/ofed/openib.conf file, search for the line specifying SET_IPOIB_CM, and change its value to "yes". For example: # Enable IPoIB Connected Mode SET_IPOIB_CM=yes 2) Reboot the database server and verify that the InfiniBand network is in "connected" mode.
Needs attention on	-
Passed on	dm01db01, dm01db02

Status on dm01db01: PASS => Database server InfiniBand network is in "connected" mode.


DATA FROM DM01DB01 - MCSDB DATABASE - VERIFY THE DATABASE SERVER INFINIBAND NETWORK IS IN "CONNECTED" MODE.



/sys/class/net/ib0/mode:connected
/sys/class/net/ib1/mode:connected

Status on dm01db02: PASS => Database server InfiniBand network is in "connected" mode.


/sys/class/net/ib0/mode:connected
/sys/class/net/ib1/mode:connected

Top

ASM disk group compatible.asm parameter

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The components in the I/O stack are tightly integrated in Exadata. You must use the proper versions of software both on the storage servers and the database servers. Setting compatible attributes defines available functionality. Setting CELL.SMART_SCAN_CAPABLE enables the offloading of certain query work to the storage servers. Setting AU_SIZE maximizes available disk technology and throughput by reading 4MB of data before performing a disk seek to a new sector location. There is minimal impact to verify and configure these settings. Risk: If these attributes are not set as directed, performance will be sub-optimal. Action / Repair: For the ASM disk group containing Oracle Exadata Storage Server grid disks, verify the attribute settings as follows: * COMPATIBLE.ASM attribute is set to 11.2.0.2 or higher. * COMPATIBLE.RDBMS attribute is set to the minimum Oracle database software version in use. * CELL.SMART_SCAN_CAPABLE attribute is TRUE. * AU_SIZE attribute is 4M. if these attributes are not set properly, correct the condition.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => All disk groups have compatible.asm parameter set to recommended values


DATA FROM DM01DB01 - MCSDB DATABASE - ASM DISK GROUP COMPATIBLE.ASM PARAMETER



ASM DATA_DM01.compatible.asm = 11.2.0.3.0
ASM DBFS_DG.compatible.asm = 11.2.0.3.0
ASM RECO_DM01.compatible.asm = 11.2.0.3.0

Top

ASM Cell smart scan

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Critical Benefit / Impact: The components in the I/O stack are tightly integrated in Exadata. You must use the proper versions of software both on the storage servers and the database servers. Setting compatible attributes defines available functionality. Setting CELL.SMART_SCAN_CAPABLE enables the offloading of certain query work to the storage servers. Setting AU_SIZE maximizes available disk technology and throughput by reading 4MB of data before performing a disk seek to a new sector location. There is minimal impact to verify and configure these settings. Risk: If these attributes are not set as directed, performance will be sub-optimal. Action / Repair: For the ASM disk group containing Oracle Exadata Storage Server grid disks, verify the attribute settings as follows: COMPATIBLE.ASM attribute is set to the Oracle ASM software version in use. COMPATIBLE.RDBMS attribute is set to the Oracle database software version in use. CELL.SMART_SCAN_CAPABLE attribute is TRUE. AU_SIZE attribute is 4M. If these attributes are not set properly, correct the condition.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => All disk groups have CELL.SMART_SCAN_CAPABLE parameter set to true


DATA FROM DM01DB01 - MCSDB DATABASE - ASM CELL SMART SCAN



ASM DATA_DM01.cell.smart_scan_capable = TRUE
ASM DBFS_DG.cell.smart_scan_capable = TRUE
ASM RECO_DM01.cell.smart_scan_capable = TRUE

Top

ASM disk group compatible.rdbms parameter

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: The components in the I/O stack are tightly integrated in Exadata. You must use the proper versions of software both on the storage servers and the database servers. Setting compatible attributes defines available functionality. Setting CELL.SMART_SCAN_CAPABLE enables the offloading of certain query work to the storage servers. Setting AU_SIZE maximizes available disk technology and throughput by reading 4MB of data before performing a disk seek to a new sector location. There is minimal impact to verify and configure these settings. Risk: If these attributes are not set as directed, performance will be sub-optimal. Action / Repair: For the ASM disk group containing Oracle Exadata Storage Server grid disks, verify the attribute settings as follows: * COMPATIBLE.ASM attribute is set to the Oracle ASM software version in use. * COMPATIBLE.RDBMS attribute is set to the minimum Oracle database software version in use. * CELL.SMART_SCAN_CAPABLE attribute is TRUE. * AU_SIZE attribute is 4M. if these attributes are not set properly, correct the condition. NOTE: If the compatible.rdbms diskgroup parameter is higher than any database instance version than that instance can not access those higher compatibility disk groups . If compatible.rdbms is not set properly, then the rdbms software version and database must be upgraded or the diskgroup must be recreated.
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => All disk groups have compatible.rdbms parameter set to recommended values


DATA FROM DM01DB01 - MCSDB DATABASE - ASM DISK GROUP COMPATIBLE.RDBMS PARAMETER



lowest rdbms version = 112030
ASM DATA_DM01.compatible.rdbms = 11.2.0.2.0
ASM DBFS_DG.compatible.rdbms = 11.2.0.2.0
ASM RECO_DM01.compatible.rdbms = 11.2.0.2.0

Top

ASM allocation unit size for all disk groups

Success Factor	DBMACHINE X2-2 AND X2-8 AUDIT CHECKS
Recommendation	Benefit / Impact: In order to achieve fast disk scan rates with today's disk technology, it is important that segments be laid out on disk with at least 4MB of contiguous disk space. This allows disk scans to read 4MB of data from disk before having to perform a seek to another location on disk and therefore ensures that most of the time during a scan is spent transferring data from disk. Risk: Time could be spent seeking between disk locations for data. Action / Repair: To ensure that segments are layed out with 4MB of contiguous data on disk, you will need to set the ASM allocation unit (AU) size to 4MB and ensure that data file extents are at least 4MB in size. The ASM allocation unit can be specified when a disk group is created. For Exadata, we recommend setting the AU size to 4MB. The ASM allocation unit size (AU_SIZE) can be set at disk group creation time as can be seen in the following example: CREATE diskgroup data normal redundancy DISK 'o//DATA' ATTRIBUTE 'AU_SIZE' = '4M', 'cell.smart_scan_capable'='TRUE', 'compatible.rdbms'='11.2.0.0', 'compatible.asm'='11.2.0.0';
Needs attention on	-
Passed on	dm01db01

Status on dm01db01: PASS => All disk groups have allocation unit size set to 4MB


DATA FROM DM01DB01 - MCSDB DATABASE - ASM ALLOCATION UNIT SIZE FOR ALL DISK GROUPS



ASM DATA_DM01.au_size = 4194304
ASM DBFS_DG.au_size = 4194304
ASM RECO_DM01.au_size = 4194304

Top

Cluster Name	dm01-cluster
OS Version	LINUX X86-64 OELRHEL 5 2.6.32-400.1.1.el5uek
CRS Home - Version	/u01/app/11.2.0.3/grid - 11.2.0.3.0
DB Home - Version - Names	/u01/app/oracle/product/11.2.0.3/dbhome_1 - 11.2.0.3.0 - MCSDB
Exadata Version	11.2.3.2.0
Number of nodes	7
Database Servers	2 dm01db02 dm01db01 ..Hide
Storage Servers	3 dm01cel03 dm01cel02 dm01cel01 ..Hide
IB Switches	2 dm01sw-ib2 dm01sw-ib3 ..Hide
exachk Version	2.1.5_20120524
Collection	exachk_MCSDB_041614_105402.zip
Collection Date	16-Apr-2014 11:03:16

Oracle Exadata Assessment Report System Health Score is 85 out of 100 (detail)

Cluster Summary

Table of Contents

Findings Needing Attention

Database Server

Storage Server

MAA Scorecard

Findings Passed

Database Server

Storage Server

Cluster Wide

Best Practices and Other Recommendations

Clusterware version comparison

UID for GI software owner across cluster

Timezone for current user

Grid Infrastructure - Private interconnect interface name check

RDBMS software version comparison

Grid Infrastructure - Public interface name check (VIP)

Kernel version comparison across cluster

RDBMS software owner UID across cluster

Grid Infrastructure software owner time zone

Root time zone

Verify Master (Rack) Serial Number is Set [Database Server and storage server]

High Redundancy Controlfile

Check ORACLE_PATCH 13667791 13734832 for RDBMS home

Processes parameter for ASM instance

Check for parameter recyclebin

Verify celldisk configuration on flash memory devices

Verify griddisk count matches across all storage servers where a given prefix name exists

Verify total number of griddisks with a given prefix name is evenly divisible of celldisks

Verify griddisk ASM status

Verify celldisk configuration on disk drives

Verify total size of all griddisks fully utilizes celldisk capacity

Check for parameter asm_power_limit

Verify average ping times to DNS nameserver

Verify average ping times to DNS nameserver

Verify Database Server Disk Controller Configuration

Verify Database Server Physical Drive Configuration

Check for parameter memory_max_target

Check for parameter pga_aggregate_target

Check for parameter memory_target

Check for parameter sga_target

Check for parameter fast_start_mttr_target

Oracle net services configuration to ship redo

Redo transport protocol

Check for parameter undo_retention

Verify all "BIGFILE" tablespaces have non-default "MAXBYTES" values set

Verify InfiniBand subnet manager is running on an InfiniBand switch

LOG_FILE_NAME_CONVERT

Clusterware status

Logical standby unsupported datatypes

Standby recovery mode

Standby redolog status on primary

Dataguard broker confugration

High redundancy diskgroups

Physical standby status

Flashback database on primary

Database init paramter DB_BLOCK_CHECKING on standby

Scan storage server alerthistory for open alerts

Verify Exadata Smart Flash Log is Created

Verify Exadata Smart Flash Cache is created

Verify PCI bridge is configured for generation II on storage servers

Verify InfiniBand Address Resolution Protocol (ARP) Configuration on Database Servers

Database init parameter DB_BLOCK_CHECKING

Verify there are no griddisks configured on flash memory devices

Verify ASM griddisk,diskgroup and Failure group mapping

Verify storage server metric CD_IO_ST_RQ

Verify Platform Configuration and Initialization Parameters for Consolidation

High Redundancy Redolog files

log_archive_dest_n

compatible

Verify InfiniBand Cable Connection Quality on storage servers

Verify Ethernet Cable Connection Quality

Verify Ethernet Cable Connection Quality on storage servers

Verify InfiniBand Cable Connection Quality

db_recovery_file_dest_size

Recovery and Create File Destinations

cluster_interconnects

cluster_interconnects

Check for parameter parallel_execution_message_size

Oracle Exadata Assessment Report

System Health Score is 85 out of 100 (detail)