I've been doing some tests on backing up interbase databases and found a 
weird situation.  When I restore a database using -i (don't activate 
indexes), the database restores fine but I get a "blob not found" error when 
backing it up.  I confirmed this with both GBAK and IB Console, using a 
blank database.

7/14/2011 9:23:04 AM "C:\Program Files 
(x86)\borland\interbase\bin\gbak.exe" -v -z -user SYSDBA -password 
xxxxxxxx -nt "e:\databases\blankcbb.ib" 
"C:\Users\SG0892~2\AppData\Local\Temp\B05ED98E\blankcbb.gbk" -SE service_mgr
7/14/2011 9:23:05 AM gbak: gbak version WI-V10.0.2.474
7/14/2011 9:23:05 AM gbak:     Version(s) for database 
"e:\databases\blankcbb.ib"
7/14/2011 9:23:05 AM  InterBase/x86/Windows NT (access method), version 
"WI-V10.0.2.474"
7/14/2011 9:23:05 AM  on disk structure version 15.0
7/14/2011 9:23:05 AM gbak: readied database e:\databases\blankcbb.ib for 
backup
7/14/2011 9:23:05 AM gbak: creating file 
C:\Users\SG0892~2\AppData\Local\Temp\B05ED98E\blankcbb.gbk
7/14/2011 9:23:05 AM gbak: starting transaction
7/14/2011 9:23:05 AM gbak: database e:\databases\blankcbb.ib has a page size 
of 4096 bytes.
7/14/2011 9:23:05 AM gbak: writing users
7/14/2011 9:23:05 AM gbak: writing encryptions
7/14/2011 9:23:05 AM gbak: writing domains
....
7/14/2011 9:23:15 AM gbak:     writing index RDB$PRIMARY43
7/14/2011 9:23:15 AM gbak:     writing index RDB$FOREIGN44
7/14/2011 9:23:15 AM gbak:     writing index RDB$FOREIGN92
7/14/2011 9:23:15 AM gbak:     writing index REPORTHEADERFOOTER_GUID_IDX
7/14/2011 9:23:15 AM gbak:     writing data for table REPORTHEADERFOOTER
7/14/2011 9:23:15 AM gbak: ERROR: BLOB not found
7/14/2011 9:23:15 AM gbak: Exiting before completion due to errors

The table in question, REPORTHEADERFOOTER does contain valid blob data and 
the process works normally if I do the restore without the -i option.

If I try to query the blob fieds, IB Console crashes:

    select f_blobsize(reportheader), f_blobsize(reportfooter) from 
reportheaderfooter

So it appears that the BLOB fields are corrupt somehow, but only when I 
restore without activating indexes.

Any ideas?

Thanks,

Dan Palley

While I cannot explain what is happening, try doing this:

1. meta data only backup
2. Restore with -i
3. full backup

If the problem happens under this conditions, I think it will be not too 
hard to track down.

Dan Palley wrote:
> I've been doing some tests on backing up interbase databases and found a
> weird situation.  When I restore a database using -i (don't activate
> indexes), the database restores fine but I get a "blob not found" error when
> backing it up.  I confirmed this with both GBAK and IB Console, using a
> blank database.
>

Quinn, in that scenario, the database won't have any data, correct?  The 
blob error appears when i query a table that has blob data.

I tried the steps you indicated and it worked without error, but it really 
doesn't address the original problem of why using -I when restoring a 
populated database breaks the blob fields.

Should I open a support case?  It's fairly easy to duplicate with a database 
I can provide.

Dan

"quinn wildman"  wrote in message 
news:378154@forums.embarcadero.com...
> While I cannot explain what is happening, try doing this:
>
> 1. meta data only backup
> 2. Restore with -i
> 3. full backup
>
> If the problem happens under this conditions, I think it will be not too
> hard to track down.
>
> Dan Palley wrote:
>> I've been doing some tests on backing up interbase databases and found a
>> weird situation.  When I restore a database using -i (don't activate
>> indexes), the database restores fine but I get a "blob not found" error 
>> when
>> backing it up.  I confirmed this with both GBAK and IB Console, using a
>> blank database.
>>

