![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1458325.1 : SuperCluster - How To Monitor Oracle SuperCluster Using EM Cloud Control 12c
EM Exadata plugin version 12.1.0.3.0 supports 11gR2 domains running in global zones only on Sparc SuperCluster T4-4 and higher Applies to:Enterprise Manager for Exadata - Version 12.1.0.5.0 and laterOracle SuperCluster T5-8 Full Rack - Version All Versions and later Oracle SuperCluster M6-32 Hardware - Version All Versions and later SPARC SuperCluster T4-4 Full Rack - Version All Versions and later Information in this document applies to any platform. Oracle SuperCluster T4-4, T5-8 and M6-32 You need to be at EM Framework 12.1.0.4 and agent version 12.1.0.4 Exadata and DB plugins 12.1.0.6 . Also, refer to My Oracle Support Note 1323298.1 to get to the latest required patches on top of the latest release GoalThis document provides a step-by-step process for configuring the Oracle SuperCluster for use with Enterprise Manager Cloud Control 12c using the 12.1.0.3.0 and later version of the Exadata Plugin. SolutionFor SuperCluster M6-32 see also Note 1920159.1
In order to monitor your SPARC SuperCluster T4-4 and higher using Enterprise Manager Cloud Control 12c, two requirements must be met: - The Exadata Plugin 12.1.0.6.0 or later versions must be used with EM framework (12.1.0.4) Also, refer to My Oracle Support Note 1323298.1 to get to the latest required patches on top of the latest release
Please complete the steps below for successfully discovering and monitoring your Oracle SuperCluster:1. Check the installation build version by running (step1 should be skipped if you are working with the older SuperCluster T4-4 installs): svcprop -p configuration/build ssc/identification
or
svcprop -p configuration/build svc:/system/oes/id:default
If it reports any build bellow "ssc-1.1.0.build-04' please follow steps in Note 1527924.1 How to verify your SPARC SuperCluster is at version 1.1
2. Ensure these minimum versions of the following packages are installed: pkg list compmon supercluster hmp-ipmitool
NAME (PUBLISHER) VERSION IFO system/management/hmp/hmp-ipmitool 1.8.10.4-3 i-- system/platform/exadata/compmon 0.5.11-0.1.0.11 i-- system/platform/supercluster 0.5.11-1.1.0.1 i-- If the above packages do not exist on you system, please install them from the Solaris 11 exa-family repository provided in the Oct 2012 or later Quarterly Maintenance Update patch
ibnetdiscover | grep sscdb0[1,2]
[7] "H-0021280001cee60a"[2](21280001cee60c) # "sscdb01 S 192.168.10.1 HCA-1" lid 17 4xQDR [9] "H-0021280001cee61a"[2](21280001cee61c) # "sscdb01 S 192.168.10.2 HCA-2" lid 19 4xQDR [28] "H-0021280001cf023a"[2](21280001cf023c) # "sscdb02 S 192.168.10.4 HCA-2" lid 11 4xQDR [30] "H-0021280001cebd42"[2](21280001cebd44) # "sscdb02 S 192.168.10.3 HCA-1" lid 9 4xQDR [7] "H-0021280001cee60a"[1](21280001cee60b) # "sscdb01 S 192.168.10.1 HCA-1" lid 16 4xQDR [9] "H-0021280001cee61a"[1](21280001cee61b) # "sscdb01 S 192.168.10.2 HCA-2" lid 18 4xQDR [28] "H-0021280001cf023a"[1](21280001cf023b) # "sscdb02 S 192.168.10.4 HCA-2" lid 10 4xQDR [30] "H-0021280001cebd42"[1](21280001cebd43) # "sscdb02 S 192.168.10.3 HCA-1" lid 8 4xQDR If `ibnetdiscover | grep your_db_nodes` does not return output, you must run /bin/ib_set_node_desc_ssc.sh as the root user to set the node descriptions from all database nodes. Then repeat step 3 again.
4. Ensure that READ permissions are open for all files in this directory as well as /opt/oracle.SupportTools/em directory. The agent must be able to read these files during DBM discovery.
5. Ensure BOTH /opt/ipmitool/bin/ipmitool and /opt/ipmitool/sbin/ipmitool exists. If not, please create links as necessary. For example: root@sscdb01:/opt/ipmitool/sbin# ls -la
total 7 drwxr-xr-x 2 root root 3 Nov 15 12:45 . drwxr-xr-x 5 root bin 5 Nov 15 12:44 .. lrwxrwxrwx 1 root root 26 Nov 15 12:45 ipmitool -> /opt/ipmitool/bin/ipmitool 6. The 12.1.0.4.0 Exadata plug-in depends on the output of the new Oracle Exadata Deployment Assistant (OEDA) from the latest version the OneCommand patch to deploy and render the proper schematic of the SuperCluster. If you do not have the latest accurate schematic file(s) - either databasemachine.xml or catalog.xml under /opt/oracle.SupportTools/onecommand, then you must generate them as described below. Refer to Database Machine and Exadata Storage Server 11g Release 2 (11.2) Supported Versions <Note 888828.1> for the latest OneCommand patch link. - Follow link in 888828.1 under Section OneCommand for latest OneCommand patch. - Download and extract patch on your local machine. - Under the extracted patch navigate to the exaconf directory and then launch the corresponding exaconf shell or command file depended on your OS. - Populate the necessary fields with the information specific to your installation. - When you reach the "Review and Edit Details" page, click the Generate Configuration Data button. - After reviewing to correctness, click "Next" > "Create Files" - On the first 11gR2 database node, `mv /opt/oracle.SupportTools/onecommand /opt/oracle.SupportTools/onecommand.preoeda` - Create a new onecommand directory on the first 11gR2 database node `mkdir /opt/oracle.SupportTools/onecommand` - Copy the new files generated with the OEDA to /opt/oracle.SupportTools/onecommand
- Setup >> Extensibility >> Self Update, then click on Agent Software - Select Oracle Solaris on SPARC (64-bit) - If the status is Available, then click Download from the Actions menu - Once downloaded, you must apply it to the OMS from the same Self Update page For more details on Self Update in Online or Offline mode, please see the EM 12c Administrator's Guide or simply click on Help and search for Offline Update
8. EM 12.1.0.4 and higher includes Exadata 12.1.0.4.0 agent. If you don't have the plugin on your OMS, run Self Update from the EM Console to download the 12.1.0.6.0 or later Exadata Plug-in on the OMS. - Setup >> Extensibility >> Self Update, then click on Plug-ins - Select "Oracle Exadata" version 12.1.0.3.0 or higher - If the status is Available, then click Download from the Actions menu - Once downloaded, you must Apply it to the OMS from the same Self Update page
9. Install an agent on each of the DB nodes be them global or non-global zones on the Oracle SuperCluster . - Setup >> Add Target >> Add Targets Manually - Select Add Host Targets (selected by default) and click Add Host - Continue with the install wizard and ensure that you run root.sh on each node once installation is completed Note: You may run into BUG 13822068 / base BUG 13822068 where you have to edit the Ciphers entry in /etc/ssh/sshd_config and restart ssh. Use Note SSHD Connection Errors After Upgrading To Exadata Version 11.2.3.1.0 <Note 1437596.1>
10. Configure the database nodes for DBM discovery 11. Discover Exadata DBM from the GUI using Manual Discovery wizard. This discovery process is the same as any other Exadata DBM target. 12. Discover the HA RAC Cluster and the cluster databases and configure each target as usual. IMPORTANT: To prevent agent hangs with the EM agent on Solaris, follow the steps in <Note 1427773.1> to update sysman/config/java.security
Attachments This solution has no attachment |
||||||||||||
|