Oracle Video Server Messages

Stream Service Messages

OVS-02001: cannot allocate circuit: mzcErr=num

Cause: Could not find a pump thread for an emulated set-top box

Action: Start up more vpump processes

OVS-02002: send failed

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

OVS-02005: marshalling error in str

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

OVS-02006: [num] call to str with a context that isn't bound to a downstream

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.

OVS-02050: connect service DSMPhys-spump query failed: error num

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

OVS-02051: error during circuit release: num - ignoring

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

OVS-02052: mzsisSetup: error adding stats component to mzsi instance

Cause: An error occurred enabling SNMP monitoring in the stream instance

Action: Examine the log for accompanying MediaNet errors

OVS-02053: stats server: memory error during marshaling

Cause: An error occurred returning SNMP information. Probably low memory.

Action: Make sure the stream instance isn't in a low memory state.

OVS-02054: stats server: error returning to call

Cause: An error occurred returning SNMP information.

Action: Make sure the SNMP agent is still active.

OVS-02055: client terminated abnormally, ctx: num, mnId: num. Marking for cleanup.

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.

OVS-02105: [num-str] file str given not indexed for sending

Cause: The stream service was asked to boot with an untagged boot file.

Action: All boot files must be tagged with mtuwrap.

OVS-02106: in str: str failed with error num

Cause: MediaNet reported a client error receiving a BLOB

Action: Examine logs for further MediaNet information

OVS-02107: [num-str] in mzsTransferBlob: mnBlobPrepare failed with error: num (server could not send a BLOB)

Cause: MediaNet reporter a server error sending a BLOB

Action: Examine logs for further MediaNet information

OVS-02108: [num-str] in str: index file not compatible with current code

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

OVS-02111: [num-str] file str is not a tag file; it cannot be prepared

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.

OVS-02152: in str: problem num occurred getting info for file str

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.

OVS-02153: [num-str] in str: BLOB failed with mzsErr num, mnErr num

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.

OVS-02154: [num-str] in str: bad position for partial blob send (str, closest tag str). Retransmitting entire blob.

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.

OVS-02155: [num-str] in str: BLOB retransmission starting at byte pos str

Cause: MediaNet asked us to partially retransmit a BLOB.

Action: This does not normally constitute an error.

OVS-02156: error creating RPC server

Cause: mzsi was unable to register itself with the process server.

Action: Examine logs for further MediaNet information.

OVS-02157: error registering server

Cause: mzsi was unable to register itself with the process server.

Action: Examine logs for further MediaNet information.

OVS-02158: error adding common mib to mzsi instance

Cause: mzsi was unable to add SNMP monitoring support for itself.

Action: Examine logs for information from the SNMP agent.

OVS-02159: cannot allocate all user contexts

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.

OVS-02162: [num-str] error starting wildcard search for mzsQuery

Cause: An mds error was encountered when trying to perform a wildcard query

Action: Examine logs for further mds information.

OVS-02163: output file error - continuing

Cause: A disk error was detecting during an mtuedit

Action: Examine logs for further mds information

OVS-02165: file creation error - exiting

Cause: A disk error occurred creating a file for mtuedit

Action: Examine logs for further mds information

OVS-02166: unknown video stream startCode! hex

Cause: An syntax error was found when parsing MPEG content.

Action: Verify that the content is uncorrupted and valid.

OVS-02167: PID num exp=num, got=num (curpkt hexhexhexhex at str, lastpkt hexhexhexhex at str)

Cause: A continuity error was found when parsing MPEG content.

Action: Verify that the content is uncorrupted and valid.

OVS-02168: str invalid video elementary stream: num; continuing

Cause: An syntax error was found when parsing MPEG content.

Action: Verify that the content is uncorrupted and valid.

OVS-02169: error pushing on queue

Cause: An internal error occurred during tagging.

Action: Report to Oracle.

OVS-02170: [str] file str is not compatible

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.

OVS-02171: [str] could not find a match when trying to prime cache

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.

OVS-02172: [str] member file #num has no PTS's

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.

OVS-02173: error writing mkctHdr to file

Cause: A disk error occurred when trying to write a tag file.

Action: Examine logs for further mds information.

OVS-02174: cannot read header

Cause: A disk read error occurred when trying to patch a tag file.

