db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1786) a crash during re-encryption of an existing database with lot of tables can make database unrecoverable on a next boot.
Date Thu, 31 Aug 2006 00:24:23 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1786?page=comments#action_12431756 ] 
            
Suresh Thalamati commented on DERBY-1786:
-----------------------------------------

Hi Rick, 

This is related to new feature (re-encryption(DERBY-1156)). not a regression.  User will hit
this issue only if  
user does  (re)encryption of an existing database and  if  there is a power outage in a small-window
of work. 
I will try to fix this for 10.2  , so that I can sleep in peace :-)


/suresh



> a crash during re-encryption of an existing  database with lot of tables can make database
unrecoverable on a  next boot.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1786
>                 URL: http://issues.apache.org/jira/browse/DERBY-1786
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.2.1.0, 10.3.0.0
>            Reporter: Suresh Thalamati
>         Assigned To: Suresh Thalamati
>         Attachments: stk.txt
>
>
> While running reencryt  crash/recovery functional test  with  1000 tables (>2000 containers)
, I hit a following boot failire. 
> ERROR XJ040: Failed to start database 'wombat_pwd_en', see the next exception fo
> r details.
> ERROR XSTB0: An exception was thrown during transaction abort.
> java.sql.SQLException: Failed to start database 'wombat_pwd_en', see the next ex
> ============= begin nested exception, level (1) ===========
> ERROR XSRS4: Error renaming file (during backup) from E:\suresht\adhoctests\reencryption\dbs\wombat_pwd_en\seg0\c340.dat
to E:\suresht\adhoctests\reencryption\dbs\wombat_pwd_en\seg0\n340.dat.
> ---
> After bit of  debugging ; my suspicion  is this problem is happening becuase of more
than one log file switch during re-encryption and current 
> re-encryption recovery code does not seem to handle it correctly. 
>   

-- 
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