Database Reference
In-Depth Information
Now that you know the key concepts for Consolidation Planner, it is important to also understand a few
constraints you should be aware of. These constraints center on the source server and the destination server.
Source server constraints are based on compatibility or exclusivity. Servers are considered compatible if certain
properties and configuration values match. These properties include the following: lifecycle status, department, and
location. As an example, a property may need to be set when source servers must remain within a specific location
or geographical area. Additionally, source servers can be defined by configuration values that include the following:
network domain, system vendor, system configuration, CPU vendor, CPU name, and operating system. Finally, source
servers can be mutually exclusive. This means that they can be excluded from the consolidation scope because they
do not fit within Oracle best practices. To exclude matching servers, set either or both of the following conditions:
Nodes of a RAC Database, Nodes of an Oracle Cluster.
Destination servers can be scoped out against new or existing candidate servers. The constraints associated with
destination servers are primarily expressed as a percentage of the CPU and memory resource utilization—that is,
how much of either resource type can be used by the destination server.
Now that we have defined source and destination servers, you're ready to take a closer look at how to define a
consolidation project and evaluate the scenarios.
Consolidation Planner is installed as part of the plug-in that includes the Chargeback module. To access
Consolidation Planner, choose Enterprise
➤
Consolidation Planner. This opens the Consolidation Planner module.
If this is a new implementation of Consolidation Planner, no projects will be defined. Figure
5-29
illustrates how to
open the Consolidation Planner.
Figure 5-29.
Enterprise menu options for Consolidation Planner
