Re: [opennms-install] Install error with databasechangelock - duplicate CREATE

[<in...@te...>]

Hi,

I'm using a new database created for the new version(on the same server, but a different database and different user), not the one I used for 1.6.  During the install of 1.8.1, it creates the databasechangeloglock table, but then tries to create it again (since the hasChangeLogLockTable variable is false).  

I originally was using the current version, but when I hit this error attempted to go back a few versions to see if an older/more stable version might help.  But, still getting this error.  

Please help - thanks!  I don't know how to get around this error without changing Liquibase code - but also don't understand yet why everyone else has not encountered it??  

Sasha


Benjamin Reed <ra...@op...> wrote :

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 1/28/11 11:50 AM, in...@te... wrote:
> > Looking through the Liquibase code, it looks like this would happen
> every time, since aquireLock() calls checkDatabaseChangeLockLockTable(),
> which will create the table if the hasChangeLogLockTable() returns
> false, but then aquireLock() subsequently calls
> setCanCacheLiquibaseTableInfo(), which always sets the
> hasChangeLogLockTable variable to "false".
> >
> > But then why haven't other people had the same problem installing?????
> 
> So to back up, you already have a "databasechangelog" table, but
> you're upgrading from a 1.6 schema?  Where did your databasechangelog
> table come from?  Does it work if you revert to your 1.6 backup,
> double-check you don't have a databasechangelog table, and try again?
> 
> Also, why 1.8.1?  We've done a heck of a lot of bugfixes since then...
> 
> - -- 
> Benjamin Reed
> The OpenNMS Group
> http://www.opennms.org/
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iD8DBQFNQxE0Uu+jZtP2Zf4RAuiQAJ9rGTXTm1XAjiM0XPVwKP/SpNcIDgCfY+h7
> rPs6d2czkCfiDcoTZjZ3yFI=
> =gxpZ
> -----END PGP SIGNATURE-----

___________________________________
Sent using PCI Broadband webmail