My name is Tammy Bednar from Oracle. This lesson is called monitoring a database on Bare Metal and virtual machine DB systems. In this lesson, we will learn about OCI metric charts using Enterprise Manager to monitor your DB systems and the benefits of using Enterprise Manager. The OCI metrics feature relays metric data about the health, capacity, and performance of your Cloud resources. Resources, services, and applications emit metrics to the monitoring service. Common metrics reflect data related to availability and latency, application of time and downtime, completed transactions, and failed and successful operations. Key performance indicators or KPIs, such as sales and engagement qualifiers, by query monitoring for these data and you can understand how well the systems and processes are working to achieve the service levels you've committed to your customers. Enterprise Manager provides a comprehensive monitoring and management solution for Oracle database and engineered systems deployed in the Cloud and customer data centers. You can run Enterprise Manager on-premises and in Oracle Cloud infrastructure. Enterprise Manager automates database lifecycle management from discovery, provision and cloning, patching, configuration, compliance management, and ongoing change management. Benefits of using enterprise Manager; it provides fleet monitoring management and data movement across your entire IT state, whether that be on-premises or in the Cloud. Enterprise Manager add Ops automation by providing high grade DB as a service to add self-service deployment and databases across on-premises in OCI. It uses open standards-based extensions for interoperability with third party ecosystem like Grafana. Enterprise Manager can simplify data movement from on-premises to OCI with DB Migration Workbench. As a CBA, you need tools to monitor and manage the database after watching the DB system and creating a database. Over the next few minutes, let's take a look at how to set up Enterprise Manager database control console to monitor database versions 11.2.0.4 and greater, and we're going to take a look at Enterprise Manager 13C and above to monitor 11.2.0.4 and above databases. You can use the console to perform basic administrative tasks such as managing user security, memory and storage, and to give performance information. Let's review how to set up Enterprise Manager database control console to monitor 11.2.0.4 databases and above. By default, the Enterprise Manager database control console is not enabled on 11.2.0.4 databases. You can enable the console when you create a database by the following steps: One, SSH to the database system, log-in as opc and sudo to the Oracle user. Port 1158 is the default port used for the first console enabled on a DB system, but each additional console enabled on a DB system will have a different port. You're going to open a console's port and then update the security list for the console's port. Over the next few minutes, let's take a look at how you can achieve that. After you've enabled the console and open this port in a security list, you can connect to the EM database control console as shown in the slide. The following ports will need to be open on a DB system. You'll need port 6200 for the Oracle Notification Service or ONS, and 1158 for Enterprise Manager database control. 1158 is the default port but each additional console enabled on a DB system will have a different port number. To open the port on a DB system, you will SSH to the DB system, login as opc and then sudo to the root user. You want to save a copy of the iptables as backup. Dynamically add a rule to iptables to allow inbound traffic on the console port, then you save the iptables file. The change will take effect immediately, and then you're going to update the DB system security list. You will want to review the list of ports for every port you open in iptables. You want to update the security lists used for the DB system or creating new security list. Note that port 1521 for the Oracle default listener is included in iptables, which will also be added to the security list. To update an existing security list, you will open the navigation menu. Under Database, click Bare Metal, VM, and Exadata. Chose your compartment and you will see a list of DB systems. Locate the DB system in the list. You're going to note the DB system subnet name and click its VCN network. Locate the subnet in the list, and then click under Resources Security List. Then you're going to click on "Edit All Rules" and add-in ingress rule. Now let's review how to deploy Enterprise Manager 13C. Oracle Enterprise Manager 13.4 on Oracle Cloud infrastructure can be deployed in both single and multi-node configurations allowing you to tailor Oracle Enterprise Manager to your specific infrastructure needs. This version of Enterprise Manager on Cloud infrastructure uses the latest OCI Linux image OL8. It provides the ability to create and define your own OCI resources. OMR is on the latest version of 19c pluggable database that is also TDE or transparent data encryption enabled. This is ensuring safety on the Cloud. To deploy Enterprise Manager 13.4 for a single node, you will need to review and perform all prerequisite tasks such as shape recommendation to support number of targets, OCI service limits to support this shape, and network requirements. You will log into OCI Marketplace in search for Enterprise Manager. Specify the deployment type of simple and the number of OMS nodes to one, into the VCN network details, the OMS details, WebLogic password, and the Oracle database system detail. When you click on ''Save Changes'', it'll finalize the editing in the stack and initiate the stack deployment automatically. This chart lists the required ports to be open in order to use Enterprise Manager effectively. You should refer to the documentation to confirm the ports when you provision Enterprise Manager and how to open the ports on your DB system. We want to use multi-nodes deployments to implement a high availability strategy for Enterprise Manager. In the multi-node configuration, you will also add the following services: Oracle Cloud Infrastructure load balancing service. The load balancing nodes will be on a different availability domains for high availability. Oracle managed service, you will choose a different availability domains for each LMS node if you require high availability, and the OMR. The OCI database system provides an option to have nodes on different fault domains, but will be on the same availability domains. A bastion host is required and always deployed since both Enterprise Manager and databases are deployed in a private subnet. To deploy Enterprise Manager 13.4 in a multi-node configuration, you will review and perform all prerequisite tasks such as shape recommendation to support another targets, OCI service limits to support shape, and network requirements. Login to OCI Marketplace and search for Enterprise Manager, and you can filter by type stack. Specify the deployment type to multi-node. You'll specify EM deployment size of either small, medium, large, and the number of OMS nodes to two into the VCN network details, the OMS details, where logic password and the Oracle database system details. Click on ''Save Changes'' to finalize editing the stack and this will initiate stack deployment automatically. This chart lists the required ports to be opened in order to use Enterprise Manager multi-node configuration effectively. You should refer to the documentation to confirm the ports when you provision Enterprise Manager and how to open the ports on your DB system. After listening to this lesson, you should have learned about OCI metric charts, using Enterprise Manager to monitor your DB systems, and the benefits of using Enterprise Manager.
