oracle cloud control что это

25.09.202302.07.2023 admin 0 Comments

Oracle cloud control что это

Облако нового поколения, предназначенное для более быстрого и безопасного запуска любых приложений с меньшими затратами.

Узнайте о MySQL, Graphs, JSON, NoSQL и, конечно, Oracle Database на этом двухдневном онлайн-мероприятии, включающем интерактивные сессии и практические занятия.

MySQL Autopilot предоставляет девять новых возможностей автоматизации на основе машинного обучения, при этом улучшая производительность и масштабируемость сервиса MySQL HeatWave.

OCI предоставляет возможности высокопроизводительных вычислений (HPC) в публичном облаке с наиболее экономичными ценами.

Oracle Cloud Insider

Получайте новости о последних отраслевых тенденциях, лучших практиках и обновлениях продуктовов, а также будьте в курсе новых программ обучения и предстоящих мероприятий.

Почему заказчики выбирают OCI

Oracle Cloud — первое публичное облако, созданное с нуля, чтобы стать лучшим облаком для каждого приложения. Переосмыслив базовую разработку и проектирование систем для облачных вычислений, Oracle создала инновации, ускоряющие миграцию, обеспечивающие максимальную надежность и производительность для всех приложений и предлагающие полный набор услуг, необходимых заказчикам для создания инновационных облачных приложений.

Платформа OCI’Cloud Adoption Framework помогает компаниям упростить переход в облако, предлагая множество ценных облачных ресурсов, лучших практик, руководств и вспомогательных инструментов Эта платформа помогает заказчикам определить надежную облачную стратегию, спланировать успешную миграцию нагрузок и обеспечить полную управляемость облачных сред. Cloud Adoption Framework предоставляет заказчикам методологию использования встроенных функций Oracle Cloud, таких как Cloud Lift Services, а также программ ключевых ценностей, включая Oracle Support Rewards.

Источник

1 Overview of Oracle Enterprise Manager Cloud Control 13 c

This chapter provides an overview of Enterprise Manager Cloud Control 13 c and helps you understand its architecture and the various core components that are integrated within the product. It contains the following sections:

For detailed information about Oracle Enterprise Manager Cloud Control, see the Oracle Enterprise Manager Cloud Control Documentation web site:

1.1 About Enterprise Manager Cloud Control 13 c

Oracle Enterprise Manager is Oracle’s integrated enterprise information technology (IT) management product line, which provides the industry’s only complete, integrated, and business-driven enterprise cloud management solution. Oracle Enterprise Manager creates business value for IT by leveraging the built-in management capabilities of the Oracle stack for traditional and cloud environments, enabling customers to achieve unprecedented efficiency gains while dramatically increasing service levels.

The key capabilities of Enterprise Manager include:

A complete cloud lifecycle management solution enabling you to quickly set up, manage, and support enterprise clouds and traditional Oracle IT environments from applications to disk

Maximum return on IT management investment through the best solutions for intelligent management of the Oracle stack and engineered systems with real-time integration of Oracle’s knowledge base with each customer environment

Best service levels for traditional and cloud applications through business-driven application management

Figure 1-1 illustrates how Enterprise Manager Cloud Control offers a solution that enables you to monitor and manage the complete Oracle IT infrastructure from a single console.

Figure 1-1 Enterprise Manager Cloud Control Console

For more information about Enterprise Manager Cloud Control, access the following URL:

1.2 Enterprise Manager Cloud Control Architecture

This section introduces you to the architecture of Enterprise Manager Cloud Control and describes the core components of the product. It includes the following sections:

1.2.1 Architecture of Enterprise Manager Cloud Control

Enterprise Manager Cloud Control includes the following components:

Oracle Management Agent

Oracle Management Service

Oracle Management Repository

Enterprise Manager Cloud Control Console

Figure 1-2 shows a sample Enterprise Manager Cloud Control configuration and illustrates how these core components fit into the architecture.

Figure 1-2 Enterprise Manager Cloud Control Architecture

In Figure 1-2, the load balancer and the multiple Oracle Management Service (OMS) instances are depicted only to indicate how a sample Enterprise Manager Cloud Control architecture would look in a large organization. They are not a prerequisite or a requirement for an Enterprise Manager system installation. If you do not have a load balancer, then the Management Agents communicate directly with the OMS instances.

1.2.2 About Oracle Management Agent

The Management Agent is an integral software component that enables you to convert an unmanaged host to a managed host in the Enterprise Manager system. The Management Agent works in conjunction with the plug-ins to monitor the targets running on that managed host.

With the first Oracle Management Service (OMS) you install, by default you receive a Management Agent called the Central Agent. The Central Agent is used for monitoring only the first OMS host, the first OMS, and the other targets running on the first OMS host. To monitor other hosts and the targets running on those hosts, you must install a separate Standalone Management Agent on each of those hosts.

1.2.3 About Oracle Management Service (OMS)

Oracle Management Service (OMS) is a Web-based application that orchestrates with the Management Agents and the plug-ins to discover targets, monitor and manage them, and store the collected information in a repository for future reference and analysis. The OMS also renders the user interface for Enterprise Manager Cloud Control.

The OMS is deployed to the middleware home, which is the parent directory that contains Oracle WebLogic Server, OMS, plug-ins, Java Development Kit (JDK), Oracle WT directory, Oracle Common, and other relevant configuration files and directories. While installing the OMS, the Enterprise Manager Cloud Control Installation Wizard automatically installs Oracle WebLogic Server and JDK, and therefore, a WebLogic Server admin console is available by default.

