For the purpose I have setup a VMWare virtual machine with 2 CPUs, 4GB RAM and 32 GB HDD, one network interface. After installation the network adapter won’t be available that why you have to install several packages and then compile the VMWare tools.
Before starting the installation, download the packages from OTN and transfer them to the server.
Once you are ready you could run the EM Prerequisite Kit which is run by the wizard during the installation.
Supply the repository details and please be sure to check whether the database control doesn’t exists.
Once the installation is complete you’ll get a screen with installation summary and details how to access the console. Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising.
What You See Is What You Get Element Monitoring Oracle Exadata Storage Servers by Brian Bream and Suzanne Zorn This article describes how to use Oracle Enterprise Manager Cloud Control and command-line utilities to monitor Oracle Exadata Storage Servers.
Monitoring Metrics Using the Oracle Enterprise Manager Cloud Control Console Oracle Enterprise Manager Cloud Control provides an intuitive view of Oracle Exadata status, including the status of all hardware and software components.
Note: This command produces output only if there are alerts that have not been reviewed by another administrator.
Note: The CREATE THRESHOLD command creates a threshold that specifies the conditions for the generation of a metric alert.
Oracle Enterprise Manager Cloud Control 12c provides a visual overview of the availability of the storage cells, with color-coded green and red status symbols to indicate available and unavailable, respectively (see Figure 4).
Other Patching Procedures There are a number of other Deployment Procedures available for patching. Each storage server is a separate target in Oracle Enterprise Manager Cloud Control, and the Oracle Exadata storage servers are grouped together for collective monitoring of all storage.
With Oracle Enterprise Manager Cloud Control, administrators can determine the status at a glance, and then drill down to the affected components for more information.
Studies show that many corporations world-wide expect their IT footprint to grow in the coming years. For setting database initialization parameters refer to Table-6 or Table-7 from Appendix A at the documentation. The Oracle Enterprise Manager Cloud Control console makes it easy to see the status at a glance, and provides an easy way to drill down to get more detailed information. For the rest of the version additional patches are needed, refer to MOS for more information. They require more floor space in their data centers, and also the corresponding greater power footprint. Administrators can select any Oracle Exadata target, view alerts on that target, and drill down to display more details about each alert. Have you heard of a data center where no more servers can be added because the power supply has reached its limit, or the UPS (Uninterruptible Power Supply) can no longer cope? The alert is triggered by two consecutive measurements (occurrences=2) over the threshold values. Values of one second over the threshold trigger a warning alert; values of two seconds over the threshold trigger a critical alert.
The growth seems to be endless, and this is fuelled by today's information age, where larger and larger volumes of data need to be stored and distributed to satisfy an ever-growing demand.
Comparison: Monitoring Storage Server Availability Both the CLI and Oracle Enterprise Manager Cloud Control 12c can be used to monitor storage server availability. The prerequisite checks include detailed checks for cluster health, so as to avoid unexpected failures. Using Oracle Enterprise Manager Cloud Control 12c to compare metrics across multiple servers. This Rolling Patching procedure is very useful for automating the patching of multiple RAC nodes, especially when there are more than two nodes.
The distributed CLI utility, dcli, can be used to execute commands across multiple servers on Oracle Exadata. Solaris, Linux, IBM-AIX, Microsoft Windows), and in each case there may be different versions – such as the different flavors of Linux supplied by different vendors including Oracle Enterprise Linux, Red Hat, SUSE Linux, and so on. In the case of Oracle Exadata Database Machines, the use of such procedures is highly recommended to ease the administration burden.
However, it is much more complex to manually aggregate statistics reported in its command output and make comparisons across multiple storage servers.
Final Thoughts Oracle Enterprise Manger Cloud Control 12c provides easy-to-use, intuitive monitoring of Oracle Exadata Storage Servers.
Oracle WebLogic Server patching is now also possible from Oracle Enterprise Manager Cloud Control 12c. Components include database servers (also called compute nodes), Oracle Exadata Storage Servers (also called storage cells), Oracle's Sun Datacenter InfiniBand Switch 36 switches, and Exadata Smart Flash Cache.
Status information is visually displayed, making it easy to pinpoint problems and then drill down for more detailed information. This requires a different license: the Oracle WebLogic Server Management Pack Enterprise Edition (EE).
Monitoring Technologies Oracle Exadata uses several technologies to enable the monitoring of its components.
In addition, Oracle Enterprise Manger Cloud Control provides capabilities for easily comparing metrics across multiple storage servers. These will also need to be applied to production, test, reporting, staging, and development environments in the Data Center on an ongoing basis. The WebLogic Administrator needs to search MOS for patches to apply to a WebLogic Domain, depending on the WLS version and the Platform. These technologies include Oracle Integrated Lights Out Manager (Oracle ILOM), Simple Network Management Protocol (SNMP), and Intelligent Platform Management Interface (IPMI). The CLI (cellcli command and dcli utility) can be useful for scripts and creating processes that need to be repeated. For the Database side of things, Oracle releases quarterly a combination of security fixes known as the Critical Patch Update (CPU).
The Patching Wizard in Enterprise Manager checks for conflicts, and allows you to apply the patches in parallel or in a rolling manner across the Domain. Other patches are bundled together and released every quarter in the form of a Patch Set Update (PSU), and this also includes the CPU for that quarter.
This command can be used to display detailed information about the metrics that are available for a storage cell.
Oracle ILOM is integrated service processor hardware and software that is preinstalled on Oracle servers, including the storage and database servers in Oracle Exadata. Brian also functions as an Oracle University instructor delivering courses that focus on Oracle's engineered systems, Oracle Solaris, Oracle Linux, and Oracle's virtualization and storage solutions. The service processor runs its own embedded operating system and has a dedicated Ethernet port to provide out-of-band server monitoring and management capabilities. It is of metricType Instantaneous, it is associated with objectType CELL, and it has a measurement unit of percentage. Collier IT is a full-service Platinum-level Oracle partner that provides Oracle solutions, including Oracle engineered systems, software, services, and Oracle University training. If you wish to move to the PSU, you can do so, but in that case continue only with the PSU. Oracle ILOM can be accessed via a browser-based web interface or a command-line interface, and it also provides an SNMP interface and IPMI support.
Collier IT provides its customers with complete, open, and integrated solutions, from business concept to complete implementation.


