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

## Authorization Service Messages

##### OVS-06000: error or trace logging error: str

Cause: An error occurred while attempting to write to the error log.

Action: Verify that the logger is running. If so, contact WWS.

##### OVS-06001: invalid object reference: str

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.

##### OVS-06002: persistent store data error: str

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.

##### OVS-06003: unexpected database error: str

Cause: A database error occurred while accessing the persistent store.

Action: Contact WWS.

##### OVS-06004: call to unimplemented method: str

Cause: The client application is attempting to invoke a method that has not been implemented.

Action: Only invoke methods that are implemented.

##### OVS-06005: RPC call failed: str

Cause: A communications error occurred while invoking a method.

Action: Contact WWS.

##### OVS-06006: could not allocate memory: str

Cause: A memory malloc failed in the method implementation.

Action: Contact WWS.

##### OVS-06007: could not find price: str

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.

##### OVS-06008: internal error: str

Cause: An internal error occurred in the method implementation.

Action: Contact WWS.

##### OVS-06009: value out of range: str

Cause: The value of a parameter passed to a method was out of range.

Action: Verify the method input parameter values.

##### OVS-06010: transaction begin failure: str

Cause: An error occurred while attempting to begin a transaction.

Action: Contact WWS.

##### OVS-06011: transaction rollback failure: str

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.

##### OVS-06012: transaction commit failure: str

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.

##### OVS-06013: invalid network address: str

Cause: A communication failure occurred while invoking a method.

Action: Contact WWS.

##### OVS-06014: bad parameter: str

Cause: An invalid parameter was passed to a method call.

Action: Verify input parameters, if ok contact WWS.

##### OVS-06015: unique key violation: str

Cause: Attempted to create a new object with an existing key.

Action: Choose a primary key not in use, preferrably from a sequence.

##### OVS-06016: bad service agent OR: str

Cause: Attempted to access an invalid service agent object.

Action: Contact WWS.

##### OVS-06017: bad account OR: str

Cause: Passed an invalid account object reference to a method.

Action: Use a valid account object reference.

##### OVS-06018: implementation limit: str

Cause: Required action for method has not been implemented.

Action: Contact WWS.

##### OVS-06019: invalid status on order: str

Cause: The status of an order is invalid.

Action: Contact WWS.

##### OVS-06020: service restricted

Cause: The selected service is restricted from the user.

Action: Select an unrestricted service.

##### OVS-06021: product is restricted

Cause: The selected product is restricted from the user.

Action: Select an unrestricted product.

##### OVS-06022: descriptor is restricted

Cause: The selected descriptor value is restricted from the user.

Action: Select an unrestricted descriptor value.

##### OVS-06023: budget limit reached

Cause: Attempted to make a purchase that would exceed a users budget.

Action: Raise user's budget or make a smaller purchase.

##### OVS-06024: payment unauthorized

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.

##### OVS-06025: no permission to create restriction

Cause: Attempted to use a non-primary user create a restriction.

Action: Create the restriction through a primary user.

##### OVS-06026: address type not valid

Cause: Passed an invalid address type to method.

Action: Use a valid address type.

##### OVS-06027: address owner type not valid

Cause: Passed an invalid address owner type to method.

Action: Use a valid address owner type.

##### OVS-06028: owner type for address already in use

Cause: Chose an owner type that was already associated with address.

Action: Choose an address owner type not in use.

##### OVS-06029: address primary flag value not valid

Cause: Passed an invalid primary flag value to method.

Action: Use a valid primary flag value.

##### OVS-06030: address owner already has an existing primary address

Cause: Attempted to give address owner more than one primary address.

Action: Set other owned address to be non-primary first, then re-call.

##### OVS-06031: address owner object not valid

Cause: Passed an invalid address owner object to method.

Action: Use a valid address owner object reference.

##### OVS-06032: object status value not valid

Cause: Attempted to make a purchase that would exceed a users budget.

Action: Use a valid object status value.

##### OVS-06999: unknown error: str

Cause: A peculiar error occurred in the method implementation.

Action: Contact WWS.

##### OVS-07002: Unable to open MDS File System

Cause: the utility could not contact the Media Data Store (MDS) server

Action: ensure the Media Data Store (MDS) server is running

##### OVS-07004: Unable to continue due to errors, see log for more details

Cause: the utility terminated due to a fatal error

Action: review the log for more details

##### OVS-07006: Error creating file: str

Cause: the utility was unable to create a file

Action: ensure the MDS volume used for this file is mounted read/write

##### OVS-07007: Error opening file: str

Cause: the utility was unable to open a file

Action: ensure the file exists and, if applicable, the volume is writable

##### OVS-07008: Error reading file: str

Cause: an error occurred while reading a file

Action: check the log for MDS errors during this write for more information

##### OVS-07009: Error writing file: str

Cause: an error occurred while writing a file

Action: check the log for MDS errors during this write for more information

##### OVS-07010: Marshaling Error in str, line num

Cause: the utility is out of memory

Action: make sure the utility has enough memory on its node

##### OVS-07011: Internal error in str, line num

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.

##### OVS-07012: Exiting due to invalid command line arguments

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.

##### OVS-07013: Error occurred reading header for tag file str

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.

##### OVS-07106: file I/O error

Cause: an error occurred while reading or writing a file

Action: check the log for MDS errors that clarify the problem

##### OVS-07107: error while attempting to print tag file

