Hey guys, I've got a setup of 2 controllers and 4 backends. On each
of my backends which are all MySQL I have a test1 and test2 database.
When I setup my virtualdatabase files I have called them db1-test1 and
db1-test2 and db2-test1 and db2-test2 and so on, all the way up to
db4-test2. When I load the configuration files for test1 vdb everything
loads up ok, No Problems. I'm then able to load db1-test2 and db2-test2
by loading the test2 xml file, but after that I'm unable to load
db3-test2 and db4-test2 because it says I can not use the same backends
or they are not compatible. I have checked my xml files with a fine
tooth comb and each line has different backend names and backend locations.
db1-test1 points to jdbc:mysql://db1:3306/test1
db1-test2 points to jdbc:mysql://db1:3306/test2
db2-test1 points to jdbc:mysql://db2:3306/test1
db2-test2 points to jdbc:mysql://db2:3306/test2
db3-test1 points to jdbc:mysql://db3:3306/test1
db3-test2 points to jdbc:mysql://db3:3306/test2
db4-test1 points to jdbc:mysql://db4:3306/test1
db4-test2 points to jdbc:mysql://db4:3306/test2
If you need me to post the xml files I will do so, but I was hoping
someone might have a clue as to why when I load up the second set of
test2 database backends it complains about the backends. The error I see
in the console window is as follows...
Loading of virtual databases configuration file failed (because of The
virtual database test2 could not be added to the controller (because of
Error while joining group test2
(org.continuent.sequoia.common.exceptions.ControllerException: Virtual
database configuration is not compatible with other controller settings.))).
Thanks so much in advance,
--
Matthew West
Junior Linux Administrator
Disovery Mining, Inc.
Office: (415)561-6780 x146
Mobile: (415)710-6211
Fax: (415)561-6784
[EMAIL PROTECTED]
www.discoverymining.com
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
