This presentation will concentrate on the technical aspects and concepts of the Oracle GRID technologies and its usage for monitoring Oracle Databases and Application Servers. Topics such as installation, configuration, and usage will be discussed. The presentation will include demonstration materials, technical challenges, open discussions and breaks. This workshop will be divided into three major segments. 1) Will discuss installation, startup and shutdown, and hardware configurations. 2) Will include configuration, security concepts, and agent installation. 3) Will cover monitoring and technical challenges.

1. Oracle Grid Control setupand usage challenges Jeff Hinds Database AdministratorTennessee Board of Regents

2. Description This presentation will concentrate on the technical aspects and concepts of the Oracle GRID technologies and its usage for monitoring Oracle Databases and Application Servers. Topics such as installation, configuration, and usage will be discussed. The presentation will include demonstration materials, technical challenges, open discussions and breaks. This workshop will be divided into three major segments. Will discuss installation, startup and shutdown, and hardware configurations. Will include configuration, security concepts, and agent installation. Will cover monitoring and technical challenges.

3. What is Grid Control A system management software that delivers centralized monitoring, administration, and life cycle management functionality for the complete Oracle IT infrastructure, including systems running Oracle and non-Oracle technologies. Enterprise Manager offers a single-window solution that allows you to monitor and manage the complete Oracle IT infrastructure from a single console. Robust service-level management functionality within Enterprise Manager Grid Control dramatically improves service levels through rich transaction and end-user performance monitoring and deep diagnostics for multi-tier Internet applications.

4. What is Grid Control (Cont.) Oracle's Grid Control compared to DB Control DB Control/Console DB Control is closer to the database and most of the times better support for new features. Database control is a web based tool for managing a single Oracle database that is installed on the same box as the database itself. Grid Control Oracle Grid Control you can make a global view of your entire enterprise. Grid Control is a web based tool for managing multiple Oracle databases that can be installed on a separate server and has its own database

5. What is Grid Control (Cont.) For managing lots of databases and application servers (according to Oracle Corporation, preferably in a grid solution) one could use the Oracle Enterprise Manager Grid Control. Can manage multiple instances of Oracle deployment platforms; the most recent edition also allows for management and monitoring of other platforms such as : Microsoft .NET, Microsoft SQL Server, Microsoft Active Directory NetAppFilers, BEA weblogic WebSphere Application Server JBossApplication Server Apache HTTP Server and others

6. What is Grid Control (Cont.) The architecture of the OEM for Grid Control has three distinct components: the collection agent (Oracle Management Agent or OMA) the aggregation agent (Oracle Management Server or OMS) the repository agent (Oracle Management Repository or OMR) The OMA runs on the target host and collects information on the hardware, operating system, and applications that run on the target. The OMS runs on one or two servers and collects the data generated by the OMAs. The OMS pulls the information from the OMAs and aggregates the collections into the repository. The OMS also acts as the user-interface — by generating web-pages for database administrators to view the status of systems and services. The OMR comprises an instance of the Oracle database that stores the data collected by the OMS.

7. What is Grid Control (Cont.) Graphical View of How OracleGrid Control Works

8. What is Grid Control (Cont.) Enterprise Manager Architecture While OMS acts as the brain of the Enterprise Manager Grid Control architecture responsible for communicating with Management Agents and a central repository that stores information, Management Agent acts as the hands and legs of a body responsible for collecting information from the monitored targets and transporting them to OMS. And, Management Repository is the repository configured in Oracle Database to store the collected information.

9. What is Grid Control (Cont.) Change is coming to Oracle Enterprise Manager. Current version isOEM 11g New version is OEM 12c Called “The Only Complete Cloud Management Solution”

10. Available Documents OEL5Complete Steps to Install 11.1.0.1 OMS Using 11.2 Database on 64 Bit RedHat 5 or OEL5 [ID 1130958.1] Grid Control 11g: Required External Components and Versions for Grid Control 11.1.0.1.0 [ ID 1106105.1 ] Oracle Enterprise Manager Grid Control Basic Installation Guide 11g Release 1 (11.1.0.1.0) Part Number E15838-06 Oracle Database Reference Guide available at: http://www.oracle.com/technology/documentation/database.html

