Oracle by Example brandingSetting Up Oracle Enterprise Manager 13.4 on Oracle Cloud Infrastructure

section 0Before You Begin

This tutorial guides you through the required steps for creating a stack on Oracle Cloud Infrastructure Resource Manager and using it to deploy either Single or Multiple node Enterprise Manager setup. The time to complete this setup is approximately 20 minutes for Single node and approximately 3 hours for a Multi-Node deployment.

Overview

Oracle Enterprise Manager Cloud Control is a complete, integrated, business-driven management solution for traditional and cloud environments. It takes advantage of the built-in management capabilities of the Oracle stack and enables monitoring and management of your entire infrastructure from a single console. This allows for unprecedented efficiency gains and a dramatic increase in service levels.

This version of Oracle Enterprise Manager 13.4 on Oracle Cloud Infrastructure can be deployed on both Single and Multi-Node configurations allowing you to tailor Oracle Enterprise Manager to your specific infrastructure needs. Features include:

  • Ability to create and define your own OCI resources.
  • Credentials for Enterprise Manager and Databases can be configured at spin up time.
  • OMR is on the latest version of 19c Pluggable database that is also TDE (Transparent Data Encryption) enabled, ensuring safety on the Cloud.
  • Scalability: OMS Nodes and Bastion can be scaled to fit your needs by re-running the stack and selecting a new shape for both. This applies for both Single and Multi-Node deployments.
  • Enterprise Manager 13.4 on Cloud Infrastructure uses the latest OCI Linux image: OL 8.

What's Included in this version

Oracle Enterprise Manager Cloud Control offers the latest plug-ins and features, the full list of plug-ins and features available can be found in the following links:

What's Included with Stack 1.2

The latest version of the Stack offers the following new features:

  • Default access to the Weblogic Console
  • Oracle Data Guard

Licensing

Review licensing requirements and ensure you have the appropriate licenses for the environment you are going to manage.

License used Multi-Node deployments: Oracle Database Cloud Service Enterprise Edition - Extreme Performance, the Oracle Database license is included in this edition; if you already own a license for the included services you can also utilize said license. Resources such as Load Balancer, Block Volumes, Compute Hosts and NFS will be charged as infrastructure resources. Other EM packs functionalities (such as Diagnostics Pack features) are included as well but will need to be deployed or enabled by the end user.

License used Single node deployments: Oracle Database Cloud Service Enterprise Edition.

The Oracle Enterprise Manager licensing information is available in the Enterprise Manager Licensing Information User Manual. Database licensing information is available in the Oracle Management Packs and Their Permitted Features within Oracle Database Licensing Information User Manual.

For more information on pricing including Pay as you go, Universal Credits-Monthly Flex and Bring Your Own License options, see: Oracle Cloud Infrastructure Pricing.

Component Descriptions and Definitions

  • Oracle Cloud Infrastructure Resource Manager: Component that allows you orchestrate the resources needed to deploy Oracle Enterprise Manager Cloud Control. For more information see: Overview of Resource Manager.
  • Oracle Cloud Infrastructure Load Balancing Cloud: Load balancing service used to deploy EM in high availability mode, only available for Multi-Node deployments. For more information see: Overview of Load Balancing.
  • High Availability (HA) mode - Level 3: The Multi-Node setup that provides an EM single site with load balancing, OMS in Active/Active configuration and a RAC repository. Data Guard support needs to be enabled by the user, for more information see: Steps to Enable Data Guard.

section 1Perform Prerequisites

