Board index » delphi » IB 7.5 - Safe to use??

IB 7.5 - Safe to use??


2005-03-29 08:47:00 PM
delphi41
I have read issues with IB 7.5 possibly causing database corruption (e.g.
messages on 2/14 and 2/16) and was wondering if there are other issues that
we should be concerned about before upgrading to 7.5?
I did post a restore problem that we had using both IB 7.1 AND 7.5 that no
one responded to. How do you report a problem to Borland's QC for
assistance?
Here is the restore problem....
We have a .gbk created on IB 7.1 that the database has the page buffers set
to 35,000.
If we attempt to restore on EITHER a 7.1 or 7.5 server (one is Win2000,
other is Win2003) the following error message is displayed at the point
where the index build begins:
Error 335544721
Unable to complete network request to host 127.0.0.1.
Error reading data from the connection.
An existing connection was forcibly closed by the remote host.
<end of message>
Server is a Windows 2003 Server (IB 7.5) server with 256 mb of memory. The Win2000
server (IB 7.1) is a dual processor server with 1 g of memory.
No other users connected to servers.
If you restore and deactivate indexes, the data is restored ok.
However, this requires a manual re-build of the indexes.
If we change the page buffers from 35,000 to 9,500 and re-run the backup to
create a new .gbk, the restore finishes with no errors.
Any ideas / suggestions?
Thanks,
Tom Greenway
 
 

Re:IB 7.5 - Safe to use??

Tom Greenway writes:
Quote
I have read issues with IB 7.5 possibly causing database corruption
(e.g. messages on 2/14 and 2/16) and was wondering if there are
other issues that we should be concerned about before upgrading to
7.5?
IT is running fine on the 300 user 89 gig database. No corruption issue
that I know of.
Quote
I did post a restore problem that we had using both IB 7.1 AND 7.5
that no one responded to. How do you report a problem to Borland's QC
for assistance?
go to qc.borland.com and go for it.
Quote

Here is the restore problem....

We have a .gbk created on IB 7.1 that the database has the page
buffers set to 35,000.

If we attempt to restore on EITHER a 7.1 or 7.5 server (one is
Win2000, other is Win2003) the following error message is displayed
at the point where the index build begins:

Error 335544721

Unable to complete network request to host 127.0.0.1.
Error reading data from the connection.
An existing connection was forcibly closed by the remote host.

<end of message>

Server is a Windows 2003 Server (IB 7.5) server with 256 mb of memory. The Win2000
server (IB 7.1) is a dual processor server with 1 g of memory.

No other users connected to servers.

If you restore and deactivate indexes, the data is restored ok.
However, this requires a manual re-build of the indexes.

If we change the page buffers from 35,000 to 9,500 and re-run the
backup to create a new .gbk, the restore finishes with no errors.

Use the
-BU(FFERS) override page buffers default
switch to set the buffers to 9500 when you restore and gfix -buffers to
set it back after
Of course I assumed you check to make sure you have lots of disk space
free on the disk where you temp files are put when doing the restore.
And you did look in the InterBase log file to see if InterBase left a
message before it went south.
You did check your database file for corruption?
hth
--
Rob Schieck
TeamB
 

Re:IB 7.5 - Safe to use??

Is the IB 7.1 / 7.5 restore with a .gbk that has page buffers greater than
9,500 (or so) a known problem? Is your suggestion (e.g. override page
buffers) a work around to the problem?
We currently create a "view" only database (using gbak) each night from a
backup of the production database each night. The procedure was working fine
until we increased the page buffers from 9,500 to 35,000.
I did not check the interbase log, but had checked the database for
corruption before backing up.
If there is no database corruption, what would cause one application's
database to restore with no problems (page buffers set to 35,000) and
another application's database to fail with an error?
The database that the restore worked has more tables, more total detail
records than the one that did fail.
<Robert Schieck (TeamB)>writes
Quote
Tom Greenway writes:

>I have read issues with IB 7.5 possibly causing database corruption
>(e.g. messages on 2/14 and 2/16) and was wondering if there are
>other issues that we should be concerned about before upgrading to
>7.5?

IT is running fine on the 300 user 89 gig database. No corruption issue
that I know of.

>I did post a restore problem that we had using both IB 7.1 AND 7.5
>that no one responded to. How do you report a problem to Borland's QC
>for assistance?

go to qc.borland.com and go for it.

