Error -602 returned during optical retrieval (long message)
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BF668E.B90E055A
Content-Type: text/plain;
charset="iso-8859-1"
Hi!
We have Informix Dynamic Server Version 7.31.UC3 running on Solaris
2.6 with the latest patch cluster from Sun. We have four Cygnet jukeboxes
with WORM platters. We are also running latest version of Plexus' OSM. We
have written a ESQL/C application that retrieves TIFF images stored both on
optical and magnetic and then prints these retrieved images to local and
remote printers using Vividata's PostShop (version 4.5). The application has
the exp_chk demonstration ESQL/C code folded into it.
Most of the time things work just fine but we are encountering error
-602 (Cannot open BLOB) approximately every 5000 images. Unfortunately I
have not been able to successfully trap this error. I have attempted closing
and freeing the cursor after trapping this error and the result is still the
same. For some reason after encountering this error, later BLOB retrievals
to the file system do not function normally. The permissions on the files
are inconstantly wrong or the images are not retrieved leaving empty files.
However if the application is shutdown and the requests for bad blobs are
removed, the retrievals for the other records work fine.
We have attempted other methods to reach these bad blobs. We have a
client application written in VB6 which also encounters these errors but
that application is able to successfully trap these errors. There is also a
rather long delay before the error message is returned under any scenario.
Normal functioning for the jukeboxes allows for up to fifteen seconds for
the retrieval from an optical platter however when this error is encountered
it takes anywhere from three to five minutes to appear. For giggles we also
attempted retrieval from dbaccess and experienced the same delays and
errors.
I have attempted to gain more information as to the meaning of the
optical subsystem errors but I have met with limited success. If anyone can
enlighten me as to what manual I am supposed to looking at I would greatly
appreciate it.
There are two issues that we are currently working on. First we are
looking to find a way to successfully trap this error. Second we are looking
for a method to recover these bad blobs if possible. Does anyone have any
suggestions? Thank you in advance. From past experience I have always
appreciated the prompt and useful responses that I have received from this
list. I have attached the relevant errors below:
The application returns these errors:
********Error encountered in fetch pages_cursor********
----------------------------------------------------------
SQLSTATE: IX000
SQLCODE: -602
EXCEPTIONS: Number=2 More? N
- - - - - - - - - - - - - - - - - - - -
EXCEPTION 1: SQLSTATE=IX000
MESSAGE TEXT: Cannot open blob.
CLASS ORIGIN: IX
SUBCLASS ORIGIN: IX000
- - - - - - - - - - - - - - - - - - - -
EXCEPTION 2: SQLSTATE=IX000
MESSAGE TEXT: Error 7121 from the optical subsystem.
Consult your appropriate subsystem manual.
CLASS ORIGIN: IX
SUBCLASS ORIGIN: IX000
------------------------------------
The above message will also sometimes produce under EXCEPTION 2: "Error 7120
from the optical subsystem. Consult the appropriate subsystem manual."
Unfortunately this is actually several occurrences of this error but I am
hoping it provides a more complete picture. Plexus' OSM returns the
following errors:
09:29:51 drive DR6: Process 17869 timedout waiting for buffer 1
09:29:51 drive DR6: readOD: timeout on buf 1
09:34:51 drive DR6: Process 17869 timedout waiting for
buffer 0
09:34:51 drive DR6: readOD: timeout on buf 0
09:41:51 drive DR6: Process 17869 timedout waiting for
buffer 0
09:41:51 drive DR6: readOD: timeout on buf 0
09:46:51 drive DR6: Process 17869 timedout waiting for
buffer 0
09:46:51 drive DR6: readOD: timeout on buf 0
09:47:17 drive DR6: DIO terminating
09:55:51 drive DR5: Process 17864 timedout waiting for
buffer 0
09:55:51 drive DR5: readOD: timeout on buf 0
10:00:51 drive DR5: Process 17864 timedout waiting for
buffer 0
10:00:51 drive DR5: readOD: timeout on buf 0
10:18:51 drive DR5: Process 17864 timedout waiting for
buffer 0
10:18:51 drive DR5: readOD: timeout on buf 0
10:24:51 drive DR5: Process 17864 timedout waiting for
buffer 1
10:24:51 drive DR5: readOD: timeout on buf 1
10:29:51 drive DR5: Process 17864 timedout waiting for
buffer 1
10:29:51 drive DR5: readOD: timeout on buf 1
10:34:51 drive DR5: Process 17864 timedout waiting for
buffer 0
10:34:51 drive DR5: readOD: timeout on buf 0
10:41:51 drive DR5: Process 17864 timedout waiting for
buffer 0
10:41:51 drive DR5: readOD: timeout on buf 0
10:47:51 drive DR5: Process 17864 timedout waiting for
buffer 0
10:47:51 drive DR5: readOD: timeout on buf 0
That's all folks.
Thom
------_=_NextPart_001_01BF668E.B90E055A
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Error -602 returned during optical retrieval (long =
message)</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Hi!</FONT>
<BR> <FONT SIZE=3D2>We have =
Informix Dynamic Server Version 7.31.UC3 running on Solaris 2.6 with =
the latest patch cluster from Sun. We have four Cygnet jukeboxes with =
WORM platters. We are also running latest version of Plexus' OSM. We =
have written a ESQL/C application that retrieves TIFF images stored =
both on optical and magnetic and then prints these retrieved images to =
local and remote printers using Vividata's PostShop (version 4.5). The =
application has the exp_chk demonstration ESQL/C code folded into =
it.</FONT></P>
<P> <FONT SIZE=3D2>Most of =
the time things work just fine but we are encountering error -602 =
(Cannot open BLOB) approximately every 5000 images. Unfortunately I =
have not been able to successfully trap this error. I have attempted =
closing and freeing the cursor after trapping this error and the result =
is still the same. For some reason after encountering this error, later =
BLOB retrievals to the file system do not function normally. The =
permissions on the files are inconstantly wrong or the images are not =
retrieved leaving empty files. However if the application is shutdown =
and the requests for bad blobs are removed, the retrievals for the =
other records work fine.</FONT></P>
<P> <FONT SIZE=3D2>We have =
attempted other methods to reach these bad blobs. We have a client =
application written in VB6 which also encounters these errors but that =
application is able to successfully trap these errors. There is