Before deploying Oracle Enterprise Manager, review the following information and perform all prerequisite tasks described below.

  1. Check OCI resources before you begin, the following is a list of supported and recommended VM shapes and recommended sizing information for the different EM Deployment sizes.
    EM Deployment Size Supported Compute Shapes (Management Server) Recommended Compute Shape (Management Server) Supported Compute Shapes (Database RAC Nodes) Recommended Compute Shape (Database RAC Nodes) Agent Count Target Count Concurrent User Sessions
    Simple (Single node setup) VM.Standard 2.2, 2.4, 2.8, 2.16, 2.24
    VM.DenseIO2.8, 2.16
    VM.Standard.E2.2, E2.4, E2.8    		 VM.Standard 2.4 N/A N/A <10 <100 <3
    Small (Multi-node) VM.Standard 2.2, 2.4, 2.8, 2.16, 2.24
    VM.DenseIO2.8, 2.16
    VM.Standard.E2.2, E2.4, E2.8    		 VM.Standard 2.4 VM.Standard 2.2, 2.4, 2.8, 2.16, 2.24 VM.Standard 2.4 <100 <1000 <10
    Medium (Multi-node) VM.Standard 2.4, 2.8, 2.16, 2.24
    VM.DenseIO2.8, 2.16, 2.24
    VM.Standard.E2.8    		 VM.Standard 2.8 VM.Standard 2.4, 2.8, 2.16, 2.24 VM.Standard 2.8 >=100,<1,000 >=1,000,<10,000 >=10,<25
    Large (Multi-node) VM.Standard 2.8, 2.16, 2.24
    VM.DenseIO2.16, 2.24
    BM.Standard2.52
    BM.Standard.E2.64
    BM.DenseIO2.52    		 VM.Standard 2.16 VM.Standard 2.8, 2.16, 2.24 VM.Standard 2.16 >=1,000 >=10,000 >=25,<50

    Example: If you wanted to manage a deployment of up to 100 targets, choose the Small deployment. The supported shapes for Small deployments are: VM.Standard 2.4, 2.8, 2.16, VM.DenseIO2.8, 2.16; VM.Standard.E2.2, E2.4, E2.8 and the recommended shape is: VM.Standard2.4.
    For additional resources on Enterprise Manager sizing information, see Enterprise Manager Cloud Control Sizing in Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

  2. Ensure that your Oracle Cloud Infrastructure account has the correct Service Limits for the shapes and block storage adequate for the Enterprise Manager sizing you wish to deploy. When you sign up for Oracle Cloud Infrastructure, a set of service limits are configured for your tenancy. The service limit is the quota or allowance set on a resource. For more information on Service Limits including: Viewing Your Service Limits, Quotas, and Usage; see: About Service Limits and Usage.
  3. Create Compute resources, the following is a comprehensive list of source requirements for Single node (Simple) and Multi-Node (Small, Medium & Large) configurations:
    OCI Resource Single Node (Simple)
    VCN 1 - for "Create new VCN" option
    For more information see DNS in Your Virtual Cloud Network.
    Compute 1 - for public subnet / 2 for private subnet
    OCI Resource Multi-Node (Small, Medium, Large)
    VCN 1 - for "Create new VCN" option
    For more information see DNS in Your Virtual Cloud Network.
    Compute 4 - for public subnet / 5 for private subnet
    Oracle Database VM.Standard2 OCPU Count : depends on the VM shape
    Example: Choosing a VM.Standard2.4 - would translate to 4 OCPUS (for Multi-node; as its 2-node RAC)
    Oracle Cloud Infrastructure Load Balancing service 1 for chosen shape
    Block Volume Storage 1 for each OMS node
    Shared File Storage (NFS) File System - 1 / Mount target - 1

    Note: If you have more than one VCN in your environment, choose a CIDR that does not overlap for peering purposes. Peering is not possible if VCN CIDR's match, for more information see: VCNs and Subnets.

  4. Oracle recommends the following storage disk space:
    • Single Node: 400GB boot volume storage.
    • Multi-Node (all sizes): 130GB Boot volume storage and 100GB block volume storage.
    • Database System Storage size:
      • Small: 256GB
      • Medium: 512GB
      • Large: 1024GB
    For more information, see Oracle Cloud Compute Services.

section 2Deploy Enterprise Manager in a Single Node Configuration

To deploy Oracle Enterprise Manager on a Single Node setup, follow these steps. Prerequisites are outlined in Step 1.

Single node setup is very similar to previous releases of Enterprise Manager on OCI Marketplace and supports Simple Enterprise Manager size deployments.