1.2.4 About Oracle Management Repository

The Oracle Management Repository (Management Repository) is a storage location where all the information collected by the Management Agent gets stored. It consists of objects such as database jobs, packages, procedures, views, and tablespaces.

The OMS uploads the monitoring data it receives from the Management Agents to the Management Repository. The Management Repository then organizes the data so that it can be retrieved by the OMS and displayed in the Enterprise Manager Cloud Control console. Since data is stored in the Management Repository, it can be shared between any number of administrators accessing the Enterprise Manager Cloud Control.

At the time of installation, the Enterprise Manager Cloud Control Installation Wizard configures the Management Repository in your existing, certified database. The wizard, however, does not install a new database.

1.2.5 About Plug-ins

Plug-ins are pluggable entities that offer special management capabilities customized to suit specific target types. Unlike the earlier releases of Enterprise Manager, in Enterprise Manager Cloud Control, the plug-ins work in conjunction with the OMS and the Management Agent to monitor every target in your environment. Therefore, they are deployed to the OMS as well as the Management Agent. In the earlier releases, plug-ins enabled you to monitor only third-party targets, but in Enterprise Manager Cloud Control, plug-ins enable you to monitor all types of targets in your environment.

Plug-ins have independent release cycles, so every time you have a new version of an Oracle product released, you will have a new version of the plug-in released to support monitoring of that new product version in Enterprise Manager Cloud Control. This simplifies things because you no longer have to wait to upgrade your Enterprise Manager system to support a new product version; instead you can upgrade your plug-ins to monitor the new product version.

Table 1-1 lists the default plug-ins that are installed with a new Enterprise Manager system. In addition to these plug-ins, you can optionally install other plug-ins available in the software kit (DVD, downloaded software bundle, and so on). The installer offers a screen where you can select the optional plug-ins and install them.

Table 1-1 Default Plug-ins Installed with Enterprise Manager Cloud Control

Enables you to discover, monitor, and manage Oracle Database and related targets such as Oracle Real Application Clusters (Oracle RAC), Oracle Automatic Storage Management (Oracle ASM), and so on.

Oracle Fusion Middleware

Enables you to discover, monitor, and manage Oracle Fusion Middleware products such as Oracle WebLogic Domain, Oracle WebLogic AdminServer, Oracle WebLogic Server, Oracle SOA Suite, Oracle Web Tier, and so on.

Enables you to discover, monitor, and manage Oracle Exadata targets.

Oracle Cloud Framework

Enables you to access basic features that are common across cloud services such as Middleware as a Service (MWaaS), Database as a Service (DBaaS), Infrastructure as a Service (IaaS), and Testing as a Service (TaaS).

Oracle System Infrastructure

Enables you to discover, monitor, and manage Oracle hardware systems and Super Cluster engineered systems, including server hardware, chassis, racks, power distribution unit, network equipment, operating systems, virtualization software, and clustering software.

1.2.6 About Oracle JVMD Engine

Java Virtual Machine Diagnostics (JVMD) Engine enables you to diagnose performance problems in Java applications in the production environment. By eliminating the need to reproduce problems, it reduces the time required to resolve these problems, thus improving application availability and performance.

Starting with 13 c (13.1.0.0.0), as part of the Oracle Fusion Middleware Plug-in deployment, one JVMD Engine is installed and configured by default on the OMS. For every additional OMS you deploy, you receive one JVMD Engine by default with that OMS.

While JVMD Engine is installed by default on the OMS host, you will still need JVMD Agents to be manually deployed on the targeted JVMs.

1.2.7 About Oracle BI Publisher

Oracle Business Intelligence (BI) Publisher is Oracle’s primary reporting tool for authoring, managing, and delivering all your highly formatted documents. Oracle BI Publisher makes your data stand out with pixel-perfect reports and dashboards, offers a variety of report and dashboard layouts, and enables you to create all types of highly formatted documents.

Starting with 13 c (13.1.0.0.0), Oracle BI Publisher is installed and configured by default on the OMS. For every additional OMS you deploy, you receive one Oracle BI Publisher by default with that OMS.

1.2.8 About Enterprise Manager Cloud Control Console

The Enterprise Manager Cloud Control console is the user interface you see after you install Enterprise Manager Cloud Control. See Figure 1-1. With the help of the console, you can monitor and administer your entire computing environment from one location on the network. All the systems and services including enterprise application systems, databases, hosts, middleware application servers, listeners, and so on, are easily managed from one central location.

1.2.9 About EMCTL

1.2.10 About EM CLI

The Enterprise Manager Command Line Interface (EM CLI) is a command-line tool that is accessible through classic programming language constructs, enabling tasks to be created and run either from the command-line or programatically. EM CLI enables you to access Enterprise Manager Cloud Control functionality from text-based consoles (shells and command-line windows) for a variety of operating systems.

1.3 Enterprise Manager Management Focus Areas

This section provides brief descriptions of the following management focus areas:

Источник

5 Installing Oracle Enterprise Manager Cloud Control 13c Release 1

This chapter describes how you can install a new Enterprise Manager system while utilizing an existing, certified Oracle Database to store Oracle Management Repository (Management Repository).

In particular, this chapter covers the following:

This chapter is only for installing a complete Enterprise Manager system (with a Management Repository). If you want to install an additional Oracle Management Service (OMS), then see Chapter 7.

