Ah, yeah. Thanks Oliver. That does make sense. >From what I've read in the documentation, I'm assuming you're meaning to use the "init" option after you've started the controller, and are attempting to initialize the VDB through the console. IE: http://sequoia.continuent.org/doc/infocenter/topic/org.continuent.sequoia.doc/html/Load_the_virtual_database_configuration_files_to_the_controllers.html
However, I'm getting this error when I try to run the controller.sh script to just start up the controller. I'll play with it a bit and see if I can set it up so that the VDB isn't attempting to auto-load on the controller startup. Thanks for pointing me in the right direction! Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ BlueDragon Alliance Member [EMAIL PROTECTED] Olivier Fambon wrote: > Hi Jordan, > > Jordan Michaels [02/10/07 21:01]: > ... >> >> I currently only have 1 controller and 1 database backend online. With >> the recovery log being brand-spanking new, what could make the >> controller think that it wasn't the last man down? >> >> Any suggestions on where to go from here would be greatly appreciated. I >> generally just need to be pointed in the right direction. > > > For a "first time", you want to load your vdb with the "init" option, > precisely to inform the system that you are actually initializing it. > > You may wish to refer to the following jira entry: > > https://forge.continuent.org/jira/browse/SEQUOIA-947 > > According to what is said there, you should not have to resort to the > "init" flag if your recovery-log is _really_ new, i.e. no tables > created, at all. If you have to, there might be a bug... > > A+O. > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia > > _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
