C
Hints and Tips

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.

• Troubleshooting on page C-2
• Manually Defining a Local Database on page C-5
• Manually Creating, Dropping, or Upgrading the Repository on page C-6
• Using Online Help on page C-7

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:

1. Open a DOS window and change to the \ORACLE_HOME\BIN directory.
2. Enter DIR *.OCX to list the all .OCX files.
3. Enter REGSVR32 name.OCX for each .OCX, where name corresponds to each of .OCX filenames.

For example: regsvr32 vojt.ocx

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.

Intelligent Agent

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
• Select Application from the Event Viewer on Windows NT.

For detailed information about troubleshooting the agent, please refer to Chapter 1, "Agent Configuration".

Error Messages When Starting the NT Intelligent Agent

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.

Index	Description
01	OracleAgent failed to register its Service Control Handler.
02	OracleAgent failed to report its status to the Service Control Manager.
03	OracleAgent failed to create a thread synchronization object.
04	OracleAgent failed to create a thread.
05	OracleAgent failed to allocate memory.
06	OracleAgent failed to get the encryption key.
07	OracleAgent failed to run auto-discovery script nmiconf.tcl. Look in the nmiconf.log, for more information.
08	OracleAgent failed to initialize Oracle CORE library.
09	OracleAgent failed to initialize Oracle NLS library.
10	OracleAgent failed to initialize Oracle SQL*Net library : %1.
11	OracleAgent failed to initialize DES encryption.
12	OracleAgent failed to initialize Oracle Remote Operations library.
13	OracleAgent failed to create package index for Oracle Software Manager.
14	OracleAgent failed to create file dbsnmp.ver.
15	OracleAgent failed to create/read queue file.
16	OracleAgent failed to create job scheduling symbol table.
17	OracleAgent failed to initialize its connection cache.
18	OracleAgent failed to signon to SNMP master agent.
19	OracleAgent failed to read SNMP indexes from parameter file.
20	OracleAgent failed to connect to database.
21	OracleAgent failed to build SNMP cache.
22	OracleAgent failed to build MIB.
23	OracleAgent failed to register MIB row.
24	OracleAgent failed to restart its communication thread.

 

Testing the Connectivity to Any SID

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.

Manually Defining a Local Database

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.

1. Edit \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) 
                    ) 
                ) 

2. Start Oracle Enterprise Manager and login to the repository.
3. Under Navigator-->Service Discovery-->Manually Define Services, click the Next button, then enter the node name of the PC at the node name prompt. Then click the Add button.
4. Move down to the databases: table (under the node name section) and enter the name of the database alias as defined in tnsnames.ora. In the example, the alias is local.world. Click the Next button, then click Finish.
5. From the Console window, expand the Databases folder, and double click the newly added database to confirm that the connection is working properly.

Manually Creating, Dropping, or Upgrading the Repository

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.

1. Open a DOS window and change to the \ORACLE_HOME\BIN directory.
2. At the DOS prompt, enter vobsh followed by one or more of the command line switches in Table C-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 listed in the table below.
Table C-1 Command Line Arguments for vobsh

Arguments	Description
-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. The name parameter must be in quotes.

 

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.

---