Oracle
Enterprise Manager Configuration Guide
Release 1.6.0 A63732-01 |
|
Please check the compatibility matrix in the Oracle Enterprise
Manager Readme before installing or using Enterprise Manager. The readme
is located in the $ORACLE_HOME\SYSMAN\ADMIN directory.
Oracle Enterprise Manager 1.x.x can only be installed in
the same ORACLE_HOME as an NT 8.x.x database because Oracle Enterprise
Manager 1.x.x. and the 8.x.x database share required support files. Oracle
Enterprise Manager 1.x.x can be used to administer other database versions
but cannot be installed in the same ORACLE_HOME.
This appendix describes several hints and tips which enable the use of Oracle Enterprise Manager, its components, and the Intelligent Agent.
The following are possible troubleshooting issues.
If a message alerts you that the Oracle Installer was unable
to register Enterprise Manager components or you have trouble running any
of the programs, you must register the components manually after exiting
the Oracle Installer. Use the Windows File Manager or Explorer to locate
the ORACLE_HOME\SYSMAN\OLE2 directory, then double-click on each of the
.REG files to register each component.
If you have problems with the parameters or task property sheets when creating a job with the Job Scheduling system, the .OCX files may have failed to register properly during registration. To register the .OCX files, perform the following steps:
For example: regsvr32 vojt.ocx
If you are having trouble using the Job or Event systems
of the Console, check the Daemon and Agent trace file and look for error
messages saying the Daemon could not resolve an agent address into a host
name. On a Windows NT platform, you can also check the Event viewer in
Administrative Tools.
If the Intelligent Agent does not start, check one of the following areas for information:
For detailed information about troubleshooting the agent,
please refer to Chapter 1, "Agent Configuration".
If you see an OS error when starting the agent, check to
see if it is actually an agent error as described in snmimsg.mc. If you
do not receive a print out with the cause of the error, use the Event Viewer
in the Administrative tools group of Windows NT. You should find the true
cause of the problem documented.
These messages may be incorrectly identified as OS errors.
To test the connectivity to any SID, you must configure the
tnsnames.ora to have a sqlnet connect string to connect to that
particular SID, then use sql*plus to connect to that connect string. Use
Net8 Assistant for Net8 and Oracle Network Manager/Sqlnet easy config for
sqlnet 2.x.
An example is shown below of a sqlnet connect string scott.world that will connect to the SID that has the name ORCL found on scott-PC node through TCP/IP.
scott.world= (Description= (Address_list= (Address= (community=TCP.world) (protocol=TCP) (host=scott-PC) (port=1521) ) (Address= (community=TCP.world) (protocol=TCP) (host=scott-PC) (port=1526) ) ) (connect_data= (SID=ORCL) ) )
In sql*plus type:
sqlplus> connect username/password@scott
sql*plus should return the following:
sqlplus>connected.
If sql*plus returns any errors, please refer to the Sqlnet
Configuration Guide for further details.
If your agent is not running, you can manually define a local
database. This procedure must be performed before you can use any of the
basic applications or performance pack applications against the local database.
The steps can be done on Windows95 using Personal Oracle 7. The procedure is similar for Windows NT.
In the example, local.world is used. The definition in the tnsnames.ora file should look like the following:
local.world = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = beq.world) (PROTOCOL = BEQ) (PROGRAM = oracle73) (ARGV0 = oracle73ORCL) (ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))') ) ) (CONNECT_DATA = (SID = ORCL) ) )
If the automatic repository create or upgrade (validate)
operation fails, you can use the Repository Manager (It is available under
the Start-->Programs-->Oracle Enterprise Manager folder) or run the operation
from the DOS command line. Please refer to the Oracle Enterprise Manager
Administrator's Guide for detailed information about the Repository
Manager.
You can also drop a repository from the DOS command line.
For example, the following command validates and, if necessary, upgrades the Enterprise Manager repository.
vobsh -c "scott/tiger@mydb" -o VALIDATE -p "Enterprise Manager"
Command line arguments are listed in the table below.
Table
C-1 Command Line Arguments for vobsh
Enterprise Manager uses online help to provide additional information on the entire product and its optional components. To display context-sensitive help on the Console, perform the following steps:
If you want help on a particular dialog box, press its Help
button. You can also access the help system from the Help menu on the Console.
The Contents page lists the major help topics by title. The Index page
lists topics by key words. The Find page is a Windows user option that
can be set up with a wizard. The setup is performed the first time you
access the page.