Oracle Exadata X5 Administration 1Z0-070

1. Migrating Databases to Exadata Database Machine:

   • Steps for Migration:

     1. Assess the current database environment and plan the migration, considering factors like hardware compatibility, network capacity, and storage configuration.
     2. Prepare the Exadata Database Machine by setting up the required software components and verifying their functionality.
     3. Backup the source database before migration to ensure data integrity.
     4. Use Data Pump Export/Import or RMAN to transfer data to the Exadata Database Machine.
     5. Test the migrated database to ensure it performs as expected.
     6. Perform a full data import and recover any objects missed in the initial import.
     7. Validate the migration by comparing data between the source and target systems.

   • Main Approaches for Migration:

     • In-place migration: The database remains operational throughout the migration process, with minimal impact on users.
     • Offline migration: The database is taken offline to perform a full data export and import, which can be quicker but requires downtime.

   • Appropriate Approach: The choice between in-place or offline migration depends on factors such as the size of the database, acceptable downtime, and performance requirements during migration. For minimal disruption, an in-place migration is preferred; for speed and when downtime is acceptable, an offline migration might be more suitable.

2. Bulk Data Loading:

   • Configure DBFS: Set up the Database File System (DBFS) to stage input data files. DBFS provides a unified storage interface across various storage types and allows for efficient access to files.
   • Use External Tables: Create external tables based on the data files stored in DBFS. This enables high-performance data loading into the database without the need for data import utilities.

3. Exadata Database Machine Platform Monitoring:

   • SNMP, IPMI, ILOM: These tools provide different levels of monitoring and management for the Exadata Database Machine. SNMP (Simple Network Management Protocol) is used for network-related monitoring, IPMI (Intelligent Platform Management Interface) provides hardware-level monitoring, and ILOM (Integrated Lights-Out Management) offers out-of-band management capabilities.

4. Configuring Enterprise Manager Cloud Control 12c:

   • Enterprise Manager Architecture: Understand how Enterprise Manager Cloud Control operates with the Exadata Database Machine, including its ability to manage and monitor Exadata components.
   • Discovery Process: Use Enterprise Manager to discover and map out the components of the Exadata Database Machine.
   • Post-Discovery Configurations: Configure the discovered elements for effective monitoring and management within Enterprise Manager.

5. Monitoring Exadata Database Machine:

   • Database Servers: Monitor key performance indicators, alerts, thresholds, and active sessions using either Cloud Control or the DBMCLI (Exadata Database Machine Command Line Interface).
   • Storage Servers: Track metrics, set up alerts, manage thresholds, and monitor active requests on Exadata Storage Servers. Use quarantines, disk scrubbing, and repair processes for troubleshooting and maintenance.

6. Monitoring Tools:

   • Utilize tools like Exachk, ExaWatcher, TFA Collector DiagTools, ADRCI (Automatic Database Recovery) for diagnosing issues, Imageinfo and Imagehistory for tracking Oracle home versions, and OSWatcher for operating system-level monitoring.

7. Backup and Recovery for Exadata Database Machines:

   • RMAN Optimization: Leverage the Exadata Storage Server's capabilities to optimize RMAN backups, such as offloading backup operations to storage cells.
   • Disk-based and Tape-based Backups: Implement recommended approaches for backing up databases to both disk and tape storage systems.
   • Perform Backup and Recovery: Execute regular backup routines and test recovery procedures to ensure data can be restored in case of failure.
   • Media Server Connection: Connect a media server to the Database Machine's InfiniBand network for tape backups.

8. Database Machine Maintenance tasks:

   • Regularly schedule maintenance tasks such as patching, updates, and hardware checks to ensure the system operates smoothly.

9. Exadata-specific Monitoring and Management:

   • Implement Oracle's Exadata storage cell and database server monitoring features through Enterprise Manager or the command line to maintain optimal performance.

10. Automation with Oracle Configuration Manager (OCM):

    • Use OCM to automate the deployment and configuration of Oracle software components on the Exadata Database Machine, ensuring consistency and reducing manual errors.

11. Automatic System Problem Recognizer (ASPRec):

    • ASPRec is part of the Oracle Diagnostics Pack and helps in detecting, diagnosing, and resolving system problems automatically. It can be configured to run on an Exadata Database Machine.

12. Automatic Workload Repository (AWR) and Active Session History (ASH):

    • Use AWR to monitor and analyze system performance over time. ASH provides a snapshot of active sessions at a given moment, which can be crucial for diagnosing performance issues.

By following these guidelines and utilizing the appropriate tools and methods, you can effectively migrate databases to an Exadata Database Machine, monitor its performance, ensure data integrity through backups and recovery plans, and maintain the system with minimal downtime and optimal performance.