Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <30232112.1158081803495.JavaMail.jira@brutus>
Date: Tue, 12 Sep 2006 10:23:23 -0700 (PDT)
From: "Suresh Thalamati (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@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.
In-Reply-To: <22761195.1156978523546.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1786?page=comments#action_12434220 ] 
            
Suresh Thalamati commented on DERBY-1786:
-----------------------------------------

Committed derby-1786.diff  to trunk;  revision 442647.

> 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: derby-1786.diff, 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