Recommended Setups for Single Node Deployments

Instance (Enterprise Manager & Database) placed in Public Subnet

Single Node: Instance (Enterprise Manager & Database) placed in Public subnet
Description of the illustration SingleNode.png

Instance (Enterprise Manager & Database) placed in Private Subnet

Single Node: Instance (Enterprise Manager & Database) placed in Private Subnet
Description of the illustration SingleNode1.png

Enterprise Manager on Single Node Deployment Steps

  1. Sign in to OCI and from the OCI Main Menu and navigate to Marketplace. Search and click on Oracle Enterprise Manager, for easier access you can filter by Type: Stack.
    2. Marketplace
    Description of the illustration marketplace.png
  2. Review the Oracle Enterprise Manager overview, select the compartment where the stack will be located. Checkmark the Oracle Standard Terms and Restrictions and click Launch Stack.
  3. In Edit Stack, under Stack Information enter the Name and Description for your stack (optional). The predetermined deployment name is: EnterpriseManager_Deploydate. Click Next.
  4. Specify the Deployment type Simple and Number of OMS Nodes (1). Enter the VCN Network details, the OMS details (passwords, shape, storage size), WebLogic password, and the Oracle Database System details (password, license, shape, storage).

    Note: When re-running the stack, fields marked with an asterisk (*) are user modifiable. When re-running the stack, you should not change fields without an asterisk as this will generate problems during stack deployment.

    Click Next to review and save the Stack.

    Edit Stack, Configure Variables
    Description of the illustration Edit-Stack-1.png
  5. Review the configuration variables entered, click on Save Changes to finalize editing the stack and initiate stack deployment automatically.
    Review Stack Configuration Value Changes
    Description of the illustration review-stack.png

    At this moment, the stack starts the deployment and the following steps happen in the background:

    1. Create the VCN (optional, if VCN option is chosen)
    2. Configure the security lists, network security groups, gateways and routing tables
    3. Create the OMS host
    4. Create the Bastion host (optional, required only for private subnets)
    5. Deploy and configure Enterprise Manager


    NOTE: If you are re-running the stack, navigate to Terraform Actions and click on Apply to begin stack re-deployment.

  6. In the Apply screen the name, plan resolution and tags fields are visible. You can change the job name and apply any Tags needed. Click Apply to create the OCI Resources and deploy Enterprise Manager.
  7. In the Resources section under Jobs you can track the Stack creation process. These processes will show under the Type column as Apply.
    Stack creation can be viewed by selecting the specific apply job
    Description of the illustration jobs.png
    To view the Log file at any point, navigate to Resource manager -> Click on a stack -> Choose job type: Apply -> Click on Logs.
    Viewing the Logs Option
    Description of the illustration Logs-Option-5.png
  8. The Apply job takes 20 minutes for Single node. On successful completion of the job, access to Enterprise Manager can be viewed at the Application Information tab.
    Apply Job will deploy EM with Stacks taking from 15 minutes to 3 hours depending on environment complexity
    Description of the illustration Apply-job-6.png

Port List and Single Node Post Deployment Steps

  1. Review and make a note of the following ports that Enterprise Manager on OCI will use:
    Component Service Source Port Range Destination Port for Single Node Description
    Bastion SSH "0.0.0.0/0" TCP/22 Bastion is only created if EMDB subnet is a private subnet.
    Enterprise Manager SSH Public subnet: "0.0.0.0/0"
    Private subnet: Bastion & EMDB subnet CIDR    		 TCP/22 ssh [-i private_key] -L localhost:7799:OMS_private_ip:7799 opc@bastion_public_ip
    Enterprise Manager Console Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/7799
    Enterprise Manager WebLogic Console Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/7101
    Enterprise Manager Admin Server EMDB subnet CIDR TCP/7101
    Enterprise Manager Node Manager EMDB subnet CIDR TCP/7401
    Enterprise Manager Managed Server / Java Virtual Machine Diagnostics (JVMD) Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/7301
    Enterprise Manager Agent Upload Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/4900
    Enterprise Manager Agent Listen (OMS & Database Nodes) EMDB subnet CIDR TCP/3872
    BI Publisher (BIP) BIP Console Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/9899
    Database DB Listener EMDB subnet CIDR TCP/1521 For both private and public
    Database DB Nodes Public subnet: "0.0.0.0/0"
    Private subnet: VCN CIDR    		 TCP/22
  2. A boot volume backup must be taken immediately after deployment and at regular daily or weekly intervals, this is where Simple Enterprise Manager and Database (OMR) deployments are done. For more information see: Overview of Boot Volume Backups.