Do not install Enterprise Manager Cloud Control 13c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. For more information, see My Oracle Support note 1590556.1.

5.1 Introduction to Installing an Enterprise Manager System

Before you start installing Enterprise Manager Cloud Control, you must understand the fundamentals of Enterprise Manager installation, the various installation types you can use, the components that are installed by default, and so on. This section introduces you to the installation process, and covers the following:

5.1.1 Overview of the Installation Types Offered for Enterprise Manager Cloud Control

You can install Enterprise Manager Cloud Control with either simple or advanced configuration. Table 5-1 describes the basic differences between the two installation types.

If you want to install Enterprise Manager Cloud Control for evaluation or demo purposes, then use the Simple installation type.

Table 5-1 Differences Between Simple and Advanced Installation

Meant for demonstration or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment

Meant for small, medium, and large deployments, and when you want to customize your installation with custom locations, directory names, and passwords.

Installs with minimal, default configuration settings and preferences that you need for a complete Enterprise Manager system. Does not offer too many options to customize your installation.

Offers custom or advanced configuration options that you can select to suit your environment and customize your installation.

Configures with less memory to monitor up to 30 targets, with 2 Oracle Management Agents (Management Agent) and 2 concurrent user sessions for handling about 10 jobs per day.

Offers an option to select the deployment size (small, medium, or large) of your choice, and depending on the deployment size you select, configures with the required memory.

The deployment size essentially indicates the number of targets you plan to monitor, the number of Management Agents you plan to have, and the number of concurrent user sessions you plan to have. The prerequisite checks are run regardless of the selection you make, but the values to be set for the various parameters checked depend on the selection you make

Sets lower values for database parameters.

Sets higher values for database parameters.

Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle.

Installs mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle Exadata plug-in, Oracle Cloud Framework plug-in, and Oracle System Infrastructure plug-in.

Installs any other plug-in you select in the installation wizard.

Prompts for a common password for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration.

Prompts for separate, distinct passwords for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration.

Creates a default OMS instance base directory (gc_inst) outside the Middleware home.

Allows you to change the name of the default OMS instance base directory (gc_inst) to a name of your choice, and creates that directory outside the Middleware home.

Creates tablespaces for management, configuration data, and JVM diagnostics data in default locations.

Allows you to change the locations of the tablespaces for management, configuration data, and JVM diagnostics data.

Installs with default ports.

Allows you to customize the ports according to your environment.

Has only a few interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard.

Has many interview screens to fill in the Enterprise Manager Cloud Control Installation Wizard

5.1.2 Overview of the Core Components Installed and Configured with an Enterprise Manager System

As part of a new Enterprise Manager system, the installation wizard does the following:

Installs Oracle WebLogic Server 12 c Release 1 (12.1.3.0).

Installs Java Development Kit (JDK) 1.7.0_80.

Installs Oracle Management Service 13 c Release 1.

Installs Oracle Management Agent 13 c Release 1 in the agent base directory you specify (outside the middleware home).

Installs Oracle JRF 12 c Release 1 (12.1.3.0), which includes the oracle_common directory.

Installs Oracle Web Tier 12 c Release 1 (12.1.3.0).

Installs Oracle BI Publisher 12 c Release 1 (12.1.3.0), which includes the bi directory.

Creates a plug-in directory and installs the following default plug-ins.

Oracle Database Plug-in

Oracle Fusion Middleware Plug-in

Starting with 13 c Release 1, as part of the Oracle Fusion Middleware Plug-in deployment, one Java Virtual Machine Diagnostics (JVMD) Engine is installed by default on the OMS. For every additional OMS you deploy, you receive one JVMD Engine by default with that OMS.

JVMD enables administrators to diagnose performance problems in Java applications in the production environment. By eliminating the need to reproduce problems, it reduces the time required to resolve these problems, thus improving application availability and performance.

While JVMD Engine is installed by default on the OMS host, you will still need JVMD Agents to be manually deployed on the targeted JVMs. For instructions to deploy the JVMD Agent, see Chapter 8.

Oracle Exadata Plug-in

Oracle Cloud Framework Plug-in

Oracle System Infrastructure Plug-in

Any other additional plug-ins you choose to deploy

On Microsoft Windows, a Node Manager service is NOT created. This is an expected behavior.

Configures an Oracle Management Service Instance Base location ( gc_inst ) outside the Oracle Middleware home (Middleware home), for storing all configuration details related to the OMS. In advanced installation, you can choose to change this location if you want.

Configures Oracle Management Repository in the existing, certified Oracle Database. If the database instance is created using the database template offered by Oracle, then this step is skipped.

The existing, certified Oracle Database must be one of the certified databases listed in the Enterprise Manager certification matrix available on My Oracle Support, or a database instance created with a preconfigured Oracle Management Repository (Management Repository) using the database templates offered by Oracle.

To access the Enterprise Manager certification matrix, follow the steps outlined in Appendix D.

For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Appendix C.

The database can be on a local or remote host, and if it is on a remote host, it must be monitored by Oracle Management Agent. However, Oracle Real Application Clusters (Oracle RAC) databases must only be on a shared disk.

Runs the following configuration assistants to configure the installed components for simple as well as advanced installation:

Plugins Prerequisites Check

MDS Schema Configuration

If you use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then MDS Schema Configuration is not run.

BI Publisher Schema Configuration

Plugins Deployment and Configuration

BI Publisher Configuration

Start Oracle Management Service

