NetIQ AppManager for Oracle Database on Windows Management Guide

Transcription

1 NetIQ AppManager for Oracle Database on Windows Management Guide February

2 Legal Notice THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non-dod acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement NetIQ Corporation. All Rights Reserved. For information about NetIQ trademarks, see

3 Contents About this Book and the Library 5 About NetIQ Corporation 7 1 Introduction to AppManager for Oracle Database Monitoring Oracle Features and Benefits Installing AppManager for Oracle Database System Requirements Installing the Module Deploying the Module with Control Center Silently Installing the Module Post-installation Considerations Discovering Oracle Database Resources Upgrading Knowledge Script Jobs Oracle Knowledge Scripts How Knowledge Scripts Access Oracle Databases AlertLog BGProc Block BlockingSessions Cache CallRate CallsPerTransaction ConfigDB ConsistentChangeRatio ContinuedRowRatio DatabaseDown DatafileSpace DiskSpaceAvail OpenCursors RecursiveToUserCallRatio RedoLogContention RedoLogSpaceWaitRatio Report_BackgroundProcess Report_CacheHitRatio Report_DatabaseAvailability Report_DatafileSpace Report_DiskSpaceAvailable Report_TablespaceAvailable Report_TransactionRate Report_UserLocks RollBackSegmentContention RowSourceRatio Contents 3

4 3.29 RunSql SegmentExtentAvail SortOverflowRatio SysStat TablespaceAvail TopCpuUsers TopIOUsers TopLockUsers TopMemoryUsers TransactionRate UserCallsPerParse UserRollbackRatio UserSessions NetIQ AppManager for Oracle Database on Windows Management Guide

5 About this Book and the Library The NetIQ AppManager product (AppManager) is a comprehensive solution for managing, diagnosing, and analyzing performance, availability, and health for a broad spectrum of operating environments, applications, services, and server hardware. AppManager provides system administrators with a central, easy-to-use console to view critical server and application resources across the enterprise. With AppManager, administrative staff can monitor computer and application resources, check for potential problems, initiate responsive actions, automate routine tasks, and gather performance data for real-time and historical reporting and analysis. Intended Audience This guide provides information for individuals responsible for installing an AppManager module and monitoring specific applications with AppManager. Other Information in the Library The library provides the following information resources: Installation Guide for AppManager Provides complete information about AppManager pre-installation requirements and step-bystep installation procedures for all AppManager components. User Guide for AppManager Control Center Provides complete information about managing groups of computers, including running jobs, responding to events, creating reports, and working with Control Center. A separate guide is available for the AppManager Operator Console. Administrator Guide for AppManager Provides information about maintaining an AppManager management site, managing security, using scripts to handle AppManager tasks, and leveraging advanced configuration options. Upgrade and Migration Guide for AppManager Provides complete information about how to upgrade from a previous version of AppManager. Management guides Provide information about installing and monitoring specific applications with AppManager. Help Provides context-sensitive information and step-by-step guidance for common tasks, as well as definitions for each field on each window. The AppManager library is available in Adobe Acrobat (PDF) format from the AppManager Documentation page of the NetIQ website. About this Book and the Library 5

6 6 NetIQ AppManager for Oracle Database on Windows Management Guide

7 About NetIQ Corporation We are a global, enterprise software company, with a focus on the three persistent challenges in your environment: Change, complexity and risk and how we can help you control them. Our Viewpoint Adapting to change and managing complexity and risk are nothing new In fact, of all the challenges you face, these are perhaps the most prominent variables that deny you the control you need to securely measure, monitor, and manage your physical, virtual, and cloud computing environments. Enabling critical business services, better and faster We believe that providing as much control as possible to IT organizations is the only way to enable timelier and cost effective delivery of services. Persistent pressures like change and complexity will only continue to increase as organizations continue to change and the technologies needed to manage them become inherently more complex. Our Philosophy Selling intelligent solutions, not just software In order to provide reliable control, we first make sure we understand the real-world scenarios in which IT organizations like yours operate day in and day out. That's the only way we can develop practical, intelligent IT solutions that successfully yield proven, measurable results. And that's so much more rewarding than simply selling software. Driving your success is our passion We place your success at the heart of how we do business. From product inception to deployment, we understand that you need IT solutions that work well and integrate seamlessly with your existing investments; you need ongoing support and training post-deployment; and you need someone that is truly easy to work with for a change. Ultimately, when you succeed, we all succeed. Our Solutions Identity & Access Governance Access Management Security Management Systems & Application Management Workload Management Service Management About NetIQ Corporation 7

