db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1039) Database creation should fail if specified log device path already exists
Date Thu, 23 Feb 2006 07:49:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1039?page=all ]

Knut Anders Hatlen updated DERBY-1039:
--------------------------------------

    Attachment: logd.sql

Repro provided by Suresh Thalamati:

1) run logd.sql , then kill IJ
2) change the log swith interval to
   derby.storage.logSwitchInterval=3145727
3) run logd1.sql , then kill IJ
4) reconnect to wombat1 , it will fail with following error.
ij> connect 'wombat1';
ERROR XJ040: Failed to start database 'wombat1', see the next
exception for details.
ERROR XSDB4: Page Page(1,Container(0, 896)) is at version 2, the log
file contains change version 3, either there are log records of this
page missing, or this page did not get written out to disk properly.


> Database creation should fail if specified log device path already exists
> -------------------------------------------------------------------------
>
>          Key: DERBY-1039
>          URL: http://issues.apache.org/jira/browse/DERBY-1039
>      Project: Derby
>         Type: Improvement
>   Components: Newcomer, Store
>     Versions: 10.2.0.0, 10.1.2.1, 10.3.0.0
>     Reporter: Knut Anders Hatlen
>     Priority: Minor
>  Attachments: logd.sql
>
> If a database is created with logDevice pointing to a directory
> containing old log files, one might experience errors during recovery.
>   ERROR XSDB4: Page Page(0,Container(0, 768)) is at version 2,657, the
>   log file contains change version 2,715, either there are log records
>   of this page missing, or this page did not get written out to disk
>   properly.
> To avoid this problem, database creation should fail if logDevice is
> pointing to an existing directory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message