Agent Configuration Assistant

5.1.3 Overview of the Directories Created for an Enterprise Manager System

This section describes the following:

5.1.3.1 Overview of the Directories Created for OMS Installation

Figure 5-1 shows the contents of the Middleware home for this type of installation.

Figure 5-1 Middleware Home Contents for a Fresh Installation

The OMS instance base directory (typically, gc_inst ) is maintained outside the middleware home directory, and that is why it is not shown in Figure 5-1.

5.1.3.2 Overview of the Directories Created for Management Agent Installation (Central Agent)

The following are the contents of the agent base directory for the central agent (Management Agent installed with the OMS).

Figure 5-2 shows the contents of the agent home that is within the agent base directory.

Figure 5-2 Contents of the Agent Home

5.2 Before You Begin Installing an Enterprise Manager System

Before you begin installing Enterprise Manager Cloud Control, keep these points in mind:

You must ensure that you have the latest Enterprise Manager Cloud Control software.

Ensure that there are no white spaces in the name of the directory where you download and run the Enterprise Manager Cloud Control software from. For example, do not download and run the software from a directory titled EM Software because there is a white space between the two words of the directory name.

You can install Enterprise Manager Cloud Control using the installation wizard only on a single host, that is, locally on the server where the wizard is invoked. You cannot install on multiple or remote hosts.

Oracle Management Service 13 c can communicate only with the following versions of Management Agents.

Table 5-2 Compatibility Between OMS and Management Agents Across 13c and 12c Releases

Oracle Management Agent 12c Release 3 (12.1.0.3)

Oracle Management Agent 12c Release 4 (12.1.0.4)

Oracle Management Agent 12c Release 5 (12.1.0.5)

Oracle Management Agent 13c

Oracle Management Service 13c

Do not install on a symlink. Installing in such a location may impact life cycle operations such as patching and scaling out. Also, it will impact the functioning of your additional OMS.

You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.

(Only for Graphical Mode) You must set the DISPLAY environment variable.

In bash terminal, run the following command:

For example, export DISPLAY=example.com:1.0

In other terminals, run the following command:

For example, setenv DISPLAY example.com:1.0

The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.7.0_80 and Oracle WebLogic Server 12 c Release 1 (12.1.3.0) by default. A preinstalled JDK or Oracle WebLogic Server is not supported from 13 c Release 1 onwards.

You must ensure that the Oracle WebLogic Server 12 c Release 1 (12.1.3.0) installed by the Enterprise Manager Cloud Control Installation Wizard is dedicated for Enterprise Manager Cloud Control. You must not have any other Oracle Fusion Middleware product installed in that Middleware home.

Enterprise Manager Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same Middleware home because the ORACLE_COMMON property is used by both the products.

As a prerequisite, you must have an existing Oracle Database to configure the Management Repository.

If you install the OMS and the Oracle Database, which houses the Management Repository, on the same host, then when you reboot the host, the OMS and the Management Agent installed with it will not automatically start up. You will have to manually start them.

You can optionally use the database templates offered by Oracle to create a database instance with a preconfigured Management Repository. To do so, refer to Appendix C. You can use such a database instance for simple as well as advanced installation.

However, note that the database templates are essentially designed for simple installation, although they can be used for advanced installation. Therefore, while performing an advanced installation (possibly with small, medium, or large deployment size selection), when you provide the details of such a database, you will be prompted that the database parameters need to be modified to suit the deployment size you selected. You can confirm the message to proceed further. The installation wizard will automatically set the database parameters to the required values.

Enterprise Manager is not affected when you enable or disable features such as XML DB on the Oracle Database in which you plan to configure the Management Repository. Therefore, you can enable or disable any feature in the database because Enterprise Manager does not rely on them.

In addition to the mandatory plug-ins, you can optionally install other plug-ins available in the software kit (DVD, downloaded software). The installer offers a screen where you can select the optional plug-ins and install them. However, if you want to install some plug-ins that are not available in the software kit (DVD, downloaded software), then refer to Section 5.5.1.

If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Section 5.7.

If you are installing in, or will be converting in the future to, a high-availability or a disaster-recovery configuration, then review and become familiar with the contents in the following chapters in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide before continuing with this installation:

Oracle offers bug fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for bug fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:

When determining supportability and certification combinations for an Enterprise Manager Cloud Control installation, you must consider Enterprise Manager Cloud Control’s framework components as well as the targets monitored by Enterprise Manager Cloud Control. Oracle recommends keeping your Cloud Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license.

You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc.

The locale-specific data is stored in the /nls/data directory. Oracle strongly recommends that you either set the environment variable ORA_NLS10 to /nls/data or do not set at all.

Enforcing option is supported for Security-Enhanced Linux (SELinux).

Do not discover any Oracle ZFS Storage Appliance target in 13c environment.

5.3 Prerequisites for Installing an Enterprise Manager System

Table 5-3 lists the prerequisites you must meet before installing Enterprise Manager Cloud Control.

Table 5-3 Prerequisites for Installing Enterprise Manager Cloud Control

Simple Installation	Advanced Installation

Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 1.

Operating System Requirements

For information about platforms receiving future support, refer to My Oracle Support note 793512.1.

OMS on Solaris 11 local zone is not supported.

If you use Oracle Solaris 10, then ensure that you have update 9 or higher installed. To verify whether it is installed, run the following command:

You should see the output similar to the following. Here, s10s_u6 indicates that update 9 is already installed.

