AppManager for Oracle Database allows you to monitor Oracle databases and view Oracle resources. This module provides a group of Knowledge Scripts designed to give you a comprehensive view of how Oracle databases perform on your servers.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ Web site 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 the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials Web site.
This release of AppManager for Oracle Database provides the following enhancement:
Support for Oracle Database 12c for Microsoft Windows. This release now supports Oracle Database through 12c (12.1.0.x) for Microsoft Windows. For more information, see the System Requirements.
This release also resolves the following issues:
Oracle_DiskSpaceAvail job incorrectly raises events about low archive log space. This release resolves an issue in which the Oracle_DiskSpaceAvail job generates events stating that Archive log space is running low, when disk space is actually available. With this release, the message about archive log space running low does not occur in this situation. (ENG335150)
Running discovery on a 64-bit Oracle Server fails. This release resolves an issue in which the Discovery_Oracle Knowledge Script failed if you ran the script on a 64-bit Oracle Server. The event message included the following text: OLE Automation error - the remote procedure call failed. With this release, the discovery process works as expected on a 64-bit Oracle Server. (ENG337444, ENG334567)
Running discovery fails without giving additional details. This release resolves an issue in which the Discovery_Oracle Knowledge Script failed on a 64-bit computer and a 64-bit Oracle Database, without giving additional details. With this release, an update to the Discovery_Oracle script allows the discovery process to complete successfully in this situation. (ENG332521)
This release of AppManager for Oracle Database replaces all Previous Releases.
For the most recently updated list of supported application versions, see 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 |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Oracle computers you want to monitor (AppManager agents), and on all console computers |
7.0 or later Support for Windows Server 2008 on AppManager 7.x requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes page. |
|
Microsoft Windows operating system on agent computers |
One of the following:
|
|
Oracle Database on the agent computers |
A version of Oracle Database through 12c (12.1.0.x) for Microsoft Windows, appropriate for your operating system Notes
|
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Oracle Database Management Guide, included in the download package.
AppManager for Oracle Database includes a managed object, qorcla4.dll, and Knowledge Scripts to discover and monitor Oracle Database resources. The download package includes these release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-Oracle-7.1.73.0.msi, the module installer.
AM70-Oracle-7.1.73.0.ini, a configuration file used with the AppManager setup program.
AM70-Oracle-7.1.73.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-Oracle-7.1.73.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckOracle.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_Oracle.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On the Oracle computers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
Important If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
Note If you monitor Oracle Database on a 64-bit Microsoft Windows agent computer, and you switch from 32-bit to 64-bit Oracle client software, you must uninstall and reinstall AppManager for Oracle Database. This ensures that the correct NetIQ library is installed for the Oracle client running on the agent computer.
For more information about installing this module, see the AppManager for Oracle Database Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
When you monitor a 64-bit Oracle Database server using a 32-bit Oracle client, ensure that the installation paths of the AppManager agent software and AppManager for Oracle Database do not contain parentheses. NetIQ recommends that you install the AppManager agent and AppManager for Oracle Database in a folder other than the default C:\Program Files (x86), and ensure that the installation folder name does not contain parentheses. If the folder name contains parentheses, AppManager for Oracle Database cannot connect to the Oracle databases on the agent computer, and with each iteration the module returns the following error message: TNS could not resolve the connect identifier specified. (DOC327543)
Older versions of certain Oracle Knowledge Scripts do not work with version 7.1 of this module. Older versions of the following Knowledge Scripts do not run correctly on an agent computer running version 7.1 of this module: Discovery_Oracle, Oracle_DatabaseDown, Oracle_OpenCursors, and Oracle_SegmentExtentAvail. (DOC327693)
When you add a new Oracle database to an agent computer, restart the Discovery_Oracle Knowledge Script. When you add a new Oracle database to an Oracle server that AppManager for Oracle Database is monitoring, and configure credentials for the new database using the Oracle_ConfigDB Knowledge Script or the file ckOracle.exe on the agent computer with the new Oracle database, restart the Discovery_Oracle Knowledge Script job. This allows the Discovery Knowledge Script job to retrieve the updated credentials of the new database. Otherwise, AppManager for Oracle Database returns an error stating that it could not retrieve the database credentials. (ENG327643)
This release of Oracle Database includes enhancements added in previous releases.
This release provided the following enhancements:
Ability to monitor 64-bit Oracle databases on 64-bit Microsoft Windows servers. This release allows you to monitor 64-bit Oracle databases on 64-bit Microsoft Windows servers without installing 32-bit Oracle Client software.
Support for Oracle Database 11g for Microsoft Windows. This release now supports Oracle Database through 11g Release 2 (11.2.0.x) for Microsoft Windows.
This release also resolved the following issue:
The Oracle module installation process might remove some of the tnsnames.ora file data. This release resolves an issue in which prerequisite checker, ckOracle.exe, sometimes removed part of the tnsnames.ora file that was created during installation. The module installer no longer modifies the tnsnames.ora file. (ENG274648)
This release resolved the following issue:
The Oracle_RunSQL Knowledge Script raises an error event when you run it on a 64-bit Oracle server. This release addresses an issue in which running the Oracle_RunSQL script on a 64-bit Oracle server caused an invalid column name error event. This error event did not occur with a 32-bit server. With this release, an update to the Oracle_RunSQL Knowledge Script prevents the error from occurring. (ENG304528)
This initial release resolved the following issue:
AlertLog job does not raise events for non-primary Alert logs. This release resolves an issue in which the Oracle_AlertLog Knowledge Script job, when running on an Oracle server with multiple databases, raises events only for the Alert log for the first database discovered. With this release, code changes in the Oracle_AlertLog Knowledge Script and in the managed object, qorcla4.dll, allow the AlertLog job to raise events for the Alert logs for all databases on an Oracle server. (ENG285972)
This initial release resolved the following issues:
AppManager agent fails during discovery. Before you install this release, the NetIQ AppManager Management Client service (NetIQmc), also known as the agent, fails during the running of the Discovery_Oracle Knowledge Script. After you install this release, a code change allows the Discovery_Oracle Knowledge Script job to proceed without agent failure. (ENG278013)
ODBC DSNs might not be correct. Before you install this release, the ckoracle.exe application might not always create accurate ODBC DSNs (Data Source Names) for each database. After you install this release, ckoracle.exe retrieves the service name available in the tnsnames.ora file when creating the DSN for each database. (ENG279124)
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
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. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (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.
© 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/