Adding a VDB to a controller with the 'force' flag set will result in a 'Unique
Constraint Violation' SQLException if VDB is already the 'last man down'.
---------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEQUOIA-1008
URL: https://forge.continuent.org/jira/browse/SEQUOIA-1008
Project: Sequoia
Type: Bug
Components: Recovery Log
Versions: Sequoia 2.10.9
Environment: Distributed DB
Derby backends
HSQLDB Recovery Log
JAVA 1.5.0_13)
Solaris 10 SPARC
Reporter: Nick Smith
We sometimes add VDB to a controller with the 'force' intialization flag even
if the VDB might be the 'last man down'.
If the VDB was the 'last man down' the we get a 'Unique Constraint Violation'
Exception because the
org.continuent.sequoia.controller.xml.DatabaseParser class ALWAYS inserts the
'last-man-down' checkpoint if
the 'force' flag was used but the VDB could possibly have a 'last-man-down'
checkpoint.
Solution is to always clear the 'last-man-down' checkpoint when add the virtual
database with the 'force'
flag set.
Thanks In Advance,
Nick
The patch that I have been using :
*** DatabasesParser.java Mon Oct 22 15:24:30 2007
--- DatabasesParser.java.orig Mon Oct 22 15:24:59 2007
***************
*** 696,702 ****
}
if (forceload)
{
- recoveryLog.clearLastManDown();
recoveryLog.setLastManDown();
}
if (currentVirtualDatabase instanceof DistributedVirtualDatabase)
--- 696,701 ----
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