Cause: an error occurred while printing the tag file

Action: check the log for mkct errors that clarfy the problem

##### OVS-07201: error starting children (num)

Cause: the tagger master was unable to start its slave network

Action: make sure the proper environment variables have been set

##### OVS-07203: Unable to create wildCard context

Cause: the tagger is out of memory

Action: make sure the tagger has enough memory on its node

##### OVS-07209: error opening compressed file str

Cause: the utility was unable to open a file

Action: ensure the file exists and, if applicable, the volume is writable

##### OVS-07210: cannot append to file str; could not open it.

Cause: the utility was unable to open a file

Action: ensure the file exists and, if applicable, the volume is writable

##### OVS-07211: error reading tag file header for str

Cause: the tagger was unable to read the tag file header

Action: check log for mds errors, ensure the tag file version is current

##### OVS-07215: error creating temp file: str

Cause: the utility was unable to create a file

Action: ensure the MDS volume used for this file is mounted read/write

##### OVS-07217: error while reading or writing

Cause: an error occurred while reading or writing a file

Action: check the log for MDS errors that clarify the problem

##### OVS-07218: error: Only TagMode is implemented as a network operation

Cause: the user tried to run a parallel edit or parse

Action: this is a user error

##### OVS-07219: error pushing header onto queue

Cause: the tagger is out of memory

Action: make sure the tagger has enough memory on its node

##### OVS-07220: tag queue sync error, queueGetHeadType == num

Cause: An internal error occured during tagging.

Action: Report to Oracle.

##### OVS-07221: tagger mode error

Cause: An internal error occured during tagging.

Action: Report to Oracle.

##### OVS-07222: unable to setup RPC server

Cause: An internal error occured during tagging.

Action: Report to Oracle.

##### OVS-07223: error while getting options

Cause: An internal error occured during tagging.

Action: Report to Oracle.

##### OVS-07224: error: no matches to str found

Cause: A wildcard specification provided by the user matched no files

##### OVS-07225: error: flags must be specified

Cause: The flags were not specified to the program (usually command-line -f)

Action: Rerun the program and specify the flags

##### OVS-07231: unable to open slaves: str, system error str

Cause: the tagger master was unable to start its slave network

Action: make sure the proper environment variables have been set

##### OVS-07296: RPC Error: Unable to open server

Cause: a tagger slave was unable to start up as an RPC server

Action: check log for media net messages to clarify the problem

##### OVS-07298: Tagger File Sync Error

Cause: An internal error occured during tagging.

Action: Report to Oracle.

##### OVS-07299: mtuc num: Error marshaling tag str num

Cause: the tagger is out of memory

Action: make sure the tagger has enough memory on its node

##### OVS-07400: mdsOpen failed = num

Cause: mtuwrap was unable to open a file

Action: ensure the file exists and, if applicable, the volume is writable

##### OVS-07401: mdsCreate failed = num

Cause: the utility was unable to create a file

Action: ensure the file exists and that the MDS volume is writable

##### OVS-07402: malloc of protocolmsg failed

Cause: mtuwrap is out of memory

Action: make sure mtuwrap has enough memory on its node

##### OVS-07403: malloc of formatpacket failed

Cause: mtuwrap is out of memory

Action: make sure mtuwrap has enough memory on its node

##### OVS-07406: mdsWrite failed rc = num

Cause: an error occurred while writing a file

Action: check the log for MDS errors during this write for more information

##### OVS-07410: Unable to create str file: str

Cause: the utility was unable to create a file

Action: ensure the file exists and that the MDS volume is writable

##### OVS-07411: Error creating header

Cause: mtuwrap is out of memory

Action: make sure mtuwrap has enough memory on its node

##### OVS-07412: Unable to open str

Cause: mtuwrap was unable to open a file

Action: ensure the file exists and, if applicable, the volume is writable

##### OVS-07413: Unable to close str

Cause: mtuwrap was unable to close a file

Action: check log for MDS messages that clarify the problem

##### OVS-07417: Warning: blob block size of num may be too large for most client devices

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

##### OVS-07600: Error initializing mds wildcard search: num

Cause: mds returned an error when mfsi attempted to begin a wildcard search

Action: ensure file spec is valid, report to Oracle

##### OVS-07601: Unable to create RPC server

Cause: Internal Error

Action: Report to Oracle

##### OVS-07602: Memory error in str:num

Cause: Internal Error

Action: Report to Oracle

##### OVS-07603: Error calling mnrReturnCall in str

Cause: Internal Error

Action: Report to Oracle

##### OVS-07604: MediaNet rundown called for client str

Cause: Media Net thinks the client is dead so its state must be cleaned

##### OVS-07605: Unable to find server

Cause: The server is not running or Media Net had and error

Action: Ensure the server is running

##### OVS-07650: Unique IDs must be between 1 and 255, num is invalid

Cause: The blob librarian found an invalid id number in an input script

Action: Give all blobs an id between 1 and 255

##### OVS-07651: Unable to find member num

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.

##### OVS-07653: Duplicate blob id detected: num

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.

##### OVS-07700: Unique IDs must be between 1 and 255, num is invalid

Cause: The blob librarian found an invalid id number in an input script

Action: Give all blobs an id between 1 and 255

##### OVS-07701: Unable to find member num

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.

##### OVS-07703: Duplicate blob id detected: num

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.

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