Note: If a private subnet is used for Enterprise Manager, access to the console URL will be using a tunnel running on the bastion host.

section 3Deploy Enterprise Manager in a Multi-Node Configuration

To deploy Oracle Enterprise Manager on a Multi Node setup, follow these steps. Prerequisites are outlined in Step 1.

Multi-Node deployments can be setup with Small, Medium or Large Enterprise Manager deployments on a new or existing VCN.

Recommended Setups for Multi-Node Deployments

Multi-node deployments can be set up for High Availability; the following configurations are required within the network topology to achieve this:

  • Oracle Cloud Infrastructure Load Balancing service: The Load Balancer nodes will be on different Availability-Domains for High Availability.
  • Oracle Management Service: Choose different Availability-Domains for each OMS node if you require High Availability.
  • OMR: The OCI Database System provides an option to have nodes on different Fault domains but will be on the same Availability-Domains.

  • Oracle Cloud Infrastructure Load Balancing service can be placed either in public or private subnet.
  • The bastion host (subnet-3) is required and always deployed since both Enterprise Manager and Database are deployed in a private subnet.

The following diagrams capture High Availability deployments in Level-3 mode of Enterprise Manager. All OMS and OMR Database nodes are active in this configuration:

Enterprise Manager and Database in Private subnet; Oracle Cloud Infrastructure Load Balancing service in Public subnet

Multi-Node: EM & DB in Private subnet and Load Balancer in public subnet
Description of the illustration MN4.png

Enterprise Manager Database and Oracle Cloud Infrastructure Load Balancing service in Private subnet

Multi-Node: EM,DB and Load Balancer in private Subnet.
Description of the illustration MN5.png

Enterprise Manager on Multi-Node Deployment Steps

  1. Sign in to OCI and from the OCI Main Menu and navigate to Marketplace. Search and click on Oracle Enterprise Manager, for easier access you can filter by Type: Stack.
    2. Marketplace
    Description of the illustration marketplace.png
  2. Review the Oracle Enterprise Manager overview, select the compartment where the stack will be located. Checkmark the Oracle Standard Terms and Restrictions and click Launch Stack.
  3. In Edit Stack, under Stack Information enter the Name and Description for your stack (optional). The predetermined deployment name is: EnterpriseManager_Deploydate. Click Next.
  4. Specify the deployment type: Multi-node, EM Deployment Size: Small, Medium, Large and Number of OMS Nodes (2). Enter the VCN Network details for the configuration, OMS details (passwords, shape, storage size), the Oracle Database System details (password, license, shape, storage), and WebLogic password.

    Note:

    • Fields marked with an asterisk (*) are user modifiable. You should not change fields without an asterisk as this will generate problems during stack deployment. These fields are meant to be interpreted as informative.
    • If you are re-running the stack, in this step enter your current WebLogic password. Do not enter a new password at this screen. See Enterprise Manager Deployment File Locations for Wallet file location.
    • If your deployment requires Data Guard enabled, see: Steps to Enable Data Guard.

    Click Next to review and save the Stack.

    Edit Stack, Configure Variables
    Description of the illustration Edit-Stack-3.png
  5. Review the configuration variables entered, click on Save Changes to finalize editing the stack and initiate stack deployment automatically.
    Review Stack Configuration Value Changes
    Description of the illustration review-stack-1.png

    At this moment, the stack starts the deployment and the following steps happen in the background:

    1. Create then VCN (optional, if VCN option is chosen)
    2. Configure the security lists, network security groups, gateways and routing tables
    3. Create the load balancer
    4. Create the OMS and bastion hosts
    5. Create the RAC database for the Oracle Management Repository (OMR)
    6. Deploy and configure Enterprise Manager

    NOTE: If you are re-running the stack, navigate to Terraform Actions and click on Apply to begin stack re-deployment.

  6. In the Apply screen the name, plan resolution and tags fields are visible. You can change the job name and apply any Tags needed. Click Apply to create the OCI Resources and deploy Enterprise Manager.
  7. In the Resources section under Jobs you can track the Stack creation process. These processes will have the Apply tag.
    Stack creation can be viewed by selecting the specific apply job
    Description of the illustration jobs.png
    To view the Log file at any point, navigate to Resource manager -> Click on a stack -> Choose job type: Apply -> Click on Logs.
    Viewing the Logs Option
    Description of the illustration Logs-Option-5.png
  8. The Apply job takes up to 3 hours for Multi-node. On successful completion of the job, access to Enterprise Manager can be viewed at the Application Information tab.
    Apply Job will deploy Enterprise Manager with Stacks taking from 15 minutes to 3 hours depending on environment complexity
    Description of the illustration Apply-job-6-1.png