Quinn, in that scenario, the database won't have any data, correct?  The 
blob error appears when i query a table that has blob data.

I tried the steps you indicated and it worked without error, but it really 
doesn't address the original problem of why using -I when restoring a 
populated database breaks the blob fields.

Should I open a support case?  It's fairly easy to duplicate with a database 
I can provide.

Dan

"quinn wildman"  wrote in message 
news:378154@forums.embarcadero.com...
> While I cannot explain what is happening, try doing this:
>
> 1. meta data only backup
> 2. Restore with -i
> 3. full backup
>
> If the problem happens under this conditions, I think it will be not too
> hard to track down.
>
> Dan Palley wrote:
>> I've been doing some tests on backing up interbase databases and found a
>> weird situation.  When I restore a database using -i (don't activate
>> indexes), the database restores fine but I get a "blob not found" error 
>> when
>> backing it up.  I confirmed this with both GBAK and IB Console, using a
>> blank database.
>>

Siriam, thanks for fixing.  Glad you were able to duplicate so easily.

Dan

 wrote in message 
news:378279@forums.embarcadero.com...
> Dan,
>
> Thank you for the clear report. We have reproduced the issue now with 
> employee.gdb, so we don't have a need for your database now.
>
> We will have this resolved in the next update to InterBase XE.
>
> Best wishes,
> Sriram
>
>> {quote:title=Dan Palley wrote:}{quote}
>> Quinn, in that scenario, the database won't have any data, correct?  The
>> blob error appears when i query a table that has blob data.
>>
>> I tried the steps you indicated and it worked without error, but it 
>> really
>> doesn't address the original problem of why using -I when restoring a
>> populated database breaks the blob fields.
>>
>> Should I open a support case?  It's fairly easy to duplicate with a 
>> database
>> I can provide.
>>
>> Dan
>>
>> "quinn wildman"  wrote in message
>> news:378154@forums.embarcadero.com...
>> > While I cannot explain what is happening, try doing this:
>> >
>> > 1. meta data only backup
>> > 2. Restore with -i
>> > 3. full backup
>> >
>> > If the problem happens under this conditions, I think it will be not 
>> > too
>> > hard to track down.
>> >
>> > Dan Palley wrote:
>> >> I've been doing some tests on backing up interbase databases and found 
>> >> a
>> >> weird situation.  When I restore a database using -i (don't activate
>> >> indexes), the database restores fine but I get a "blob not found" 
>> >> error
>> >> when
>> >> backing it up.  I confirmed this with both GBAK and IB Console, using 
>> >> a
>> >> blank database.
>> >>

Dan,

Thank you for the clear report. We have reproduced the issue now with employee.gdb, so we don't have a need for your database now.

We will have this resolved in the next update to InterBase XE.

Best wishes,
Sriram

> {quote:title=Dan Palley wrote:}{quote}
> Quinn, in that scenario, the database won't have any data, correct?  The 
> blob error appears when i query a table that has blob data.
> 
> I tried the steps you indicated and it worked without error, but it really 
> doesn't address the original problem of why using -I when restoring a 
> populated database breaks the blob fields.
> 
> Should I open a support case?  It's fairly easy to duplicate with a database 
> I can provide.
> 
> Dan
> 
> "quinn wildman"  wrote in message 
> news:378154@forums.embarcadero.com...
> > While I cannot explain what is happening, try doing this:
> >
> > 1. meta data only backup
> > 2. Restore with -i
> > 3. full backup
> >
> > If the problem happens under this conditions, I think it will be not too
> > hard to track down.
> >
> > Dan Palley wrote:
> >> I've been doing some tests on backing up interbase databases and found a
> >> weird situation.  When I restore a database using -i (don't activate
> >> indexes), the database restores fine but I get a "blob not found" error 
> >> when
> >> backing it up.  I confirmed this with both GBAK and IB Console, using a
> >> blank database.
> >>