8 Contacting Sales Support For questions about products, pricing, and capabilities, contact your local partner. If you cannot contact your partner, contact our Sales Support team. Worldwide: United States and Canada: Website: Contacting Technical Support For specific product issues, contact our Technical Support team. Worldwide: North and South America: Europe, Middle East, and Africa: +353 (0) Website: Contacting Documentation Support Our goal is to provide documentation that meets your needs. The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at documentation. You can also Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you. Contacting the Online User Community NetIQ Communities, the NetIQ online community, is a collaborative network connecting you to your peers and NetIQ experts. By providing more immediate information, useful links to helpful resources, and access to NetIQ experts, NetIQ Communities helps ensure you are mastering the knowledge you need to realize the full potential of IT investments upon which you rely. For more information, visit community.netiq.com. 8 NetIQ AppManager for Oracle Database on Windows Management Guide

9 1 1Introduction to AppManager for Oracle Database Oracle Database is a powerful database that also offers administration and performance monitoring features to increase its manageability and reliability. Designed for high availability, Oracle Database stores and provides access to electronic data in the form of Online Transaction Processing (OLTP) databases and data warehouses. This chapter explains the advantages of using AppManager to monitor Oracle and describes how AppManager lets you view Oracle resources. 1.1 Monitoring Oracle Any enterprise whose viability depends on unimpeded access to information must carefully scrutinize the performance of its database management system. A faltering system can interfere with internal operations, such as CRM and ERP systems, as well as a company s direct contact with its customers, such as ATM or stock transactions, or orders placed via a Web site. When you implement a database management system like Oracle Database, you might want to monitor how the components of the system perform in order to tune the system to your specific needs and provide benchmark values for subsequent performance evaluation. Understanding how your system functions under an optimal configuration lets you quickly identify degraded performance and take steps to preempt or rectify problems, as well as plan for upgrades or reconfiguration in anticipation of greater demands on the system. 1.2 Features and Benefits AppManager provides several Knowledge Scripts designed to give you a comprehensive view of how Oracle Database performs on your servers. The capabilities of the Knowledge Scripts in the Oracle category include: Monitoring the Oracle alert log for specific entries related to database operations and error conditions. Monitoring the total number of physical read/write operations per second and the total memory usage for Oracle background processes. Monitoring input/output (I/O) activity at the block level. Monitoring the hit ratios for the buffer cache, library cache, and the data dictionary. Monitoring the number of database calls from all applications and processes accessing a database instance. Monitoring the ratio of continued rows fetched to all rows fetched. Monitoring the up/down status of databases. Monitoring the amount of disk space available for the archive log file, the background process log file, and user log files for a database. Monitoring rollback segment contention for a database. Monitoring the percentage of rows retrieved using full table scans. Introduction to AppManager for Oracle Database 9

10 Monitoring the sort overflow ratio. Monitoring the percentage of attempted application transactions that are rolled back. For aspects of Oracle Database that you choose to monitor, you can set thresholds that you understand as the boundaries of optimal performance, and instruct AppManager to raise events when those thresholds are breached. In addition to monitoring, you can use Oracle Knowledge Scripts to collect performance data for use in reports. AppManager lets you generate reports that range in scope from minute-by-minute values to monthly values over a period of years, and range in purpose from evaluating a narrow window of performance data to illustrating trends to aid in capacity planning. 10 NetIQ AppManager for Oracle Database on Windows Management Guide

11 2 2Installing AppManager for Oracle Database This chapter provides installation instructions and describes system requirements for AppManager for Oracle Database. This chapter assumes you have AppManager installed. For more information about installing AppManager or about AppManager system requirements, see the Installation Guide for AppManager, which is available on the AppManager Documentation page. 2.1 System Requirements For the latest information about supported software versions and the availability of module updates, visit the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below. AppManager for Oracle Database has the following system requirements: Software/Hardware NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Oracle computers you want to monitor (AppManager agents), and on all console computers Microsoft Windows operating system on agent computers Version 7.0 or later Support for Windows Server 2008 on AppManager 7.x requires AppManager Windows Agent hotfix or later. For more information, see the AppManager Suite Hotfixes page. One of the following: Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 (32-bit and 64-bit) Windows Server 2003 R2 (32-bit and 64-bit) Installing AppManager for Oracle Database 11

