Oracle Enterprise Manager Messages Manual Release 2.2 Part Number A85245-01 |
Library | Service | Contents | Index

# 8
Oracle Enterprise Manager Framework Messages

This chapter contains probable causes and corrective actions for error messages with the following prefixes:

Messages | See Page
--- | ---
VDE-1000 to VDE- 1999 Messages VDI-0000 to VDI-0499 Messages VDN-4500 to VDN-4999 Messages VDOUS-00101 to VDOUS-00115 Messages VDR-7000 to VDR-7499 Messages VDU-6000 to VDU-6499 Messages | 8-1 8-3 8-3 8-3 8-5 8-6

## VDE-1000 to VDE- 1999 Messages

VDE-1003: Event incomplete.

  Cause: An attempt was made to register an incomplete event.

  Action: Complete the event before registering it.

VDE-1004: A system error has occurred while contacting the agent.

  Cause: The target naming service encountered a unrecoverable error while contacting the agent.

  Action: Contact Oracle Worldwide Customer Support.

VDE-1523: There is no agent on node <name of node>.

  Cause: Either the repository has been corrupted, or there is a problem with a previous discovery on that node.

  Action: Initiate auto-discovery on the node again. If the problem persists, contact Oracle Worldwide Customer Support.

VDE-1524: Insufficient privileges for removing some libraries.

  Cause: Some of the event libraries selected cannot be removed for lack of permission.

  Action: Retry on only those libraries for which you have sufficient permission.

VDE-1525: At least one of the event(s) cannot be removed because of insufficient user privileges or because some other user is currently manipulating the event(s).

  Cause: One or more of the event occurrences selected to be moved to Event History cannot be moved for lack of permission.

  Action: Any event occurrence(s) on which you had the correct permissions has been successfully moved to Event History. You will need appropriate permissions before moving the rest, however.

VDE-1527: At least one of the event occurrences cannot be moved because of insufficient privileges.

  Cause: Some of the event occurrences selected for removal cannot be removed for lack of permission.

  Action: Any event occurrence(s) on which you had the correct permissions has been successfully removed. You will need appropriate permissions before removing the rest, however.

VDE-1528: At least one event occurrence cannot be removed because of insufficient privileges.

  Cause: One or more of the events selected cannot be removed either because of lack of permission or because the event is currently being manipulated by another user.

  Action: Before you can move an event, you must obtain permission from the owner of the event, or obtain FULL event permissions from a Super User.

## VDI-0000 to VDI-0499 Messages

VDI-0001: Internal error - invalid state change from <parameter>.

  Cause: An internal error occurred in Oracle Enterprise Manager.

  Action: Contact Oracle Worldwide Customer Support.

VDI-0002: A system error has occurred.

  Cause: An internal error occurred possibly because of a lost repository connection, a corrupted repository, or an incorrect installation.

  Action: Verify connectivity to the repository. If you are able to connect to the repository, contact Oracle Worldwide Customer Support. You may also want to submit the Oracle Enterprise Manager trace file.

## VDN-4500 to VDN-4999 Messages

VDN-4510: Group <name of group> does not exist.

  Cause: The group was deleted by another user.

  Action: None.

VDN-4564: Cannot resolve host <name of host>.

  Cause: The Oracle Management Server could not find the host with the given name on the network.

  Action: Check the spelling of the hostname. Fully qualify the hostname with the domain name (e.g., production.uk.oracle.com instead of production.) This will be helpful in cases where you are trying to discover the node in a different domain.

## VDOUS-00101 to VDOUS-00115 Messages

VDOUS-00101: Error creating Java Virtual Machine

  Cause: The installation of the Oracle Management Server was incorrect.

  Action: Re-install the management pack. If this fails, contact Oracle Worldwide Customer Support.

VDOUS-00102: Unable to locate class <name> in CLASSPATH <path>.

  Cause: Components that should be installed are missing.

  Action: Reinstall the missing components.

VDOUS-00103: Unable to locate method in class <class>:<method>.

  Cause: The version of class/ZIP files in CLASSPATH is incorrect.

  Action: Remove the older versions of the class/ZIP files and re-install the management pack.

VDOUS-00104: Unable to allocate new Java object <name> in <method>.

  Cause: Java Virtual Machine is out of memory.

  Action: Shut down and restart all management pack applications.

VDOUS-00106: Not enough memory to perform allocation

  Cause: Problems occurred during the bridge start-up.

  Action: Close some of the other applications and retry.

VDOUS-00107: CoInitialize failed in GetDispatchDriver for <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00108: CLSIDFromProgID failed for <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00109: GetActiveObject/CoCreateInstance failed for <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00110: QueryInterface failed for <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00111: CoInitialize failed in <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00112: CLSIDFromProgID failed for interface <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00113: Failed to get active object for interface <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00114: Failed to get IDispatch for interface <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

VDOUS-00115: Failed to get DISPID for interface <name>.

  Cause: Problems occurred in OLE initialization.

  Action: Re-install the management pack.

## VDR-7000 to VDR-7499 Messages

VDR-7000: Error accessing regristry <name of registry>.

  Cause: A lost database connection, an invalid transaction, or an invalid SQL operation may have occurred. Details as to the failure are included in the exception.

  Action: If the case is a lost connection or a repository that has shut down, restart the Oracle Management Server. Otherwise, an internal error occurred, in which case you should contact Oracle Worldwide Customer Support and log a software problem report containing the information presented in the message.

VDR-7001: Key <name of key> cannot be registered.

  Cause: While running the Configuration Assistant, one of the following may have occurred:

  - a lost database connection

  - an invalid transaction

  - an invalid SQL operation

  Action: Redo the configuration of the Oracle Management Server.

## VDU-6000 to VDU-6499 Messages

VDU-6000: Principal still owns objects to which access is being revoked.

  Cause: Access to the job and/or the event subsystem was being revoked while the user still owns jobs or events. The jobs or events have not only been submitted or registered, but also reside in their corresponding libraries.

  Action: Reassign ownership of all of the jobs and events to another user and retry the operation.

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index