Solaris 10 10/08 s10s_u9wos_07b SPARC

Package, Kernel Parameter, and Library Requirements

Ensure that you install all the operating system-specific packages, kernel parameters, and libraries as described in Chapter 2.

Operating System Groups and Users Requirements

Ensure that you create the required operating system groups and users as described in Chapter 3.

Ensure that you use a certified browser as mentioned in the Enterprise Manager certification matrix available on My Oracle Support. To access the Enterprise Manager certification matrix, follow the steps outlined in Appendix D.

Database Version Requirements

Ensure that the existing database is a certified database as mentioned in the Enterprise Manager certification matrix available on My Oracle Support. To access the Enterprise Manager certification matrix and identify whether your database is a certified database, follow these steps in Appendix D.

Alternatively, the database can be a database instance created with a preconfigured Management Repository using the database templates offered by Oracle. For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Appendix C. Ensure that this database is dedicated to Enterprise Manager.

The database configuration types that are supported are pluggable database (PDB), lone-pluggable database (Lone-PDB), and non-container database (Non-CDB).

Database Patch Requirements

Ensure that you apply the latest PSU on the supported database.

Database Optimizer Adaptive Feature Requirement

Ensure that you disable the optimizer adaptive feature ( optimizer_adaptive_features=FALSE ) in the Oracle Database that houses the Management Repository. To do so, follow these steps:

Disable the optimizer adaptive feature by setting the optimizer_adaptive_features parameter to FALSE. To do so, run the following SQL command:

alter system set optimizer_adaptive_features=false scope=both sid=’*’;

Restart the database.

Verify that the changes have taken effect. To do so, run the following SQL command:

show parameter adaptive;

You should see the following output:

NFS Mount Point Location Requirements

If you are installing onto an NFS-mounted location, then ensure that you do the following:

Ensure that root squash is enabled with execute permission on that host where you want to perform the installation.

Ensure that the Access Control List processing is disabled for the NFS mount point. In other words, the mount point must be defined with the noacl option in the /etc/fstab file. Otherwise, the installation can fail.

To verify this, run the following command as the install user to check the contents of the /etc/fstab file. Verify if the mount point on which you plan to install Enterprise Manager has the noacl option set.

For example, in the following output, the mount point /u01/app/share1 has the noacl option set. In this case, you are ready to proceed with the installation.

nas.example.com:/export/share1 /u01/app/share1 nfs rw,bg,rsize=32768,wsize=32768,hard,nointr,tcp,noacl,vers=3,timeo=600 0 0

If you do not have the noacl option set, then contact your System Administrator to make the required changes in the /etc/fstab file.

If you are installing on an NFS-shared middleware location, and if that location is mounted with the option concurrent I/O (CIO), which allows multiple reads and writes to a file at the same time, then the installation will fail reporting linking errors.

If you verify the mounted file system, you will see the following CIO option enabled. If you have the CIO option enabled, then unmount the drive, disable the CIO option, and then re-mount the drive.

node mounted mounted over vfs date options

/dev/host1 /host1/oracle jfs2 Feb 14 18:20 rw,cio,log=/dev/xd891loglv

Middleware Home Path Requirements

Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

For example, the middleware home path C:\Oracle\MW\EM containing only 15 characters is acceptable. However, C:\OracleSoftware\OracleMiddleware\OracleEnterpriseManager\OMS\newrelease\oms containing more than 25 characters is not acceptable on Microsoft Windows platforms.

Agent Base Directory Path Requirements

(Only for Microsoft Windows) Ensure that the number of characters in the agent base directory path does not exceed 25 characters.

For example, the agent base directory path C:\Oracle\Agent\ containing only 16 characters is acceptable. However, C:\Oracle\ManagementAgent\12c\new containing more than 25 characters is not acceptable.

Unique Host Name and Static IP Address Requirements

Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network.

Note: Oracle recommends that you use static IP address. If you use dynamic IP address, and if the host is rebooted, then the host might receive a new IP, and as a result, the OMS startup will fail.

Temporary Directory Space Requirements

Ensure that you allocate 10 GB of hard disk space for the temporary directory.

Central Inventory Requirements

Ensure that you allocate 100 MB of space for the central inventory directory.

For a typical non-HA environment, the Central Inventory (oraInventory) can be in a shared or non-shared location. If you use a shared location, then ensure that only one shared location is maintained per host, and no two hosts update the same shared location. One inventory file is meant only for one host, so it must not be shared and edited by other hosts. When you use the /etc/oraInst.loc file, ensure that the inventory location specified there is not pointing to such a location. If you have configured a shared location that is common for two or more hosts, then switch over to a non-shared location.

For a typical HA environment with primary and standby disaster recovery sites using storage replication and alias host names, the Central Inventory (oraInventory) for software installed on the shared storage using the alias host name should be located in a shared location that is common between the OMS host in the primary site and the OMS host in the standby site. This shared location should be located on the replicated storage so that the oraInventory can be accessed from the active site for software maintenance activities.

UMASK Value Requirements

Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file.

Bourne or Korn Shell

CLASSPATH Environment Variable Requirements

Ensure that you unset the CLASSPATH environment variable. You can always reset the variable to the original value after the installation is complete.

File Descriptor Requirements

Ensure that the max user processes parameter and the open files parameter are set to 30000.

Ensure that you set the file descriptor limit to a minimum of 65536.

Ensure that the ip_local_port_range parameter is set between 11000 to 65000.

Host File Requirements

Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct host name or IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.

