SCALABLE ENTERPRISEapplication servers, and can be configured to send automatedalerts and warnings when the target resource utilization reachesthreshold values established by the system administrator.Grid Control installation and configurationThis article describes the installation and configuration of GridControl on the Red Hat ®Enterprise Linux 3 operating system (OS).Best practices dictate installing Grid Control on a system that doesnot have an Oracle database installed and is not being used as anapplication server. 2Download the three Grid Control gzip files and unzip them to adirectory to which the Oracle users have read and write privileges.Unzip the files and obtain the cpio archives:# gzip –d linux_grid_control_10_1_0_2_Disk1.cpio.gz# gzip –d linux_grid_control_10_1_0_2_Disk2.cpio.gz# gzip –d linux_grid_control_10_1_0_2_Disk3.cpio.gzAfter unzipping the files and obtaining the cpio archives, copythe files from the archive using the cpio command:# cpio -idmv < linux_grid_control_10_1_0_2_Disk1.cpio# cpio -idmv < linux_grid_control_10_1_0_2_Disk2.cpio# cpio -idmv < linux_grid_control_10_1_0_2_Disk3.cpioThe preceding steps create three directories called Disk1, Disk2,and Disk3. The administrator should open an xterm session andexecute the command runInstaller from within the Disk1 directoryto start the Grid Control installer.Installation of management service. The management serviceinstallation includes the management service and managementrepository. For a new installation, administrators should select theoption “Enterprise Manager 10g g Grid Control using a new database.”If the environment already has an Oracle database to house themanagement repository, administrators should select the option“Enterprise Manager 10ggGrid Control using an existing database.”Administrators can then complete either installation by followingthe on-screen instructions. After installation of the managementservice, the Grid Control management console is accessible fromthe browser at HostName:7777/em.Installation of management agent. The management agent mustbe installed on all the nodes that require monitoring. Administratorscan select the option “Additional management agent” from the ProductSelection menu during installation. The management agent requirescredentials such as host name and port number of the server thatis running the management service. After specifying these details,administrators should follow the on-screen instructions to complete theinstallation. After installation, the management agent should automaticallycommunicate with the server running the management serviceand appear as a target in the Grid Control management console.Management of database cluster nodes using Grid ControlGrid Control has features to help database administrators managemultiple database instances. Using Grid Control, an administrator candynamically modify parameters of the database instances, such as buffersize and sort area, depending on the workload on the systems. GridControl provides a console that displays real-time data for server activities.If an excessive load develops on a particular group of instances,the administrator can manually add an extra system and create anotherdatabase instance without affecting the other systems. 3Cloning. Grid Control simplifies database cloning. Cloning createsa copy of the existing database on a new set of target servers and helpscreate test instances or backup instances of a production database. AGrid Control feature known as multicast allows the administrator to selectan $ORACLE_HOME on a system and to clone the existing $ORACLE_HOMEto multiple destination servers. Environment-specific parameters suchas host name and IP address are automatically updated as part of thecloning process. The only requirement is that target servers must havethe Grid Control management agent up and running. The entire cloningoperation can be scheduled using the built-in EM job scheduler.The sidebar “Cloning a database with Grid Control” in this articleprovides an example scenario of Grid Control cloning capabilities.Automated upgrades and patching. Grid Control can help automatethe upgrade process for database instances. The critical patchadvisory feature proactively notifies the administrator of importantpatches that are available on metalink.oracle.com, which is thepatch repository for Oracle products. Grid Control also maintainsan inventory of the different hosts as well as the patch sets andinterim patches that administrators have applied to them. Whenconfigured properly, the critical patch advisory feature of EM candownload the relevant patches from MetaLink and maintain them ina patch cache. The patch cache is a staging area for patches, whichcan be used to apply patches to other systems at a later time. Patchinstallation for different systems can be scheduled for a particulardate and time using EM job scheduling mechanisms.The critical patch advisory feature also checks for sufficient diskspace on systems before applying the patches, and issues an alertwhen failures occur. Pre- and post-patch processing steps can also2For more detailed installation information, review the section “Preinstallation Requirements for Enterprise Manager” in the Oracle Enterprise Manager Grid Control Installation and Basic Configuration Guide, which isavailable at download-east.oracle.com/docs/html/B12012_03/toc.htm.3For more information about real-time diagnostics and tuning of Oracle database instances using EM Grid Control, see “Exploiting Automated Database Diagnostics in Oracle Database 10g” by Ramesh Rajagopalan,Uday Datta Shet, C.S. Prasanna Nanda, and Bharat Sajnani in <strong>Dell</strong> <strong>Power</strong> <strong>Solutions</strong>, February 2005.96POWER SOLUTIONS Reprinted from <strong>Dell</strong> <strong>Power</strong> <strong>Solutions</strong>, February 2005. Copyright © 2005 <strong>Dell</strong> Inc. All rights reserved. February 2005
SCALABLE ENTERPRISEbe automated by writing custom scripts that are invoked by thecritical patch advisory feature during patch deployment.Monitoring of applications and service-level management. Inaddition to the database, Grid Control monitors mid-tier softwareand applications. The tool provides a holistic view of the systems onwhich the management agents are running, which helps administratorsproactively monitor systems and anticipate any major issues.Grid Control also provides features that allow administrators tomonitor and record critical application-specific business transactionsthat may be relevant for system tuning.The Policy Manager feature in Grid Control enables administratorsto set an enterprise-wide set of policies to be enforced on alldatabase instances. Some examples of policies include:• Disabling initialization parameters on undocumented ordeprecated systems• Enabling the use of an OS password file for authenticationGrid Control also enables administrators to create a systembaseline. After setting up the system and ensuring that the behaviorof the system is optimal, administrators can record a set of baselinemetrics for the system. These baseline metrics can be used to determinethe optimal values for various system thresholds (such as CPUand memory utilization, available file system space, and responsetime). An alert displays on the Grid Control management consoleif the system reaches any of these thresholds. Administrators canalert appropriate IT personnel by configuring relevant notificationmechanisms using SMTP traps, e-mail, or user-defined scripts.Automation for effective, scalable database managementDatabase administrators generally manage multiple databases, anddatabase deployment consumes much of their available time. OracleEnterprise Manager Grid Control is advanced software that providesfeatures to help manage and deploy multiple database instances andOracle RAC clusters. Enterprise Manager Grid Control can help automateand schedule many of the routine activities involved in databasemanagement, enabling database administrators to manage and scaleout to a large number of database instances efficiently.CLONING A DATABASE WITH GRID CONTROLIn this example scenario, an administrator has configured four <strong>Dell</strong> <strong>Power</strong>Edge servers running an Oracle9i i RAC database. The administratorhas purchased two new <strong>Power</strong>Edge servers and plans to scale out theexisting infrastructure in response to an increase in workload.Using Oracle Enterprise Manager Grid Control, the administrator canmigrate the existing Oracle RAC database to the new nodes with just a fewclicks. After installing the operating system and Oracle9iiRAC database onthe two additional server nodes, the administrator installs the Grid Controlagent on both nodes. Once the two nodes start communicating with theserver running Grid Control, the administrator performs the following sixsimple steps:1. Select the source database. On the Grid Control home pageDeployments tab, click “Clone Database.” Then select the runninginstance of the database to clone.2. Supply the credentials. Enter the username, password, role, andOracle user credentials to log in to the target database.3. Select the destination. Supply the global database name of thedestination host and the destination host name.4. Create the schedule. Determine a schedule to run the databaseclone job. This job can be scheduled immediately or can be scheduledto run later.5. Review.After all the necessary parameters have been supplied,Grid Control displays a summary of the job (see Figure A).6. Submit. After reviewing the job settings in the preceding step,submit the job for execution. The job will start executing at thestart time set in step 4. Administrators can monitor a running jobby viewing the Status column on the Jobs tab.Rudramuni B is an engineering manager for the Enterprise <strong>Solutions</strong> and OS Engineeringteams in the <strong>Dell</strong> Product Group in Bangalore, India. He has an M.Tech. in Systems Analysis andComputer Applications from Karnataka Regional Engineering College in Surathkal, India.C.S. Prasanna Nanda is an engineering analyst on the <strong>Dell</strong> Database and Applicationsteam in the <strong>Dell</strong> Product Group. He has a B.E. in Computer Science from the Birla Instituteof Technology and Science in Pilani, India.Uday Datta Shet is a senior engineering analyst on the <strong>Dell</strong> Database and Applicationsteam in the <strong>Dell</strong> Product Group. He has a B.E. in Computer Science and is also an OracleCertified Professional (OCP).Figure A. Database cloningwww.dell.com/powersolutions Reprinted from <strong>Dell</strong> <strong>Power</strong> <strong>Solutions</strong>, February 2005. Copyright © 2005 <strong>Dell</strong> Inc. All rights reserved. POWER SOLUTIONS 97