Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: An error occurred while attempting to write to the error log.
Action: Verify that the logger is running. If so, contact WWS.
Cause: An invalid object reference was passed to a method implementation.
Action: Verify that the client application is passing a valid object reference. If so, contact WWS.
Cause: An error occurred while accessing the persistent store. This typically means a database error has occurred. Refer to the explicit ORA-XXXX database error for more information.
Action: Contact WWS.
Cause: A database error occurred while accessing the persistent store.
Action: Contact WWS.
Cause: The client application is attempting to invoke a method that has not been implemented.
Action: Only invoke methods that are implemented.
Cause: A communications error occurred while invoking a method.
Action: Contact WWS.
Cause: A memory malloc failed in the method implementation.
Action: Contact WWS.
Cause: No price is associated with the selected product or product item.
Action: Verify that the selected product or product item has a price associated with the active price list for the user.
Cause: An internal error occurred in the method implementation.
Action: Contact WWS.
Cause: The value of a parameter passed to a method was out of range.
Action: Verify the method input parameter values.
Cause: An error occurred while attempting to begin a transaction.
Action: Contact WWS.
Cause: An error occurred while attempting to rollback a transaction.
Action: Verify that the transaction was started correctly using the T_BEGIN macro. If so, contact WWS.
Cause: An error occurred while attempting to commit a transaction.
Action: Verify that the transaction was started correctly using the T_BEGIN macro. If so, contact WWS.
Cause: A communication failure occurred while invoking a method.
Action: Contact WWS.
Cause: An invalid parameter was passed to a method call.
Action: Verify input parameters, if ok contact WWS.
Cause: Attempted to create a new object with an existing key.
Action: Choose a primary key not in use, preferrably from a sequence.
Cause: Attempted to access an invalid service agent object.
Action: Contact WWS.
Cause: Passed an invalid account object reference to a method.
Action: Use a valid account object reference.
Cause: Required action for method has not been implemented.
Action: Contact WWS.
Cause: The status of an order is invalid.
Action: Contact WWS.
Cause: The selected service is restricted from the user.
Action: Select an unrestricted service.
Cause: The selected product is restricted from the user.
Action: Select an unrestricted product.
Cause: The selected descriptor value is restricted from the user.
Action: Select an unrestricted descriptor value.
Cause: Attempted to make a purchase that would exceed a users budget.
Action: Raise user's budget or make a smaller purchase.
Cause: Either session and account payment device were one and the same or balance exceeded credit limit.
Action: Either make the session account and account payment device account distinct or raise account credit limit.
Cause: Attempted to use a non-primary user create a restriction.
Action: Create the restriction through a primary user.
Cause: Passed an invalid address type to method.
Action: Use a valid address type.
Cause: Passed an invalid address owner type to method.
Action: Use a valid address owner type.
Cause: Chose an owner type that was already associated with address.
Action: Choose an address owner type not in use.
Cause: Passed an invalid primary flag value to method.
Action: Use a valid primary flag value.
Cause: Attempted to give address owner more than one primary address.
Action: Set other owned address to be non-primary first, then re-call.
Cause: Passed an invalid address owner object to method.
Action: Use a valid address owner object reference.
Cause: Attempted to make a purchase that would exceed a users budget.
Action: Use a valid object status value.
Cause: A peculiar error occurred in the method implementation.
Action: Contact WWS.
Cause: the utility could not contact the Media Data Store (MDS) server
Action: ensure the Media Data Store (MDS) server is running
Cause: the utility terminated due to a fatal error
Action: review the log for more details
Cause: the utility was unable to create a file
Action: ensure the MDS volume used for this file is mounted read/write
Cause: the utility was unable to open a file
Action: ensure the file exists and, if applicable, the volume is writable
Cause: an error occurred while reading a file
Action: check the log for MDS errors during this write for more information
Cause: an error occurred while writing a file
Action: check the log for MDS errors during this write for more information
Cause: the utility is out of memory
Action: make sure the utility has enough memory on its node
Cause: An error occurred trying to parse an input blob script, possibly out of memory.
Action: Make sure the tool has adequate memory. If the problem persists, contact Oracle.
Cause: The blob librarian cannot function due to an errant command line argument.
Action: Make sure a library name, tagfile name, and input script name have been specified.
Cause: When trying to read the specified tag file, a problem occurred.
Action: Make sure the tag file is a valid tag file with the correct version. Also, consult the log for other errors.
Cause: an error occurred while reading or writing a file
Action: check the log for MDS errors that clarify the problem
Cause: an error occurred while printing the tag file
Action: check the log for mkct errors that clarfy the problem
Cause: the tagger master was unable to start its slave network
Action: make sure the proper environment variables have been set
Cause: the tagger is out of memory
Action: make sure the tagger has enough memory on its node
Cause: the utility was unable to open a file
Action: ensure the file exists and, if applicable, the volume is writable
Cause: the utility was unable to open a file
Action: ensure the file exists and, if applicable, the volume is writable
Cause: the tagger was unable to read the tag file header
Action: check log for mds errors, ensure the tag file version is current
Cause: the utility was unable to create a file
Action: ensure the MDS volume used for this file is mounted read/write
Cause: an error occurred while reading or writing a file
Action: check the log for MDS errors that clarify the problem
Cause: the user tried to run a parallel edit or parse
Action: this is a user error
Cause: the tagger is out of memory
Action: make sure the tagger has enough memory on its node
Cause: An internal error occured during tagging.
Action: Report to Oracle.
Cause: An internal error occured during tagging.
Action: Report to Oracle.
Cause: An internal error occured during tagging.
Action: Report to Oracle.
Cause: An internal error occured during tagging.
Action: Report to Oracle.
Cause: A wildcard specification provided by the user matched no files
Cause: The flags were not specified to the program (usually command-line -f)
Action: Rerun the program and specify the flags
Cause: the tagger master was unable to start its slave network
Action: make sure the proper environment variables have been set
Cause: a tagger slave was unable to start up as an RPC server
Action: check log for media net messages to clarify the problem
Cause: An internal error occured during tagging.
Action: Report to Oracle.
Cause: the tagger is out of memory
Action: make sure the tagger has enough memory on its node
Cause: mtuwrap was unable to open a file
Action: ensure the file exists and, if applicable, the volume is writable
Cause: the utility was unable to create a file
Action: ensure the file exists and that the MDS volume is writable
Cause: mtuwrap is out of memory
Action: make sure mtuwrap has enough memory on its node
Cause: mtuwrap is out of memory
Action: make sure mtuwrap has enough memory on its node
Cause: an error occurred while writing a file
Action: check the log for MDS errors during this write for more information
Cause: the utility was unable to create a file
Action: ensure the file exists and that the MDS volume is writable
Cause: mtuwrap is out of memory
Action: make sure mtuwrap has enough memory on its node
Cause: mtuwrap was unable to open a file
Action: ensure the file exists and, if applicable, the volume is writable
Cause: mtuwrap was unable to close a file
Action: check log for MDS messages that clarify the problem
Cause: The blob block size should not be larger than the client device can buffer for one MediaNet packet. If so, the blob will always fail.
Action: Make sure that the client device can buffer a MediaNet packet of the specified size, or pick a smaller packet size. mtutc
Cause: mds returned an error when mfsi attempted to begin a wildcard search
Action: ensure file spec is valid, report to Oracle
Cause: Internal Error
Action: Report to Oracle
Cause: Internal Error
Action: Report to Oracle
Cause: Internal Error
Action: Report to Oracle
Cause: Media Net thinks the client is dead so its state must be cleaned
Cause: The server is not running or Media Net had and error
Action: Ensure the server is running
Cause: The blob librarian found an invalid id number in an input script
Action: Give all blobs an id between 1 and 255
Cause: The blob librarian was asked to extract a blob with an unknown id number.
Action: Use mtutagprint to find the valid id numbers for blobs in the library.
Cause: The blob librarian found two blobs in the input file with the same id number.
Action: These number must be unique. Give each blob a unique id number.
Cause: The blob librarian found an invalid id number in an input script
Action: Give all blobs an id between 1 and 255
Cause: The blob librarian was asked to extract a blob with an unknown id number.
Action: Use mtutagprint to find the valid id numbers for blobs in the library.
Cause: The blob librarian found two blobs in the input file with the same id number.
Action: These number must be unique. Give each blob a unique id number.
