Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## Boot Image Server Messages

##### OVS-04000: num: expected but did not find string

Cause: A string was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04001: num: expected but did not find comma

Cause: A comma was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04003: num: Expected but did not find 'boot' string

Cause: The string "boot" was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04004: num: expected but did not find open brace

Cause: An open brace was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04005: num: expected but did not find close brace

Cause: A close brace was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04006: num: expected but did not find EOF

Cause: End of file was expected on the indicated line of the configuration file.

Action: Edit the configuration file to conform with the documented syntax.

##### OVS-04007: cannot open boot config file 'str' for reading

Cause: An error occurred while attempting to open the indicated file.

Action: Confirm that the indicated file exists and is available for reading.

##### OVS-04008: cannot allocate memory for boot context

Cause: Memory was not available for the context of this process.

Action: Check memory allocation on the system/processor that was being used to run this program.

##### OVS-04009: boot config file did not contain 'str' rule

Cause: The configuration file did not contain the specified and required rule/mapping.

Action: Edit the configuration file and add the appropriate mapping. 4010 UNUSED

##### OVS-04011: error #num storing boot image context

Cause: The indicated error was returned when the context was stored via mtcctxPut.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04012: error retrieving boot image context

Cause: The indicated error was returned when the context was retrieved via mtcctxPut.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04013: boot image server exiting cleanly

Cause: The process ended normally.

Action: No action required.

##### OVS-04014: cannot update boot DB from file str

Cause: An error occurred while updating the internal mappings from the indicated configuration file.

Action: The type of error should appear in the log previous to this message. Check the error and edit the configuration file to conform with the documented syntax.

##### OVS-04015: cannot allocate memory for new client mapping

Cause: Memory was not available for a new mapping entry.

Action: Check memory allocation on the system/processor that was being used to run this program.

##### OVS-04016: error #num when trying to convert physical address

Cause: The provided physical address was malformed.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04017: boot image server exiting with errors

Cause: An error occurred which caused the boot image server to abend.

Action: Check the log for previous errors and take the appropriate action.

##### OVS-04018: failure creating a marshalling context for server stub

Cause: The data structure required for retrieving arguments could not be acquired.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04019: error during marshalling operation in server stub

Cause: A failure occurred while retrieving the arguments from a remote procedure call.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04020: RPC return call failed with error num

Cause: An error occurred when the results of an RPC were being returned to the remote client.

Action: This is an internal error. Contact Oracle for assistance.

##### OVS-04021: MDS initialization failed.

Cause: An error occured while attempting to initialize the MDS interface.

Action: Confirm that MDS is running on your system and check error log for possible failures.

##### OVS-04022: Malformed file name str provided.

Cause: The file name provided could not be formated by MDS.

Action: Verify that the file name provided is correctly formed for MDS native or host file operation.

##### OVS-04023: Attempt to access a host file while detached.

Cause: The file name provided points to a file on the host file system which is not currently accessible since this process has detached.

Action: Only MDS native files are accessible at this time. Use an MDS file instead.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index