Watch, Follow, &
Connect with Us
Public Report
Report From: InterBase/Examples    [ Add a report in this area ]  
Report #:  6700   Status: Withdrawn
Corrupt db
Project:  InterBase Build #:  7.1
Version:    7.1 Submitted By:   Sergey Odinzov
Report Type:  Crash / Data loss / Total failure Date Reported:  12/24/2003 4:28:32 AM
Severity:    Critical / Show Stopper Last Updated: 1/3/2004 12:00:33 PM
Platform:    Windows 95/98/NT 4.0 on Intel Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
A bit later works the base falls. In it(her) are spoilt primary key. ???? the tests successfully pass on versions 7.0 and 6.0. We would like to proceed(pass) with 7.0 on 7.1, but it is impossible, as a database simply falls.

I have seen that you plan to let out InterBase 7.1 Service Pack 2.
Whether it is possible it(him) to receive for testing.
We and our clients would like to buy IB 7.1 (or to proceed(pass) to him(it)),
but those mistakes which there exist do not allow to make it.
We hope, that after updating Service Pack 2 these mistakes will disappear.


Database: E:\FME_CONS.GDB
Index 1 is corrupt on page 153 in table RDB$RELATION_FIELDS (5)

Russian
????? ????????? ????? ?????? ?????? ????. ? ??? ???????? primary key. ???? ????? ??????? ???????? ?? ??????? 7.0 ? 6.0. ?? ?????? ?? ??????? ? 7.0 ?? 7.1, ?? ??? ??????????, ??? ??? ?????? ?????? ???? ??????.
? ?????? ??? ?? ?????????? ????????? InterBase 7.1 Service Pack 2.
????? ?? ??? ???????? ??? ????????????. ??? ? ????? ???????? ???????? ?????? IB 7.1 (??? ??????? ?? ????),
?? ?? ?????? ??????? ??? ?????????? ?? ????????? ??????? ?????.
?? ????????, ??? ????? ?????????? Service Pack 2 ??? ?????? ????????.
Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments

None

Server Response from: ETNACODE01