12 Software/Hardware Oracle Database on the agent computers Version A version of Oracle Database through 12c ( x) for Microsoft Windows, appropriate for your operating system. Notes On 32-bit computers, the Microsoft ODBC Driver for Oracle must be installed and is usually installed with your operating system. A newer version of the driver might be available in the latest Microsoft Data Access Components package from the Microsoft Download Center. On 64-bit computers, the 64-bit Oracle Provider for OLE DB should be installed for your version of Oracle Database. You can install this from the Oracle Client or Oracle Data Access Components (ODAC) software packages. This module supports only 64-bit Oracle Database software on 64-bit Windows operating systems. This module does not support 32-bit Oracle Database software on 64-bit Windows operate systems. 2.2 Installing the Module Run the module installer on the Oracle Database computers you want to monitor (agents) to install the agent components, and run the module installer on all console computers to install the Help and console extensions. Access the AM70-Oracle-7.x.x.0.msi module installer from the AM70_Oracle_7.x.x.0 selfextracting installation package on the AppManager Module Upgrades & Trials page. For Windows environments where User Account Control (UAC) is enabled, install the module using an account with administrative privileges. Use one of the following methods: Log in to the server using the account named Administrator. Then, run the module installer.msi file from a command prompt or by double-clicking it. Log in to the server as a user with administrative privileges and run the module installer.msi file as an administrator from a command prompt. To open a command-prompt window at the administrative level, right-click a command-prompt icon or a Windows menu item and select Run as administrator. You can install the Knowledge Scripts and the Analysis Center reports into local or remote AppManager repositories (QDBs). The module installer installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager. 12 NetIQ AppManager for Oracle Database on Windows Management Guide