Port List and Multi-Node Post Deployment Steps

  1. Review and make a note of the following ports that Enterprise Manager on OCI will use:
    Component Service Source Port Range Destination Port for Multi-node Description
    Bastion SSH "0.0.0.0/0" TCP/22 Connecting to EM Console via Bastion SSH tunnel (Not needed if Load Balancer is public):
    ssh [-i private_key] -L localhost:5443:LBaaS_Private_IP:443 opc@bastion_public_ip
    Connecting to OMS/DB nodes:
    ssh -i private_key opc@oms/db privateip -o "proxycommand ssh -W %h:%p -i private_key opc@bastionhost"
    Load Balancer Console Public Load Balancer: "0.0.0.0/0"
    Private Load Balancer: VCN CIDR    		 TCP/443
    Load Balancer WebLogic Console Public Load Balancer: "0.0.0.0/0"
    Private Load Balancer: VCN CIDR    		 TCP/7101
    Load Balancer Agent Upload Public Load Balancer: "0.0.0.0/0"
    Private Load Balancer: VCN CIDR    		 TCP/4900
    Load Balancer Java Virtual Machine Diagnostics (JVMD) Public Load Balancer: "0.0.0.0/0"
    Private Load Balancer: VCN CIDR    		 TCP/7301
    Load Balancer BI Publisher(BIP) Public Load Balancer: "0.0.0.0/0"
    Private Load Balancer: VCN CIDR    		 TCP/5443
    Enterprise Manager SSH Bastion & EMDB subnet CIDR TCP/22
    Enterprise Manager Console VCN CIDR TCP/7799 EMCLI will also be routed via Load Balancer.
    Enterprise Manager Admin Server EMDB subnet CIDR TCP/7101
    Enterprise Manager Node Manager EMDB subnet CIDR TCP/7401
    Enterprise Manager Managed Server / JVMD Load Balancer and EMDB subnet CIDR TCP/7301
    Enterprise Manager Agent Upload VCN CIDR TCP/4900
    Enterprise Manager Agent Listen (OMS and Database Nodes) EMDB subnet CIDR TCP/3872
    Database DB Listener EMDB subnet CIDR TCP/1521
    Database DB Nodes Bastion and EMDB subnet CIDR TCP/22
    Database DB Nodes (ONS/FanManager) EMDB subnet CIDR TCP/6200
    NFS NFS Service EMDB subnet CIDR UDP/111
    UDP/2048
    TCP/111
    TCP/2048-2050
  2. A Backup must be taken immediately after installation and at regular daily or weekly intervals. Enterprise Manager deployments are done on a block volume, and OMR is deployed on an OCI Database. For more information and detailed instructions see: Overview of Block Volume Backups and Backing Up a Database.
    Shared storage for the software library and BI Publisher are handled via NFS, this allows for storage that is inherently redundant with resilient data protection from OCI and can be excluded from the backups.

