readme_oemagent.txt

Debian中文参考手册,系统介绍了Debian系统

			     README FILE

   	    Oracle Intelligent Agent Version 9.2.0.1.0 
			      April 2002 

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This document provides some basic information on the Oracle Intelligent Agent. It also provides information on significant changes and enhancements with version 9.2.0.1.0 of the Agent and bugs fixed in this release. For details see the Oracle Enterprise Manager documentation set. Bug fixes are listed at the end of the Readme.

A. OVERVIEW 
-----------

Oracle Intelligent Agent is an autonomous process running on remote nodes in the network. It is responsible for executing job tasks, monitoring events and collecting statistical data on Oracle and host services discovered by it, as requested by Oracle Enterprise Manager and Diagnostic Packs users. The Agent also handles requests to generate SNMP(Simple Network Management Protocol) data corresponding to events which can be sent to any third party application that supports SNMP.

In Agent versions prior to version 9, the functionality of collecting statistical data on services existed in the Data Gatherer. Beginning with version 9, this functionality has been consolidated within the Agent and hence the Data Gatherer no longer exists. As a result, events specific to the Data Gatherer(Data Gatherer updown, Data Gatherer Alert) are not supported by Agent version 9. 

For further details, please consult the Oracle Intelligent Agent User's Guide available as part of Enterprise Manager documentation.


B. CONFIGURATION PARAMETERS
---------------------------

The properties for tracing and logging the Agent used to start with "nmi" for versions prior to version 9.   Starting with version 9, these now begin with "dbsnmp".    All configuration parameters should be in lowercase.

Tracing and logging parameters are available for:

1) The Agent process "dbsnmp"
2) A "dbsnmpj" process spawned for a job by the Agent and 
3) agentctl 


Undocumented Configuration Parameters:
-------------------------------------
This is an additional snmp_rw.ora parameter that has not been included in the documentation:

dbsnmp.notificationtimeout = <nn>

where nn is number of milli seconds. If the Agent fails to deliver a notification to the Oracle Management Server within this time, the Agent will be automatically re-started. The default value is 6 minutes.


C. ADDITIONS and CORRECTIONS TO AGENT DOCUMENTATION
---------------------------------------------------
This section lists additional agent configuration that have not been included in the Agent documentation.

1)Blackouts
a) To blackout specific subsystems
Use the "-s<ubsystem/s" option to blackout jobs, and/or events, and/or historical collections. By default, all subsystems (jobs and events and collections) will be blacked out.

Usage:
agentctl start blackout <target> -d<uration> -s<ubsystem/s>

... where subsystem is one or more of the following:  jobs events collections

Example:
To blackout events on target 'mytarget' for 30 minutes:

% agentctl start blackout mytarget -d 0:30 -s events
  
b) Showing status of blackouts
The agentctl command to show the status of blackouts is:

agentctl status blackout

The Agent Guide incorrectly documents this as: 'agentctl show blackout'.
 
2) Specifying a password for encrypting agent files
By default, the agent files are encrypted using the hostname (of the host on which the agent resides) as a key or password for encryption.  To specify a different password to be used for encryption, start the agent as follows:

agentctl start agent password=<new password>

Example:
% agentctl start agent password=mynewpassword

To prevent people from doing a "ps -efo" and looking at the command-line arguments to get the password, there is an option of putting the password in a file and giving the file as the argument to agentctl. This file can then be permission protected to prevent viewing by unauthorized users. Only the first 8 characters of the file are used as the password.  The usage is as follows:

agentctl start agent password_file=<location of password file>

Example:
% agentctl start agent password_file=/u1/myhome/newpassword.txt


D. AGENT UPGRADE AND MIGRATION
------------------------------
1) In order to upgrade from a 9.0.x Agent to a 9.2 Agent,  follow the instructions as documented in section "Upgrading from 8.0.6/8.1.6/8.1.7 Intelligent Agents to 9.x" of Chapter 2 of the Oracle Intelligent Agent User's Guide, Release 9.2.0.   These same instructions will apply to a 9.0.x to 9.2 Agent upgrade.

2) Migrating Agent files from a 32-bit platform to a 64-bit platform is NOT supported using the NMUMIGR8 utility (Bug 2237433).  Contact Oracle Worldwide Support for a workaround. 