11. Available Documents (Cont.) NOTE: 1059516.1 - Step by step Installation of 11.1 Grid control NOTE: 1063112.1 - Grid Control 11g: Example for Installing WebLogic Server 10.3.2 on OEL 5.3 x86_64 NOTE: 1063587.1 - Grid Control 11g: Example jdk1.6 0n Linux x86_64 Install for WebLogicServer 10.3.2 and Grid Control 11.1.0.1.0 NOTE: 1064441.1 - Grid Control 11g: Database Considerations for the Grid Control 11.1.0.1.0 Repository

12. Available Documents (Cont.) NOTE: 235562.1 - Issues Affecting Automatic Service Registration NOTE: 278100.1 - How To Drop, Create And Recreate DB Control In A 10g Database NOTE: 428665.1 - Installation Checklist for Testing Networking Configurations Prior to Installing EM Components NOTE: 433693.1 - Service / Instance Not Registering with Listener NOTE: 561429.1 - Connections To 11g TNS Listener are Slow.

13. Questions?

14. Installation Note Installation order for all products: System Required Packages Oracle Database Services and any needed patches and/or CPU updates. Create a database to be used as a repository Install the required version of Java SDK version 1.6.0_18 WebLogic Server and required patches Grid Control Services Grid Control Agents on systems to be monitored/managed

15. System Requirements For a small environment (< 100 monitored targets), you need following servers parameters: For the OMS: 2 CPUs, 4 GB RAM and 7 GB space excluding the installation which is 5.5 GB For the Management Repository: 2 CPUs, 2 GB RAM (3 recommended) and 50 GB space

16. System Requirements The following or later version of packages for Oracle Enterprise Linux 5, and Red Hat Enterprise Linux 5 must be installed: binutils-2.17.50.0.6 compat-libstdc++-33-3.2.3 compat-libstdc++-33-3.2.3 <--32 bit elfutils-libelf-0.125 elfutils-libelf-devel-0.125 gcc-4.1.2 gcc-c++-4.1.2 glibc-2.5-24 glibc-2.5-24 <-- 32 bit glibc-common-2.5

17. System Requirements (Cont.) The following or later version of packages for Oracle Enterprise Linux 5, and Red Hat Enterprise Linux 5 must be installed: glibc-devel-2.5 glibc-devel-2.5 <-- 32 bit glibc-headers-2.5 ksh-20060214 libaio-0.3.106 libaio-0.3.106 <-- 32 bit libaio-devel-0.3.106 libaio-devel-0.3.106 <-- 32 bit libgcc-4.1.2

18. System Requirements (Cont.) The following or later version of packages for Oracle Enterprise Linux 5, and Red Hat Enterprise Linux 5 must be installed: libgcc-4.1.2 <-- 32 bit libstdc++-4.1.2 libstdc++-4.1.2 <-- 32 bit libstdc++-devel-4.1.2 make-3.81 numactl-devel-0.9.8.x86_64 sysstat-7.0.2 unixODBC-2.2.11 unixODBC-2.2.11 <-- 32 bit unixODBC-devel-2.2.11 unixODBC-devel-2.2.11 <-- 32 bit

19. System Requirements (Cont.) Kernel settings for x86-64 Linux Redhat 5 system: kernel.sem = 250 32000 100 128 semmsl 250 semmns 32000 semopm 100 semmni 128 shmmni 4096 net.ipv4.ip_local_port_range = 9000 65500 fs.aio-max-nr = 1048576 fs.file-max = 6815744

20. System Requirements (Cont.) Kernel settings for x86-64 Linux Redhat 5 system: kernel.shmall = 2097152 kernel.shmmax = 536870912 kernel.shmmni = 4096 net.core.rmem_default = 262144 net.core.rmem_max = 4194304 net.core.wmem_default = 262144 net.core.wmem_max = 1048586

