readme_em.htm

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

chmod 755 /usr/local/bin/altbrowser
<p>&nbsp;&nbsp;&nbsp;&nbsp; 3.&nbsp; In the ClientConfig.properties file
located in the $ORACLE_HOME/sysman/config/ directory, add the
<br>&nbsp;&nbsp;&nbsp;&nbsp; following line to the end of the file:
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
user.browser=/usr/local/bin/altbrowser</blockquote>
<a NAME="Install"></a><b>1.3&nbsp; Installation</b>
<blockquote>1.3.1&nbsp; The JRE is installed by various Oracle products.&nbsp;&nbsp;
However, there is only one shared JRE per system.&nbsp; Hence, if after
installing Enterprise Manager Release 9.0 you install a previous release
of Enterprise Manager (i.e. Release 2.2), the JRE (Java Runtime Environment)
installed as part of Release 9.0 will be downgraded automatically; no error
messages will appear.&nbsp; This downgrade from JRE Release 1.1.8.10 to
1.1.7.30 will cause problems for Enterprise Manager Release 9.0. Consequently,
do no install Enterprise Manager Release 2.2 after installing Enterprise
Manager Release 9.0.&nbsp; Installing a pre-9.0 Oracle database will also
cause the same problem of downgrading the JRE.&nbsp; If you run into this
situation, you can workaround the problem by re- installing JRE 1.1.8.10&nbsp;
from the CD-ROM you installed Enterprise Manager Release 9.0 (most likely
from a Release 9.0 CD-ROM). Re-install the JRE by re-installing Oracle
Universal Installer; as the Installer has a dependency on the JRE.</blockquote>
<a NAME="Misc"></a><b>1.4&nbsp; Miscellaneous</b>
<blockquote>1.4.1&nbsp; If you select a different window after launching
the Console, the login dialog will not display in the foreground.&nbsp;
You may need to minimize any active windows or use&nbsp; ALT -> tab and
select the Console application to bring the login dialog to the foreground.&nbsp;
(Bug 806713)
<p>1.4.2&nbsp; When you open a modal dialog box&nbsp; in an Oracle Enterprise
Manager application (a modal dialog box is one that requires user action
before being able to return to the application) and request context-sensitive
help on that dialog box, the help is displayed in a modal help topic window.
Before you can return to the modal dialog box, you must close the help
topic window that is displaying the help topic for the modal dialog box.
<p>1.4.3&nbsp; During discovery of remote nodes and their targets,&nbsp;
if the node is available and reachable via the network, but the Intelligent
Agent on that node is down,&nbsp; the discovery wizard will give the error&nbsp;
"VNI-4044 : Cannot contact agent. Node may be down, or the network may
be down or slow."&nbsp; Instead of&nbsp; the expected error "<i>VNI-4009
: Cannot contact agent on the node. Agent may be down or network communication
to the node has failed."&nbsp; </i>If this occurs, log on to the remote
node and check the status of the Intelligent Agent via the agentctl utility:
<br><font face="Arial,Helvetica">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
agenctl status agent</font>
<br>If the Agent is not up, start the Agent via:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font face="Arial,Helvetica">agenctl
start agent</font>
<br>then perform Discovery again.&nbsp; (Bug 1874173)
<p>1.4.4&nbsp; The Enterprise Manager Configuration Guide chapter 2 Standalone,
section "Standalone Repository", incorrectly states that Index Tuning Wizard
requires a standalone repository.&nbsp; Index Tuning Wizard does not require
a standalone repository.
<p>1.4.5&nbsp; The Enterprise Manager Configuration Guide chapter 3 Configuring
and Controlling the Management Server, section "Configuring a Local Management
Server to Use a New Release 9<i>i </i>Repository", incorrectly states that
you should not change the password for SYS during database creation via
Database Configuration Assistant as Enterprise Manager Configuration Assistant
assumes that the password is "change_on_install".&nbsp; This is no longer
a restriction.
<p>1.4.6&nbsp; To use Enterprise Manager functionality other than SQL*Plus
Worksheet as a non-DBA user, you must have the appropriate privilege. A
DBA user will already have the appropriate privileges to manage the database.
<ul>
<li>
For 8.x databases: You must have been granted the SELECT_CATALOG_ROLE.
Ask the System Administrator or Super Administrator to grant you this role.
To create, edit, or drop objects outside of your schema, you must have
been granted the DBA role or the appropriate privileges for the object.&nbsp;
Note: The SELECT_CATALOG_ROLE is only available for Oracle8.x databases.</li>