The quarterly patching requirement, as a direct recommendation from Oracle, is followed by many companies which prefer to have their Databases secured with the latest security fixes.
Since 1991, Collier IT has specialized in creating and implementing robust infrastructure solutions for organizations of all sizes.
Collier IT was a go-to partner for Sun Microsystems for ten years prior to the acquisition of Sun by Oracle in 2009. However, if there are hundreds of development, test, staging and production Databases in the Data Center to be patched, the situation quickly turns into a major manual exercise every three months. Oracle BI Publisher Enterprise Reports can also be used, but BI Publisher needs to be configured for use with Enterprise Manager.
SNMP is an open, industry-standard protocol used to monitor and manage devices on an IP network. As a former Sun Executive Partner and now as a Platinum-level Oracle partner, Collier IT is aligned to provide customers with complete solutions that address their business needs.
DBAs and their Managers start planning for the patch exercise in advance, and a lot of resources are allocated to make it happen – with the Administrators working on each Database serially, at times overnight and at times over the weekend. For more information on the setup required, refer to the Cloud Control Advanced Installation and Configuration Guide.
Suzanne Zorn has over twenty years of experience as a writer and editor of technical documentation for the computer industry. There are a number of steps involved in patching each Database, such as locating the appropriate patch in My Oracle Support (MOS), downloading the patch, transferring it to each of the target servers, upgrading the OPATCH facility in each Oracle Home, shutting down the Databases and Listeners running from that Home, applying the patch, starting each of the Databases in restricted mode, applying any supplied SQL scripts, restarting the Databases in normal mode, and checking the patch inventory.
Summary Oracle Enterprise Manager Cloud Control 12c allows automation of the tedious patching procedure used in many organizations today to patch their Oracle Databases and Servers. SNMP also enables active management of devices, such as modifying the device configuration remotely. Previously, Suzanne worked as a consultant for Sun Microsystems' Professional Services division specializing in system configuration and planning.
These steps have to be manually repeated on every Database Home on every server, and on every Database in that Home. This is achieved via the Oracle Database Lifecycle Management Pack, which is one of the main licensable packs for Oracle Enterprise Manager.
Suzanne has a BS in computer science and engineering from Bucknell University and an MS in computer science from Rensselaer Polytechnic Institute.
Dull repetition of these steps in patching the hundreds of servers in a data center is a very monotonous task, and it can lead to an increase in human errors. Sophisticated Deployment Procedures are provided out-of-the-box to fulfill many different types of patching tasks. To avoid these issues inherent in manual patching, some companies decide not to apply the quarterly patches on their Databases. This helps you to achieve mass patching of multiple targets with multiple patches in a fully automated manner, for substantial savings in administrative time and effort. They wait for a year, or a couple of years, before they consider patching, and some even prefer to apply year-old patches instead of the latest patches.
This is counter-productive and leads to their Databases being insecure and vulnerable to attacks, since the latest recommended CPUs from Oracle have not been applied.
Different types of patches can be applied in this manner, including CPUs, PSUs, Patch sets, and other one-off patches.
IPMI is an open, industry-standard protocol used primarily for remote server configuration and management across a network.
In Oracle Exadata, the database and storage servers contain built-in IPMI support in Oracle ILOM.
If the patching process can be mostly automated (but still under the control of the DBAs), it would reduce the quarterly patching effort to a great extent. For the first time, upgrade of single-instance databases is also possible via Oracle Enterprise Manager Cloud Control 12c. Companies would then have the confidence that their existing team of DBAs would be able to manage the patching of hundreds of Databases in a controlled and automated manner, keeping human error to a minimum. There is full integration of Oracle Enterprise Manager's patching capabilities with My Oracle Support (MOS). The Database Lifecycle Management pack for Oracle Enterprise Manager Cloud Control 12c is able to achieve this via its Patch Automation capability.
The support site retains the configuration of all the components managed by Oracle Enterprise Manager inside your company. We will now look into Patch Automation and the close integration of Enterprise Manager with My Oracle Support. Since the current version and patch information of the components is known, My Oracle Support is able to provide appropriate patch recommendations for many targets, including the latest security fixes. The cellcli command is used for management and monitoring of individual Oracle Exadata storage cells.
We assume that Enterprise Manager Cloud Control 12c has been installed with the appropriate architecture on a central site, and Enterprise Manager Agents have been pushed to all production, test and development targets. In addition, the dcli (distributed CLI) utility can be used to execute scripts and commands, such as those for shutting down compute nodes, across multiple storage cells from a single interface.
A full Division of Roles is available, such as Patch Administrator, Designer, and Operator.
It is possible to take the My Oracle Support recommendations, select patches for targets, put them into a patch plan, deploy the patch plan, and then create a plan template from it. The template can then be published to any operator who can then create patch plans for other targets. This system management platform provides integrated hardware and software management (see Figure 1). Its hardware view includes a schematic of storage cells, compute nodes, and switches, as well as hardware component alerts. In all, Oracle Enterprise Manager Cloud Control 12c offers valuable automation methods for Mass Patching, allowing Administrators to ensure that their systems have the latest security patches, and enabling them to control the application of patches on development, test and production servers from the centralized location of the Software Library. Its software view includes software alerts as well as information about performance, availability, and usage organized by databases, services, and clusters.
About the Author Porus Homi Havewala is the Senior Manager in the Enterprise Technology Program Office of Oracle Singapore, and is the ASEAN regional SME and business development lead on Oracle Enterprise Manager technology. A Double Oracle Certified Master (OCM) in Oracle 10g and Oracle 11g, Porus has more than 25 years of experience in the IT industry, including more than 18 years of experience using Oracle technologies. Oracle Enterprise Manager Cloud Control 12c screenshot showing the status of various hardware components in Oracle Exadata Database Machine. However, Oracle Exadata can be configured to send SNMP alerts to other SNMP managers on the network. Monitoring Architecture of Oracle Enterprise Cloud Control Before using Oracle Enterprise Manager Cloud Control 12c with Oracle Exadata, an Oracle Management Agent and Oracle Exadata plug-in must be installed on every Oracle Exadata database server (see Figure 2). This agent monitors software targets, such as the database instances and Oracle Clusterware resources, on the database servers. The plug-in enables monitoring of other hardware components in Oracle Exadata, including the storage servers, switches, and power distribution units. On the storage servers, the CELLSRV process provides the majority of Oracle Exadata storage services and is the primary storage software component.
We can see the list of Bugs resolved by this patch, the Last Updated date and Size of the patch, and also the Read Me – which has important information about the patch.
The Management Server (MS) process receives the metrics data from CELLSRV, keeps a subset of metrics in memory, and writes to an internal disk-based repository hourly.
The number of total downloads for this patch is visible, as is the Community Discussion on this patch in the Oracle Forums.
In addition, the MS process can generate alerts for important storage cell hardware or software events.