21. System Requirements (Cont.) Add the following lines in the /etc/security/limits.conf file: oracle soft nproc 2047 oracle hard nproc 16384 oracle soft nofile 1024 oracle hard nofile65536 If it does not already exist, add the following line to the /etc/pam.d/login file. session required pam_limits.so Set umask to 022

22. Database Requirements Database Initialization Parameters cluster_database= TRUE (Only for Oracle RAC Database) max_commit_propogation_delay = 0 (Only for Oracle RAC Database) compatible = 10.2.0.1.0 or higher remote_login_passwordfile = SHARED or EXCLUSIVE statistics_level = TYPICAL timed_statistics = TRUE undo_management = AUTO

23. Database Requirements (Cont.) Once the database is installed, Configure the init.oraparameters. workarea_size_policy = AUTO db_block_size = 8192 or greater log_buffer = 10485760 or greater processes = 500 or greater session_cached_cursors = 200 or greater open_cursors = 300 or greater

24. Database Requirements (Cont.) Other Parameters instance_groupsAs described in Oracle Database Reference Guide job_queue_processes = 10(For Upgrade) If you are upgrading Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, then ensure that you set the value to 0 before upgrading. And after upgrading, reset it to the original value that existed before upgrading the product. memory_targetAs described in Oracle Database Reference Guide sga_targetAs described in Oracle Database Reference Guide

25. Database Requirements (Cont.) Setting the undo tablespaceBy default the UNDO tablespacedatafile (commonly undotbs1.dbf) may not be aqequately sized for Grid Control's expectations, which is 200MB. To check this value prior to installing Grid Control, use the following query:select file_name,bytes/1048576 from dba_data_files where tablespace_namelike '%UNDOT%'; If the value comes back with less than 200, adjust with the following statement:alter database datafile '<filepath_to>/undotbs1.dbf' resize 200M;

26. Database Requirements (Cont.) Listener Registration Validate using the lsnrctl status commandExample output: Services Summary...Service "db11.oracle.com" has 1 instance(s).Instance "db11", status READY, has 1 handler(s) for this service... NOTE: Do not continue until this works for your databases

27. Database Requirements (Cont.) See the following two notes for help with listener registration. Note: 433693.1 Service / Instance Not Registering with Listener Note: 235562.1 Issues affecting Automatic Service Registration Network Bug 6874286 with host files. If using an 11.2 database beware of a Network bug using hosts files: Bug 6874286Note: 561429.1 Connections To 11g TNS Listener are Slow.

28. Database Requirements (Cont.) Verify connectivity to the databaseMy need to update the tnsnames.ora file Check the DBSNMP account in the Database.Make a sqlplus connection to the database using the DBSNMP account. If the account is locked, unlock the account and test connectivity again. Note: The Agent that installs with Grid Control requires this account. Run sql scripts on the database.Run the dbmspool.sql script and utlrp.sql scripts in the database.

29. Database Requirements (Cont.) Remove the Dbconsole/DbcontrolContains the SYSMAN schema that was created when the database was installed. It must be removed before the installation of Grid Control can begin. Run the following to remove the DBconsole from the database. EMCA syntax for 10/11g Database Repository: Set the ORACLE_HOME to the Oracle home of the database. Set the ORACLE_SID to the SID of the database $<ORACLE_HOME>bin/emca -deconfigdbcontroldb -repos drop Note 278100.1: How to Drop and Recreate the DB Control Repository

30. Database Requirements (Cont.) Check and verify environment before Grid Control is installed. Two 32bit OS Packages that are needed in the 64 bit environment as well as the ones that were checked earlier compat-libstdc++-296-2.96-138 (i386) compat-db-4.2.52-5.1 (i386) LD_LIBRARY_PATH should not be set.

31. Middle Tier Requirements Java JDK version 1.6.0_18 WebLogic 10.3.2 1 –GHz CPU processor Minimum of 1 Gb RAM (2 GB of RAM recommended) 8-bit color depth (256 colors) is required for graphical-mode installation

