When you use the Oracle Enterprise manager Cloud Control single system upgrade method,
backup of the Oracle Management Repository (OMR) is not necessary ____________.
A.
When all the practice upgrades on the test system are successful
B.
When you already have daily backup
C.
When disk space is not available
D.
When flashback is enabled
E.
But recommended as a best practice
Explanation:
Note:
*Oracle Management Repository (Repository) is responsible for data storage, rollup and purging
Overview of Upgrade Approaches
Oracle offers the following upgrade approaches to upgrade your existing Enterprise Manager system:
1-System Upgrade Approach: This approach enables you to upgrade to Enterprise Manager Cloud Control on the same host where your earlier release of Enterprise Manager is running. This approach also upgrades the Oracle Management Repository (Management Repository) in the existing database. Since the upgrade happens on the same host, there is a reasonable downtime involved.
This approach does not refer to upgrading of an Enterprise Manager system in an environment with one Oracle Management Service (OMS). It refers to upgrading of an Enterprise Manager system on the same host as the old one, and having only one Enterprise Manager system existing at any point. To learn about upgrading a multi-OMS environment, see Chapter 21.
2-System Upgrade Approach: This approach enables you to install Enterprise Manager Cloud Control on a host that is different from the host where your existing Enterprise Manager system is running.
This approach does not upgrade the Management Repository in the existing database, but upgrades the one in the backed up database, thus enabling two Enterprise Manager systems to exist. Since a new Enterprise Manager system coexists with the old one, there is no or near zero downtime involved.
1-System Upgrade Approach on a Different Host: This approach enables you to install Enterprise Manager Cloud Control on a host different from where the existing Enterprise Manager is running.
This approach is similar to the 2-System upgrade approach, but unlike the 2-System upgrade approach, this approach upgrades the Management Repository in the existing database itself. Since only one Enterprise Manager system exists at any point, there is a reasonable downtime involved.