Written by Syed Jaffar Hussain Summary Managing, monitoring and maintaining Oracle Exadata Database Machine full stack is not an easy task, it demands a high level of technical skills and comprehensive knowledge of various layers of Exadata, such as, Networking, Database, RAC, Storage Cell, switches etc. Oracle Enterprise Manager (OEM) Cloud Control 13c delivers an easy Management, monitoring and maintenance capabilities for Exadata Database Machine and all its components. The purpose of this paper is to summarize the procedures to achieve the following actions: Creating an OEM repository database Installation and Configuration of OEM Cloud Control 13c Deploying OEM Agent software to the source (compute nodes) Exadata Database Machine discovery Discovering additional sources, such as, Grid Infrastructure, Listeners, Databases Creating OEM repository database with DBCA Prior to installing and configuring OEM Cloud Control 13c, as a best practice, it is recommended to setup a repository database beforehand. This is best accomplished using a predefined database template. It is available as a complimentary resource labeled “Database Template (with EM 13.1.0.0 repository pre-configured) for Installing Oracle Enterprise Manager Cloud Control 13c Release 1 (13.1.0.0)”. OEM then uses this repository database to store all its EM related data. Although the database can be created during EM installation, it is, however, best advised to create a database in advance using the EM database template, which can be downloaded from the Oracle site. Download DB template To download the database template, go to Oracle site, choose Oracle Enterprise Manager Downloads and click on Download DB Templates , as shown below: After downloading the zip file, unzip the file under $ORACLE_HOME/assistants/dbca/templates location on the source where you want you have the database. The source can be the host where you want to have your OEM configured or it can be a separate host. Create DB with preconfigured database template To create a repository database, use the easy and the most popularly used tool, DBCA. Use the EM13 template that fits into your business requirements as part of Database Template . Select the right sized database template as per the need: Large deployments, Medium deployments, Small deployments , as shown below: You can input any Database name as per your standard naming convention. Go ahead and complete the rest of the DB creation process, which is typically same as how the traditional DB are created using the DBCA tool. Installation and Configuration of OEM Cloud Control 13c Post database creation, now it’s time to start with OEM Cloud Control 13c installation/configuration procedure. Launch installation procedure executing the ./em13100_linux64.bin (depending on the Platform you choose) and continue with the installation procedure. Ensure all prerequisite checks are passed. If any, fix and proceed further. Choose Advanced option from the Installation Types screen, as shown below: Input the Installation Details for Middleware Home Location, Agent Base directory , as shown below: If you want to install the any non-default plug-ins, as displayed in the below screen shot, select them and hit Next button. The installation software will warn on “Oracle Engineered System Healthchecks” selection, saying it has become obsolete. Later while installing agents on the Exadata it will be required. If the goal is to manage Exadata Machines, you might want to select this plug-in and ignore the warning at this stage. Provide the EM repository database connection details. The one created earlier. See the below image: Ensure the following ports are accessible to DB nodes. Review the details below and hit the Install button to start the OEM installation. After OEM successful installation, launch the main screen through your browser and enter the user credentials, as shown below: Exadata Database Machine Discovery Before you start the Exadata Database Machine Discovery process, it is highly recommend to run thoroughly the following prerequisites for a smooth and successful installation. exadataDiscoveryPreCheck Script To avoid running into various configuration mismatch issues while discovering Exadata machine, Oracle developed an exadataDiscoveryPreCheck.pl script that can help the customers to capture the most common configuration problems. Download the script from the Prerequisite script for Exadata Discovery in Oracle Enterprise Manager Cloud Control 12c and 13c (Doc ID 1473912.1) . Once you downloaded the script on the source system, run it as oracle user, as demonstrated hereunder: $ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/db_home1 $ $ORACLE_HOME/per/bin/perl exadataDiscoveryPreCheck.pl For the complete usage, look at the syntax below: Review the output and ensure you address all the concerns that has been reported in the output. Setup ILOM Service Process User (oemuser) An ILOM Service user ( oemuser ) must be created prior to Exadata Database machine discovery. This user is essential for OEM agent communication with an ILOM service processor. The oemuser must be created on all DB Nodes, as explained below: On the first DB node, login as root and connect to ILOM as root user, as mentioned in the below example: $ ssh db01-ilom –l root Go to the ILOM users and perform the following set of actions: -> cd /SP/users -> create oemuser (enter the password on prompt) -> cd /oemuser Define the role (cro or aucro) as defined below -> set role = 'aucro' -> exit Repeat the above steps to create the oemuser and set the role on the rest of the DB nodes. After the oemuser has been successfully setup on all Exadata DB nodes, then, run the following command to test ILOM user setup: $ ipmitool –l lanplus –H db01-ilom oemuser –P -L USER set list last 10 Monitoring credentials As part of the Exadata discovery process, you will be required to enter the host credentials for various Exadata components, therefore, have them beforehand: Cell and Compute node host user name and passwords Cell root password ILOM (oemuser) InfiniBand Switch (nm2user password) Deploy Management Agent on compute nodes Deploying Management Agent to the respective DB nodes is another important step that needs to be completed prior to discovering Exadata Database Machine. This segment will demonstrate how to push/install Agent Software across all compute (DB) nodes of an Exadata database machine. From the Setup -> Add Target -> Add Targets Manually , hit Install Agent on Host button, as shown in the below screen shot: Add all compute (DB) nodes hostname on the below page. The hostname must be specified with the full qualifier and select the right Platform for the Agent Software. Click Next to proceed further. Review the installation details and input values in the next screen and start the Management agent deployment across all DB nodes. Discovery of Exadata Database Machine This segment will focus on the required procedure pertaining to Exadata Database Machine discovery process with OEM Cloud Control 13c. Ensure the Management Agent is successfully deployed across all DB nodes of Exadata, as it is critical for Exadata discovery process. Launching discovery procedure Login to OEM Cloud Control 13c, from Setup choose Add Targets Manually option. And click on Add Using Guided Process , as shown below: Select Oracle Exadata Database Machine option from the list shown on the page, show shown below, and click on Add button: Select the options highlighted in the below picture and hit Discover Targets button to initiate the discovery process: Note : The Discover newly added hardware components in an existing Database Machine as targets option is typically used to discover any newly added hardware of existing Exadata Database Machine or can be used to rediscover the components of already discovered Exadata Database Machine. Pick the Agent URL on the below screen by clicking the option: Add the Schematic File Location for all agents URL, set the oracle user credentials and hit Test Connection button to test the connectivity. Optionally, check the Save As option to save the credentials in the EM for future usage. Note: Possibly, you might encounter Invalid username and/or password LOG. Local Authentication Failed… Attempt PAM authentication… PAM failed with error… Authentication failure . (As shown in the below picture) One of the following workarounds could be used to resolve the issue: As root user on the DB node, go to /ect/pam.d and copy the sshd file as emagent under the same location. Or use one the solutions mentioned in How to Configure the Enterprise Management Agent Host Credentials for PAM and LDAP (Doc ID 422073.1) , related to the OS you are running. Once the above problem is resolved, hit Next button to proceed further. Enter the user credentials for InfiniBand discovery, as shown in the below example and screen shot: InfiniBand Switch Host Name : Username : nm2user Password : welcome1 Hit Test Connection button to test the user credentials, optionally save the credentials in EM for future usage. Once the test is successful, hit Next button to continue. You should see the below picture when there are no issues with the prerequisite check. Hit Next button to proceed further. The Database Machine Discovery Components page should display all the components hostname and possibly Management IPs of the components. Hit Next button to proceed further. In the subsequent screens, OEM lists all the monitoring agents’ information, primary and secondary, and shows Review information of all components. When Next button is hit on the Review page, OEM stars the discovery process, as shown below: For Management Agent on DB nodes, set the credentials, test the connectivity, as shown below: Enter the credentials for Storage Server and InfiniBand Switch, as shown below: For PDU and CISCO Switch, use the following user (admin) credentials. Community string for SNMP credentials (PDU & Cisco) is public . Test the connection and click on Next to proceed. After completing the discovery process, you will have a summary page of all the components (System targets, Compute nodes, cell storage, InfiniBand switch, Ethernet Switch, PDU etc) that have been discovered. Hit the Launch DB Machine Home button to launch the Exadata Database Machine in your OEM. Discover Grid Control, Listeners, ASM & Databases Upon successful discovery of Exadata Database machine, the subsequent job is to discover the Grid Control (Clusterware & ASM instances), Listeners and Databases configured on the DB nodes. As a first step, logon to OEM, if not already logged in. Then, select Add Target Manually option and click on Add Using Guided Process button, as shown in the below picture: Choose Oracle Cluster and High Availability Service from the list displayed on Add Using Guided Process screen and hit Add button, as shown below: Specify the compute host name, probably first DB node name and hit Discover Target button, as shown below: OEM then discovers the Cluster details, as shown below. Hit Save button to store the Cluster configuration in E. The following confirmation will be appeared on a popup window, click on Close button to close the window. After adding the cluster and high availability details, let’s now discover Listeners, ASM instances and Databases registered against the cluster. Choose the Oracle Database, Listener, ASM option from the list and hit Add button, as shown below: Specify the cluster name that was discovered earlier, or choose the cluster from the list, hit Next button: OEM then starts discovering the targets and brings you the following screen, where you will have to input the ASM instance connection credentials. Input the Password under the Monitoring Credentials against each ASM instance and then click the Test Connection button. Click the Next button and review the results in the next screen and save the information, as shown below. Conclusion At this point of time, you have successfully discovered the Exadata database machine and all its major components. Now, you can manage, monitor and maintain your Exadata through an OEM Cloud Control 13c. You may now configure the alerts, to receive the notification on any particular action either through email, SMS or combination of both. The following example shows the successful discover of Exadata boxes. References Prerequisite steps before discovering Exadata DB machine within Oracle Enterprise Manager 12c (Doc ID 1437434.1) Prerequisite script for Exadata Discovery in Oracle Enterprise Manager Cloud Control 12c and 13c (Doc ID 1473912.1) http://www.toadworld.com/platforms/oracle/w/wiki/11418.discover-exadata-database-machine-in-oracle-enterprise-manager-12c Oracle Enterprise Manager 12c: Oracle Exadata Discovery Cookbook https://oracle-base.com/articles/13c/cloud-control-13cr1-installation-on-oracle-linux-6-and-7
↧
Wiki Page: Oracle Enterprise Manager Cloud Control 13c:- Oracle Exadata Database Machine Discovery
↧