32. Middle Tier Installation Follow Note 1063112.1 Example for Installing WebLogic Server 10.3.2 on OEL 5.3 x86_64 Under the goal section of the note, there is a link to a pdf file showing the GUI installation steps and screens for the WebLogicinstall. To locate the correct file follow steps below. Example command line to start the installaer: $JAVA_HOME/bin/java -d64 -jar /u01/tmp/wls1032_generic.jar

33. Database Repository Install and patch the Oracle Binaries Use the DBCA to create a database Use the built-in “General Purpose or Transaction processing” template Use the “Same Administrative Password” for all accounts Use the Flash Recovery area, set the size to 512Mb Use the DBCA to create a database (cont.) Disable Archiving Set Memory at 350M or more Ensure that the UNDO tablespace and the TEMP tablespace are autoextensiblein the existing, certified Oracle Database. Moreover, resize UNDO tablespaceto >200M.

34. Database Repository (Cont.) Set/define Init.ora parameters Note: Once these are set, you will need to restart the database for the setting to take affect. SQL> alter system set "_optimizer_distinct_agg_transform"=false scope=spfile; SQL> alter system set log_buffer=10485760 scope=spfile; SQL> alter system set processes = 500 scope=spfile; SQL> alter system set session_cached_cursors=200 scope=spfile; SQL> alter database datafile'/u01/app/ora11gr2/oradata/EMREP/undotbs01.dbf‘ resize 256M;

35. Database Repository (Cont.) Check that fine grained access control is installed.select value from v$option where parameter = 'Fine-grained access control'; DeinstallDB Control./emca -deconfigdbcontroldb -repos drop Validate the database and Listener Remember to run the root.sh and/or allroot.sh scripts as instructed.

36. WebLogic Server Installation Some notes and tips On the Choose Product and Components screen in the installation process, UNCHECK “Oracle Coherence” Can use Sun Java SDK or the Jrocket java for running the WebLogic Server. At the end of the Weblogic install a checkbox selection is presented for quickstart of Weblogic. The run quickstart checkbox should not be checked and Weblogic should not be started, as this will interfere with the 11.1.0.1 OMS Installation. Only the binaries for Weblogic should be installed. Once WebLogic server has been install, it must be patched. See Oracle Note 1063112.1 Grid Control 11g: Example for Installing WebLogic Server 10.3.2 on OEL 5.3 x86_64 for instructions on installing patch WDJ7.

37. Oracle Grid Control Installation and setup. Download Grid Control 11.1.0.1 from OTN.http://www.oracle.com/technology/software/products/oem/index.html1.6.0_18 java, and 10.3.2 WebLogic must be installed prior to the installation. Make sure the Database and Listener are started and running. Install 11.1.0.1 Grid Control.Note 1059516.1 Step by step Installation of 11.1 Grid Control shows a graphical representation of the steps during the Grid Control installationThe install guide, Part Number E15838-05, can also be used for step by step installation. Once installed, launch the Grid Control website and make sure it loads.Usually on https://servername.domain:7799/em

38. Grid Control Agents Installation Notes Version 10.2.0.5 the OUI (Oracle Universal Installer) a response file agent deployment Version 11.1.0.1 a response file agent deployment

39. Grid Control Agents Installation Notes Information from Grid Control server will be required Management Server host and port number Connection agent password Hardware requirements Standalone agent 1024MB physical memory 850MB Disk space (not including download file)

40. Any Questions about the setup?

41. Break Time

42. Grid Control Start and Stop Once the installation is completed the grid control could be accessed athttp://<server-name>:<port>/em (the port number is in general 4889. If not, see $ORACLE_HOME/sysman/setupinfo.txt) Commands to START the Grid Control: <Parent_Directory>/db10g/bin/dbstart<Parent_Directory>/oms10g/opmn/bin/opmnctlstartall<Parent_Directory>/agent10g/bin/emctl start agent Commands to STOP the Grid Control: <Parent_Directory>/agent10g/bin/emctl stop agent<Parent_Directory>/oms10g/opmn/bin/opmnctlstopall<Parent_Directory>/db10g/bin/dbshutNOTE: The dbstart and dbshut commands require the "/etc/oratab" file to be edited to allow auto startup/shutdown.

