Oracle Enterprise Manager Installation Guide

Hints and Tips

Troubleshooting
Manually Creating, Dropping, or Upgrading the Repository
Starting the Agent
Using Online Help

This appendix describes several hints and tips which enable the use of Oracle Enterprise Manager, its components, and the Intelligent Agent.

Troubleshooting

The following are possible troubleshooting issues.

System Registry Errors

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:

Open a DOS window and change to the \ORACLE_HOME\BIN directory.

Enter DIR *.OCX to list the all .OCX files.

Enter REGSVR32 name.OCX for each .OCX, where name corresponds to each of .OCX filenames. For example:

regsvr32 vojt.ocx

Updating OLE Registration

When Enterprise Manager is installed for the first time on a PC, the machine should be re-booted for OLE to be updated. Without this, many of the OLE-related activities may not function in the product. For example, you may not be able to launch an application from the launch palette.

Environment

An environmental variable named TEMP that points to a writable directory on your NT PC must be set up before running Oracle Enterprise Manager. If necessary, use the System option of the Control Panel to create the environmental variable TEMP.

Character Sets

The Oracle Enterprise Manager Console must be run with a character set that is equal to or greater than the Oracle database. For example, if the Console is set to American_America.WE8ISO8859P1, it should not be connected to a multi-byte database. However, if the Console is set to American_America.JA16SJIS, it can be connected to a multi-byte database because the character sets match.

Job and Event Systems

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.

Manually Creating, Dropping, or Upgrading the Repository

If the automatic repository create or upgrade (validate) operation fails, you can run the operation from the DOS command line. You can also drop a repository from the DOS command line.

Open a DOS window and change to the \ORACLE_HOME\BIN directory.

At the DOS prompt, enter vobsh followed by one or more of the command line switches in Table 5-1: Command Line Arguments for vobsh. 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:


-b	Sets batch mode. All prompting will be disabled.
-c cn	Sets the connect string. The parameter cn must be a quoted string containing the user/password specification, such as "scott/tiger@mydb".
-h	Displays the command line options.
-o option	Sets the repository manager option. Valid options are CREATE, DROP, and VALIDATE the repository.
-p name	Sets the product name and identifies the specific repository. The name must be a valid sub-component name or a valid group name. Valid sub-component names are Enterprise Manager, Software Manager, Oracle Expert, and Oracle Trace. Valid group names are: ALL, CONSOLE, PERFORMANCE. ALL and PERFORMANCE include all sub-component repositories. CONSOLE includes the Enterprise Manager and Software Manager repositories.

Table 5-1: Command Line Arguments for vobsh

Starting the Agent

Every time the agent starts, it writes the dbsnmp.ver file to the $ORACLE_HOME\network\agent directory. This text file contains agent version information that is used by the Enterprise Manager Console.

nmiconf.tcl

The nmiconf.tcl script can execute other Tcl scripts written specifically to discover other services on the node. If other scripts are used, they should be installed with nmiconf.tcl in the $ORACLE_HOME\network\agent\config directory (Windows platforms), and their names should be listed, one script per line, in the nmiconf.lst file located in the same directory. If errors occur during discovery, these are written to the $ORACLE_HOME\network\log\nmiconf.log file.

Using Online Help

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:

1.: Move the mouse pointer to your specific area of interest.
2.: Press the F1 key.

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.

Copyright © 1996 Oracle Corporation.
All Rights Reserved.