In some platforms, the installer does not validate the host name mentioned in the /etc/hosts file, therefore make sure the host names or IP addresses are correct.

Ensure that localhost is pingable and resolves to 127.0.0.1 (or resolves to ::1 for IPv6 hosts).

The following is the recommended format of the /etc/hosts file:

127.0.0.1 localhost.localdomain localhost

172.16.0.0 myhost.example.com myhost

Also, if DNS server is configured in your environment, then you should be able to use DNS to resolve the name of the host on which you want to install the OMS.

For example, all these commands must return the same output:

If alias host names are implemented in /etc/hosts, then it is not necessary to be able to use DNS to resolve the alias host name on which you want to install the OMS.

Installing User Requirements

Ensure that you meet the following requirements:

(For UNIX only) The installation must NOT be run by a root user.

(For Microsoft Windows only) User must be part of the ORA-DBA group and have administrator permissions.

(For Microsoft Windows only) User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process.

Ensure that you have write permission in the Middleware home and the Oracle Management Service Instance Base location.

Ensure that you have write permission in the location where you want to create the Central Inventory ( oraInventory ) if it does not already exist. If the Central Inventory already exists, then ensure that you have write permission in the inventory directory.

Ensure that the user who installed the existing Oracle Database has write permission in the data file locations where the data files for the new tablespaces will be copied.

These tablespaces and data files are created while configuring Enterprise Manager Cloud Control. While installing with simple configuration (Section 5.4), the installer automatically honors the default locations so you are not prompted for them. However, while installing with custom configuration (Section 5.5), the installer prompts you to validate or enter the locations explicitly.

Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.

To verify if a port is free, run the following command:

On Microsoft Windows:

Internet Connection Requirements

Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

These updates should be obtained before starting the 13c installation so they can be available to the installer at the proper time.

5.4 Installing an Enterprise Manager System for a Demonstration Site ( Simple Configuration)

To install Enterprise Manager Cloud Control for evaluation or demonstration purposes, use the Simple installation type. This installation type installs with default configuration settings and preferences that you need for a complete Enterprise Manager system. It does not offer too many options to customize your installation. For example, only the default plug-ins are deployed with the installation, and you are not provided with a separate screen to manually select the other plug-ins you want to deploy.

Therefore, this installation type is primarily meant for demonstration or evaluation purposes, and small deployments, and when you do not want to worry about the granular control of the installer and want to install the Enterprise Manager system quickly, with less memory, and for monitoring fewer targets in their environment.

To install Enterprise Manager Cloud Control for evaluation or demonstration purposes, follow these steps:

Oracle recommends you to run the EM Prerequisite Kit before invoking the installer to ensure that you meet all the repository requirements beforehand. Even if you do not run it manually, the installer anyway runs it in the background while installing the product. However, running it manually beforehand sets up your Management Repository even before you can start the installation or upgrade process. For information on the kit, to understand how to run it, and to know about the prerequisite checks it runs, see Appendix A.

However, if you plan to use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure you pass the following parameter while invoking the EM Prerequisite Kit.

Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 3.

For example, for Linux platform, run /u01/software/em/em13100_linux64.bin.

To invoke the installation wizard on UNIX platforms, run em13100_

.bin. To invoke on Microsoft Windows platforms, run setup_em_win64.exe.

The directory specified by this parameter will also be used as the location for the Provisioning Advisor Framework (PAF) staging directory, which is used for copying the Software Library entities related to the deployment procedures. The PAF staging directory is used only for provisioning activities — entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).

On the Software Updates screen, select Search for Updates, and then select one of the following options to apply the latest software updates:

Local Directory, if you do not have Internet connectivity on your host, and want to download the updates in offline mode and apply them while performing the installation.

My Oracle Support, if you have Internet connectivity on your host, and want to connect to My Oracle Support directly via the installer to download the updates in online mode and apply them while performing the installation.

During installation, you will be prompted for the details of a database where Oracle Management Repository can be configured. If you plan to provide the details of a database that already has an Oracle Management Repository preconfigured using the database templates offered by Oracle, then the software updates selected on this screen cannot be automatically applied. In such a case, you must manually download and apply these software updates after the installation.

If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).

If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:

On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.

Enter the full path to a directory where the inventory files and directories can be placed.

Ensure that you have read, write, and execute permissions on the default inventory directory. If you do not have the required permissions, then exit the installer, invoke the installer again with the INVENTORY_LOCATION parameter, and pass the absolute path to the alternative inventory location.

However, note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.

Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.

The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.

The status of the prerequisite check can be either Warning, Failed, Succeeded, Not Executed, In Progress, or Pending.

If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.

However, all package requirements must be met or fixed before proceeding any further. Otherwise, the installation might fail.

If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun. The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Chapter 2. To understand the logic the installation wizard uses to verify these packages, see Section 2.1.1.

On the Installation Details screen, do the following:

Enter the Middleware home where you want to install the OMS and other core components.

For example, /u01/software/em13c/oraclehome

The Enterprise Manager Cloud Control Installation Wizard installs Oracle WebLogic Server 12 c Release 1 (12.1.3.0) and JDK 1.7.0_80 by default in this middleware home directory you enter here. A preinstalled JDK or Oracle WebLogic Server is not supported from 13 c Release 1 onwards.

Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

By default, the OMS instance base directory (gc_inst) is created outside the middleware home, and at the same parent level as the middleware home. For example, if you enter u01/software/oracle/middleware as the middleware home, then the instance base directory is created as u01/software/oracle/gc_inst.