You can add your own comment for this patch, if required, by selecting Reply to the Discussion. The Restart Server (RS) process is used to start up and shut down the CELLSRV and MS processes. Thus, at a glance you can find out how popular the patch is (number of downloads) and any experience of other Oracle DBAs regarding this patch – whether positive or negative.
Patch Plan You can view the information about the patch by clicking on the Full Screen button. The primary components of Oracle Enterprise Manger Cloud Control 12c are the Oracle Management Service, the Oracle Management Repository, and the Cloud Control Console.
You can download the patch either to the Software Library in Enterprise Manager or to your desktop. The Oracle Management Service communicates with the agents on the managed targets and stores information in the Oracle Management Repository. Finally, you can directly add this patch to a new or existing Patch Plan, which we will do next. If you want to add multiple patches to the Plan, select the patches first and then add to them the Plan. This is now the recommended method and creates a new Oracle Home, which is then patched while the previous Home is still operational. Using this mechanism means that the only downtime will take place when the Databases from the previous Home are switched to run from the new Home.
If there is any issue with the Database patch, you can switch back to the previous unpatched Home since it is still available. Also, if there are multiple Databases running in the previous Home, you can decide which ones to switch to the new patched Home. This is obviously an advantage, otherwise you would be forced to simultaneously patch all the Databases in a Home.
Also, if proper housekeeping is not done later on, it can lead to a proliferation of Oracle Homes on a server where patches are being applied regularly using this mechanism. This kind of selective patching and minimal downtime is not possible if you use the previously available method of In Place Patching, which uses a separate Deployment Procedure to shut down all Databases running from an Oracle Home before applying the patches on the same Home.
The Databases can only be restarted normally after the patching process is over, and this obviously takes more downtime and affects all Databases in a Home. Depending on the method you choose, the appropriate Deployment Procedure will be automatically selected and used. This will compare the installed software and patches on the targets with the new patches you have selected in your plan, and attempt to validate them. This validation may take a few minutes to complete, since it also checks the Oracle Home for readiness, computes the space requirements for the home, and conducts other checks such as cluster node connectivity (if you are patching a RAC Database).
If you drill down to the analysis job itself by clicking on Show Detailed Progress, you can see that it does a number of checks to validate if the targets are supported for patching, verifies the normal and super user credentials of the Oracle Home, verifies the target tools, commands, and permissions, upgrades OPATCH to the latest version, stages the selected patches to Oracle Homes, and then runs the prerequisite checks, including those for cloning an Oracle Home. If the prerequisite checks succeed, the analysis job skips the remaining steps and stops at this point with a successful status. Along with the Database which is in the Patch Plan, a new impacted target has been found by the analysis process and added to the list of impacted targets. The Deployment Procedure that will be used is Clone and Patch Oracle Database, since Out of Place patching is being used, and all Instances and Listeners running in the previous Oracle Home are being switched to the new Home. A job for preparation of the Out of Place Patching starts, including Cloning of the original Oracle Home and applying the patches to the cloned home. At this time, downtime will be required since the Database instances using the previous Oracle Home will be shut down and switched across. The Deploy job successfully completes (after about 21 minutes in our Virtual Machine), we can see that it works iteratively over the list of Hosts and Oracle Homes in the Patch Plan. It starts a Blackout for the Database instances in the Oracle Home (so that no alerts are raised), stops the instances, migrates them to the cloned Oracle Home, starts them in Upgrade Mode, applies SQL scripts to patch the instance, applies Post-SQL scripts, and then restarts the Database in normal mode. The Deploy job applies other SQL scripts and recompiles invalid objects (except in the case of Patch Sets). It then migrates the Listener from the previous Oracle Home using the Network Configuration Assistant (netca), updates the Target properties, stops the Blackout, and detaches the previous Oracle Home.
The Review & Deploy page of the Patch Plan now shows the status of Deployment Successful, as shown in Figure 10. Such a template can then be used to apply the successful Patch Plan to multiple other targets. Inside the Plan Template, the Create Plan button is used to create a new plan based on this template and this can be done repeatedly for multiple targets. This screen displays a list of all the Patch Plans and Plan Templates that have been created. The successfully deployed Sainath Patch Plan and the new Patch Plan Template also shows up here (Figure 11).
This role has full privileges on any Patch Plan or Patch Template in the Enterprise Manager system and maintains the Patching infrastructure. The Patch Designer normally identifies patches to be used in the patching cycle across development, testing and production.
The Patch Designer creates Patch Plans, then Plan Templates, and grants privileges on these Plan Templates to the Patch Operator. As an example, the Patch Designer will select a set of recommended and other manually selected patches for an Oracle 11g Database and create a Patch Plan. This role will then test the patching process in a development environment, and save the successfully analyzed or deployed Patch Plan as a Plan Template. The Patch Designer will then publish the Oracle 11g Database Patching Plan Template to the Patch Operator –probably the Junior DBA or Application DBA in a real world scenario. Next, the Patch Operator creates new Patch Plans out of the Template (but cannot create a Template), and adds a different list of targets, such as other Oracle 11g Databases in the test, staging, or production environment. This role then schedules the deployment of the patches to all these environments – using the same Template again and again. Refreshes An out-of-box Enterprise Manager job runs everyday and gets the latest patch information from My Oracle Support (MOS).
This job is important for you to receive timely notification of Critical Patch Advisories and other patches from Oracle.
Then select the job type as Refresh From My Oracle Support and Scheduled Start of Last 7 days. This displays all the out-of-box refreshed jobs that have run and are scheduled for the future. If there is a requirement to set up your own refresh job (for example, if you would like the MOS Patch Recommendations for your Databases to be refreshed immediately instead of waiting for the next scheduled running of the job), then perform the following steps.
You now have up to date My Oracle Support Patch Recommendations for your Enterprise Manager targets. My Oracle Support obviously needs to know about the Configuration information of all your targets, in order to make the right recommendations. For example, it needs to know if your Database is already patched up to a certain CPU and PSU. There is another recurring refresh cycle that occurs overnight and performs the Configuration inventory collection for all the targets managed and monitored by Enterprise Manager.
This submits a request to the agent to re-collect the Configuration inventory for that Oracle Home. The other method to force the collection is by using the emctl command in the Agent Home on the actual Target Host.



Cloud backup uk home loan
Free word cloud generator software download espa?ol


Comments

  1. 23.06.2016 at 18:22:26


    Your OpenStack cloud in minutes entrust large volumes of data to the.

    Author: Prodigy
  2. 23.06.2016 at 10:42:28


    Sharing and playing with those files storage option for your company top five.

    Author: Felina
  3. 23.06.2016 at 12:15:50


    Provider should have extensive audit capabilities highlight only the.

    Author: S_a_d_i_s_T
  4. 23.06.2016 at 20:42:54


    Enterprises are?moving to the cloud, but HIPAA-compliant cloud storage makes the.

    Author: UREY
  5. 23.06.2016 at 22:32:10


    Large library of files that we cannot not guaranteed with saves You.

    Author: Aglayan_Gozler