Action: Examine logs for further mds information.

OVS-02175: no such member:num

Cause: The -m flag to mtutagpatch indicated an invalid member number.

Action: mtutagprint the tag file, and reexecute with a valid member number.

OVS-02176: [str] the requested bitrate (num bps) is less than that of each of the members

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.

OVS-02177: [str] the requested format is incompatible with each of the members

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.

OVS-02178: [str] there is no member with a presentation rate of num

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.

OVS-02179: [str] tag #num in stream 'str' is corrupt; ignoring

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.

OVS-02180: [str] cannot have start time str after end time str when going forwards

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.

OVS-02181: [str] cannot have start time str before end time str when going backwards

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.

OVS-02200: [num-str] Play was requested at rate num for which there is no member

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.

OVS-02204: str context passed to str

Cause: The server received invalid context information.

Action: This indicates an internal error in some piece of software. Report to Oracle.

OVS-02211: [num-str] given an invalid timtype num at time: (str)

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.

OVS-02250: [num-str] BLOB was not indexed; exiting

Cause: An effort was made to download a blob without a tagfile.

Action: Tag the BLOB using mtuwrap and download using the tagfile.

OVS-02251: [num-str] BLOB file not compatible with current code

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.

OVS-02252: no destination passed to mzsBoot()

Cause: The stream service received a bad boot request.

Action: This indicates an error in the software

OVS-02253: [num-str] stream file str not found

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.

OVS-02254: [num-str] error num getting length of file 'str'

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.

OVS-02255: (client passed non-null terminated stream id to query)

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

OVS-02256: error creating file: str

Cause: An error occurred creating a parse output file.

Action: Examine logs for further mds information.

OVS-02258: Error tagging input, bad content discovered at file position str

Cause: The tagger is unable to tag the content provided

Action: use mtumpeg to determine more clearly what is wrong with the file

OVS-02259: Error, lost transport sync at file position str, received byte 0xhex

Cause: The tagger is unable to tag the content provided

Action: replace mpeg file, it is invalid

OVS-02300: [num-str] POD service refused prepare

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.

OVS-02600: [str] internal error. Call support

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02601: [num-str] out of memory error in str

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02602: call cannot be dispatched

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02603: asynch RPC call failed

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02604: [num-str] error in communication with pump

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02605: [num-str] failed to contact boot image server

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02606: [num-str] error retrieving boot image name from server

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02607: [num-str] Media Net Error in call to pump. MnCtx: num, error: num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02608: [num-str] Error telling pump to shutdown, tearing down context

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02650: internal error in mzsAllocCtx, #num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02651: client and server out of sync on wildcard contexts

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02652: internal error: mkcaOpen returned num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02653: illegal member file when getting BLOB info

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02654: [num-str] internal error in str: str failed with error: num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02655: [num-str] mzsSendBlobPiece: size str != size num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02656: [num-str] internal error in mzsBoot: newCtx given to existing ctx

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02657: illegal member index found during mzsBoot

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02658: [num-str] mkctc error when priming tag cache

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02659: illegal member found when preparing clip

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02660: [num-str] internal error: repos inserted num bytes (num max); continuing

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02661: current member file does not exist

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02662: trying to play with an unprimed cache

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02663: RPC loop abnormally terminated

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02664: mtcctx internal error with mzsiLocalData

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02665: error using mnrConvertId on id num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02666: [num-str] received a done command with an empty outstanding queue

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02667: cannot set up cleanup handler

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02668: error binding local context to client

Cause: The server has detected an error in its internal state.

Action: Call Oracle. ## mkc