However, if you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. Modify the lock file location in the httpd.conf file to map to a location on a local file system. For instructions, refer to Section 5.7.

Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. For example, if the middleware home is /u01/software/em13c/oraclehome, then you can specify the agent base directory as /u01/software/em13c/agentbasedir.

Ensure that this location is empty and has write permission. Also ensure that it is always maintained outside the middleware home.

Ensure that the number of characters in the middleware home path does not exceed 70 characters for Unix platforms and 25 characters for Microsoft Windows platforms.

Validate the name of the host where you want to configure the OMS.

Accept the default host name, or enter a fully qualified domain name that is registered in the DNS and is accessible from other network hosts, or enter an alias host name that is defined in the /etc/hosts file on all the OMS instances at this site.

The host name must resolve to the local host or virtual host because the host name is used for the local Oracle WebLogic Server as well as the Oracle Management Service. Do not provide a remote host or a load balancer virtual host in this field. Do not enter an IP address. Do not use underscores in the name. Short names are allowed, but you will see a warning, so Oracle recommends that you enter a fully qualified domain name instead.

On the Configuration Details screen, do the following:

Enter an administrator password, which can be used as a common password for configuring the Enterprise Manager Cloud Control.

Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.

Table 5-4 describes what the administrator password is used for.

Table 5-4 Usage of Administrator Password

Requirement	Description

Creates SYSMAN User Account

The user account is used as the super administrator for configuring the SYSMAN schema in the Management Repository.

Creates Default WebLogic User Account weblogic

The user account is used as the administrator for creating the default WebLogic domain GCDomain.

Creates Default Node Manager User Account nodemanager

The user account is automatically created during the configuration of Enterprise Manager Cloud Control.

A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

Authenticates New Management Agents

The agent registration password is used for authenticating new Management Agents that join Enterprise Manager system, where the communication between the OMS and the Management Agent is secure.

Provide details of the existing, certified database where the Management Repository needs to be created. If you have already created a database instance with a preconfigured Management Repository using the database templates offered by Oracle, then provide details about that database instance.

The installer uses this information to connect to the existing database for creating the SYSMAN schema and plug-in schemas. If you provide details of a database that already has a preconfigured Management Repository, then the installer only creates plug-in schemas.

For information about creating a database instance with a preconfigured Management Repository using the database templates offered by Oracle, refer to Appendix C.

If you connect to a database instance that was created using the database template offered by Oracle, then the password assigned to user accounts SYSMAN, SYSMAN_MDS, SYSMAN_APM, and SYSMAN_OPSS, which were created while preconfiguring the Management Repository, are automatically reset with the administrator password you enter here on this screen. We also unlock all these user accounts.

To identify whether your database is a certified database listed in the certification matrix, follow the steps outlined in Appendix D.

If you are providing the details of a pluggable database (PDB), then use the full service name instead of the alias. For example, pdb.example.com. If you are providing the details of a lone-pluggable database (Lone-PDB), then use the full service name. For example, pdb.example.com. If you are providing the details of a non-container database (Non-CDB), then use the SID.

If you are providing the details of an Oracle RAC database that is configured with Single Client Access Name (SCAN), then enter the SCAN name as the host name.

For information on all the database initialization parameters that are set, and all the prerequisite checks that are run, and for instructions to run the prerequisite checks manually if they fail, see Appendix A.

If your Oracle RAC database 11.2 or higher is configured with Single Client Access Name (SCAN) listener, then you can enter a connection string using the SCAN listener.

If you are connecting to an Oracle Database that is configured with CDB or PDB, then make sure you open the PDB before you provide the PDB details on this screen.

If you see an error stating that the connection to the database failed with ORA-01017 invalid user name/password, then follow these steps to resolve the issue:

(1) Verify that SYS password provided is valid.

(2) Verify that the database initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to Shared or Exclusive.

(3) Verify that password file with the file name orapw exists in the /dbs directory of the database home. If it does not, create a password file using the ORAPWD command.

When you invoke the installer on Microsoft Windows, the Enterprise Manager Shared Location Details screen does not show the Config Volume and Cluster Volume options. This is an expected behavior.

On the Enterprise Manager Shared Location Details screen, do the following:

(Optional) Configure Oracle Software Library.

Oracle Software Library (Software Library) is a feature within Enterprise Manager Cloud Control that acts as a repository to store software entities such as software patches, virtual appliance images, reference gold images, application software, and their associated directive scripts. You require the Software Library for operations such as provisioning, patching, and so on.

Select Configure Oracle Software Library, and enter the absolute path leading up to a unique directory name. By default, the storage location that is configured is the OMS Shared File System location, so Oracle strongly recommends that the location you enter is a mounted location on the OMS host. This helps when you install additional OMS instances that can use the same mounted Software Library location.

Configuring the Software Library at the time of installation is optional. Even if you do not select this option and configure it now, your installation will succeed. You always have the option of configuring the Software Library later using the Initial Setup Console or the Software Library Administration Console (available within the Enterprise Manager Cloud Control Console). However, Oracle strongly recommends that you select this option and configure it at the time of installation so that the installer can automatically configure it for you. This saves time and effort, and enables you to install an additional OMS, immediately after the first OMS, and configure it to use the same Software Library location.

(Optional) Configure a shared location for Oracle BI Publisher that is installed and configured by default. The shared storage location will act as a common location for storing the report catalog and associated management information for the first OMS you are installing now and also for the additional OMS you plan to install in the future.