43. Grid Control Main Window Initial Screen shows a dashboard of all monitored/ managed services.

44. Grid Control Main Window (Cont.)

45. Grid Control Main Window (Cont.)

46. Grid Control Main Window (Cont.)

47. Grid Control All Targets

48. Grid Control All Targets (Cont.)

49. Grid Control All Targets (Cont.)

50. Grid Control All Targets (Cont.)

51. Grid Control Down Targets

52. Grid Control Down Targets(Cont.)

53. Grid Control Host Targets

54. Grid Control Host Targets (Cont.)

55. Grid Control Host Targets (Cont.)

56. Grid Control Host Targets (Cont.)

57. Grid Control Database Targets

58. Grid Control Database Targets (Cont.)

59. Grid Control Database Targets (Cont.)

60. Grid Control Database Targets (Cont.)

61. Grid Control Target Database (Cont.)

62. Grid Control Target Database (Cont.)

63. Grid Control Database Targets (Cont.)

64. Grid Control Database Target

65. Grid Control Database Target (Cont.)

66. Grid Control Database Target (Cont.)

67. Grid Control Database Target (Cont.)

68. Grid Control Database Target (Cont.)

69. Grid Control Database Target (Cont.)

70. Grid Control Database Target (Cont.)

71. Grid Control Database Target (Cont.)

72. Grid Control Database Target (Cont.)

73. Grid Control Database Target (Cont.)

74. Grid Control Database Target (Cont.)

75. Grid Control Database Target (Cont.)

76. Grid Control Database Target (Cont.)

77. Grid Control Database Target (Cont.)

78. Grid Control Database Target (Cont.)

79. Grid Control Database Target (Cont.)

80. Grid Control Database Target (Cont.)

81. Grid Control Database Target (Cont.)

82. Grid Control Database Target (Cont.)

83. Any Questions about the setup?

84. Break Time

85. Grid Control Users and Groups Do NOT attempt to create Grid users at the database. Permissions issue Interface issues Use Target Groups to limit access Define Target lists Associate Grid users to Target Groups How?

86. Grid Control Users and Groups (cont.) Click on Setup located in the upper right corner of any of the Grid Control Screens.

87. Grid Control Users and Groups (cont.)

88. Grid Control Users and Groups (cont.)

89. Grid Control Users and Groups (cont.)

90. Grid Control Users and Groups (cont.) RolesUsed to group Enterprise Manager system and target privileges, and grant these to administrators or to other roles. Privileges give the administrator rights to perform management actions within Enterprise Manager. Using roles and privileges allows you to manage security across all functional areas of Enterprise Manager.Creating roles is an easy way to grant a predefined set of privileges to a group of administrators. If you change a role, the changes are automatically propagated to all administrators who are assigned that role.Roles can be based on: Geographic location. For example, you can define a role for UK administrators to manage UK systems. Line of business. For example, you can define a role for administrators of the human resource systems. Any other IT model.

91. Grid Control Users and Groups (cont.) AdministratorsDatabase users defined in the Management Repository who can log in to Enterprise Manager to perform management tasks. The breadth of management tasks available in Enterprise Manager depends on the privileges and roles assigned to the administrators.There are two types of accounts: Super Administrator AccountEnterprise Manager is installed with a default super administrator account named SYSMAN. During the installation, you are prompted provide a password for SYSMAN. You use the SYSMAN account for the initial login to Enterprise Manager. The super administrator account cannot be deleted or renamed.The super administrator account can manage all other administrator accounts and set up all administrator credentials Administrator AccountAdministrator accounts provide users permission to perform administrative tasks and access administrative information.

