Escolar Documentos
Profissional Documentos
Cultura Documentos
Objectives
After completing this lesson, you should be able to: Describe the recommendations for optimizing Exadata performance
Optimizing Performance
Start with best practices for ASM and Oracle Database Areas for special consideration:
Flash memory usage Compression usage Index usage ASM allocation unit size Minimum extent size
Optimizing Performance
Optimizing the performance of your Exadata environment begins with following good practices for database design and application development development. From an administration viewpoint, you should continue to follow the best practices for ASM and Oracle Database in conjunction with advice and statistics provided by tools such as SQL monitor and SQL Tuning Advisor. In addition, there are a number of areas for special consideration listed in the slide. These are covered in the remainder of this lesson.
Speeds up access to frequently accessed data Uses all available flash memory by default Can be managed automatically for maximum efficiency
Beneficial for OLTP and Data Warehouse workloads Uses flash memory as a premium storage device Must be configured by an administrator Requires deliberate planning to use efficiently Additional benefits for specific applications
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Compression Usage
Compression Method Basic Compression CREATE/ALTER TABLE Syntax COMPRESS [BASIC] Compression Ratio High for direct path inserts Conventional path inserts and updates are not compressed High for all transaction types CPU Overhead Minimal: Oracle Database performs compression and decompression Typical Applications DSS
OLTP Compression
Minimal: Oracle Database performs compression and decompression, compression for DML is performed in batches Higher: Decompression is performed by Exadata
Warehouse Compression
Higher for direct path inserts High for conventional path inserts and updates Highest for direct path inserts High for conventional path inserts and updates
DSS
Archiving
Compression Usage
Many people think of data compression as they approach the capacity limits of their storage. Commonly data compression is seen as a performance overhead, Commonly, overhead which must be tolerated in order to deliver extra storage capacity. However, in cases where I/O bandwidth is limited, data compression can be an effective tool to increase performance by using available CPU capacity to effectively increase the I/O throughput of a storage system. Oracle Database provides the following modes of data compression: Basic compression compresses data at the Oracle block level. It allows more data to be stored in each block by replacing duplicate values with a smaller symbolic representation. t ti For F example, l if the th numeric i value l 99999 was present t 50 ti times in i a block of data it could be replaced by 50 occurrences of the # symbol along with an entry in a symbol table (also stored in the block) defining the use of the symbol. The degree of compression depends on the level of duplication in each block. Higher compression ratios can be achieved by using larger block sizes or by sorting data to increase the coincidence of duplicate values. Data remains in row-major format where the columns in each row are stored together. Compression occurs when data is loaded using a direct path load operation, such as CREATE TABLE AS SELECT or direct path SQL*Loader. Tables that use basic compression support DML operations, however any data that is inserted or updated remains uncompressed. Basic compression is useful in decision support systems (DSS) where the compressed data is subject to minimal change. Exadata and Database Machine Administration Workshop 7 - 6
In addition to the basic and OLTP compression modes provided by Oracle Database, Exadata provides Exadata Hybrid Columnar Compression. Exadata Hybrid Columnar Compression technology uses a modified form of columnar storage instead of row-major storage. Sets of rows are stored in an internal structure called a compression unit. Within each compression unit, the values for each column are stored together along with metadata that maps the values to the rows. Compression is achieved by replacing repeating values with smaller symbolic references. Because a compression unit is much larger than an Oracle block, block and because column organization brings similar values together, Exadata Hybrid Columnar Compression can deliver much better compression ratios than both basic and OLTP compression. The best rates of compression are achieved using direct path loads. Exadata Hybrid Columnar Compression provides a choice of compression modes to achieve the proper trade-off between disk usage and CPU overhead: Warehouse compression: This type of compression is optimized for query performance, and is intended for DSS and data warehouse applications. Online archival compression: This type of compression is optimized for maximum compression ratios, and is intended for historical data and data that does not change. Exadata Hybrid Columnar Compression supports DML operations on compressed data. However, such operations attract a considerable CPU overhead and yield a lower compression ratio than for direct path loads. In addition, DML on tables using Exadata Hybrid Columnar Compression requires the entire compression unit to be locked, which may reduce concurrency. Finally, updates to rows using Exadata Hybrid Columnar Compression cause rowids to change. As a result, Exadata Hybrid Columnar Compression is recommended for situations where data changes are infrequent or where data sets are reloaded rather than substantially changed. In conclusion, Exadata Hybrid Columnar Compression makes effective use of Exadata server hardware to deliver the highest levels of compression for data in an Oracle database. It is best suited su ed to o cases where e e the e da data a is s not o subjec subject to o subs substantial a a c change. a ge For o transactional a sac o a da data a se sets, s, you should consider OLTP compression instead of Exadata Hybrid Columnar Compression. In all cases, you should be aware of the relative merits and overheads associated with each compression type in order to choose the best approach for your situation.
Index Usage
With Exadata, scans might perform better than index lookups for some queries. Consider removing indexes where scans deliver acceptable p p performance. Removing unnecessary indexes will:
Improve DML performance Save storage space
Index Usage
Some queries that require indexes when using conventional storage will perform acceptably without indexes using Exadata Exadata. Review your queries that use indexes to determine if they would run acceptably with Exadata scans. To test if queries run acceptably without an index, you can make the index invisible to the optimizer. An invisible index still exists and is maintained by DML operations, but it is not used by the optimizer for queries. To make an index invisible, use the following command: ALTER INDEX <index_name> INVISIBLE Removing unnecessary indexes will aid the performance of DML operations and will save storage space.
TRUE: Sets an 8 MB minimum extent size, but will trim last unloaded extents to 64 KB boundary for direct loads ALWAYS: Sets an 8 MB minimum extent size and also minimizes the creation of suboptimal extent sizes at the end of a load DEFAULT: Uses traditional extent allocation
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Quiz
For which of the following scenarios would it make sense to consider altering the default Exadata Smart Flash Cache in order to configure a flash-based tablespace in your database. 1. When you can fit 10 or more of your tables into a flash-based t bl tablespace. 2. When you can fit at least 80% of your most used tables into a flash-based tablespace. 3. When moving specific tables and indexes to a flash-based tablespace will soak up heavy write activity, freeing disk I/O bandwidth for other operations. operations 4. When you have key application objects (such as a star-schema fact table) that you wish to cache all the time, you understand their space requirements intimately, and you are prepared to accept the additional management effort of configuring a flashbased tablespace.
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Answer: 3, 4
Quiz
Which of the following CREATE TABLE compression clauses are only available to use in conjunction with Exadata storage. 1 COMPRESS BASIC 1. 2. COMPRESS FOR OLTP 3. COMPRESS FOR QUERY 4. COMPRESS FOR ARCHIVE
Answer: 3, 4
Summary
In this lesson, you should have learned how to: Describe the recommendations for optimizing Exadata performance
Additional Resources
Lesson Demonstrations (Viewlets)
Configuring Flash-Based Disk Groups
Objectives
After completing this lesson, you should be able to: Describe the architecture and various configuration options for Database Machine
14 Exadata Storage Servers (all high performance or all high capacity) 1 Cisco Ethernet switch (48-port)
8 Intel-based 2 CPU Sun Fire database servers Keyboard, Video, Mouse (KVM) hardware 2 Power Distribution Units (PDUs) at rear
3 Sun Datacenter InfiniBand Switch 36 (36-port managed QDR switch i h - 40Gb/s) 40Gb/ )
14 Exadata Storage Servers (all high performance or all high capacity) 1 Cisco Ethernet switch (48-port)
3 Sun Datacenter InfiniBand Switch 36 (36-port managed QDR switch i h - 40Gb/s) 40Gb/ )
8 x Eight-Core Intel Xeon X7560 Processors (2.26 GHz) 1 TB (128 x 8 GB) Eight 300 GB 10K RPM SAS disks Disk controller HBA with 512 MB battery backed cache Eight InfiniBand 4X QDR (40Gb/s) ports (4 dual-port PCE 2.0 express modules) Two Network Express Modules (NEM), providing a total of Eight 1GbE Ethernet ports and Eight 10 GbE Ethernet SFP+ ports
(4 Fabric Express Modules (FEM) using Intel 82599 10GbE controller technology)
X2-2 X2-2 Quarter Half Rack Rack High Performance Raw Disk1 High Capacity
21 TB 72 TB 1.1 TB 50 TB 168 TB 2.6 TB 14 TB 50 TB
6 TB 21 TB
1 - Raw capacity calculated using 1 GB = 1000 x 1000 x 1000 bytes and 1 TB = 1000 x 1000 x 1000 x 1000 bytes. 2 - User Data: Actual space for uncompressed end-user data, computed after single mirroring (ASM normal redundancy) and after allowing space for database structures such as temporary space, logs, undo space, and indexes. Actual user data capacity varies by application. User Data capacity calculated using 1 TB = 1024 * 1024 * 1024 * 1024 bytes.
12.5 GB/s 25 GB/s 7 GB/s 25 GB/s 25,000 12 500 12,500 500,000 14 GB/s 50 GB/s 50,000 25 000 25,000
Raw Flash Throughput1 Raw Disk IOPS2 Flash IOPS2 High Performance High Capacity
1,000,000 1,000,000
1 Bandwidth is peak physical disk scan bandwidth, assuming no compression. 2 IOs per second (IOPS) Based on IO requests of size 8K
Scalable
Scale to eight g racks by y adding g cables Scale beyond eight racks by adding InfiniBand switches Scale to hundreds of storage servers to support multipetabyte databases
Quiz
Bonded interfaces are used for the InfiniBand storage network on Database Machine servers to provide: 1. Fault Tolerance and High Availability 2 Increased Bandwidth and Performance 2. 3. Both of the above
Answer: 1
Each database server and Exadata server is configured with bonded network interfaces which g is used so the aggregate gg g use the InfiniBand HCA ports on the server. Active/passive bonding bandwidth of the links is not used simultaneously. For each bonded network interface, each InfiniBand port is connected to a different leaf switch. This configuration provides fault tolerance and high availability by removing the InfiniBand switch as a potential single point of failure.
Quiz
Which of the following scalability options are supported? 1. Upgrading a Quarter Rack Database Machine to a Half Rack Database Machine 2 Upgrading a Half Rack Database Machine to a Full Rack 2. Database Machine 3. Interconnecting two Quarter Rack Database Machines 4. Interconnecting two or more Full Rack Database Machines
Answer: 1, 2, 4
Interconnecting Database Machines is only supported for Half Rack and Full Rack configurations configurations.
Summary
In this lesson, you should have learned how to: Describe the architecture and various configuration options for Database Machine
Objectives
After completing this lesson, you should be able to: Describe the installation and configuration process for Database Machine. Describe the default configuration for Database Machine Machine. Describe supported and unsupported customizations for Database Machine.
Site planning: space, space power, power cooling, cooling logistics logistics Configuration planning: hostnames, IP addresses, databases Network preparation: DNS, NTP, cabling
Reconfigure storage using non-default settings Create additional databases Configure Enterprise Manager Configure backup and recovery
4. Post-installation
Ongoing g g monitoring g and maintenance Conducted by customer or Oracle services engagement
Generates a series of configuration files that drive the installation and configuration programs
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Getting Started
Getting Started
The slide shows a brand new Configuration Worksheet. The values in the worksheet are all pre-defined pre defined defaults defaults. The worksheet version is displayed at the very top of the worksheet worksheet. Please check with your Oracle representative to ensure that you are using the latest available version. Notice that the Configuration Worksheet implies a set of conventions for naming the various components of Database Machine. For example, the Compute Node Hostname is derived by concatenating the DB Machine Prefix along with the Compute Node Base Name and then adding a two digit numeric identifier at the end. Notice also that the private InfiniBand network is configured by default to use addresses in the 192.168.10.X range. Because this network is self-contained within Database Machine, in most cases there is no requirement to change this setting. While the Configuration Worksheet is quite flexible and allows many opportunities for customization, it is highly recommended that customers should stick to the default conventions wherever possible. This not only reduces the possibility for errors or misconfigurations but it also helps to ensure that the resulting configuration is easier to misconfigurations, support.
In this example all the other fields contain default values. Other fields that might typically be set to non-default values include: Cell Disk Size: Set this field to 600G for systems with high performance disks or 2TB for systems with high capacity disks. Backup requirements: Select from one of the available options (Tape backup, Disk backup only, Both Disk and Tape backup). This setting influences the default size of the ASM disk groups that are configured later in the worksheet. Subnet Mask: If the default values are not suitable, the various subnet mask fields should be adjusted to reflect the network where the Database Machine resides. Gateway: If the default values are not suitable, the various gateway fields should be adjusted to reflect the network where the Database Machine resides. Exadata and Database Machine Administration Workshop 9 - 8
DATA
(220G)
RECO
(ALL ~ 309G)
1 2
Physical Preparation
Provide adequate cooling capacity Provide proper ventilation and airflow Provide adequate floor space with adequate floor loading Provide required power outlets Provide required network drops
The Database Servers are also configured symmetrically by default. Each database server is installed with the same operating system configuration, including the same Oracle user account and group definitions. The database servers are configured as a cluster under the control of Oracle Clusterware software. An ASM cluster is also configured. Finally, Oracle Database software is installed on each database server and a Real Application Clusters (RAC) database is established across all the cluster nodes. Note the following particulars regarding the installation and configuration of Oracle Grid Infrastructure and Oracle Database on Database Machine. Grid Naming Service (GNS) is not configured configured. DNS is the preferred naming service for Database Machine. RAC databases created as part of the installation and configuration process are administrator-managed by default. To create a policy-managed RAC database on Database Machine you must manually create the database using the Database Configuration Assistant (DBCA). By default, Database Control is not configured for databases created by the installation and configuration process.
Replace the Ethernet switch Connect a tape library for backup Create and configure additional databases Configure database features
Oracle Data Guard Database File System (DBFS)
Configure Enterprise Manager Customize the storage configuration; ASM and Exadata
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Note: Consult y your Oracle representative p to determine whether other configuration g activities are supported or not.
Quiz
Using the Configuration Worksheet you can set specific IP addresses for each database server and Exadata server in Database Machine: 1. True 2. False
Answer: 1
You can set individual IP addresses by modifying the addresses generated after you click the g Worksheet. Beware that if y you modify y the default Generate button in the Configuration addressing policy you must ensure that the resulting addresses are valid and there are no duplicates. Note that while the Configuration Worksheet is quite flexible and allows customers many opportunities for customization, it is highly recommended that customers should stick to the default conventions wherever possible. This not only reduces the possibility for errors or misconfigurations, but it also helps to ensure that the resulting configuration is easier to support.
Quiz
Which of the following options for connecting to existing SAN storage is supported in conjunction with Database Machine? 1. Install a fiber channel HBA into each database server 2 Use a server connected to the existing SAN as a storage 2. gateway and connect it to Database Machine using NFS over Ethernet 3. Use a server connected to the existing SAN as a storage gateway and connect it to Database Machine using NFS over InfiniBand
Answer: 2, 3
Connecting Database Machine to other servers using Ethernet or InfiniBand is supported. Adding g components to Database Machine servers is not supported.
Summary
In this lesson, you should have learned how to: Describe the installation and configuration process for Database Machine. Describe the default configuration for Database Machine Machine. Describe supported and unsupported customizations for Database Machine.
Additional Resources
Lesson Demonstrations (Viewlets)
Database Machine Configuration Example using Configuration Worksheet
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/091DBMConfig Worksheet/091dbmconfigworksheet_viewlet_swf.html
Objectives
After completing this lesson, you should be able to: Describe the general steps to migrate your database to Database Machine List the main approaches for migrating your database to Database Machine Identify the most appropriate approach for different circumstances
1 Capacity planning
3 Migration
4 Post-migration tasks
CALIBRATE
High Capacity Disk
384 GB 24 TB Up to 7 TB Up to 1 1,000 000 Up to 3,600 Up to 36,000 Up to 1,440 Up to 75,000
Source database
AWR Report
Raw Disk Capacity Uncompressed Data Capacity Raw Disk Throughput (MBPS) Effective Throughput with Flash (MBPS) Effective Throughput with Flash and Compression (MBPS)
Size
IOPS
MBPS
Disk I/Os per Second (IOPS) Flash I/Os per Second (IOPS)
Exadata, ASM and database software must run release 11.2.0.1 or greater. ASM disk group attributes:
COMPATIBLE.ASM=11.2.0.0.0 COMPATIBLE.RDBMS=11.2.0.0.0 CELL.SMART_SCAN_CAPABLE=TRUE AU SIZE 4M AU_SIZE=4M
Weigh up the costs and favor methods that facilitate best practices
Implementing best practices is important in the long term because your future performance depends on it Remember:
ASM 4MB AU size can only be set at disk group creation Large extents (8MB) are set at extent allocation
Streams
Minimal down time
Data Pump
For migration during a planned maintenance period
Note: Logical Standby Database and Streams both have additional considerations which may contradict their use. Firstly, both approaches are unable to natively handle all Oracle Database data types. While there are methods to overcome this limitation, the extra effort required to implement and maintain these methods should not be overlooked. Also, both approaches will fail to duplicate NOLOGGING operations that are conducted on the primary database.
Linux x86_64 only y Linux x86_64 only Linux x86_64 only Limited Little endian
Medium
Low
Recovery Manager
Tablespace level migration
Transportable Database
Migration to a different platform with the same endian format
Transportable Tablespace
Migration to a different platform with different endian format
No
Yes
Broad
Medium
Medium
Note: Database segments created using Oracle Database versions prior to 11g may not align properly on ASM extent boundaries. For data files copied from pre-11g databases, this misalignment can cause a single I/O request issued by the database to result in two physical I/Os split across an ASM extent boundary, and possibly across two physical disks. Because this behavior is most evident when large contiguous I/Os are issued, the impact is likely to be low for OLTP workloads workloads. However, However for workloads that contain many full table scans, the impact can be significant. To create the most efficient extent alignment, data must be loaded into new segments. This can be achieved using a logical migration approach, or using a CREATE TABLE ... AS SELECT command to re-create the segments into a new tablespace after a physical migration.
Other Approaches
Data Integration Tools
Oracle GoldenGate Oracle Data Integrator
Custom Code
Query over database link PL/SQL routines
Hybrid Approaches
For example, Transportable Tablespaces from current production database to staging database outside Database Machine, then Data Pump to unload from staging database and load into Database Machine
Other Approaches
The previous slides introduced a number of migration approaches based on tools and technologies g that are p part of Oracle Database. In addition, , there are many y other migration g technologies and approaches including: Data integration technologies such as Oracle GoldenGate or Oracle Data Integrator can be used to migrate, and if necessary transform data. Typically, such environments provide a high degree of flexibility along with a productive way of defining and implementing the required data integrations and transformations. Also, these technologies are often used to facilitate data migration while the source system continues to run. In some cases, customers have specific circumstances that result in the use of custom code for data migration. This approach typically uses queries over database links as the main data transportation mechanism. These distributed queries are sometimes encapsulated in PL/SQL routines. Custom code is often used in situations where existing routines can be easily repurposed to perform a migration to Database Machine. There are also many potential hybrid approaches that combine two or more of the methods introduced in this lesson. For example, a customer may already use Transportable Tablespaces in their environment so using them as a data source for a migration would be easy and convenient. However, the physical organization of the data in the Transportable Tablespaces may not be ideal for Database Machine so they may choose to re-load the data in fresh segments using Data Pump. Exadata and Database Machine Administration Workshop 10 - 11
Quiz
What are two important best practices when migrating to Exadata storage? 1. Double the size of your SGA. 2 Configure ASM allocation units to 4 MB 2. MB. 3. Double the size of your disk space. 4. Configure database extents to multiples of 4 MB.
Answer: 2, 4
Quiz
Which of the following physical migration approaches is most universally applicable? 1. ASM Online Migration 2 Physical Standby Database 2. 3. Transportable Tablespaces
Answer: 3
Using transportable tablespaces you can migrate to Database Machine from a much broader g of platforms than either of the other approaches. range
Summary
In this lesson, you should have learned how to: Describe the general steps to migrate your database to Database Machine List the main approaches for migrating your database to Database Machine Identify the most appropriate approach for different circumstances
Additional Resources
Lesson Demonstrations (Viewlets) Migrating to Database Machine Using Transportable Tablespaces
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT &id=737460.1
Data Guard Support for Heterogeneous Primary and Standby Systems in Same Data Guard Configuration
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT &id=367445.1
Additional Resources
Documentation and White Papers
Oracle Streams Concepts and Administration 11g Release 2 (11.2)
http://www.oracle.com/pls/db112/to_toc?pathname=server.112/ e10704/toc.htm
Objectives
After completing this lesson, you should be able to: Describe the best practices for bulk data loading into Database Machine Describe the process to configure the Database File System (DBFS) feature for staging input data files Use external tables based on input data files stored in DBFS to perform high-performance data loads
Source System
Database Machine
Target Database Staging Database DBFS CREATE ... AS SELECT ... INSERT ... SELECT ...
Data File
Target tables
Exceptions: compressed files, data read from a pipe or a tape Each file is treated as a granule The number of files determines the maximum degree of parallelism You must use multiple files to manually enable parallelism If using multiple files, then try to keep them similar in size If the file sizes vary significantly, then list them in order from largest to smallest in the external table definition
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Create a bigfile tablespace for DBFS storage C t a DBFS user account Create t
SQL> create user dbfs identified by dbfs quota unlimited on <DBFS Tablespace>; SQL> grant create session, create table, create procedure, dbfs_role to dbfs;
Create a mount point for DBFS with ownership and group permissions i i set tt to th the O Oracle l software ft owner, or user th that t will mount the DBFS file system
# mkdir /data # chown oracle:dba /data
$ cd $ORACLE_HOME/rdbms/admin $ sqlplus dbfs/dbfs SQL> @dbfs_create_filesystem_advanced.sql <TS Name> <FS Name> nocompress nodeduplicate noencrypt non-partition
Mounting DBFS
Using DBFS
Access DBFS through <DBFS Mount Point>/<FS Name>
Copy data files to DBFS using network file transfer methods such as FTP and NFS
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Set the INITIAL storage parameter to 8MB Set the CELL_PARTITION_LARGE_EXTENTS initialization parameter to TRUE or ALWAYS
Use unlimited quotas to bypass quota management Use the parallel clause to set the default degree of parallelism for the target tables
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Transformations using g SQL Q functions Sort data while loading to optimize Exadata storage indexes
Quiz
To facilitate parallel loading from typical flat files your external table definitions must reference numerous smaller data files rather than one file containing all the data: 1. True 2. False
Answer: 2
Oracle automatically divides typical flat files into 10MB granules to facilitate parallel processing Oracle is unable to use this approach with compressed files or data read from a processing. pipe or a tape device.
Quiz
While DBFS is fully functional if it is co-located with your target database, it is recommended to you should configure DBFS in a separate staging database: 1. True 2. False
Answer: 1
Summary
In this lesson, you should have learned how to: Describe the best practices for bulk-data loading into Database Machine Describe the process to configure the Database File System (DBFS) feature for staging flat files Use external tables based on flat files stored in DBFS to perform high-performance data loads
Additional Resources
Lesson Demonstrations (Viewlets)
Bulk Data Loading with Database Machine
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/111DBMBulkD ataLoad/111dbmbulkdataload_viewlet_swf.html
Objectives
After completing this lesson, you should be able to: Describe how RMAN backups are optimized using Exadata Describe the recommended approaches for disk-based disk based and tape-based backups of databases on Database Machine. Describe the recommended best practices for backup and recovery on Database Machine.
Initially, run RMAN using one database instance and two RMAN channels Add another instance with two channels if required Add an additional two channels per instance if required
InfiniBand Network
For SAN attached tape devices you must configure persistent bindings so the device address does not change. If the device address changes, the media servers cannot access the device unless you update the device configuration within the media server software. Therefore, it is very important that your environment maintains consistent device addresses. Persistent bindings are a part of your SAN infrastructure setup. Typically you will configure persistent bindings through the HBA or the operating system. The configuration steps may vary by platform and vendor.
Allocate one RMAN channel per tape drive Configure IORM and DBRM to control resource allocation between backups and application workloads
Relatively y cheap p backup p media that can be stored off site Readily available with high performance access
If no existing data files are present present, restore using up to 2 database instances Recommended number of RMAN channels:
For disk-based restoration, use 2 to 4 RMAN channels per database instance For tape-based restoration restoration, set the number of RMAN channels based on the total number of tape drives
Use your chosen file system backup management software or Oracle Secure Backup can be used Copies of the Oracle Cluster Registry are automatically maintained on the Database Server file system and should be included in Database Server file system backups
Exadata software
File system level backups are not recommended
Use the Exadata Software Rescue Procedure if both system disks fail simultaneously
Quiz
To facilitate disk-based backups you can install additional high capacity Exadata servers into the available space in a Half Rack Database Machine based on high performance disks: 1. True 2. False
Answer: 2
Adding Exadata servers into the same rack as a Half Rack Database Machine is only supported using the Half Rack to Full Rack upgrade package package, and the resulting Full Rack Database Machine can only utilize one disk type; high performance or high capacity. The only supported way to add high capacity cells to a Half Rack Database Machine using high performance cells is to install the high capacity cells into a separate rack and connect them to the Database Machine storage network using the spare ports on the Database Machine InfiniBand switches.
Quiz
How many RMAN channels should you use for tape-based backups? 1. 2 per database instance 2 4 per database instance 2. 3. 1 per tape drive
Answer: 3
Summary
In this lesson, you should have learned how to: Describe how RMAN backups are optimized using Exadata Describe the recommended approaches for disk-based disk based and tape-based backups of databases on Database Machine. Describe the recommended best practices for backup and recovery on Database Machine.
Additional Resources
Lesson Demonstrations (Viewlets)
Backup Optimization Using RMAN and Exadata
Objectives
After completing this lesson, you should be able to: Describe the monitoring tools provided with Database Machine Describe the support support, update and patching considerations that apply to Database Machine
ILOM Overview
ILOM Capability Dedicated service processor and resources What You Can Do Manage the server without consuming system resources Continue to manage the server using standby power even when the server is powered-off Monitor system status and event logs supplies fans, fans disks, disks CPUs, CPUs memory, memory and motherboard Monitor power supplies, Monitor component temperatures Monitor sensors, including voltage and power, and indicators (LEDs) Identify part numbers, versions, and product serial numbers Identify NIC card MAC addresses Redirect the system serial console Access keyboard, video, and mouse (KVM) on remote systems Power the system on or off, either locally or remotely Force power-off for emergency shutdown or perform a graceful shutdown Monitor system BIOS, POST, and sensor messages Monitor hardware and system-related errors, as well as ECC memory errors, reported into SP logs, syslog, and remote log-host Monitor components using industry-standard SNMP commands and the IPMItool utility
Hardware inventory and presence Remote Access System power control and monitoring Error and fault management System alerts, including SNMP traps, IPMI PETs, remote syslog, and email alerts
ILOM Overview
Integrated Lights Out Manager (ILOM) provides advanced service processor hardware and software that you can use to manage and monitor Database Machine servers servers. ILOMs ILOM s dedicated hardware and software is preinstalled on the database servers and Exadata servers inside Database Machine. ILOM enables you to actively manage and monitor the server independently of the operating system state. With ILOM, you can proactively: Learn about hardware errors and faults as they occur Remotely e ote y co control to t the e po power e state o of you your se server e View the graphical and non-graphical consoles for the host View the current status of sensors and indicators on the system Determine the hardware configuration of your system Receive generated alerts about system events in advance through IPMI PETs, SNMP traps, or email alerts. The slide shows a broader list of ILOM capabilities capabilities.
ILOM Example
$ ssh root@eidmdb01-ilom Password: <Password> Sun(TM) Integrated Lights Out Manager Version 3.0.6.10.b r52264 ... -> show /SYS/T_AMB /SYS/T_AMB Targets: Properties: type = Temperature ipmi_name = T_AMB class = Threshold Sensor value = 23.000 degree C upper_nonrecov_threshold = 50.000 degree C upper_critical_threshold = 45.000 degree C ... -> reset /SYS Are you sure you want to reset /SYS (y/n)? y Performing hard reset on /SYS
ILOM Example
The slide shows a simple example using the command line interface to ILOM. In the example, a remote connection is established to ILOM using the dedicated network address associated with ILOM on the specified server. After the connection is established you can execute ILOM commands to perform various functions. In the example, the first ILOM command shows information relating to the servers temperature sensors, while the second command reboots the server. Note that the ILOM session continues beyond the reboot and other ILOM commands can be executed even while the server reboots. For more information, refer to the ILOM documentation located at htt //d http://docs.sun.com/app/docs/coll/ilom3.0 / /d / ll/il 3 0
DCLI Overview
The dcli utility allows you to simultaneously execute a command on multiple Database Machine servers Command types:
Operating system commands CellCLI commands Operating system scripts CellCLI scripts
Commands are executed in separate parallel threads I t Interactive ti sessions i are not t supported t d Python 2.3 and SSH user-equivalence are required Command output is collected and displayed in the terminal executing the dcli utility
DCLI Overview
The dcli utility facilitates centralized management across Database Machine by automating the execution of a command on a set of servers and returning the output to the centralized management location where dcli was run. The types of commands supported by dcli includes operating system commands, CellCLI commands, operating system scripts, and CellCLI scripts. The dcli utility runs commands on multiple servers in parallel threads. However, it does not support an interactive session with a remote application on a server. By default, the dcli utility is located at /opt/oracle/cell/cellsrv/bin/dcli on each Exadata server and at t /usr/local/bin/dcli / /l l/bi /d li on each hd database t b server. Y You can also l copy th the dcli d li utility tilit to t a server outside of Database Machine and centrally execute commands from that server. The dcli utility requires Python version 2.3 or later on the server running dcli. You can determine the version of Python by running the python -V command. In addition, dcli requires prior setup of SSH user-equivalence between all the servers. You can use the dcli utility initially with the -k option to set up SSH user-equivalence between a group of servers. Command output (to stdout and stderr) is collected and displayed after command execution is finished on the specified servers. The dcli options allow command output to be abbreviated to filter output, such as removing messages showing normal status. Exadata and Database Machine Administration Workshop 13 - 7
DCLI Examples
$ dcli g mycells date eidmcel01: Sun May 16 20:48:09 CDT 2010 eidmcel02: Sun May 16 20:48:09 CDT 2010 $ dcli c eidmcel01,eidmcel02 cellcli e list cell eidmcel01: eidmcel01 online eidmcel02: eidmcel02 online $ dcli g mycells x cellclicommands.scl $ dcli g mydbservers l root x dbwork.sh
DCLI Examples
The slide shows a series of examples using the dcli utiltiy. The first example shows dcli d li being used to execute the operating system date d t command. command The g option specifies a file (mycells) which identifies the list of target servers to which the command (date) is sent. The servers can be identified by host names or IP addresses. The servers can be database servers or Exadata servers. The second example uses the c option to specify the target servers (eidmcel01,eidmcel02) on the command line. It invokes CellCLI to report the cell status. The third example uses the x x option to specify a command file file. The command file must exist on the server executing the dcli utility. The command file is copied to the target servers and executed. A file with the .scl extension is run by the CellCLI utility on the target server. A file with a different extension is run by the operating system shell on the target server. The file is copied to the default home directory of the user on the target server. Files specified using the x option must have execute privileges or else dcli will report an error. The final example adds the use of the l option to specify the user to connect as on the remote t servers. By B default, d f lt the th dcli d li utility tilit connects t as th the celladmin ll d i user. For more information, refer to the chapter entitled Using the dcli Utility in the Oracle Exadata Storage Server Software User's Guide 11g Release 2 (11.2). Exadata and Database Machine Administration Workshop 13 - 8
infinicheck
Verifies connectivity across the Database Machine storage network links and checks bandwidth across the links
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Verifying User Equivalance of user=root to all hosts. (If it isn't setup correctly, an authentication prompt will appear to push keys to all the nodes) Verifying User Equivalance of user=root to all cells. (If it isn't setup correctly, an authentication prompt will appear to push keys to all the nodes)
#### CONNECTIVITY TESTS #### [COMPUTE NODES -> STORAGE CELLS] (30 seconds approx.) [SUCCESS]..............Connectivity verified [ [SUCCESS]....... ] All ll h hosts can talk lk to all ll storage cells ll Verifying Subnet Masks on Hosts and Cells [SUCCESS] ......... Subnet Masks is same across the network Checking for bad links in the fabric [SUCCESS].......... No bad fabric links found [COMPUTE NODES -> COMPUTE NODES] (30 seconds approx.) [SUCCESS]..............Connectivity verified [SUCCESS]....... All hosts can talk to all other nodes
####
PERFORMANCE TESTS
####
[(1) Every COMPUTE NODE to its STORAGE CELL] (30 seconds approx.) [SUCCESS]........ Network Bandwidth looks OK. .......... To view only performance results run ./infinicheck -d -p [(2) Every COMPUTE NODE to another COMPUTE NODE] (30 seconds approx.) [SUCCESS]........ Network Bandwidth looks OK. ...... To view only performance results run ./infinicheck -d -p [(3) Every COMPUTE NODE to ALL STORAGE CELLS] (90 seconds approx.) (looking for SymbolErrors) [SUCCESS]....... No port errors found #
Compatibility between these different pieces of software needs to be maintained Patches and updates are rolling rolling in nature wherever possible Key information is maintained in My Oracle Support bulletin 888828.1
Patches can generally be applied online, online while the database is up and running Exadata automatically maintains firmware levels No additional software, RPMs or otherwise, should be installed
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Double-check compatibility of patches with Database Machine Oracle supplies Bundle Patches for Database Machine
Check Exadata patches for database server firmware and operating system updates
Quiz
ILOM enables you to actively manage and monitor an individual server independently of the operating system state. With ILOM, you can proactively: 1. Learn about hardware errors and faults as they y occur 2. Learn about Exadata software faults as they occur 3. Remotely control the power state of your server 4. View the graphical and non-graphical consoles for the host 5. View the contents of the database alert log 6. View the current status of sensors and indicators on the server 7. View information about the hardware configuration of the server
Answers: 1, 3, 4, 6, 7
ILOM does not generate Exadata software alerts, however a hardware fault may generate an ILOM alert and an Exadata alert alert. ILOM does not natively provide a view of the database alert log, however you can use ILOM to remotely access the console for a database server and using that console access you can log into the sever as a DBA user and view the database alert log.
Quiz
Which of the following statements is a broad overview of the recommended approach for patching and updating Database Machine: 1. All updates p for Database Machine are specific p to Database Machine, and these are the only updates that should be applied to Database Machine 2. Use Unbreakable Linux Network (ULN) to update Linux on database servers and Exadata servers, and apply specific database and Exadata updates p for the remaining g software 3. Use Exadata-specific update bundles for the Exadata servers, and use normal database updating practices for the database servers
Answer: 3
Summary
In this lesson, you should have learned how to: Describe the monitoring tools provided with Database Machine Describe the support support, update and patching considerations that apply to Database Machine
Additional Resources
Lesson Demonstrations (Viewlets)
Using the distributed command line utility (dcli)
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/131DBMDCLI/ 131dbmdcli_viewlet_swf.html
Objectives
After completing this lesson, you should be able to: Describe the new features of Exadata and Database Machine introduced in update release 11.2.1.3.1
Alerts for disk failures on database servers SNMP alerts from InfiniBand switches
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Included with hardware warranty and Oracle Premier Support for Systems
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Oracle Support Engineer Oracle Field Engineer Field Replaceable Unit (FRU) dispatched by Support Engineer Service Request routed to Support Engineer
Oracle Case Management System
Fault occurs
Customer
ASR Manager
ASR Service
ASR requirements
ASR Manager requirements:
Qualified Sun server running Oracle Linux 5.3 (or higher) or Solaris 10 update 6 (or higher) ASR Manager g version 2.7 or higher g Connectivity to the management network of Database Machine https connectivity to Oracle Support Can upgrade an existing ASR Manager to monitor Database Machine Can use a Database Machine database server as the ASR Manager, though not recommended
Technical system administrator contact for the Database Machine registered with Oracle Support
ASR requirements
The slide lists the requirements for using ASR in conjunction with Database Machine. See http://www oracle com/asr for more information including a list of qualified Sun servers which http://www.oracle.com/asr can be used to run the ASR Manager.
ASM re-creates lost data using mirrored extents sooner Greater protection from potential data loss associated with multiple overlapping disk failures
Summary
In this lesson, you should have learned how to: Describe the new features of Exadata and Database Machine introduced in update release 11.2.1.3.1