E. ISSUES & RESOLUTIONS
-----------------------

1) Required Solaris Patches

In order to run Agent version 9.2.0.1.0 on Solaris 2.6 and 2.7, the following Solaris operating system patches are required:

1.1) On Solaris 2.6:

1.1.1) Solaris Patch 105181-23 - Required by 105210-33. Refer to  http://sunsolve.sun.com/pub-cgi/retrieve.pl?type=0&doc=fpatches/105181.

1.1.2) Solaris Patch 105210-33 - Required by 105568-21. This is needed for 9.2.0.1.0 Agent due to race condition of fork1 and env lock and thread safety issues with localtime_r.

1.1.3) Solaris Patch 105568-21 - Required by 105210-33. Needed for 9.2.0.1.0 Agent due to race condition for fork1 and env lock.


1.2) On Solaris 2.7:

1.2.1) Solaris Patch 106541-14 - This is needed for version 9.2.0.1.0 Agent due to race condition for fork1 and env lock. This requires patch 107544-03. 

1.2.2) Solaris Patch 107544-03 - Required by patch 106541-14.

1.2.3)Solaris Patch 109104-04.

Please contact Sun's Technical Support to procure the above mentioned patches.


2) Running the Agent via Terminal Server
In some situations, when running the agent via NT Terminal Server, the agent may hang.  To work around this problem, shutdown and restart the agent.  (Bug 2259632)


3) Stopping the Agent when tracing is enabled
When agent tracing is enabled at level 15 or 16 (i.e. dbsnmp.trace_level = 15 or 16),  then stopping the Agent via 'agentctl stop' will cause a segmentation fault and will not stop the agent. (Bug 2282126)
To stop the agent:
a) Get listing of processes with 'dbsnmp'
b) You should see the 'dbsnmp' process and its watchdog process 'dbsnmpwd'
c) Manually kill both these processes


4) To reduce the size of the Intelligent Agent, after you've installed it, you can remove the following files from $ORACLE_HOME/bin:

agentctl0 
dbsnmp0 
dbsnmpj0 
nmu7q280 
nmudg0 
nmumigr80 
oemevent0 
oratclsh0 



F. BUGS FIXED IN THIS RELEASE
------------------------------
1) 2160268 - Agent fails to start when there are many targets.
2) 1867659 - Job fails - Permission denied on services.ora when the OS User specified in Preferred Credentials is not in unix DBA group
3) 2233584 - TOP SESSIONS NO LONGER SHOWS ALL SESSIONS - REGRESSION FROM 8.1.7
4) 2224724 - MASTER_PEER CRASHES WHEN DECODING CERTAIN ILL-FORMED PDUS
5) 2186552 - ERROR: ROLLUP_TABLES DO_ROLLUP FAILED, ODG-05113  (occurs when monthly table is rolled up when day table does not exist)
6) 2184769 -- HP: Predefined Reports hang when scheduled for "Immediate" execution.
7) 2126413 - Digital Alpha/Open VMS: AGENTCTL DOES NOT SHOW USAGE INSTRUCTIONS
8) 2098949 - Windows XP: DGMETRIC EVENTS FAIL FOR SPECIFIC NT_OS CARTRIDGE RESOURCES ON WINDOWS XP PRO
9) 2029214 - Windows 2000: In the EM console, Property page of an Windows 2000 host displays  WINNT5.0 instead of WINDOWS 2000 
10) 1952581 - CMANAGER.TCL DISCOVERY SCRIPT NOT USING CORRECT LOGGING MECHANISM
11) 1920174 - CUSTOMIZATIONS REQUIRED TO MONITOR EXTPROC LISTENERS 
12) 1900677 - INTELLIGENT AGENT FAILS TO RETURN OUTPUT TO CONSOLE IF > CONNECTION SDU SIZE.
13) 1897880 - For SQL Server 7.0, problem showing data in charts if agent is shutdown for some period of time.
14) 1844998 - CURRENT SQL FOR SESSION SHOWS BY DEFAULT SQL LINES IN WRONG ORDER
15) 1630410 - NO HELP AVAILABLE FOR THE APPS CHARTS