Oracle Enterprise Manager Configuration Guide Release 1.5.0 A57696-01 |
|
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:
ORACLE_HOME/network/log/dbsnmp*.log
file for errors on UNIX
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.
Two agent error messages and a possible solution are listed below:
ErrorMessageId=0xD Severity=Error Facility=Runtime SymbolicName=SNMIMSG_PKGINDEX_FAILED Language=English OracleAgent failed to create package index for Oracle Software Manager. MessageId=0xF Severity=Error Facility=Runtime SymbolicName=SNMIMSG_QUEUE_FAILED Language=English OracleAgent failed to create/read queue file.
In order to start fresh with the intelligent agent, you may need to delete all files (not the directories) in the network/agent directory (the *.q files and a few other files). Then start the agent (the agent might be reading some old information from the *.q files). If the problem exists, move the osm.dll to a different directory and see if the agent starts without it.
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.
\orawin95\net80\admin\tnsnames.ora
and define a local database.
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) ) )
tnsnames.ora
. In the example, the alias is local.world
. Click the Next button, then click Finish.
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.