New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full shutdown causes database corruption if it happens when SuperServer is running a query modifying data [CORE1610] #2031
Comments
Modified by: Sergei Rubanik (sergeir)Attachment: CORE1610_create_db.sql [ 10670 ] |
Modified by: Sergei Rubanik (sergeir)Attachment: CORE1610_test_db.sql [ 10671 ] |
Modified by: Sergei Rubanik (sergeir)description: HOW TO REPRODUCE: 1. Edit database file name in both scripts (we use the same scripts as in CORE1299). 2. Create test database by create_db.sql. 3. Run test_db.sql and shut down the database while the script is running with gfix -shut full -force 0 Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:23:48 2007 -- Log End -- 4. If no errors happened on step 3, restart the database with gfix -online and repeat step 3. 5. Restart the database with gfix -online 6. Validate database with gfix -f -v It reports: ----------------- Start log on 22/11/2007 11:25:10 ------------------ ------------------ End log on 22/11/2007 11:25:10 ------------------- Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 -- Log End -- => HOW TO REPRODUCE: 1. Edit database file name in both scripts (we use the same scripts as in CORE1299). 2. Create test database by CORE1610_create_db.sql. 3. Run CORE1610_test_db.sql and shut down the database while the script is running with gfix -shut full -force 0 Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:23:48 2007 -- Log End -- 4. If no errors happened on step 3, restart the database with gfix -online and repeat step 3. 5. Restart the database with gfix -online 6. Validate database with gfix -f -v It reports: ----------------- Start log on 22/11/2007 11:25:10 ------------------ ------------------ End log on 22/11/2007 11:25:10 ------------------- Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 -- Log End -- |
Modified by: Sergei Rubanik (sergeir)description: HOW TO REPRODUCE: 1. Edit database file name in both scripts (we use the same scripts as in CORE1299). 2. Create test database by CORE1610_create_db.sql. 3. Run CORE1610_test_db.sql and shut down the database while the script is running with gfix -shut full -force 0 Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:23:48 2007 -- Log End -- 4. If no errors happened on step 3, restart the database with gfix -online and repeat step 3. 5. Restart the database with gfix -online 6. Validate database with gfix -f -v It reports: ----------------- Start log on 22/11/2007 11:25:10 ------------------ ------------------ End log on 22/11/2007 11:25:10 ------------------- Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 -- Log End -- => How to reproduce: 1. Edit database file name in both scripts (we use the same scripts as in CORE1299). 2. Create test database by CORE1610_create_db.sql. 3. Run CORE1610_test_db.sql and shut down the database while the script is running with gfix -shut full -force 0 Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:23:48 2007 -- Log End -- 4. If no errors happened on step 3, restart the database with gfix -online and repeat step 3. 5. Restart the database with gfix -online 6. Validate the database with gfix -f -v It reports: ----------------- Start log on 22/11/2007 11:25:10 ------------------ ------------------ End log on 22/11/2007 11:25:10 ------------------- Firebird.log contains: -- Log Start -- SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 SERGEI (Server) Thu Nov 22 11:25:10 2007 -- Log End -- |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: Sergei Rubanik (sergeir)environment: OS: Windows Server 2003 Standard Edition SP 2, Windows XP Professional SP2 => OS: Windows Server 2003 Standard Edition SP 2, Windows XP Professional SP2 summary: Full shutdown causes database corruption if happens when server is running a query modifying data => Full shutdown causes database corruption if it happens when SuperServer is running a query modifying data |
Commented by: maziar (maziar) I have same problem in fb 2.1 beta 2 it is MAJOR BUG |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 RC1 [ 10201 ] Fix Version: 2.0.4 [ 10211 ] |
Modified by: @pcisarWorkflow: jira [ 13492 ] => Firebird [ 14078 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Sergei Rubanik (sergeir)
Jira_subtask_outward CORE1615
Attachments:
CORE-1610_create_db.sql
CORE-1610_test_db.sql
Votes: 1
How to reproduce:
1. Edit database file name in both scripts (we use the same scripts as in CORE1299).
2. Create test database by CORE1610_create_db.sql.
3. Run CORE1610_test_db.sql and shut down the database while the script is running with
gfix -shut full -force 0
Firebird.log contains:
-- Log Start --
SERGEI (Server) Thu Nov 22 11:23:47 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
database C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC shutdown
internal gds software consistency check (error during savepoint backout (290), file: exe.cpp line: 3731)
SERGEI (Server) Thu Nov 22 11:23:48 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
database C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC shutdown
-- Log End --
4. If no errors happened on step 3, restart the database with
gfix -online
and repeat step 3.
5. Restart the database with
gfix -online
6. Validate the database with
gfix -f -v
It reports:
----------------- Start log on 22/11/2007 11:25:10 ------------------
Exception
Company name: BUG5.FDB
Exit Code = 0. Summary of validation errors
Number of index page errors : 8
Number of database page errors : 1
------------------ End log on 22/11/2007 11:25:10 -------------------
Firebird.log contains:
-- Log Start --
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt on page 198 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 1 is corrupt (missing entries) in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Index 2 is corrupt (missing entries) in table T1 (128)
SERGEI (Server) Thu Nov 22 11:25:10 2007
Database: C:\PROGRAM FILES\HERBST SOFTWARE\HERBST INSIGHT 2 SERVER\BUG5.FDB.ACC
Page 211 is an orphan
-- Log End --
Commits: df6706b d276641
The text was updated successfully, but these errors were encountered: