[ http://issues.apache.org/jira/browse/DERBY-1786?page=all ]
Suresh Thalamati updated DERBY-1786:
------------------------------------
Component/s: Store
Fix Version/s: 10.2.1.0
10.3.0.0
committed to 10.2 as part of meg-merge done by Rick. on revision 446700.
> 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
> Components: Store
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Suresh Thalamati
> Assigned To: Suresh Thalamati
> Fix For: 10.2.1.0, 10.3.0.0
>
> 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
