Oracle Enterprise Manager Messages Manual Release 9.2.0 Part Number A96671-01 |
|
This chapter contains the error messages that are specific to the Oracle Management Pack for SAP R/3. If you receive other error messages while using the Oracle Management Pack for SAP R/3, see the appropriate chapters of this manual for more information on those messages.
Some of the Oracle Management Pack for SAP R/3 error messages ask you to provide debug output for the Oracle Data Gatherer to Oracle Support Services. See Getting Started with Oracle Management Pack for SAP R/3 manual for more information on running the Oracle Data Gatherer on NT and UNIX in debug mode.
Cause: An illegal service name was entered in the logon dialog box.
Action: The service name that you provide for logon should have a format of <application-server>:<sid>:<system-number>, with an optional :<language> key.
Cause: The username entered in the logon dialog box was not an SAP R/3 username or the user's password was wrong. Or, you did not enter preferred credentials for a SAP R/3 system before registering an event against that system.
Action: Make sure that the right credentials are entered.
Cause: Make sure that the SAP R/3 user has the right privileges.
Action: SAP R/3 users must have the S_A.CPIC, S_A.SCON, and S_A.SYSTEM privileges.
Cause: A connection cannot be made to the specified SAP R/3 system.
Action: Make sure that the SAP system is running, and that the host is reachable via the network.
Cause: The SAP system has been shut down. The system is only handling the startup and shutdown of single application instances. The central instance (the instance that holds the message server) may be down.
Action: Check the network connection (and restart the SAP system).
Cause: A fatal error has occurred in the SAP R/3 collection cartridge.
Action: If the error can be reproduced, provide debug output and the log file, alert_dg.log, to Oracle Support Services.
Cause: This is an error during the initialization of the connection to an SAP R/3 system.
Action: If the error can be reproduced, contact Oracle Support Services and provide them with the release number and patch level of the specific SAP R/3 system.
Cause: No more memory can be allocated.
Action: Contact Oracle Support Services and provide them with information about the memory consumption of the Oracle Data Gatherer process.
Cause: A fatal RFC error has occurred.
Action: If the error can be reproduced, provide debug output and the log file, alert_dg.log, to Oracle Support Services.
Cause: You specified an incorrect language key as part of the SAP service name. The service name that you provide should have a format of <application-server>:<sid>:<system-number>, with an optional :<language> key.
Action: Make sure that you specify the correct language key.
Cause: There has been an internal error in the communication between the client and the Oracle Data Gatherer. These errors may mean that the client is unable to deliver the resources for the callback. This type of problem might mean that an Oracle Performance Manager user will be unable to drill down on a chart or to restart a work process, for example.
Action: If the error can be reproduced, provide debug output and the log file, alert_dg.log, to Oracle Support Services.
Cause: Make sure that the user has the right privileges.
Action: The user must have the S_A.SYSTEM privilege.
Cause: Make sure that the user has the right privileges.
Action: The user must have the S_A.SYSTEM privilege.
Cause: The user has registered a Bad Buffer Quality event test to monitor a nonexistent buffer.
Action: Try to register the event test again using a correct buffer name.
Cause: The user has registered a Bad Response Time event test for a nonexistent SAP R/3 application instance.
Action: Try to register the event test again using a correct application instance name.
Cause: A user has registered a memory event test (for example, the In-Memory Roll Area Too Small event test, In-Memory Page Area Too Small event test, or the Extended Memory Too Small event test) for a nonexistent application instance.
Action: Try to register the event test again using a correct application instance name.
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|