92. Grid Control Users and Groups (cont.) Other useful items in the Setup Page Notification Methodsallow you to define different mechanisms for sending notifications. These include e-mail, SNMP traps, or running custom scripts—or all three. Once defined, these methods can then be used with Notification Rules for sending notifications to administrators as a result of alert occurrences. Registration Passwordsset registration passwords to secure Management Agents against any Management Service that uses the central Management Repository. Blackoutsallow Enterprise Manager administrators to suspend any data collection activity on one or more monitored targets

93. Grid Control Users and Groups (cont.)

94. Grid Control Users and Groups (cont.)

95. Grid Control Users and Groups (cont.)

96. Grid Control Users and Groups (cont.)

97. Grid Control Users and Groups (cont.)

98. Grid Control Users and Groups (cont.)

99. Grid Control Users and Groups (cont.)

100. Grid Control Users and Groups (cont.)

101. Grid Control Users and Groups (cont.)

102. Any Questions?

103. Grid Control Review The architecture of the OEM for Grid Control has three distinct components: the collection agent (Oracle Management Agent or OMA) the aggregation agent (Oracle Management Server or OMS) the repository agent (Oracle Management Repository or OMR) The OMA runs on the target host and collects information on the hardware, operating system, and applications that run on the target. The OMS runs on one or two servers and collects the data generated by the OMAs. The OMS pulls the information from the OMAs and aggregates the collections into the repository. The OMS also acts as the user-interface — by generating web-pages for database administrators to view the status of systems and services. The OMR comprises an instance of the Oracle database that stores the data collected by the OMS.

104. Grid Control Review (Cont.) Graphical View of How OracleGrid Control Works

105. Grid Control Review (Cont.) Installation order for all products: System Required Packages Oracle Database Services and any needed patches and/or CPU updates. Create a database to be used as a repository Install the required version of Java SDK version 1.6.0_18 WebLogic Server and required patches Grid Control Services Grid Control Agents on systems to be monitored/managed

106. Grid Control Review (Cont.) For a small environment (< 100 monitored targets), you need following servers parameters: For the OMS: 2 CPUs, 4 GB RAM and 7 GB space excluding the installation which is 5.5 GB For the Management Repository: 2 CPUs, 2 GB RAM (3 recommended) and 50 GB space

107. Grid Control Review (Cont.) For the Middle Tier (WebLogic service) Java JDK version 1.6.0_18 WebLogic 10.3.2 For Grid Agent on each target server Standalone agent 1024MB physical memory 850MB Disk space (not including download file)

108. Grid Control Review (Cont.) Do NOT attempt to create Grid users at the database. Permissions issue Interface issues Use Target Groups to limit access Define Target lists Associate Grid users to Target Groups

109. Any Questions?

110. Grid Control Source OEL5Complete Steps to Install 11.1.0.1 OMS Using 11.2 Database on 64 Bit RedHat 5 or OEL5 [ID 1130958.1] Grid Control 11g: Required External Components and Versions for Grid Control 11.1.0.1.0 [ ID 1106105.1 ] Oracle Enterprise Manager Grid Control Basic Installation Guide 11g Release 1 (11.1.0.1.0) Part Number E15838-06 Oracle Database Reference Guide available at: http://www.oracle.com/technology/documentation/database.html NOTE: 1059516.1 - Step by step Installation of 11.1 Grid control NOTE: 1063112.1 - Grid Control 11g: Example for Installing WebLogic Server 10.3.2 on OEL 5.3 x86_64 NOTE: 1063587.1 - Grid Control 11g: Example jdk1.6 0n Linux x86_64 Install for WebLogic Server 10.3.2 and Grid Control 11.1.0.1.0 NOTE: 1064441.1 - Grid Control 11g: Database Considerations for the Grid Control 11.1.0.1.0 Repository NOTE: 235562.1 - Issues Affecting Automatic Service Registration NOTE: 278100.1 - How To Drop, Create And Recreate DB Control In A 10g Database NOTE: 428665.1 - Installation Checklist for Testing Networking Configurations Prior to Installing EM Components NOTE: 433693.1 - Service / Instance Not Registering with Listener NOTE: 561429.1 - Connections To 11g TNS Listener are Slow. Google searches Trial and error efforts

111. Thank You