VMware

This Question is Answered

1 "helpful" answer available (6 pts)
7 Replies Last post: Oct 25, 2009 5:53 PM by Mllii  

Error During upgrade posted: Sep 21, 2009 5:27 PM

Click to view Mllii's profile Novice 22 posts since
May 31, 2007
I am getting this error when i get to the Database upgrade for LCm

Error Database error Mismatch database version (found version '1.40', was expecting version '1.41')
Any ideas on this?

2009-09-22_102116.jpg

Attachments:

Re: Error During upgrade

1. Sep 29, 2009 4:32 AM in response to: Mllii
Click to view Todor Todorov's profile Enthusiast 35 posts since
Nov 19, 2007
Hi Mllii,

Are you trying to reuse an old database with LCM 1.0.2? If yes, from which LCM version is the database?
If you're trying to migrate an LCM 1.0.1 configuration to LCM 1.0.1 then you should point to a new database and use the migration tool to migrate data.
If you're trying to migrate from an earlier LCM 1.0.2 version (like early access build or beta) then this is not a supported upgrade path.

Regards,
Todor

Re: Error During upgrade

3. Oct 7, 2009 2:00 PM in response to: Mllii
Click to view [Douglas]'s profile Novice 7 posts since
Aug 20, 2008
Just click on the UPDATE link in the upper part of the screen ("Install. Database update required. UPDATE")

And LCM should quickly update your DB structure, aligning it to 1.41 schema.


(I hope that you're not already getting that error after clicking on that link :))

Re: Error During upgrade

5. Oct 7, 2009 10:15 PM in response to: Mllii
Click to view Todor Todorov's profile Enthusiast 35 posts since
Nov 19, 2007
Hi,

As I wrote in my previous comment, this is a not supported use case.
In order to upgrade 1.0.1 to 1.0.2 you need to specify a blank database and use the migration tool to export data from 1.0.1 and import it in 1.0.2.
You can take a look at LCM Administration guide for details on how to do it.

Regards,
Todor

Re: Error During upgrade

6. Oct 8, 2009 12:58 AM in response to: Todor Todorov
Click to view VirtualDouglas's profile Novice 5 posts since
Jan 16, 2008

Yes, as I did last time I updated: trying to update from a pervious version of DB (without recreating it from scratch) causes several inconsistencies and LCM instability...

Re-creating the DB from scratch is the best solution (with a possible import of previously imported data, if you made an export/backup).

Remember also to apply the lastest 1.0.2.1 patch released by VMWare a week ago... (it fixes some further little bugs).

Bye!


VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities