Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
Action: This is an internal error. Contact customer support.
Action: This is an internal error. Contact customer support.
Action: This is an internal error. Contact customer support.
Action: This is an internal error. Contact customer support.
Cause: A OCS config file was not found.
Cause: A keyword was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: An open brace was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: A close brace was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: An upstream address was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: An equal sign was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: A downstream address was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: A upstream address was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: A downstream address was expected in the OCS config file
Action: Correct error in the OCS config file and restart.
Cause: A syntax error in the OCS config file
Action: Correct syntax error in the OCS config file and restart.
Cause: A separator character was expected in the OCS config file
Action: Correct syntax error in the OCS config file and restart.
Cause: Disk reads may not complete in time when your volume is overloaded or a stream is in ff/rw mode some disk is dead.
Action: Verify all disks in your volume are healthy and make sure you have configured a volume that is big enough to support all your concurrent streams.
Cause: The stream service asked the pump to play from past the end of a file.
Action: Verify the file being played and its tag file are valid and up to date.
Cause: The pump was asked to write to a downstream device that was not previously opened. The device can either be opened at initialization time via command line arguments or at run time via an RPC call from the upstream manager.
Action: Verify that either your DSM specifier command line argument is correct or that that upstream manager has been configured with network provisioning turned on.
Cause: The hostname given in the DSM specifier on the vpump command line is unknown by the system.
Action: Check that the hostname is listed in /etc/hosts or use the IP address directly in the DSM specifier.
Cause: An error occurred in the operating system UDP/IP library.
Action: Verify UDP is alive and working on your server.
Cause: An error occurred in the operating system UDP/IP library.
Action: Verify UDP is alive and working on your server.
Cause: The video pump can not open the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: The video pump can not open the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: The video pump can not send data to the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: The video pump can not send data to the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: Media net was unable to create an RPC service.
Action: This is an internal error. Contact customer support.
Cause: Media net was unable to register an RPC service.
Action: Verify media net and, in particular, the name service are ok.
Cause: MDS was unable to create the raw dump file.
Action: Verify the raw dump file name specified on the command line is a valid MDS file name. Make sure MDS is up and running.
Cause: Communication with the connection service failed.
Action: Verify the connection service is up.
Cause: The stream service issued an unrecognized command to the pump.
Action: This is an internal error. Contact customer support.
Cause: The lookup operation on the connection service failed.
Action: Verify the connection service is up.
Cause: The video pump can not connect to the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: The video pump can not close the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: A file could not be opened in a reasonable amount of time.
Action: Make sure MDS is up and functioning properly.
Cause: The initial reads of a file to prime the internal cache did not complete in a reasonable amount of time.
Action: Make sure MDS is up and functioning properly.
Cause: The video pump can not open the downstream device.
Action: Verify the down stream device is functioning properly.
Cause: The video pump can not initialize MDS.
Action: Make sure MDS is up and functioning properly.
Cause: A spurious stop RPC was received.
Action: This is somewhat unusual but not harmful, no action needed.
Cause: A spurious initialize RPC was received.
Action: This is somewhat unusual but not harmful, no action needed.
Cause: Media net was unable process the RPC call.
Action: This is an internal error. Contact customer support.
Cause: The video pump could not make sense out of data in the file.
Action: Verify the file in question is valid.
Cause: During ff/rw, invalid file data was seen.
Action: Verify that the playing file is valid.
Cause: During ff/rw, invalid file data was seen.
Action: Verify that the playing file is valid.
Cause: During ff/rw, invalid file data was seen.
Action: Verify that the playing file is valid.
Cause: The stream service is issuing invalid RPC calls to the video pump.
Action: This is an internal error. Contact customer support.
Cause: The video pump was not started with a valid buffer size argument.
Action: Examine the video pump's usage statement and add the correct argument to the command line.
Cause: The video pump was not started with a valid buffer size argument.
Action: The output buffer size must be a multiple of the format packet size.
Cause: The video pump could not make sense out of data in the file.
Action: Verify the file in question is valid.
Cause: The video pump ran out of communication buffer space.
Action: Verify you have enough memory to run all your streams.
Cause: Requested address familiy did not match the one supported by this binary.
Action: Check arguments to insure the FamilyPVC resource is being set to the correct family.
Cause: mzup could not connect to the specified vc/vp.
Action: check your configuration to insure that the vc/vp is valid.
Cause: The program thinks the service has gone down. It may be really dead, or the system may be overloaded and a request to the service has timed out even though the service is still alive.
Action: find out if the service really is dead, or the system is slow. If the service is dead, decide if you can restart it by hand, or if you will need to restart the entire system.
Cause: the program is forgetting it ever knew about the service. attempts to requery for data about that service will fail.
Cause: The program thinks the process has gone down. It may be really dead, or the system may be overloaded and a request to the process has timed out even though the process is still alive.
Action: find out if the process really is dead, or the system is slow. If the process is dead, decide if you can restart it by hand, or if you will need to restart the entire system.
Cause: the program is forgetting it ever knew about the process. attempts to requery for data about that process will fail.
Cause: this is often caused by (a) a missing or broken master snmp agent (b) missing 'snmp.ora' file, or (c) bad syntax in the snmp.ora file
Action: (a) check to see if your master snmp agent is present and running correctly by running SNMP queries to standard MIBs. (b) make sure you have ORACLE_HOME defined in your environment and have an 'snmp.ora' in ORACLE_HOME/network/admin. (c) locate your syntax error by progressively simplifying your 'snmp.ora' file until the agent will start. An empty file is legal and should work.
Cause: Could not find a pump thread for an emulated set-top box
Action: Start up more vpump processes
Cause: Either a client could not reach its stream instance, or a stream instance could not reach its corresponding video pump
Action: Check to make sure these parts of the server are running properly
Cause: An error occurred trying to marshal RPC data - usually out of memory
Action: See if the reporting process is in a low memory state
Cause: A call to alloc didn't succeed, but the client continued to try to use the context.
Action: This indicates application error, following a server configuration problem. Use the logs to figure out why the allocate failed, and fix the application to not use invalid contexts.
Cause: An error occurred trying to map to a pump for an emulated STB
Action: Make sure a sufficient number of pumps are running and OCS is up and functional
Cause: Something unusual was noted when tearing down a circuit. This is normal for emulated STB's
Action: For emulated STB's, nothing. For real STB's, make sure OCS and all video pumps are still functional
Cause: An error occurred enabling SNMP monitoring in the stream instance
Action: Examine the log for accompanying MediaNet errors
Cause: An error occurred returning SNMP information. Probably low memory.
Action: Make sure the stream instance isn't in a low memory state.
Cause: An error occurred returning SNMP information.
Action: Make sure the SNMP agent is still active.
Cause: The process server has notified us that a client is no longer active.
Action: None; this merely notes an abnormal termination of a client.
Cause: The stream service was asked to boot with an untagged boot file.
Action: All boot files must be tagged with mtuwrap.
Cause: MediaNet reported a client error receiving a BLOB
Action: Examine logs for further MediaNet information
Cause: MediaNet reporter a server error sending a BLOB
Action: Examine logs for further MediaNet information
Cause: An effort was made to boot with a boot file from an incompatible version of server software
Action: Retag the boot image with the current software version
Cause: Either someone tried to prepare a non-tagfile, or the tagfile has been corrupted.
Action: Verify that the file in question is really a tagfile. If so, it may have been corrupted and should be retagged.
Cause: When trying to get information on a file for an mzsQuery, we were unable to open a file.
Action: Examine logs for further MDS information.
Cause: An error was reported by MediaNet during a blob transfer.
Action: Examine logs for further MediaNet information and see the reported MediaNet error number.
Cause: MediaNet asked us to do a partial retransmit of a blob from an invalid starting point.
Action: This will not prevent BLOB download, but will make it less efficient. Retag the BLOB. If the problem persists, it is likely a MediaNet error.
Cause: MediaNet asked us to partially retransmit a BLOB.
Action: This does not normally constitute an error.
Cause: mzsi was unable to register itself with the process server.
Action: Examine logs for further MediaNet information.
Cause: mzsi was unable to register itself with the process server.
Action: Examine logs for further MediaNet information.
Cause: mzsi was unable to add SNMP monitoring support for itself.
Action: Examine logs for information from the SNMP agent.
Cause: There was insufficient memory to allocate all requested contexts.
Action: Either provide more memory for the stream instance, or lower the requested number of streams per instance.
Cause: An mds error was encountered when trying to perform a wildcard query
Action: Examine logs for further mds information.
Cause: A disk error was detecting during an mtuedit
Action: Examine logs for further mds information
Cause: A disk error occurred creating a file for mtuedit
Action: Examine logs for further mds information
Cause: An syntax error was found when parsing MPEG content.
Action: Verify that the content is uncorrupted and valid.
Cause: A continuity error was found when parsing MPEG content.
Action: Verify that the content is uncorrupted and valid.
Cause: An syntax error was found when parsing MPEG content.
Action: Verify that the content is uncorrupted and valid.
Cause: An internal error occurred during tagging.
Cause: The stream service discovered an error, such as an incompatible version, when opening the specified tag file.
Action: Make sure the tagfile version matches the current server, and if not, retag it.
Cause: All members of a tagfile were inappopriate for the client who requested a play. This is usually caused by having no member with the correct compression format or all members having a bitrate that is too high for the client.
Action: Make sure the client is requesting a stream appropriate for them.
Cause: When trying to access a tag file, we found no MPEG time stamps.
Action: Attempt to retag the content. If the problem recurs, the content is likely invalid.
Cause: A disk error occurred when trying to write a tag file.
Action: Examine logs for further mds information.
Cause: A disk read error occurred when trying to patch a tag file.
Action: Examine logs for further mds information.
Cause: The -m flag to mtutagpatch indicated an invalid member number.
Action: mtutagprint the tag file, and reexecute with a valid member number.
Cause: All members of a tagfile were inappopriate for the client who requested a play.
Action: Make sure the client is requesting a stream appropriate for them.
Cause: All members of a tagfile were inappopriate for the client who requested a play.
Action: Make sure the client is requesting a stream appropriate for them.
Cause: All members of a tagfile were inappopriate for the client who requested a play.
Action: Make sure the client is requesting a stream appropriate for them.
Cause: The stream service has detected an MPEG2 tag with nonsensical data This can be caused by an old version of the tagger, or a corrupt file.
Action: Retag the file with the current version of the tagger. If the problem persists, report to Oracle.
Cause: A start time after an end time was given when going forwards.
Action: This indicates a bad parameter passed from a client. Try again with legal times.
Cause: A start time before an end time was given when going backwards.
Action: This indicates a bad parameter passed from a client. Try again with legal times.
Cause: The client registered as incapable of single-stream rate control and requested a play rate for which there no encoded member
Action: Make sure the client is requesting a stream appropriate for them.
Cause: The server received invalid context information.
Action: This indicates an internal error in some piece of software. Report to Oracle.
Cause: An mzs command was called with time specified in a time format that is not yet supported.
Action: This indicates a client software error. The client must call mzs with a time format currently supported, as indicated in mzs.h.
Cause: An effort was made to download a blob without a tagfile.
Action: Tag the BLOB using mtuwrap and download using the tagfile.
Cause: The tag file for a BLOB was wrapped with a version of the server that is incompatible with the current version.
Action: Use mtuwrap to wrap the BLOB again.
Cause: The stream service received a bad boot request.
Action: This indicates an error in the software
Cause: The stream service was asked to play a movie, boot image, or blob that has no tag file.
Action: Either correct the name or tag the content if necessary.
Cause: The server was asked to play a piece of content without a tag file, and could not determine the length of the raw content.
Action: Examine logs for further mds information.
Cause: A client passed a non-null terminated stream id to query.
Action: The server will prepare this, but it is not desirable and the client software should be changed to prevent this. ## mkc
Cause: An error occurred creating a parse output file.
Action: Examine logs for further mds information.
Cause: The tagger is unable to tag the content provided
Action: use mtumpeg to determine more clearly what is wrong with the file
Cause: The tagger is unable to tag the content provided
Action: replace mpeg file, it is invalid
Cause: When the stream service tried to authorize movie play via the POD service, the request was denied.
Action: Verify that the client is in fact authorized for the given content.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: The client asked to perform a VCR operation that their box cannot support.
Action: This indicates an error in the client software.
Cause: We were unable to find the pump servicing a particular STB
Action: This indicates a problem with the address allocation system. Make sure the upstream manager, OCS, and video pumps are functional.
Cause: We were not able to establish a session for a given STB's pump
Action: This indicates an mzsi/vpump communication error. Examine the video pump and MediaNet network to identify possible problems.
Cause: A client has expressed interest in playing streams faster than the server can currently support.
Action: This is unsupported. Do not do it.
Cause: An mzsPlay call was made without a preceding mzsPrepare call.
Action: This indicates a problem with the client software.
Cause: We were not able to send a command to a given STB's pump
Action: This indicates an mzsi/vpump communication error. Examine the video pump and MediaNet network to identify possible problems.
Cause: We were not able to send a command to a given STB's pump
Action: This indicates an mzsi/vpump communication error. Examine the video pump and MediaNet network to identify possible problems.
Cause: This occurs if a client tries to position past either end of a stream.
Action: Confine requests to the size of the stream.
Cause: An error occurred preparing data for communication with the vpump. This was probably caused by low memory.
Action: Make sure there is sufficient memory for the stream instance.
Cause: An effort was made to random access a piece of content without a tag file.
Action: This is unsupported. Tag the content if random access is required.
Cause: An error occurred preparing data for communication with the vpump. This was probably caused by low memory.
Action: Make sure there is sufficient memory for the stream instance.
Cause: The client passed an unknown context to the mzsFinish call.
Action: This indicates either a client software error or an internal error in the stream instance. If the latter, call Oracle.
Cause: The stream instance was asked to boot a STB, but the given address is invalid.
Action: This probably indicates a client software or MediaNet problem.
Cause: The stream instance was asked to boot a STB, but there does not appear to be a pump for the given STB.
Action: This indicates a problem with the address acquisition mechanism. Make sure MediaNet, OCS, and the vpump are functional.
Cause: The boot file selected for a client is inappropriate for the client. This would be the case if it is wrapped in a transport that the box does not understand.
Action: Rewrap the image, or boot with a different appropriate boot image.
Cause: An error occurred when trying to reposition in a stream.
Action: Examine the log for surrounding errors that give more details.
Cause: A client tried to reposition in a stream that has a null tagfile.
Action: Null tagfiles cannot be used for random access. If it is required, create a full tagfile for the content.
Cause: mzsPrepare was called with the PlayNow flag. The prepare succeeded, but the play failed for some reason.
Action: The log should indicate the reasons for the play failing.
Cause: Unsupported flags were passed for a BLOB transer.
Action: This indicates an error with the client software.
Cause: An internal error occurred while preparing to play at a non-1x rate.
Cause: An error occurred preparing data for communication with the vpump. This was probably caused by low memory.
Action: Make sure there is sufficient memory for the stream instance.
Cause: The stream ID passed to TransferBlob did not appear to be a member number and library name specified by a space
Action: Make sure all blobs are in library format and are requested in this format.
Cause: A blob number less than 1 or greater than 255 was detected in a blob request.
Action: Only request blobs with valid identification numbers
Cause: When trying to parse the member number for a blob library member, a non-numeric digit was found.
Action: Make sure blobs are requested with stream ID's in the proper format.
Cause: When verifying a tag file, a potentially corrupt tag was found.
Action: Retag the file. If the problem persists, call Oracle.
Cause: When verifying a tag file, a potentially corrupt tag was found.
Action: Retag the file. If the problem persists, call Oracle.
Cause: The server has detected an error in its internal state.
Cause: The server has detected an error in its internal state.
Cause: A string was expected on the indicated line of the configuration file.
Action: Edit the configuration file to conform with the documented syntax.
Cause: A comma was expected on the indicated line of the configuration file.
Action: Edit the configuration file to conform with the documented syntax.
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.
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.
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.
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.
Cause: An error occurred while attempting to open the indicated file.
Action: Confirm that the indicated file exists and is available for reading.
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.
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
Cause: The indicated error was returned when the context was stored via mtcctxPut.
Action: This is an internal error. Contact Oracle for assistance.
Cause: The indicated error was returned when the context was retrieved via mtcctxPut.
Action: This is an internal error. Contact Oracle for assistance.
Cause: The process ended normally.
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.
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.
Cause: The provided physical address was malformed.
Action: This is an internal error. Contact Oracle for assistance.
Cause: An error occurred which caused the boot image server to abend.
Action: Check the log for previous errors and take the appropriate action.
Cause: The data structure required for retrieving arguments could not be acquired.
Action: This is an internal error. Contact Oracle for assistance.
Cause: A failure occurred while retrieving the arguments from a remote procedure call.
Action: This is an internal error. Contact Oracle for assistance.
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.
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.
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.
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.
Cause: The file service process ended normally.
Cause: The file service has detected an error in its internal state.
Action: This is an internal error. Contact Oracle for assistance.
Cause: Allocation of an unmarshalling data structure failed.
Action: This is an internal error. Contact Oracle for assistance.
Cause: Allocation of a marshalling data structure failed.
Action: This is an internal error. Contact Oracle for assistance.
Cause: Allocation of a global context failed.
Action: This is an internal error. Contact Oracle for assistance.
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.
Cause: Media net could not bind a server context.
Action: This is an internal error. Contact Oracle for assistance.
Cause: Incoming RPC dispatch failed due to a network error.
Cause: Incoming RPC call could not be completed due to a network error.
Cause: This program requires that a voltab file be specified.
Action: Rerun the program and specify the voltab file using the appropriate command line option.
Cause: An internal error occurred while trying to verify the volume information on the disk.
Action: Contact Oracle customer support.
Cause: Cannot open or access the voltab file.
Action: Verify that the voltab file exists and its access permissions allow the program to read it.
Cause: The process failed to open and initialize the indicated disk for the reasons above.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: MDS failed to mount all volumes.
Action: See the log for related error messages.
Cause: The number of disks in the volume must be a multiple of the raid width, which is indicated in the "width" parameter in the voltab file.
Action: Fix the voltab file by modifying the raid width or the number of disks that comprise the volume.
Cause: An internal error occurred while seeking within the indicated file.
Action: Contact Oracle customer support.
Cause: All disks in a volume must have the same size.
Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).
Cause: All disks in a volume must have the same size.
Action: Check that all disks within the volume have the same size. Replace the odd-sized disk(s).
Cause: The indicated disk name does not have the proper format.
Action: Fix the syntax error which occurred, most likely in the voltab file or on the command line.
Cause: This server cannot access the indicated volume because the version of the server is incompatible with the version of the volume. This volume was probably created by a newer version of MDS whose format is not recognized by older versions of MDS.
Action: Use a more current version of MDS.
Cause: The process received the signal indicated.
Action: No action required. The log may contain errors from failures related to receipt of this signal.
Cause: An internal error occurred while reading within the indicated file.
Action: Contact Oracle customer support.
Cause: An internal error occurred while writing within the indicated file.
Action: Contact Oracle customer support.
Cause: The MDS server failed to read the table of contents for the indicated volume.
Action: Check the log for related error messages concerning disk I/O.
Cause: The stripe size indicated by "width" in the voltab file is not a legal value.
Action: Modify the voltab file to use a legal stripe size.
Cause: A syntax error was found in the voltab file.
Action: Fix the syntax error in the voltab file by using the format specified in the documentation.
Cause: None of the disks are responding to queries about their disk size.
Action: See the log for related error messages.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: The indicated volume was not mounted.
Action: See the log for related error messages.
Cause: The indicated volume needs to be converted to a different format in order to be compatible with MDS. The conversion can only occur if the volume is mounted in read-write mode.
Action: Remount the volume in read-write mode.
Cause: The table of contents is full.
Action: Remove unused files from the volume.
Action: Remove unused files from the volume.
Action: Contact Oracle customer support.
Cause: An internal error occurred while copying files.
Action: Contact Oracle customer support.
Action: No action required. The log may contain errors from failures related to the lost message.
Cause: This process is an MDS client and is unable to locate the MDS server.
Action: Verify that an MDS server is running and accessible to the client.
Cause: The indicated voltab filename contains a syntax error.
Action: Rerun the program using a voltab filename with legal syntax.
Action: Contact Oracle customer support.
Cause: A write to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: A flush to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: An internal error occurred while reading within the indicated file.
Action: Contact Oracle customer support.
Cause: An internal error occurred while writing within the indicated file.
Action: Contact Oracle customer support.
Cause: A read to the indicated disk failed for the reasons given.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The system-dependent error indicated occurred while waiting for disk I/O to complete.
Action: See your operating system documentation.
Cause: The voltab specification includes more disks per volume than allowed.
Action: Modify the voltab file to use fewer disks.
Cause: The indicated I/O operation failed because too many errors occurred.
Action: See the log for related error messages.
Cause: This program requires that the indicated argument be a legal filename.
Action: Rerun the program with a valid target filename.
Cause: An error occurred while verifying the volume's attributes.
Action: See the log for related error messages.
Action: Contact Oracle customer support.
Cause: The process cannot allocate memory for the I/O operation.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: An error occurred while modifying the table of contents.
Action: See the log for related error messages.
Cause: The table of contents is full.
Action: Remove unused files from the volume.
Action: Remove unused files from the volume.
Cause: MDS failed to mount the indicated volume.
Action: See the log for related error messages.
Action: Contact Oracle customer support.
Cause: An error occurred during rebuild.
Action: See the log for related error messages.
Action: Contact Oracle customer support.
Cause: The indicated disk is not responding to queries about its disk size.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The server does not have as much bandwidth as the client requested in the indicated volume.
Action: Be prepared to encounter out-of-bandwidth errors. No immediate action required.
Cause: The server does not have enough bandwidth for the client in the indicated volume.
Action: Wait for other processes to free up bandwidth.
Cause: An I/O did not complete because it timed-out.
Action: See the log for related error messages.
Cause: A request to the MDS server did not complete because it timed-out.
Action: See the log for related error messages.
Cause: The number or size of the input files have changed since the program was run.
Cause: The indicated input file has changed since the program was run.
Cause: The process failed to open the indicated disk.
Action: Contact Oracle customer support.
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: A volume can only be rebuilt if it is mounted in read-only or read-write mode.
Action: Remount volume in read-only or read-write mode.
Cause: The TOC of a volume can only be initialized if it is mounted in read-write mode.
Action: Remount volume in read-write mode.
Cause: The disk indicated needs to be rebuilt.
Action: Run mdsrebuild immediately.
Cause: The disks above both need to be rebuilt. However, since the failures are within the same raid stripe, they cannot both be rebuilt.
Action: Contact Oracle customer support.
Cause: An I/O error occurred on the disk indicated.
Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.
Cause: An I/O error occurred on the disk indicated.
Action: Determine if the disk is broken. If it is, bring up MDS and specify the disk as a broken disk. Replace the disk with a working one and rebuild it immediately.
Cause: The volume attributes on disk do not match the input voltab for any of the disks. The volume probably has not been initialized via mdsinit.
Action: If this is the case, run mdsinit to initialize the volume attributes.
Cause: Each volume or volume set can only support one outstanding disk rebuild at any time.
Action: Wait until the conflicting rebuild has completed before starting this disk rebuild.
Cause: Cannot read the volume attributes or mode from the indicated disk. In addition, the disk cannot be rebuilt because the volume does not contain parity information.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: The volume indicated cannot be mounted because the volume it is supposed to share bandwidth with is not mounted.
Action: Mount the volume with its own bandwidth resources or mount the volume whose bandwidth is to be shared first.
Cause: A volume must have a bandwidth capacity specified in order to be mounted.
Action: Specify the bandwidth capacity for the volume when mounting it.
Cause: The address is either negative or exceeds the size of the file.
Action: Rerun the program with a legal input address.
Cause: The start address must be smaller than the end address.
Action: Rerun the program with a legal start address.
Cause: The input voltab must correspond to the volume containing the disk being rebuilt.
Action: Rerun the program with the correct voltab or initialize the disk directly.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: The file indicated cannot be opened.
Action: Verify that the file exists and that its access permission allow the desired type of access.
Cause: The host file operation indicated failed.
Action: Verify that the file exists and that its access permission allow the desired type of access.
Cause: The server cannot be created for reasons provided above.
Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.
Cause: The server cannot be registered for reasons provided above.
Action: If the name server already contains an entry for MDS, restart the system. Otherwise, contact Oracle customer support.
Cause: Another MDS server or utility is holding the lock to the global lock manager.
Action: If this process is still hung, contact Oracle customer support.
Cause: The rebuild process cannot open a file that needs to be rebuilt.
Action: See the log for related error messages.
Cause: A volume must be mounted in read-write mode in order to be converted to a version compatible with this server.
Action: Remount the volume in read-write mode.
Action: Contact Oracle customer support.
Cause: The host file indicated cannot be created.
Action: Verify that the filename is legal and the directory's access permissions.
Cause: The host file indicated cannot be closed.
Action: Verify that the file exists.
Cause: The file indicated is being written by another MDS client.
Action: Wait for that process to close the file.
Cause: The defragmentation slaves could not be launched.
Action: Verify that the defragger was started up as indicated in the documentation. If the problem persists, contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: A previous error occurred.
Action: See the log for related error messages.
Cause: A previous error occurred.
Action: See the log for related error messages. The indicated file must be reloaded since its image on disk may have been corrupted.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: The indicated process is not exiting due to a previous error.
Action: Inform Oracle customer support. No immediate action required.
Cause: The indicated process is not exiting due to a previous error.
Action: Inform Oracle customer support. No immediate action required.
Cause: The volume indicated cannot be mounted because of the mount status of another MDS server.
Action: Remount the volume in a mode that does not conflict with the other MDS server(s).
Cause: The read operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The write operation indicated failed.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The disk cannot be set to normal mode.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The disk cannot be set to rebuild mode.
Action: Check to see if the disk or disk driver has failed. If no hardware or operating system problems are found, contact Oracle customer support.
Cause: The address is either negative or exceeds the size of the file.
Action: Rerun the program with a legal input address.
Action: Contact Oracle customer support.
Cause: A volume must have a bandwidth capacity specified in order to be mounted.
Action: Specify the bandwidth capacity for the volume.
Cause: A volume cannot be unmounted if MDS clients are actively reading and writing files in that volume.
Action: Wait for all MDS clients to close the files in that volume before unmounting it.
Cause: A volume cannot be remounted if MDS clients are writing to files in that volume.
Action: Wait until all MDS clients have finished writing to the volume.
Action: Contact Oracle customer support.
Cause: The volume indicated was not unmounted.
Action: See the log for related error messages.
Cause: The volume indicated was not remounted.
Action: See the log for related error messages.
Cause: The errors encountered while trying to remount the indicated volume are fatal.
Action: See log fore related error messages. Contact Oracle customer support.
Cause: A volume cannot be remounted with less bandwidth capacity.
Action: Remount the volume with at least the same amount of bandwidth capacity.
Cause: To mount a volume, the voltab must be specified.
Action: Remount the volume and specify the voltab.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Action: Contact Oracle customer support.
Cause: Files that have been deleted cannot be modified.
Action: If you really want to write to the deleted file, recover the file first by undeleting it.
Cause: The volume's table of contents is larger than the volume.
Action: Verify that the volume hasn't inadvertently shrunk. If not, then decrease the TOC size by specifying a smaller value in the voltab.
Cause: The size of the volume's TOC has probably been recently increased. The new TOC is occupying disk space also occupied by the indicated file.
Action: If the size of the volume's TOC has indeed been recently increased, then revert back to the original TOC size. Remove the conflicting files before increasing the TOC size.
Cause: The user has specified the same filename for both the source and destination file for an operation that requires the source filename to be different than the destination. Example: mdscp, mdsconcat.
Action: Use different files for src and dst; be aware that wildcarding or links may cause different filenames to refer to the same file.
Cause: The user has specified incompatible resources. A common cause is specifying incompatible arguments to a process, such as both length_in_bytes and end_address for mdssum.
Action: Consult the documentation for the correct usage.
Cause: The user has specified a relative filename and the resource mds.cwd is not set. Mds does not know where the file may reside.
Action: Specify an absolute pathname (beginning with /mds), or set the mds.cwd resource, i.e. setenv MDS_CWD /mds/int1
Cause: The TOC of the volume appears to be corrupt. This is usually caused by having run mdsvolinit on the volume to change the spec of the TOC, and using a modified voltab file with a different raidsize or stripe width.
Action: If the cause is as described above, rerun mdsvolinit with the correct voltab information. If not, contact WWS.
Cause: The indicated volume is currently being mounted by another MDS server and has not yet been rebuilt. Consequently, the disk mode cannot be set to normal.
Action: Rebuild the indicated disk as soon as possible.
Cause: The volume attributes on this disk do not correspond with the volume's.
Action: Check the voltab information and verify that it is correct. If the disk should be rebuilt or spared, follow the procedure as documented.
Cause: An attempt to read volume information for the indicated disk failed. MDS expects this disk to be up and readable because either the volume doesn't have parity or another disk disk within the same raid stripe has already failed.
Action: Check the voltab information and verify that it is correct. Check that the disk is on-line and operating correctly. If the error still occurs, contact Oracle customer support.
Cause: MDS expects all of the volumes that exist on the indicated disk to be listed in the input voltabs.
Action: Check that all volumes that exist on the indicated disk are on one of the input voltabs and that the input voltabs are correct.
Cause: MDS is unable to read or find the disk status information for the indicated volume.
Action: Check that the voltab information is correct. Verify that all disks in the volumes are in the correct mode. Verify that all disks in the volume are on-line and operating correctly. If the error still occurs, contact Oracle customer support.
Cause: Another MDS process has exclusively control of the MDS lock.
Action: Wait for a few seconds and rerun mdsrebuild.
Action: Contact Oracle customer support.
Cause: If a disk is in use a spare, another disk cannot be spared to it.
Action: Either: choose another disk to spare to or unspare the spare disk.
Cause: Spare disks depend on parity protection to rebuild missing info. Without parity, you cannot spare a disk.
Action: None possible other than a complete redo of volume with parity.
Cause: Mds believes that the disk is potentially in use by another server. As such, it cannot safely return the disk to normal mode until all known and in-use partitions on the disk have been rebuilt.
Action: Run mdsrebuild within the other servers to rebuild the other partitions of the new disk. When the disk is completely rebuilt, use mdsdiskmode to return the disk to normal mode.
Cause: The volume was created with a spare disk that is no longer specified or does not match the name of the spare that was originally used.
Action: Correct the voltab to list the original spare disk name, or run "mdsvolinit -s" to change the spare disk name on the other disks.
Cause: You cannot spare an operating disk to another operating disk. You can only spare a normal operating disk to a specified spare.
Action: Make sure you are sparing a normal disk in the volume to one of the specified spares for that volume.
Cause: The disk (or possibly simulated disk, i.e. a file) is too small.
Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: The TAR header appears to be corrupt.
Action: Obtain a new copy of the TAR archive.
Cause: mdstar was unable to open the archive (usually a physical device).
Action: Check the device or archive name for legality and the correct permissions. Check for hardware connectivity problems.
Cause: mdstar was unable to close the archive (usually a physical device). May be caused by premature shutdown or loss of archive device.
Action: None. However this warning may indicate that the TAR archive may be incomplete.
Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.
Action: Obtain a new copy of the TAR archive.
Cause: The TAR archive appears to be corrupt. Tar must always read block multiples of 512 bytes.
Action: Obtain a new copy of the TAR archive.
Cause: The TAR archive appears to be corrupt. mdstar expected a TAR archive header and found a bad checksum within the header.
Action: Obtain a new copy of the TAR archive.
Cause: The segment length and offset are invalid. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: Missing a segment. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed and complete. If they are, contact WWS.
Cause: Failed to parse the next segment name. This could either be an internal error, or tar is encountering filenames with incorrect segment information.
Action: Check the segmented filenames carefully to see if they are properly formed. If they are, contact WWS.
Cause: Unexpected write error probably caused by read-only volume, or having a locked file with the same name present in Mds.
Action: Bring up Mds in read/write mode, or remove the locked file.
Cause: Unexpected read error. Probably caused by disk unavailability.
Action: None. By default mdstar will try several times to read/write in the face of intermittent errors. Check possible physical problems and for interference from other disk intensive processes.
Cause: An expected resource was not set or was set incorrectly.
Action: Check to see that the resource is set properly, usually via the command line.
Cause: mdstar must either extract, create, or list archives.
Action: Specify an action via the command line.
Cause: mdstar has reached the end of the archive. Reading a multi-volume archive or creating an archive that is larger than a physical tape will cause mdstar to assume that the archive is spread across multiple tapes.
Action: Insert the next tape and hit return.
Cause: The specified disk is not part of any of the volumes currently mounted by the MDS server. A disk rebuild can only occur if the volumes on that disk are mounted.
Action: Verify that the disk name is correct. If it is, start up the MDS server with the associated volumes mounted.
Action: Specify only one of the options: -I, -R, -W.
Action: Specify the volume with only one of the options: -i, -r, -w.
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.
Cause: A database error occurred while accessing the persistent store.
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.
Cause: A memory malloc failed in the method implementation.
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.
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.
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.
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.
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.
Cause: The status of an order is invalid.
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.
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
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.
Cause: An internal error occured during tagging.
Cause: An internal error occured during tagging.
Cause: An internal error occured during tagging.
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.
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: 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.