Note:

  • If the SSH keys for logging into the bastion, OMS or Database system needs to be rotated, DO NOT overwrite other public keys in the authorized_keys file that is used by stack. If these keys are flashed these keys OMR will lose access, only rotate public keys owned by end user.
  • If a private subnet is used for Load balancers, access to the console URL will be using a tunnel running on the bastion host.
  • The CIDR of the new regional private subnet to create the Enterprise Manager and Database instances should not overlap with 192.168.16.16/28. Also, the netmask should be at least 28 or larger. Example: 10.0.1.0/28. For more information see: Network Setup for DB Systems.

Steps to Enable Data Guard

This is an optional step available from stack 1.2 onward for Multi-Node deployments that require Data Guard or if a High Availability deployment is being configured. Only enable Data Guard from the stack setup when deploying Oracle Enterprise Manager 13.4 on Oracle Cloud Infrastructure to avoid configuration errors. To enable, follow these steps:

  1. During step two of the stack configuration, Configure Variables, at the end of the Repository Database System Details section, select the Enable Data Guard for Management Repository checkbox.

    NOTE: The Data Guard checkbox and all Data Guard fields marked with * are user editable and can be edited after deployment by re-running the stack with the new parameters.

  2. Once the Data Guard Configuration fields have activated enter the following information into its respective field:
    • Data Guard DB System Name: The name of the Data Guard Database system.
    • Select an Availability Domain for the Data Guard: The availability domain for the Data Guard database nodes, we recommended you choose a different availability domain than the primary database system.
    • Data Guard DB System Instance Shape: The shape for the two DB system instances for Data Guard. For more information see Perform Prerequisites for a complete table listing of supported shapes by deployment size.
    • Data Guard Database Hostname Prefix: The Database Hostname Prefix.
  3. After you have set the Data Guard settings, save and apply the stack. For more information see steps 5 through 7 in Enterprise Manager on Multi-Node Deployment Steps.
  4. We recommend once Data Guard is set up, you log into Enterprise Manager and verify that both Databases appear Up and properly labelled as Primary and Data Guard.

NOTE: During a Switchover or Failover, Enterprise Manager availability will see a less than 5-minute service interruption while the switching from primary to Data Guard occurs. For more information using Data Guard, including To perform a database switchover and To perform a database failover see: Using Oracle Data Guard.

section 4Troubleshoot Oracle Enterprise Manager Deployment

Troubleshoot OCI Resource Issues

  • Errors will be written in the log file and can be located within the Oracle Resource Manager and can be accessed by navigating to Resources and click on Logs.

    For further information on viewing and accessing logs, see To view the log job in Managing Stacks and Jobs under Using the Console.

  • If you experience Resource Availability error, verify that your Service Limits are set correctly. For more information on Service Limits including: Viewing Your Service Limits, Quotas, and Usage; see: About Service Limits and Usage.
  • OMS Node and Host:
    Error: Service error:LimitExceeded. The following service limits were exceeded: shape-count
    Check the limits for Compute service in the specific compartment and availability domain. Description: Chosen load balancer bandwidth.
  • Load Balancer:
    Error: Service error:LimitExceeded. The limit for this tenancy has been exceeded
    Check the limits for the Load Balancer service in the specific compartment and region. Description: Chosen compute shape.
  • File Storage or Mount Target:
    Error: Service error:LimitExceeded. The mount target limit for this availability domain has been exceeded
    Check the limits for File Storage service in the specific compartment and availability domain. Description: Mount Target Count.
  • Database System:
    Error: Service error:LimitExceeded. You have reached your service limit of XX Virtual Machine CPU Cores in this Availability Domain.
    Check the limits for the Database service in the specific compartment and availability domain. Description: VM.Standard2 OCPU Count.
  • Terraform Actions:
    Error: Unsupported Terraform Core version when performing actions like Plan, Apply, Import State and Destroy on a stack created using Oracle Enterprise Manager 13.4-BP1-1.0, see MOS note 2672961.1.

