Oracle Enterprise Manager Messages Manual
Release 1.5.0

A57693-01

Library

Product

Contents

Index

Prev Next

11
Generic Oracle Enterprise Manager Messages

VAX-00000 to VAX 10011: Critical Generic Error Messages

VAX-00001: Failed to load resource DLL (filename).

Cause: An attempt to load the specified DLL failed.

Action: Make sure the DLL is either in the current directory or in the path.

VAX-00002: Failed to locate the MFC DLL (filename) in the Windows NT system directory.

Cause: An attempt to load MFC40.DLL failed.

Action: Make sure the MFC DLL is in the Windows NT system directory.

VAX-00003: You should use a version of MFC DLL higher than or equal to specified version.

Cause: An attempt to use the wrong version of the MFC DLL.

Action: Make sure the version of MFC DLL is higher than or equal to the specified version.

VAX-01000: Error detected while opening file.

Cause: Internal exception. Cannot open file.

Action: Check that the file is not already open.

VAX-01001: Error detected while writing to file.

Cause: Internal exception. Cannot write to file.

Action: Check that the file has write permission.

VAX-01003: Internal Error: Failed to find IUnknown for Discovery Cache.

Cause: An OLE error has occurred.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01004: Internal Error: Unable to obtain IDispatch from Discovery Cache.

Cause: An OLE error has occurred. The Dispatch interface for the Discovery Cache is not available.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01005: Internal Error: Unable to load Object List from the Discovery Cache.

Cause: An OLE error has occurred. The Object List from the Discovery Cache is not available.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01006: Internal Error: Unable to load Database Groups from the Discovery Cache.

Cause: An OLE error has occurred. The Database Groups from the Discovery Cache are not available.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01007: Internal Error: Unable to commit job.

Cause: An OLE error has occurred. The job could not be committed.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01008: Internal Error: Unable to set job schedule.

Cause: An OLE error has occurred. The job schedule could not be set.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01009: Internal Error: Unable to set job destinations.

Cause: An OLE error has occurred. The job destinations could not be set.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01010: Internal Error: Unable to set job script.

Cause: An OLE error has occurred. The job script could not be set.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01011: Internal Error: Unable to set job name.

Cause: An OLE error has occurred. The job name could not be set.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01012: Internal Error: Unable to initialize the job.

Cause: An OLE error has occurred. The job could not be initialized.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01013: Internal Error: Unable to obtain unique services from the Discovery Cache.

Cause: An OLE error has occurred. The unique services from the Discovery Cache are not available.

Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.

VAX-01201: Could not open file for writing.

Cause: Internal exception.

Action: Check that the file is not read-only or already open.

VAX-01202: Error while writing line to file.

Cause: Internal exception.

Action: Check that the file is not read-only or that the file is not already open.

VAX-01203: Out of memory, must set filter on this container.

Cause: The number of items in the tree is too large for the amount of memory in the system.

Action: Insert a filter to display a reduced number of items.

VAX-01204: Database connection failed.

Cause: Invalid connect string.

Action: Enter the connect string again.

VAX-01206: You do not have SELECT privilege on the Data Dictionary Views. Application is terminating.

Cause: You did not have the SELECT privileges that are needed to run this application.

Action: Login with a User that has SELECT privileges on the data dictionary views.

VAX-01207: Connection is lost, collapse the database instance.

Cause: This tree node no longer has a connection to database.

Action: Collapse the first database instance in the tree above the selected node.

VAX-10011: Oracle not available.

Cause: The database is down.

Action: Start the database.

VAX-13100 to VAX 15512: Other Generic Messages

VAX-13100 and VAX-13101 appear as a single error message.

VAX-13100: This operation interrupts your work in progress in the name dialog box.
VAX-13101: Do you wish to apply your changes before proceeding?

Cause: A user action is interrupting changes made to a particular dialog box or property sheet.

Action: Click Yes to apply the current changes, click No to abort the changes, or click Cancel to abort the action that interrupted the changes.

VAX-13102: Unable to initialize object; database session is invalid.

Cause: Internal error. The database connection is invalid.

Action: Check that SQL*Net is working correctly.

VAX-13103: A database needs to be selected for this application.

Cause: An application has been launched from the Console and the application cannot obtain valid connection information for the type of object selected.

Action: Select a service object, such as DATABASE, LISTENER, or NAMES SERVER.

VAX-13104: The target database must be an Oracle8 database.

Cause: The launched application requires the target database to be an Oracle8 database.

Action: Enter the connect string for an Oracle8 database.

VAX-14001: The repository (version number) is not compatible with the Oracle Enterprise Manager (version number).

Cause: The Oracle Enterprise Manager repository you are attempting to log into is older than (and incompatible with) the current version of the Oracle Enterprise Manager console.

Action: Check the last statement in the SMPCRE.SQL because that statement creates a SMP_REP_VERSION table which contains the OEM version number. See the README file for Oracle Enterprise Manager console/repository compatibility and upgrade instructions. Either upgrade the repository or log into a compatible repository.

VAX-14002: Please log into a compatible repository or upgrade the repository.

Cause: The Oracle Enterprise Manager repository you are attempting to log into is older than (and incompatible with) the current version of the Oracle Enterprise Manager console.

Action: See the README file for Oracle Enterprise Manager console/repository compatibility and upgrade instructions. Either upgrade the repository or log into a compatible repository.

VAX-14003: To upgrade the repository, refer to the Oracle Enterprise Manager Readme.

Cause: The Oracle Enterprise Manager repository you are attempting to log into is newer than (and incompatible with) the version of the Oracle Enterprise Manager console you are running.

Action: See the README file for Oracle Enterprise Manager console/repository compatibility. Either log into a compatible repository or install a newer version of Oracle Enterprise Manager.

VAX-14004: Please log into a compatible repository or install a compatible version of Oracle Enterprise Manager."

Cause: The Oracle Enterprise Manager repository you are attempting to log into is newer than (and incompatible with) the version of the Oracle Enterprise Manager console you are running.

Action: See the README file for Oracle Enterprise Manager console/repository compatibility. Either log into a compatible repository or install a newer version of Oracle Enterprise Manager.

The messages VAX-14005 through VAX-14007 are show in a dialog as a single message.

VAX-14007: The necessary installation scripts have been run on the database.

Cause: An attempt was made to log into a schema that does not have the repository tables installed.

Action: Log into an account that has the repository tables.

VAX-15501: Execution mode invalid or not found.

Cause: Bad execution mode.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15502: Frequency clause invalid or not found.

Cause: The frequency clause is invalid.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15503: Start time invalid or not found.

Cause: Bad start date.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15505: Day of the week was not specified.

Cause: A day of the week was not specified.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15506: No day of the month was specified.

Cause: A day of the month was not specified.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15507: End time precedes start time.

Cause: The end time is before the start time.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15508: Interval out of range.

Cause: The interval is not valid.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15509: Generic

Cause: Unknown schedule error.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15510: Setting schedule to Immediate

Cause: A day of the week was not specified.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15511: Revert to previous schedule?

Cause: A day of the week was not specified.

Action: Do not save or submit a job which has an invalid schedule.

VAX-15512: Invalid Schedule Format

Cause: The schedule was invalid.

Action: Do not save or submit a job which has an invalid schedule.




Prev

Next
Oracle
Copyright © 1997 Oracle Corporation.

All Rights Reserved.

Library

Product

Contents

Index