(i) Identify a shared location that you can use for Oracle BI Publisher.

If you do not have an existing shared location, create a new one and ensure that it is visible on the host where you are installing the first OMS and also on other hosts where you plan to install additional OMS instances.

At install time, for the installation to be successful, you can reserve approximately 400 MB of hard disk space for the shared directory. However, Oracle recommends that you scale it to at least 10 GB eventually, and ensure that it can be extended further in the future because the space utilization increases over a period of time as you install additional plug-ins and create more reports.

If you already have a shared location that you were using for the Software Library or for staging gold images in the previous release of Enterprise Manager, then you can choose to use the same location. However, ensure that the directories within the shared location are unique for Oracle BI Publisher, Software Library, and staged gold images. For example, if you already are using the shared location /u01/software/examplehost/shrd/ where the Software Library is configured in /u01/software/examplehost/shrd/SW, then you can use the same location, but make sure the directory within this shared location for Oracle BI Publisher is /u01/software/examplehost/shrd/BIP.

(ii) On this screen, select Configure a Shared Location for Oracle BI Publisher. Enter the following directory paths. Ensure that the user account that you are using to install the first OMS has read and write permission on these paths.

When you invoke the installer on Microsoft Windows, the Enterprise Manager Shared Location Details screen does not show the Config Volume and Cluster Volume options. This is an expected behavior.

For Config Volume, enter the path leading up to the /config directory on the shared storage location where Oracle BI Publisher repository and configuration files can be stored. For example, /ntwkshrd/bip/config

For Cluster Volume, enter the path leading up to the /cluster directory on the shared storage location where Oracle BI Publisher scheduler storage can be maintained for Oracle BI Publisher to operate in a high-availability environment. For example, /ntwkshrd/bip/cluster

Do not delete these directories after the installation. The directories are required for proper functioning of Oracle BI Publisher, and therefore are required during the installation and also after the installation.

(Optional) Enable or disable the installed and configured Oracle BI Publisher. Enabling Oracle BI Publisher starts the software and keeps it ready for use within the Enterprise Manager system. Disabling Oracle BI Publisher leaves the software as it is without starting it.

To enable Oracle BI Publisher, select Enable Oracle BI Publisher.

If you choose to disable Oracle BI Publisher during the installation, then you can enable it after the installation by running the following EM CTL command from the bin directory of the Oracle home.

The command only enables Oracle BI Publisher, but does not start it. To start it, run the following command from the bin directory of the Oracle home.

On the Review screen, review the details you provided for the selected installation type.

If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.

After you verify the details, if you are satisfied, click Install to begin the installation process.

On the Install Progress screen, view the overall progress (in percentage) of the installation and the status of each of the configuration assistants. Configuration assistants are run for configuring the installed components of Enterprise Manager Cloud Control.

If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and retry the configuration assistant.

If you accidently exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the Oracle home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.bat script.

If the runConfig.sh script fails, then clean up your environment and redo the installation.

If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.

On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.

For more information about this installation, refer to the following file in the Oracle home of the OMS:

If a Server Load Balancer (SLB) is configured in your environment, and the upload port is locked, then configure the SLB for JVMD Engines, and then secure the OMS.

If an SLB is configured in your environment, but the upload port is unlocked, then decide whether you want to route the JVMD traffic through the SLB. If you do, then configure the SLB for JVMD Engines, and then secure the OMS.

To secure the OMS, run the following command:

If you have run the installation wizard and let the installation wizard take corrective actions to correct the repository settings, and if you have exited the wizard without completing the installation process, then remember that the repository settings might not reset to their original values because you abruptly ended the installation. In this case, before invoking the installation wizard again, run the EM Prerequisite Kit to manually reset the values. To do so, run the following command and pass a response file that captures the details for the EM Prerequisite Kit:

./em13100_linux64.bin EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE=

The response file should contain the following:

5.5 Installing an Enterprise Manager System for a Production Site ( Advanced Configuration)

To install Enterprise Manager Cloud Control in a production environment, use the Advanced installation type. This installation type offers custom or advanced configuration options that enable you to customize your installation to suit your needs.

This installation type provides the following benefits:

Offers an option to select the deployment size (small, medium, or large) of your choice, and depending on the deployment size you select, configures with the required memory. The deployment size essentially indicates the number of targets you plan to monitor, the number of Management Agents you plan to have, and the number of concurrent user sessions you plan to have.

Allows you to use a database where the Management Repository is preconfigured using the database templates offered by Oracle.

Deploys the mandatory plug-ins such as Oracle Database plug-in, Oracle Fusion Middleware plug-in, Oracle Exadata plug-in, Oracle Cloud Framework plug-in, and Oracle System Infrastructure plug-in. In addition, enables you to select and deploy other optional plug-ins of your choice.

Allows you to change the name of the default user account weblogic for the WebLogic domain GCDomain.

Prompts for separate, distinct passwords for WebLogic Server administration, Node Manager, SYSMAN user account, and Management Agent registration.

Allows you to change the name of the default OMS instance base directory (gc_inst) to a name of your choice, and creates that directory outside the Middleware home.

Allows you to change the locations of the tablespaces for management, configuration data, and JVM diagnostics data.

Allows you to customize the ports according to your environment.

To install Enterprise Manager Cloud Control for a production site, follow these steps:

Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 3.

For example, for Linux platform, run /u1/software/em/em13100_linux64.bin.