>
>Here is the restore problem....
>
>We have a .gbk created on IB 7.1 that the database has the page
>buffers set to 35,000.
>
>If we attempt to restore on EITHER a 7.1 or 7.5 server (one is
>Win2000, other is Win2003) the following error message is displayed
>at the point where the index build begins:
>
>Error 335544721
>
>Unable to complete network request to host 127.0.0.1.
>Error reading data from the connection.
>An existing connection was forcibly closed by the remote host.
>
><end of message>
>
>Server is a Windows 2003 Server (IB 7.5) server with 256 mb of memory. The Win2000
>server (IB 7.1) is a dual processor server with 1 g of memory.
>
>No other users connected to servers.
>
>If you restore and deactivate indexes, the data is restored ok.
>However, this requires a manual re-build of the indexes.
>
>If we change the page buffers from 35,000 to 9,500 and re-run the
>backup to create a new .gbk, the restore finishes with no errors.
>

Use the

-BU(FFERS) override page buffers default

switch to set the buffers to 9500 when you restore and gfix -buffers to
set it back after

Of course I assumed you check to make sure you have lots of disk space
free on the disk where you temp files are put when doing the restore.

And you did look in the InterBase log file to see if InterBase left a
message before it went south.

You did check your database file for corruption?

hth


--
Rob Schieck
TeamB
 

Re:IB 7.5 - Safe to use??

Tom Greenway writes:
Quote
We currently create a "view" only database (using gbak) each night
from a backup of the production database each night. The procedure
was working fine until we increased the page buffers from 9,500 to
35,000.
I don't have a good answer for you on this one. I know of one currently
on 7.5 that is using 128,000 buffers and it restores just fine.
Please log it in Quality Central with the steps to reproduce it.
--
Rob Schieck
TeamB
 

Re:IB 7.5 - Safe to use??

3/31/2005
Using Gbak with the -Buffers setting allowed the restore to finish with no
errors. Following with the GFix to set the buffers back to 35,000 also
worked.
However....
This technique only works using the Gbak utility. We attempted to use the
IBX component in our Delphi program that we wrote to schedule backups and
restores, but changing the "buffers" still caused the restore to fail with
"connection lost to database" (same as IBConsole).
This still seems like some type of "bug" in Interbase....
<Robert Schieck (TeamB)>writes
Quote
Tom Greenway writes:

>I have read issues with IB 7.5 possibly causing database corruption
>(e.g. messages on 2/14 and 2/16) and was wondering if there are
>other issues that we should be concerned about before upgrading to
>7.5?

IT is running fine on the 300 user 89 gig database. No corruption issue
that I know of.

>I did post a restore problem that we had using both IB 7.1 AND 7.5
>that no one responded to. How do you report a problem to Borland's QC
>for assistance?

go to qc.borland.com and go for it.

>
>Here is the restore problem....
>
>We have a .gbk created on IB 7.1 that the database has the page
>buffers set to 35,000.
>
>If we attempt to restore on EITHER a 7.1 or 7.5 server (one is
>Win2000, other is Win2003) the following error message is displayed
>at the point where the index build begins:
>
>Error 335544721
>
>Unable to complete network request to host 127.0.0.1.
>Error reading data from the connection.
>An existing connection was forcibly closed by the remote host.
>
><end of message>
>
>Server is a Windows 2003 Server (IB 7.5) server with 256 mb of memory. The Win2000
>server (IB 7.1) is a dual processor server with 1 g of memory.
>
>No other users connected to servers.
>
>If you restore and deactivate indexes, the data is restored ok.
>However, this requires a manual re-build of the indexes.
>
>If we change the page buffers from 35,000 to 9,500 and re-run the
>backup to create a new .gbk, the restore finishes with no errors.
>

Use the

-BU(FFERS) override page buffers default

switch to set the buffers to 9500 when you restore and gfix -buffers to
set it back after

Of course I assumed you check to make sure you have lots of disk space
free on the disk where you temp files are put when doing the restore.

And you did look in the InterBase log file to see if InterBase left a
message before it went south.

You did check your database file for corruption?

hth


--
Rob Schieck
TeamB
 

Re:IB 7.5 - Safe to use??

Tom Greenway writes:
Quote
This still seems like some type of "bug" in Interbase....
Have you submitted this to the IB QA folks? You can ship the DB on a
DVD if it is too big for you to FTP. If you have a reproduceable test
case I am sure they'd love to see it.
-Craig
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
IB 6 versions prior to 6.0.1.6 are pre-release and may corrupt
your DBs! Open Edition users, get 6.0.1.6 from mers.com
 

Re:IB 7.5 - Safe to use??

Tom Greenway writes:
Quote
I have read issues with IB 7.5 possibly causing database corruption (e.g.
messages on 2/14 and 2/16) and was wondering if there are other issues that
we should be concerned about before upgrading to 7.5?
I have a database that consistently kills the server when I delete certain
records in it:
internal gds software consistency check (partner index description not found
(175), file: idx.c line: 1189)
The problem can't be reproduced with 7.1SP2.
I'm not sure if the problem also causes database corruption as the above was
enough to halt and abort our customers plans to upgrade to 7.5.
I have not reported the problem anywhere previously and probably won't have time
to do it until one of our customers pays me to do so. I am aware of the
consequences of that decision.
 

