Subject | Re: [firebird-support] BLOB not found |
---|---|
Author | Helen Borrie |
Post date | 2004-02-18T01:03:25Z |
At 09:19 PM 17/02/2004 -0300, you wrote:
interface. This means you are using the API (not embedded SQL) so I
recommend that you rebuild that table (using a gbak copy of the database)
and omit the SEGMENT SIZE parameter. I don't *know* that specifying a
segment size would cause a problem...but my understanding is that the API
does its own thing with blob segments and the error you reported involved
segment lengths, as I recall. Maybe your driver is doing something
unpredictable on the basis of your having defined a segment size explicitly.
Another thing I do know about WRT blobs is that their database page-links
can get broken if you work on file-copy copies of your database. The
problems can show up long after you actually make the copy, if the blobs
are not accessed for some time.
Large blobs are also prone to errors during operations if you are using a
system with faulty RAM or a bad network connection.
Also, if you're not using the Firebird JDBC driver, then you should.
It would make sense for you to post your problem in the Firebird-Java forum
if you find it persists.
Helen
>Helen,You mention in another message that you are using Java as your
>
>The problem does not occurs on the Linux with Firebird 1.0.3.
>
>The exact DDL is:
>
>CREATE TABLE BSMST (
> MFN INTEGER NOT NULL,
> TAG INTEGER NOT NULL,
> OCC INTEGER NOT NULL,
> SUB CHAR(1) NOT NULL,
> VAL BLOB SUB_TYPE 1 SEGMENT SIZE 128 NOT NULL);
interface. This means you are using the API (not embedded SQL) so I
recommend that you rebuild that table (using a gbak copy of the database)
and omit the SEGMENT SIZE parameter. I don't *know* that specifying a
segment size would cause a problem...but my understanding is that the API
does its own thing with blob segments and the error you reported involved
segment lengths, as I recall. Maybe your driver is doing something
unpredictable on the basis of your having defined a segment size explicitly.
Another thing I do know about WRT blobs is that their database page-links
can get broken if you work on file-copy copies of your database. The
problems can show up long after you actually make the copy, if the blobs
are not accessed for some time.
Large blobs are also prone to errors during operations if you are using a
system with faulty RAM or a bad network connection.
Also, if you're not using the Firebird JDBC driver, then you should.
It would make sense for you to post your problem in the Firebird-Java forum
if you find it persists.
Helen