13 You can install the module manually, or you can use Control Center to deploy the module to a remote computer where an agent is installed. For more information, see Section 2.3, Deploying the Module with Control Center, on page 14. However, if you use Control Center to deploy the module, Control Center only installs the agent components of the module. The module installer installs the QDB and console components as well as the agent components on the agent computer. To install the module: 1 Double-click the module installer.msi file. 2 Accept the license agreement. 3 Review the results of the pre-installation check. You can expect one of the following three scenarios: No AppManager agent is present: In this scenario, the pre-installation check fails, and the installer does not install agent components. An AppManager agent is present, but some other prerequisite fails: In this scenario, the default is to not install agent components because of one or more missing prerequisites. However, you can override the default by selecting Install agent component locally. A missing application server for this particular module often causes this scenario. For example, installing the AppManager for Microsoft SharePoint module requires the presence of a Microsoft SharePoint server on the selected computer. All prerequisites are met: In this scenario, the installer installs the agent components. 4 To install the Knowledge Scripts into the QDB: 4a Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts, object types, and SQL stored procedures. 4b Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name. 5 (Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. 6 (Conditional) If you use Control Center 8.x, run the module installer only for the primary QDB. Control Center automatically replicates this module to secondary QDBs. 7 Run the module installer on all console computers to install the Help and console extensions. 8 Run the module installer on the Oracle Database computers you want to monitor (agents) to install the agent components. 9 Perform required configuration tasks appropriate for your environment. For more information, see Section 2.5, Post-installation Considerations, on page If you have not discovered Oracle Database resources, run the Discovery_Oracle Knowledge Script on all agent computers where you installed the module. For more information, see Section 2.6, Discovering Oracle Database Resources, on page To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.7, Upgrading Knowledge Script Jobs, on page 21. After the installation has completed, you can find a record of problems encountered in the Oracle_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\ServerName folder. NOTE: If you are monitoring Oracle Database on a 64-bit Microsoft Windows agent computer, and you switch from 32-bit to 64-bit Oracle client software (or from 64-bit to 32-bit), you must uninstall and reinstall NetIQ AppManager for Oracle Database. This ensures that the correct NetIQ library is installed for the Oracle client running on the agent computer. Installing AppManager for Oracle Database 13

14 2.3 Deploying the Module with Control Center You can use Control Center to deploy the module to a remote computer where an agent is installed. This topic briefly describes the steps involved in deploying a module and provides instructions for checking in the module installation package. For more information, see the Control Center User Guide for AppManager, which is available on the AppManager Documentation page Deployment Overview This section describes the tasks required to deploy the module on an agent computer. To deploy the module on an agent computer: 1 Verify the default deployment credentials. 2 Check in an installation package. For more information, see Section 2.3.2, Checking In the Installation Package, on page Configure an address to receive notification of a deployment. 4 Create a deployment rule or modify an out-of-the-box deployment rule. 5 Approve the deployment task. 6 View the results Checking In the Installation Package You must check in the installation package, AM70-Oracle-7.x.x.0.xml, before you can deploy the module on an agent computer. To check in a module installation package: 1 Log in to Control Center using an account that is a member of a user group with deployment permissions. 2 Navigate to the Deployment tab (for AppManager 8.x) or Administration tab (for AppManager 7.x). 3 In the Deployment folder, select Packages. 4 On the Tasks pane, click Check in Deployment Packages (for AppManager 8.x) or Check in Packages (for AppManager 7.x). 5 Navigate to the folder where you saved AM70-Oracle-7.x.x.0.xml and select the file. 6 Click Open. The Deployment Package Check in Status dialog box displays the status of the package check in. 7 To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.7, Upgrading Knowledge Script Jobs, on page Silently Installing the Module To silently (without user intervention) install the module, run the following command from the folder in which you saved the module installer: msiexec.exe /i "AM70-Oracle-7.x.x.0.msi" /qn where x.x is the actual version number of the module installer. 14 NetIQ AppManager for Oracle Database on Windows Management Guide

15 To create a log file that describes the operations of the module installer, add the following flag to the command noted above: /L* "AM70-Oracle-7.x.x.0.msi.log" The log file is created in the folder in which you saved the module installer. NOTE: To perform a silent install on an AppManager agent running Windows Server 2008 R2, open a command prompt at the administrative level and select Run as administrator before you run the silent install command listed above. To silently install the module to a remote AppManager repository, you can use Windows authentication or SQL authentication. Windows authentication: AM70-Oracle-7.x.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_MOINSTALL=0 MO_B_SQLSVR_WINAUTH=1 MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName SQL authentication: AM70-Oracle-7.x.x.0.msi /qn MO_B_QDBINSTALL=1 MO_B_MOINSTALL=0 MO_B_SQLSVR_WINAUTH=0 MO_SQLSVR_USER=SQLLogin MO_SQLSVR_PWD=SQLLoginPassword MO_SQLSVR_NAME=SQLServerName MO_QDBNAME=AM-RepositoryName 2.5 Post-installation Considerations After installing AppManager for Oracle Database, depending on your database setup, you might need to complete the following post-installation processes. You should complete all processes relevant to your setup before you begin discovering Oracle Database servers with AppManager Setting Up Oracle Database Accounts Before running the Discovery_Oracle Knowledge Script, use the Oracle Database administration tools to set up Oracle Database accounts that AppManager Knowledge Scripts use. Give the accounts the privilege Select any table, and connect to an Oracle Database to monitor. If you need more restrictive privileges for a specific database, configure the account with SELECT privileges to the following Oracle Database tables: dba_data_files dba_extents dba_rollback_segs dba_tables dba_temp_files sys.fet$ sys.ts$ v_$bgprocess v_$datafile dba_extents dba_free_space dba_segments dba_tablespaces dba_users sys.seg$ v_$archive_dest v_$database v_$instance Installing AppManager for Oracle Database 15

16 v_$librarycache v_$lock v_$process v_$session v_$statname v_$thread v_$lock v_$parameter v_$rowcache v_$sesstat v_$sysstat v_$version NOTE: One exception is the RunSql Knowledge Script. Depending on the type of SQL statement you run, you might need to grant privileges on additional tables in the Oracle database Configuring the Oracle Database Server Before running the Discovery_Oracle Knowledge Script for the first time, configure the Oracle Database server using the ckoracle.exe command-line utility. You need to pass specific parameters to the ckoracle.exe utility to complete the server configuration. The ckoracle.exe utility generates the system Data Source Name (DSN), which is required to configure the Oracle Database server. The following is an example of a generated system DSN: C:\Documents and Settings\Administrator>ckoracle -setup -user system -password netiq123 -netiqms central03 -netiqmc accthome OracDb10g_1$ORCL The ckoracle.exe utility automatically configures the Oracle Database server. The following example describes the typical information you need to configure the Oracle Database server: Oracle Database user name: admin02 Oracle Database password: xt4a9z AppManager management server on the computer named central03 Agent computer name (managed client): accthome To configure your Oracle Database server with this account information, enter the following at the command prompt: ckoracle.exe -setup -user admin02 -password xt4a9z -netiqms central03 -netiqmc accthome 16 NetIQ AppManager for Oracle Database on Windows Management Guide

17 NOTE The program displays an error if you omit even a single configuration parameter. The following is a typical error message: ERROR - The -user, -password, -netiqms, and -netiqmc flags must be specified with the -setup option. Type ckoracle -help for more information. If the ckoracle.exe utility cannot contact the AppManager management server, the Oracle credentials will not be properly stored in the QDB, which causes the Discovery_Oracle Knowledge Script to fail. In this situation, manually enter the Oracle credentials into AppManager Security Manager. For more information, see Section 2.5.3, Configuring Permissions for Running Oracle Knowledge Scripts, on page 18. Use the -help parameter with the ckoracle.exe command-line utility to list all ckoracle parameters. To configure AppManager for Oracle Database on each agent computer: 1 On your Oracle Database server, open a command-prompt window. 2 Switch to the AppManager program directory on this server. The default AppManager installation directory is C:\Program Files\NetIQ\AppManager\bin. 3 At the command prompt, type the following: ckoracle.exe -setup -user oracle_user_account -password password -netiqms ms_computer_name -netiqmc oracle_computer_name For oracle_user_account password ms_computer_name oracle_computer_name Substitute The name of the Oracle Database user account, which you specify when you run the Discovery Knowledge Script. The same user account needs to be set up for each database you want to discover. The password for the Oracle Database user account The name of the computer on which your AppManager management server is running The name of the computer on which Oracle Database is running 4 After running ckoracle.exe, launch AppManager Security Manager and, on the Oracle tab, confirm that Security Manager correctly populated the Oracle account information for the Oracle Database server. 5 (Conditional) To configure AppManager for Oracle Database on 64-bit Oracle server computers, perform the following additional steps: 5a Install the 32-bit or 64-bit Oracle Provider for OLE DB software by installing the Oracle Client or ODAC software for the version of Oracle Database being monitored on the agent computer. 5b From the Start menu, click Programs and select the name of your Oracle home directory for your Oracle database or client software. 5c Click Configuration and Migration Tools, and then click Net Configuration Assistant. Installing AppManager for Oracle Database 17

18 5d Select Local Net Service Name configuration and follow the instructions in the wizard to create a service name entry for each Oracle database that will be monitored on the local agent computer. 5e Check that the service names added match with the databases to be monitored using the Test option in the Local Net Service Name configuration or open the tnsnames.ora file manually Configuring Permissions for Running Oracle Knowledge Scripts AppManager for Oracle Database uses the AppManager Security Manager extension to securely supply Oracle Database user account information to the Oracle Knowledge Scripts. As part of the process described in Section 2.5.2, Configuring the Oracle Database Server, on page 16, Oracle Database account information is automatically made available to Security Manager. However, you might want to change or update this information later. For instructions on using Security Manager, see the Administrator Guide for AppManager. NOTE: You should have all of your Oracle Database account information (database name, user account name, home name, and password) ready before using Security Manager. The information you enter into Security Manager is stored in the AppManager repository, but Security Manager cannot verify the accuracy of the information you provide. As a result, Knowledge Scripts that you try to run using the corresponding Oracle Database user account fail. On the Oracle tab in Security Manager for each agent computer, complete the following mandatory fields for the computer on which Oracle Database is running: Field User Password Confirm password Database Description Name of the Oracle Database user account that needs to be used to run Oracle Knowledge Scripts. Password associated with the user account. Provide the password again to verify that you typed it consistently. Home name and corresponding database to which the user name and password apply. You can also select the names of previously entered databases from the list. The format is HomeName$DatabaseName. For example, ORACLEHOME$ACC. NOTE: The Database list contains the databases that the ckoracle.exe utility found when you configured the Oracle Database server. For more information, see Section 2.5.2, Configuring the Oracle Database Server, on page NetIQ AppManager for Oracle Database on Windows Management Guide

19 2.5.4 Running Discovery After an Upgrade After you upgrade the AppManager agent on an Oracle Database server, you need to update the Oracle Database user information in the AppManager repository. After you update the user information, you must run the Discovery_Oracle Knowledge Script to discover Oracle Database servers. After discovery: Existing servers appear in the TreeView pane with the naming convention Oracle server:<server name> Server resources appear in the TreeView pane with the naming convention Oracle server:orahome After an upgrade, your old jobs continue to run. However, if you run the Discovery_Oracle Knowledge Script again, a new tree in the TreeView pane displays all installed Oracle Database servers in addition to the old tree that displays running old jobs. You should run new jobs on the new tree. Eventually, you need to delete the old tree. NOTE: If you are not running any jobs before upgrading, you should delete the old tree and then run the update Configuring the Agent to Monitor a Virtual Oracle Database Server Before you install the AppManager for Oracle Database module, ensure the virtual Oracle Database server is active on the cluster node on which you are installing the module. Discovery of the virtual Oracle Database can take place only when the virtual server is active. It is recommended that you move the active virtual server to each node before installing the module Monitoring Clustered Resources Microsoft Cluster Server (MSCS) is a built-in feature of Windows that allows servers to work together as one machine, to provide failover and increased availability of applications. MSCS can automatically detect and recover from server or application failures. MSCS facilitates moving server workload to balance utilization and to provide for planned maintenance without downtime. MSCS offers a Cluster Server Manager that allows you to install Oracle Database on multiple servers, and to place data files on a shared drive (such as a RAID) that is not on either computer. Oracle Database is then automatically registered with MSCS. Thus, when one computer fails, the cluster server switches to the application on the other computer. After installing the AppManager for Oracle Database module, you can run most Oracle Knowledge Scripts to monitor a virtual Oracle Database Server. However, to monitor clustered resources, you must run the appropriate MSCS Knowledge Script, not the Oracle Database equivalent. For example, to check the availability of Oracle Database services on a virtual Oracle Database server, run the MSCS_ResourceDown Knowledge Script, not the Oracle_DatabaseDown Knowledge Script. To monitor a virtual Oracle Database server: 1 Ensure you have a Windows domain, account name, and password for the AppManager agent to use. The agent on each node of a cluster must run as a Windows login account, not the LocalSystem account, for monitoring Oracle Database. Installing AppManager for Oracle Database 19

20 2 Run the AMAdmin_SetResDependency Knowledge Script to identify the shared logical drive where the virtual application resides, and define the services that must be available in the cluster in order to run Oracle Knowledge Script jobs. 3 Run the AMAdmin_SetResDependency Knowledge Script on all nodes in the cluster. In the Values tab of the Knowledge Script Properties dialog box, set the following parameters. Parameter Knowledge Script or job category Required available resources Required active services Type Oracle as the Knowledge Script category for which you want to specify resource dependencies. Type the name of the shared logical disk where the Oracle Database resides. For example, G: Type the Oracle services required to run Oracle Database Server. For example, OracleServiceSales 2.6 Discovering Oracle Database Resources Use the Discovery_Oracle Knowledge Script to discover configuration and resource information for Oracle Database servers. Before running discovery for the first time, you must complete a series of post-installation procedures. For more information, see Section 2.5, Post-installation Considerations, on page 15. If you delete or add a resource object, or if you make any other kind of change that might affect the monitoring of your resources, run the Discovery_Oracle Knowledge Script again to update your list of resource objects. In addition, if you are running this module on AppManager 8 or later, you can use the delta discovery feature in Control Center to run discovery on a schedule to more quickly detect changes to your environment. Set the Values tab parameters as needed: Description Username Specify the username for logging on to the Oracle server. The username must have permission to access Oracle on the target computer. Use Security Manager to specify which user accounts have access to specific computers. The default username is system. Raise event if discovery succeeds? Event severity when discovery succeeds Event severity when discovery fails Event severity when discovery partially succeeds This Knowledge Script always raises an event if the discovery job fails for any reason. In addition, you can set this parameter to y to raise an event if the job succeeds. The default is n. Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery succeeds. The default is 25. Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery fails. The default is 5. Set the severity level, from 1 to 40, to indicate the importance of an event in which discovery returns some data but also generates warning messages. The default is NetIQ AppManager for Oracle Database on Windows Management Guide

21 2.7 Upgrading Knowledge Script Jobs If you are using AppManager 8.x or later, the module upgrade process now retains any changes you might have made to the parameter settings for the Knowledge Scripts in the previous version of this module. Before AppManager 8.x, the module upgrade process overwrote any settings you might have made, changing the settings back to the module defaults. As a result, if this module includes any changes to the default values for any Knowledge Script parameter, the module upgrade process ignores those changes and retains all parameter values that you updated. Unless you review the management guide or the online Help for that Knowledge Script, you will not know about any changes to default parameter values that came with this release. You can push the changes for updated scripts to running Knowledge Script jobs in one of the following ways: Use the AMAdmin_UpgradeJobs Knowledge Script. Use the Properties Propagation feature Running AMAdmin_UpgradeJobs The AMAdmin_UpgradeJobs Knowledge Script can push changes to running Knowledge Script jobs. Your AppManager repository (QDB) must be at version 7.0 or later. Upgrading jobs to use the most recent script version allows the jobs to take advantage of the latest script logic while maintaining existing parameter values for the job. For more information, see the Help for the AMAdmin_UpgradeJobs Knowledge Script Propagating Knowledge Script Changes You can propagate script changes to jobs that are running and to Knowledge Script Groups, including recommended Knowledge Script Groups and renamed Knowledge Scripts. Before propagating script changes, verify that the script parameters are set to your specifications. New parameters might need to be set appropriately for your environment or application. If you are not using AppManager 8.x or later, customized script parameters might have reverted to default parameters during the installation of the module. You can choose to propagate only properties (specified in the Schedule and Values tabs), only the script (which is the logic of the Knowledge Script), or both. Unless you know specifically that changes affect only the script logic, you should propagate both properties and the script. For more information about propagating Knowledge Script changes, see the Running Monitoring Jobs chapter of the Control Center User Guide for AppManager. Installing AppManager for Oracle Database 21

22 2.7.3 Propagating Changes to Ad Hoc Jobs or Knowledge Script Groups You can propagate the properties and the logic (script) of a Knowledge Script to ad hoc jobs started by that Knowledge Script. Corresponding jobs are stopped and restarted with the Knowledge Script changes. You can also propagate the properties and logic (script) of a Knowledge Script to corresponding Knowledge Script Group members. After you propagate script changes to Knowledge Script Group members, you can propagate the updated Knowledge Script Group members to associated running jobs. Any monitoring jobs started by a Knowledge Script Group member are restarted with the job properties of the Knowledge Script Group member. To propagate changes to ad hoc Knowledge Script jobs or Knowledge Script Groups: 1 In the Knowledge Script view, select the Knowledge Script or Knowledge Script Group for which you want to propagate changes. 2 Right-click the script or group and select Properties propagation > Ad Hoc Jobs. 3 Select the components of the Knowledge Script that you want to propagate to associated ad hoc jobs or groups and click OK: Select Script Properties To propagate The logic of the Knowledge Script. Values from the Knowledge Script Schedule and Values tabs, such as schedule, monitoring values, actions, and advanced options. If you are using AppManager 8.x or later, the module upgrade process now retains any changes you might have made to the parameter settings for the Knowledge Scripts in the previous version of this module. 22 NetIQ AppManager for Oracle Database on Windows Management Guide

23 3 3Oracle Knowledge Scripts AppManager for Oracle Database on Windows provides the following Knowledge Scripts for monitoring Oracle Database resources. From the Knowledge Script view of Control Center, you can access more information about any NetIQ-supported Knowledge Script by selecting it and clicking Help. In the Operator Console, click any Knowledge Script in the Knowledge Script pane and press F1. Knowledge Script AlertLog BGProc Block BlockingSessions Cache CallRate CallsPerTransaction ConfigDB ConsistentChangeRatio ContinuedRowRatio DatabaseDown DatafileSpace DiskSpaceAvail OpenCursors RecursiveToUserCallRatio RedoLogContention RedoLogSpaceWaitRatio What It Does Scans the Oracle Database Alert log for a search string that you specify. Monitors the total memory usage and the total number of physical read/write (I/O) operations per second for Oracle background processes. Monitors block-level database activity. Monitors the number of user sessions that are blocking other processes from accessing the Oracle database. Monitors the frequency with which requested data and resources are retrieved from the buffer cache, data dictionary, and library cache. Monitors the demand placed on a database instance from all sources. Monitors the demand placed on a database instance by each transaction. Updates AppManager with information about the Oracle databases you want to monitor. Monitors the extent to which applications exercise the read consistency mechanism to ensure database consistency. Monitors rows that span more than one database block. Monitors a database and its services to verify whether they are running. Monitors the size of an Oracle datafile. Monitors the amount of disk space available for the archive log file, the background process log file, and user log files. Monitors the percentage of cursors opened per session, as well as the total number of cursors open in the system. Monitors the ratio of recursive calls to overall database user calls. Monitors the number of times that a process attempts to write an entry in the redo log buffer. Monitors the redo log space wait ratio, which measures memory allocation. Oracle Knowledge Scripts 23

24 Knowledge Script Report_BackgroundProcess Report_CacheHitRatio Report_DatabaseAvailability Report_DatafileSpace Report_DiskSpaceAvailable Report_TablespaceAvailable Report_TransactionRate Report_UserLocks RollBackSegmentContention RowSourceRatio RunSql SegmentExtentAvail SortOverflowRatio SysStat TablespaceAvail TopCpuUsers TopIOUsers TopLockUsers TopMemoryUsers TransactionRate UserCallsPerParse UserRollbackRatio What It Does Generates a report about total memory use, and the total number of physical read/write operations per second for Oracle background processes. Generates a report about buffer cache hit ratio, data dictionary hit ratio, and library cache hit ratio for Oracle servers. Generates a report about the up/down status of Oracle databases, and the OracleServer, OracleListener, and OracleStart services. Generates a report about the size (in MB) of Oracle Database data files. Generates a report about the amount of disk space (in MB) available for the archive, background process, and user log files. Generates a report about the free disk space available for tablespaces, disk space used by tablespaces, and the size of tablespaces. Generates a report about the number of transactions per second for Oracle databases. Generates a report about the number of user-held locks on an Oracle database. Monitors the ratio of wait counts to total requests in the rollback segment. Monitors the row source ratio, which measures the percentage of rows that were retrieved using full table scans. Runs SQL statements. Monitors the percentage of extents (extensions of free space) available to each segment in a tablespace. Monitors the sort overflow ratio, which measures the number of sorts that are using temporary segments. Retrieves statistics from the V$SYSSTAT table, which stores all the key statistics for a database instance. Monitors the percentage of disk space available to all the tablespaces in a database. Monitors the CPU time for current user sessions. Monitors physical reads and writes (I/O) for current user sessions. Monitors the current number of user-held locks on an Oracle database. Monitors memory usage (User Global Area and PGA) for current user sessions. Monitors the transaction rate for an Oracle database. Monitors the number of user calls per parse. Monitors the user rollback ratio for an Oracle database, which indicates the percentage of attempted application transactions that fail. 24 NetIQ AppManager for Oracle Database on Windows Management Guide

25 Knowledge Script UserSessions What It Does Monitors the total number of user sessions accessing an Oracle database. 3.1 How Knowledge Scripts Access Oracle Databases To gather the statistics and resource information needed to monitor an Oracle Database, an Oracle Knowledge Script must log on to that database. The Oracle user account controls access to the Oracle Database. The Oracle user s Windows and SQL Server privileges have no effect on access to an Oracle database. When you run a Knowledge Script on an Oracle Database, you specify an Oracle Database user account that has been set up on that database for the Username parameter. The corresponding password is retrieved from the Oracle repository and sent, in encrypted format, to the AppManager agent on the Oracle Database server. The password is decrypted by the AppManager agent, which uses it to log on to the Oracle Database and run the Knowledge Script. When you install the AppManager for Oracle Database module on an Oracle Database server, the setup program gathers a single Oracle Database user account name. In addition, it gathers the corresponding password for each database. The Oracle Database user account name must be the same on all databases, but each database can have a unique password associated with that user account. Having a single Oracle user account is a requirement only to ensure that discovery succeeds. After discovery, you can use the Oracle user account gathered during installation to begin running Oracle Knowledge Scripts immediately, or you can use the AppManager Security Manager to store additional Oracle user account names and passwords in the AppManager repository. NOTE: Oracle Knowledge Scripts provide one parameter for specifying an Oracle user account name to be used to log on to the databases you want to monitor. To run a single Knowledge Script job on multiple databases, each database must be configured with the same Oracle username. 3.2 AlertLog Use this Knowledge Script to scan the Oracle Alert log for entries that match a search string that you specify. You can set a threshold for the maximum number of occurrences of the search string found during any single scan of the log file. You can also specify a list of Oracle databases that you do not want to monitor with this script. Each database maintains an Alert log file where it records database operations (such as creating or dropping a database) and error conditions (such as deadlocks). This Knowledge Script provides a general-purpose tool for scanning a database s alert log for specific entries. When this Knowledge Script starts, it does not scan existing entries in the Alert log, and therefore it does not return any results or collect data on its first scan. As it continues to run at the intervals specified on the Schedule tab, this Knowledge Script scans the Alert log for any new entries created since the last scan. If, during any single scan, the number of matching entries exceeds the threshold you specify, the job raises an event. The detail message returns the number of occurrences of the search string found. Oracle Knowledge Scripts 25