Re:IB 7.5 - Safe to use??

Have you tried reporting this to your local support office? Naturally,
you'll need a support contract to do so.
Anders Melander writes:
Quote
Tom Greenway writes:


>I have read issues with IB 7.5 possibly causing database corruption (e.g.
>messages on 2/14 and 2/16) and was wondering if there are other issues that
>we should be concerned about before upgrading to 7.5?


I have a database that consistently kills the server when I delete certain
records in it:

internal gds software consistency check (partner index description not found
(175), file: idx.c line: 1189)

The problem can't be reproduced with 7.1SP2.

I'm not sure if the problem also causes database corruption as the above was
enough to halt and abort our customers plans to upgrade to 7.5.
I have not reported the problem anywhere previously and probably won't have time
to do it until one of our customers pays me to do so. I am aware of the
consequences of that decision.

 

Re:IB 7.5 - Safe to use??

It is not safe. See message "Remote connect hang up" 11.03.2005.
 

Re:IB 7.5 - Safe to use??

"εΧΗΕΞΙ? writes:
Quote

It is not safe. See message "Remote connect hang up" 11.03.2005.
I've got an enterprise system running 24/7 on 7.5 without problems.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
A human being should be able to change a diaper, plan an invasion, butcher
a hog, conn a ship, design a building, write a sonnet, balance accounts, build
a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act
alone, solve equations, analyze a new problem, pitch manure, program a computer,
cook a tasty meal, fight efficiently, die gallantly. Specialization is for
insects. (RAH)
 

Re:IB 7.5 - Safe to use??

See my post 'Corruption again with IB7.5' on the 14/02
Regards
Brian
"Tom Greenway" <XXXX@XXXXX.COM>writes
Quote
I have read issues with IB 7.5 possibly causing database corruption (e.g.
messages on 2/14 and 2/16) and was wondering if there are other issues
that
we should be concerned about before upgrading to 7.5?

I did post a restore problem that we had using both IB 7.1 AND 7.5 that no
one responded to. How do you report a problem to Borland's QC for
assistance?

Here is the restore problem....

We have a .gbk created on IB 7.1 that the database has the page buffers
set
to 35,000.

If we attempt to restore on EITHER a 7.1 or 7.5 server (one is Win2000,
other is Win2003) the following error message is displayed at the point
where the index build begins:

Error 335544721

Unable to complete network request to host 127.0.0.1.
Error reading data from the connection.
An existing connection was forcibly closed by the remote host.

<end of message>

Server is a Windows 2003 Server (IB 7.5) server with 256 mb of memory. The Win2000
server (IB 7.1) is a dual processor server with 1 g of memory.

No other users connected to servers.

If you restore and deactivate indexes, the data is restored ok.
However, this requires a manual re-build of the indexes.

If we change the page buffers from 35,000 to 9,500 and re-run the backup
to
create a new .gbk, the restore finishes with no errors.

Any ideas / suggestions?

Thanks,
Tom Greenway



 

Re:IB 7.5 - Safe to use??

Quinn Wildman writes:
Quote
Have you tried reporting this to your local support office? Naturally,
you'll need a support contract to do so.
No, I haven't done anything.
I haven't got the time at the moment and since 7.5 has been put on hold because
of this problem (and the ones reported by others here) it doesn't have high
priority for us.
 

Re:IB 7.5 - Safe to use??

Hi all;
this is important topic, because subject is Data (customer data)
Quote
"IT is running fine on the 300 user 89 gig database. No corruption issue
that I know of." <Robert Schieck (TeamB)>
Quote
"I've got an enterprise system running 24/7 on 7.5 without problems."
<Jeff Overcash (TeamB)>
At this point:
I used IB in my old application Delphi4, BDE, IB5.x, TQuery, TUpdateSQL
with cached Updates
and my Database 350 MB approximate and don't crash in five years work
always, (I love;)
(note: Size is not very important because i very see corrupt DB with small
size).
and Important Coding technique:
I used below command in above application
StartTransaction, Commit Or Rollback
and Now:
Most users used new IBX command becasue easily :
CommitRetaining and Rollbackreatining: But not is good; My friend used this
command and 50MB-100MB Database sometimes corrupting...
What use or Coding technique :
I think now best component is ClientDataset, See : "ClientDataset
Articles" Bill Todd
because Used Commit and Rollback command with Provider Component;
and My Question to TeamB:
1- Which use in IB projects TClientDataset or TIBClientDataset
2- What do you think my this message!
thank you very much!
Sorry my poor English and language error