<li>
For 9.x databases: You must be granted the Select Any Dictionary privilege.
Ask the System Administrator or Super Administrator to grant you this role.</li>
</ul>
1.4.7&nbsp; If you select to show an HTML-formatted file (Explain Plan
report, Latest Product Information from the Help main menu, etc.),&nbsp;
from an installed Enterprise Manager Console and the HTML-formatted file
does not appear then in the ClientConfig.properties file located in the
$ORACLE_HOME/sysman/config/ directory, add the following line to the end
of the file:&nbsp; (Bug 1961020)
<p>user.browser=&lt;full_path_to_browser>
<p>1.4.8&nbsp; On some Windows platforms, Enterprise Manager intermittently
hangs after supplying login credentials and clicking the OK button on the
Login dialog. When this problem occurs, launch the Windows Task Manager;
end/kill the JREW process, and relaunch the Enterprise Manager Console.&nbsp;&nbsp;
(Bug 2317052)
<p>1.4.9&nbsp; The Enterprise Manager Configuration Guide chapter 1 Introduction,
section "Certifications", incorrectly states the processor and RAM requirements
for a machine running the Management Server or the Management Server and
Client.&nbsp; The correct requirements for this type of deployment as well
as the deployment where all tiers are running on the same machine are below:
<br>&nbsp;
<table BORDER COLS=3 WIDTH="100%" >
<tr>
<td></td>

<td><b>Minimal</b></td>

<td><b>Recommended</b></td>
</tr>

<tr>
<td><b>Management Server or Management Server and Client</b></td>

<td>Pentium 266 MHz with 128 MB RAM</td>

<td>Pentium 300 MHz with 256 MB RAM</td>
</tr>

<tr>
<td><b>Management Server, Client, Agent, HTTP Server</b></td>

<td>Pentium II 866 MHz with 256 MB RAM</td>

<td>Pentium III 1GHz with 512 MB RAM</td>
</tr>
</table>
</blockquote>

<p><br><a NAME="Event and Job"></a><b><font color="#3333FF"><font size=+1>2.&nbsp;
Event and Job Systems</font></font></b>
<blockquote>2.1&nbsp; If your User-Defined event has failed with an error:
<i>"User
Defined Event" failed:&nbsp; No result returned in output: </i>then this
means the tagged output specific to user-defined events could not be found
in standard output.&nbsp;&nbsp;&nbsp;&nbsp; This may mean your script failed
to execute for a variety of reasons.&nbsp; Some things to look into:
<blockquote>a) check that the path to the monitoring script you specified
is correct
<br>b) check the execute permissions on the monitoring script
<br>c) in the script text, check that the path to the interpreter specified
is correct.
<br>As an additional check, log on to the monitored node using the Node
credentials used for the event, then make sure the monitoring script runs
correctly.</blockquote>
2.2&nbsp; Associating fixit jobs with unsolicited events is only supported
by 9.x Intelligent Agents.
<p>2.3&nbsp; If the OS character set when the Intelligent Agent is started
up and the database character set which the Agent is managing are different,&nbsp;
the "Alert" event returns corrupted characters.&nbsp; This happens if alert.ora
file has non-US7ASCII characters. (Bug 1689939)
<br>Please set the default OS character set by defining the OS locale and
define the NLS_LANG parameter properly before the Intelligent Agent gets
started.
<p>2.4 Event Handler
<blockquote>2.4.1&nbsp; If the command to be executed by the Command Executor
doesn't seem to be invoked as expected, make sure all tokens in the command
are enclosed in double-quotes (").&nbsp;&nbsp; (Bug 1894728)&nbsp; For
example:
<p>/com/oracle/sysman/em/commandexecutor/templates/allEvents2/command="C:/myApp/myProg"
"arg1=%node%"&nbsp; "arg2=%targetname%" "-d" "arg3=Event:%eventname% Severity:%severity%&nbsp;
Result:%output%"
<p>2.4.2&nbsp; Event Logger on Windows platforms
<br>The default event handler configuration will log event information
to the file %ORACLE_HOME%/sysman/log/eventhandler.log.
<br>For example,&nbsp; if the ORACLE_HOME is c:\orant,&nbsp; then the logfile
specification will look like this:
<p>/com/oracle/sysman/em/eventlogger/templates/allevents/logfile =c:\orant/sysman/log/eventhandler.log
<p>However, directory names that use the backlash (\) delimiter will not
work for configuration information -- these directory delimiters must be
specified as forward-slashes (/).
<br>To workaround the problem,&nbsp;&nbsp; change the filename specification
to use all forward slashes (/), e.g.
<p>/com/oracle/sysman/em/eventlogger/templates/allevents/logfile =c:/orant/sysman/log/eventhandler.log
<p>Refer to the Event Handler chapter in the Enterprise Manager Administrator's
Guide for details on changing event handler configuration. (Bug 1902918)</blockquote>
2.5&nbsp; When a job is created by a user, there is an option to override
preferred credentials by specifying new credentials to be used for the
<br>job.&nbsp;&nbsp;&nbsp; If new credentials are specified, and if other
users are then given access to this job (via View, Modify, or Full permissions
on the
<br>job) then these users can potentially re-use the credentials in other
jobs via 慶opy