Database Reference
In-Depth Information
You can see the availability information for each component in the schematic view. The Overview section at the
top shows the summary of incidents and availability information for all targets within the database machine. It also
has the option to display the temperature for each component. The target navigation bar on the left of the schematic
view allows drilling down to any particular component of your choice. The schematic display also supports viewing
multiple Exadata nodes that are connected to each other using the same InfiniBand network.
If you have more than one Exadata Database Machine in Oracle Enterprise Manager, they can be monitored from
a high-level view by using the Groups framework. Using this framework, you can create a management dashboard
that provides a single consolidated view of performance and usage metrics across many Oracle engineered systems
and their components.
Testing Phase
When you're migrating or upgrading your applications to the Oracle engineered systems, you need to think about
any potential impacts on response time and throughput of the application. Also, you need to understand all the
dependencies and potential risks that may affect the application and plan for comprehensive testing within the
environment to mitigate any of those risks associated with the migration.
For a typical migration and deployment onto an engineered system, such as the Oracle Exadata Database
Machine, you could consider the following three-step process:
1.
Identify applications to be migrated.
2.
Create a test environment.
3.
Validate application performance.
The following sections cover each of these steps.
Identifying Applications to Be Migrated
As discussed in Chapter 5, Oracle Enterprise Manager Consolidation Planner can be used to help identify resources
that could benefit from consolidation. Consolidation Planner can also be a valuable tool when looking to move to an
engineered system. The data collected by EM12c can be leveraged to help derive business and technical requirements
to validate consolidation plans to an engineered system. Additionally, Consolidation Planner can be used to analyze
various migrations or upgrade scenarios and identify application concerns that need to be addressed before a migration.
Each consolidation scenario takes three inputs:
•
Details of the pre-consolidation environment
•
Technical, business, or compliance constraints
•
Details of the destination environment
■
When creating a consolidation project as outlined in Chapter 5, you can optionally choose to generate three
preconfigured consolidation scenarios to add to the project. these out-of-the-box scenarios represent conservative,
aggressive, and medium consolidation schemas.
Note
