Release 9.0.1
Part Number A88720-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle Enterprise Manager Getting Started with the Oracle Management Pack for Oracle Applications Release 9.0.1 Part Number A88720-01 |
|
This appendix lists some of the problems you might encounter while using the Management Pack for Oracle Applications, along with some possible solutions and workarounds. Sections include:
Table A-1 lists symptoms the Management Pack for Oracle Applications may exhibit and refers you to the appropriate section for information. The table is also divided into sections which reflect the nodes where the problems may occur.
This section describes problems related to the Intelligent Agent and possible solutions.
The user cannot start the Intelligent Agent on Windows NT. The user gets the message stating: "The Oracle Performance Utility has been found. Please disable or deinstall in order to start the Oracle Intelligent Agent".
The Oracle Performance Utility is not compatible with the Oracle Intelligent Agent.
The Oracle Performance Utility is a service that allows Windows NT users to monitor their Oracle instance using the Microsoft NT Performance Monitor tool. This utility is not compatible with the Oracle Intelligent Agent.
Deinstall the Oracle Performance Utility using the Oracle Installer you used to install the local database. Alternatively, rename or delete the registry key for Oracle Performance Utility. For example, rename the following key from:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleOHOME80\Performance to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OracleOHOME80\RENAMED_Performance
|
Note: You will not be able to run the Oracle Performance Utility after this key has been renamed or deleted. To run the Oracle Performance Utility, restore the registry key to its original state. |
User cannot connect to the Oracle Management Server.
Unknown
Verify that the maximum number of sessions on the Oracle Management Server repository (database) has not been exceeded. If needed, increase the "processes = " init.ora parameter for this database, and then stop and restart the database.
Use SQL*Plus or another tool to verify that you can connect from the Oracle Management Server ORACLE_HOME to the database being used as the Oracle Management Server repository.
The user cannot connect to the repository when using either the Performance Manager or Capacity Planner applications.
An empty connect string was given when the Oracle Management Server repository was created. Alternatively, an unqualified DNS hostname was given at the time of creation and you are trying to connect from a separate DNS domain.
Modify the repository credentials and specify the connect string even though you want to use the local database. If you are connecting to the Oracle Management Server from outside the DNS domain in which the Oracle Management Server repository was created, use a fully qualified hostname when creating the repository (for example, use omshost.acme.com not omshost).
See "Creating the Oracle Management Server Repository" for additional information.
The user cannot start Performance Manager in the context of the Oracle Enterprise Manager console.
Performance Manager makes a direct connection to the Oracle Enterprise Manager repository based on a connect string Performance Manager retrieves from the Oracle Management Server. This process fails when invoked from hosts in external DNS domains if you do not specify a fully qualified connect string during the repository creation process (in the Configuration Assistant). Also, this process fails if the local tnsnames.ora file does not have an entry for the database being used for the Oracle Management Server repository.
Modify the repository credentials with a connect string to the repository database. This also includes the situation where the repository and the database are on the same machine.
Verify that the local tnsnames.ora file contains the correct Oracle Net connect alias by using SQL*Plus or another tool to connect to the Oracle Management Server repository database.
The user receives the following messages when attempting to connect to the repository when using Performance Manager:
VTD-0057: Error connecting to repository. Exception VdbLostConnectionException{wstring reason = "ORA-12203: TNS:unable to connect to destination"; long oracleError=12203;}
When the user continues, the following message appears:
VTD-0058: Repository-based operations will not be available.
Unknown
Use the vtm -debug command from the command line to run Performance Manager in tracing mode. Then connect to the Oracle Management Server and search the trace output for the service Performance Manager is using to connect to the repository.
This symptom may be caused by incorrect Oracle Net configuration on the client node where you are experiencing this behavior. This symptom can occur if you used an Oracle Net connect alias (for example, mydatabase.world), instead of the colon-separated (for example, myhost.acme.com:1521:mySID) syntax when you created the Oracle Management Server repository.
Use SQL*Plus or another tool to verify that you can connect from this node to the database being used as the Oracle Management Server repository. Use the exact Oracle Net connect alias (for example, foo.world) you used when creating the repository.
See "Creating the Oracle Management Server Repository" for additional information.
User cannot save work performed in Performance Manager.
If you start Performance Manager in standalone mode and Performance Manager is connected to a database directly without using the Oracle Management Server, you are not able to save your work.
You can save your work to the repository by starting Performance Manager in the context of the Oracle Enterprise Manager console. Follow the menu path Tools=>Application Management=>Performance Manager.
User is attempting to connect to an Oracle Applications instance using Performance Manager or Capacity Planner and receives the following error message:
Error: A required patch has not been applied to this Oracle Applications instance
The patch for Oracle Applications bug #1302931 for Oracle Applications version 10.7 or the patch for Oracle Applications bug #1371501 for Oracle Applications version 11.0 and higher was not applied to the Applications instance.
Apply the patch for bug #1302931 or bug #1371501 to the Applications instance.
While viewing charts from a service, the following message appears indicating that the connection to the service has been lost.
VTM-0002: Error displaying chart Pending Requests per Manager Error reading response from Data Gatherer, connection lost for service NT110
Attempts to reconnect to the service fail.
The Intelligent Agent has stopped running.
Restart the Intelligent Agent.
While scheduling either an event or a job, user sees the following error:
Agent version on the node is incompatible.
Events and jobs are specific to certain versions of the Agent, for example, versions 8.1.7 or later of the Agent, or versions 8.1.6 or earlier of the Agent.
Use the correct version of the event/job with the associated version of the Agent.
The Enterprise Manager console does not display the Management Pack for Oracle Applications advanced events in the browser.
The Management Pack for Oracle Applications was not installed in the Oracle home in which the Oracle Management Server is running.
Install the Management Pack for Oracle Applications in the same Oracle home as the Oracle Management Server. Stop and restart the Oracle Management Server.
User has encountered the 'Failed to authenticate user' error message while running a job.
A Windows NT user account does not exist that has the log on as batch job privilege.
For the Intelligent Agent to execute jobs on a managed node (Windows NT only), a Windows NT user account must exist that has the log on as batch job privilege. The privilege can be assigned to an existing local or domain user (starting with Oracle Server release 7.3.3) or a new Windows NT user. The preferred credentials for the node must be set for that user in the Enterprise Manager console. Refer to the Oracle Enterprise Manager Configuration Guide for information on setting preferences. The user must have permission to write to the $ORACLE_HOME/network or $ORACLE_HOME\Net80 directories.
The user sees the same Concurrent Manager instance listed more than once in the Oracle Enterprise Manager Console.
The database alias name in the oapps.ora file was modified after the instance was discovered.
In the Oracle Enterprise Manager Console, right-mouse click on the old concurrent manager instance and select Remove.
When the user starts recording a Performance Manager chart then closes the Enterprise Manager console window, the recording stops.
The Performance Manager application runs in the same process space as the Enterprise Manager console. This is a restriction of the console.
Keep the Enterprise Manager console window open or minimize the window.
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|