Oracle Network Products Troubleshooting Guide

NMR Error Messages (NMR-00001 to 00500)

NMR-00001 generic operation failure

Cause: A ROS operation failed.

Action: The error generally appears below a more general error which will tell you where the problem is occurring. See the action text for that error.
NMR-00100 unexpected end of file

Cause: A ROS file operation detected an end-of-file when it was not expecting one, probably because the file has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00101 object not found

Cause: A ROS fetch operation failed to find any objects.

Action: The error generally appears below a more general error which will tell you where the problem is occurring. See the action text for that error.
NMR-00102 object unexpectedly found

Cause: A ROS operation found an object when it was not expecting to.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00103 value too big

Cause: A ROS operation received an incorrect value.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00104 invalid value

Cause: A ROS operation received an invalid value. expecting one, probably because the file has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00105 invalid data store

Cause: A ROS operation detected an invalid data store, probably because the data store has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00106 invalid object type

Cause: A ROS operation received a value with an invalid type.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00107 unexpected NULL value

Cause: A ROS operation received an unexpected empty value.

Action: n internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00108 undefined or invalid table name

Cause: A ROS operation was performed on an invalid table.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00109 invalid argument

Cause: A ROS operation received an invalid argument.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00200 ROS file error

Cause: A ROS file operation detected an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00201 unique key violation

Cause: A ROS file operation detected a unique key constraint violation.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00205 page split occurred

Cause: A ROS file operation detected a page split.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00207 cannot close, commit is pending

Cause: The ROS user attempted to close a data store with a commit pending.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00210 error creating file

Cause: The ROS file store create operation failed.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00211 file version error

Cause: ROS detected a file store with an incorrect version.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00212 file already open read-only

Cause: A ROS file operation received an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00213 file already open read-write

Cause: A ROS database operation received an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00301 disk space exhausted

Cause: The application has run out of memory.

Action: Add more memory or run fewer processes.
NMR-00402 memory allocation failed

Cause: The application has run out of memory.

Action: Add more memory or run fewer processes.
NMR-00403 memory free failed

Cause: The application's memory heap has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.