type
status
date
slug
summary
tags
category
icon
password
URL
下载EMCC软件安装的产品系统条件端口安装修改系统参数创建OEM安装目录数据库准备(OMR)开始安装EMCC(Enterprise Manager Cloud Control)修改/etc/oratab文件EMCC地址设置开机启动
下载EMCC软件
https://www.oracle.com/enterprise-manager/downloads/cloud-control-downloads.html
https://www.oracle.com/enterprise-manager/downloads/linux-x86-64-13c-rel5-downloads.html

Directions
- Download all the files including .bin in same directory.No need to unzip the downloaded software.
- As the install user who will be installing the product, set the execute permission for the .bin file. Example: chmod +x em13500_linux64.bin
- Installation guides and general Enterprise Manager documentation can be found here
安装的产品
As part of a new Enterprise Manager system, the installation wizard does the following:
- Installs Oracle WebLogic Server 12c Release 2 (12.2.1.4.0).
- Installs Java Development Kit (JDK) 1.8.0_261.
- Installs Oracle Management Service 13c Release 5.
- Installs Oracle Management Agent 13c Release 5 in the agent base directory you specify (outside the middleware home).
- Installs Oracle JRF 12c Release 2 (12.2.1.4.0).
- Installs Oracle Web Tier 12c Release 2 (12.2.1.4.0).
- Creates a plug-in directory and installs the following default plug-ins.
- Oracle Database Plug-in
- Oracle Fusion Middleware Plug-in
Note:
Starting with 13c 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 Installing JVM Diagnostic Agents.
- Oracle Exadata Plug-in
- Oracle Cloud Framework Plug-in
- Oracle System Infrastructure Plug-in
- Any other additional plug-ins you choose to deploy
- Creates an Oracle WebLogic domain called GCDomain. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. In advanced installation, you can choose to change this if you want.
- Creates a Node Manager user account called nodemanager. 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.
Note:
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.
For example, if the Middleware home is /u01/software/em13c/oraclehome, then the instance base location is /u01/software/em13c/gc_inst. You can choose to change this, if you want, in the installer. However, you can change it for only advanced installation and not for simple installation.
- 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.
兼容性:
Oracle Management Service 13c Release 5 can communicate only with the following Oracle Management Agents versions you may have deployed from earlier Enterprise Manager Cloud Control versions: 13.4.0.0.0 and 13.3.0.0.0.
Table 5-2 Compatibility Between OMS and Management Agents Across 13c and 12c Releases
- | Oracle Management Agent 12c Release 5 (12.1.0.5) | Oracle Management Agent 13c Release 1 | Oracle Management Agent 13c Release 2 | Oracle Management Agent 13c Release 3 | Oracle Management Agent 13c Release 4 |
Oracle Management Service 13c Release 5 | no | no | no | no | no |
系统条件
端口
- Enterprise Manager Cloud Control
Table 2-2 Default Port for Enterprise Manager Grid Control
- | Upload Port | Console Port |
HTTP Port | The first available free port from the range 4889 to 4898 is selected. | The first available free port from the range 7788 - 7798 is selected. |
HTTPS Port | 1159If 1159 is not available, then the first available free port from the range 4899 to 4908 is selected. | The first available free port from the range 7799 - 7809 is selected. |
- Oracle Management Agent
The default upload port for Management Agent is 3872. The same port is used for both HTTP and HTTPS. If 3872 is not available, then the first available free port from the range 1830 to 1849 is selected.
- Administration Server
The default HTTPS port for Admin Server is 7101. If 7101 is not available, then the first available free port from the range 7101 to 7200 is selected.
- Node Manager
The default HTTPS port is the first available free port from the range 7401 to 7500 is selected.
- Managed Server
The default HTTP port is the first available free port from the range 7201 to 7300 is selected.
The default HTTPS port is the first available free port from the range 7301 to 7400 is selected.
- JVM Diagnostics Managed Server
If SLB is not configured, then the aforementioned HTTP and HTTPS upload ports of Enterprise Manager Cloud Control are used. If SLB is configured, then the ports configured for JVM Diagnostics on the SLB are used. Alternatively, in addition to the SLB configuration, if the HTTP upload port is enabled for Enterprise Manager Cloud Control, then the HTTP upload port also can be used by the JVM Diagnostics Agents for communicating with the JVM Diagnostics Engine.
- Oracle HTTP Server
The default HTTP port for Oracle HTTP Server is 9788. If 9788 is not available, then the first available free port from the range 9751 to 9800 is selected.
The default HTTPS port for Oracle HTTP Server is 9899. If 9899 is not available, then the first available free port from the range 9851 to 9900 is selected.
- Java Object Cache (JOC)
The default JOC port is 23456. If 23456 is not available, no alternate port is used, so ensure that port 23456 is free.
安装
修改系统参数
https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/embsc/package-kernel-parameter-and-library-requirements-enterprise-manager-cloud-control.html#GUID-7C29D5C1-5331-45D4-AAC4-87FA2D3C04A0
- 避免端口被占用,修改最小端口到11000。
修改/etc/sysctl.conf 文件,修改如下内容
修改nproc Kernel Parameter
- 修改kernel.shmmax内核参数
https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/embsc/package-kernel-parameter-and-library-requirements-enterprise-manager-cloud-control.html#GUID-A1AEBDCD-4211-4A2A-9DBA-710C9B7FA522
如果OMS(Oracle Management Server)和OMR(Management Repository)在不同的主机上,那么OMS的主机kernel.shmmax参数设置为小于4G或者4294967295。直接修改/etc/sysctl.conf文件修改,然后运行sysctl -p生效即可。
如果OMS和Management Repository(database)在同一个主机上,那么kernel.shmmax参数以Oracle数据库文档要求的为准。 这里我们将OMS和OMR都放在一台机器上。
- 修改参数禁用Address Space Layout Randomization (ASLR)
kernel.randomize_va_space=0
kernel.exec-shield=0
sysctl -p
创建OEM安装目录
注意:请确保/u01目录的剩余空间足以安装EMCC。EMCC 13.3软件安装完成后,大约需要26G的空间;而agent大约需要2G的空间。
在安装过程中,/tmp目录至少需要12G的空间,或者至少有一个目录的空闲空间有12G,需要存放临时解压文件,安装完成后会释放该空间
数据库准备(OMR)
OMR:Oracle Management Repository
OEM 13c只支持从版本12.1.0.2.0开始的OMR数据库,这里使用19c的数据库。
注意:不能安装EM,即DC。
EMCC 13.3可以监控11g的数据库,例如11g的rac
开始安装EMCC(Enterprise Manager Cloud Control)















修改/etc/oratab文件
修改/etc/oratab文件,加入内容:
EMCC地址
http://ip:37803/em
OMS启动日志:
/u01/app/oracle/middleware/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log, emoms.trc, emoms_pbs.trc
OMS启动和关闭:
emctl start oms
emctl stop oms
设置开机启动
- 作者:NotionNext
- 链接:https://tangly1024.com/5829e76b1d8b4bcfb22091d5b9ff72ef
- 声明:本文采用 CC BY-NC-SA 4.0 许可协议,转载请注明出处。