OVS-02669: in str: str internal error num. Continuing

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02670: internal system stream state machine error num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02671: fatal error: cannot open str

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02672: fatal error: unsupported input format (num)

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02673: error opening file: str

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02674: sequence error

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02675: unknown system stream startcode hexchar

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02676: indexing terminated due to file error num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02677: error pushing on queue

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02679: internal transport stream state machine error num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02680: internal error: mkcReadTransHdr handed non header-data: synch=hex

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02681: internal error: stream had more than num pids. Exiting

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02682: str corrupted pes header check bits: num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02683: mkcReadVStreamByte: stResynch internal error num. Continuing

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02684: str MPEG2 video elementary stream state machine error num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02685: unsupported input file format: num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02686: fatal error signaled, exiting

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02687: editing is currently not supported for MPEG2 files. Exiting

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02688: memory allocate for stream context failed

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02689: [str] bad format type num given for repositioning

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02690: error allocating memory for tag context

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02691: error allocating memory for tag cache

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02692: str: cannot open tag file str

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02693: no memory to create new header

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02694: no memory to read in tag file header

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02695: header of input file is unreadable

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02696: error: tag file not current format

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02697: read error num detected (str:num)

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02698: mkcaCtx memory corrupted, reallocing and attempting to continue

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02699: [str] no member file for compression num, bitrate num, presentation rate num

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-02854: [num-str] trying to pause on a set top that cannot pause

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02855: [num-str] trying to scan on a set top that cannot scan

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02856: [num-str] trying to seek on a set top that cannot seek

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02857: [num-str] trying to frame advance on a set top that cannot frame advance

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02858: [num-str] trying to pause a stream that cannot be paused

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02859: [num-str] trying to scan forward in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02860: [num-str] trying to scan backwards in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02861: [num-str] trying to frame advance forwards in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02862: [num-str] trying to frame advance backwards in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02863: [num-str] trying to seek forwards in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02864: [num-str] trying to seek backwards in a stream that doesn't allow it

Cause: The client asked to perform a VCR operation that their box cannot support.

Action: This indicates an error in the client software.

OVS-02865: [num-str] could not locate downstream for set-top str

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.

OVS-02866: [num-str] could not initiate communications with downstream for set-top str

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.

OVS-02867: [num-str] bitrate num greater than maximum allowable bitrate of num

Cause: A client has expressed interest in playing streams faster than the server can currently support.

Action: This is unsupported. Do not do it.

OVS-02868: [num-str] cannot play without first preparing a stream

Cause: An mzsPlay call was made without a preceding mzsPrepare call.

Action: This indicates a problem with the client software.

OVS-02869: [num-str] error num telling the pump to pause

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.

OVS-02870: [num-str] error num telling the pump to unpause

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.

OVS-02871: [num-str] error num repositioning stream

Cause: This occurs if a client tries to position past either end of a stream.

Action: Confine requests to the size of the stream.

OVS-02872: [num-str] error num creating a pump insert command

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.

OVS-02873: [num-str] you may not reposition a non-indexed stream

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.

OVS-02874: [num-str] error num telling the pump to play

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.

OVS-02875: [num-str] invalid context passed to mzsFinish

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.

OVS-02876: invalid MediaNet address passed to boot

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.

OVS-02877: [num-str] mzsSend was passed a client who has no downstream

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.

OVS-02878: [num-str] boot file str does not reference a usable image for this set-top box

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.

OVS-02879: [str] tag cache error num while repositioning

Cause: An error occurred when trying to reposition in a stream.

Action: Examine the log for surrounding errors that give more details.

OVS-02880: [str] tag cache chose member file that has no tags. Cannot reposition.

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.

OVS-02881: [num-str] could not automatically play after a prepare request

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.

OVS-02882: [num-str] unsupported flags num given for transferring blob

Cause: Unsupported flags were passed for a BLOB transer.

Action: This indicates an error with the client software.

OVS-02884: [num-str] Error num while initializing rate control

Cause: An internal error occurred while preparing to play at a non-1x rate.

Action: Call Oracle.

OVS-02897: [num-str] Could not create play command @str, l=str, kp=num

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.

OVS-02900: [num] No blob number given with blob library str

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.

OVS-02901: [num] Invalid blob number num given with blob library str

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

OVS-02902: [num] Bad digit found in blob number 'str'

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.

OVS-03017: WARNING: num erroneous tags found, file is invalid

Cause: When verifying a tag file, a potentially corrupt tag was found.

Action: Retag the file. If the problem persists, call Oracle.

OVS-03040: Tag num invalid:

Cause: When verifying a tag file, a potentially corrupt tag was found.

Action: Retag the file. If the problem persists, call Oracle.

OVS-03100: aborting query: cannot find context list

Cause: The server has detected an error in its internal state.

Action: Call Oracle.

OVS-03101: aborting query: context list is internally inconsistent

Cause: The server has detected an error in its internal state.

Action: Call Oracle.