Troubleshoot Enterprise Manager Issues

  • In some cases, the configuration between the RAC DB node YUM with the corresponding regional YUM repository may not happen, this will impact the functionality of the YUM tool. For more information on troubleshooting the YUM tool see: Known Issues YUM. We have not seen this happen on OMR Node YUM deployments.
  • If you notice that your Pluggable Databases appear as down, or the Database charts are not displayed in the home page. Delete and re-discover the cluster database target and this will automatically clean up and re-discover the related targets, see Discovering and Adding Database Targets.

Enterprise Manager Deployment File Locations

  • OMS: /u01/app/oracle/em/middleware_134 and /u01/app/oracle/em/gc_inst_134
  • EM Agent: /u01/app/oracle/em/emagent
  • Database Simple (Single Node): /u01/app/oracle/database/product
  • Database Multi-Node (Small, Medium, Large): See Bare Metal and Virtual Machine DB Systems.
  • Wallet file location for Simple (Single Node): /u01/app/oracle/database/admin/emrep/wallet/tde
  • Wallet file location for Multi-Node (Small, Medium, Large): On the Database Node, /opt/oracle/dcs/commonstore/wallets/tde/<db_unique_name>
  • Diagnostics Kit path locations for Multi-Node:
    OMSVFY: /u01/app/oracle/em/middleware_134/emdiag
    REPVFY: /u01/app/oracle/em/middleware_134/emdiag_rep
    AGTVFY: /u01/app/oracle/em/emagent/emdiag
  • WebLogic and Node Manager password location within Primary OMS node: /home/oracle/.em_wls_password

Enterprise Manager Home Directories for Single Node Configurations

  • Oracle Management Service: /u01/app/oracle/em/middleware_134
  • Agent: /u01/app/oracle/em/emagent/agent_13.4.0.0.0
  • Database: /u01/app/oracle/database/product

Enterprise Manager Home Directories for Multi-Node Configurations

  • Oracle management service: /u01/app/oracle/em/middleware_134
  • Agent: /u01/app/oracle/em/emagent/agent_13.4.0.0.0
  • Database monitoring agent (Database node/management repository): /u01/emagent/agent_13.4.0.0.0

Enterprise Manager Multi-Node Configuration Backups are found in the following locations:

  • OMS Nodes 1 and 2:
    /u01/app/oracle/em/gc_inst_134/em/EMGC_OMS1/sysman/backup
    /u01/app/oracle/em/gc_inst_134/em/EMGC_OMS2/sysman/backup
  • Shared Location (redundant backup):
    /u01/app/oracle/em_shared_fs/oms_config

section 5Use Oracle Enterprise Manager

Oracle Enterprise Manager can be used to monitor and manage on-premises or cloud resources like database systems or Fusion Middleware targets. Monitoring can be done using local Cloud Control Agents.

For details on getting started with monitoring various targets, review the following resources:

  • To deploy agents on your hosts, add the following entry in the /etc/hosts file of the host or VM instance where the target is running: 
     $ oms1 <private IP address of the EM VM>
    $ oms2 <private IP address of the EM VM>
    To proceed with installing local Cloud Control Agents, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.
  • To discover targets, see Discovery.
  • To setup monitoring see Monitoring and Managing Targets.
  • To setup Oracle Cloud Infrastructure Email Delivery Service with SMTP see Configure SMTP Connection.
  • To enable Hybrid Cloud, navigate to Setup->Extensibility->Plug-ins and enable the following plug-ins:
    • Oracle Virtualization (oracle.sysman.vt)
    • Cloud Services Management (oracle.sysman.csm)
    • Oracle Cloud Application (oracle.sysman.ssa)
    You can access the Hybrid Cloud section located under Setup. To learn more about Hybrid Cloud, including setup and discovering targets, see Hybrid Cloud Management in Oracle Enterprise Manager Cloud Control Administrator's Guide.

more informationWant to Learn More?