what if i...
backup the 2.2.0 MacOSX db.. and restore it onto the linux db..
theoretically, it ought to have
the same table structure and datacontent. then i just switch over the
codebase to 2.2.0 ?
-keith
Keith Ching wrote:
hmm.. i'm not sure what the difference is.. both databases contain
hmm.. i'm not sure what the difference is.. both databases contained
"exactly" the
same data. ie. a backup of the linux db was restored to the MacOSX db
before update.
and surprisingly the linux db was the one that failed. The databases
have BASE2 data only.
-keith
Jari Häkkinen wrote:
> I h
I have upgraded a couple of servers. All are running in OpenSuse 10.2.
In my case, I noticed that servers that contain BASE 1 migrated data
fails the upgrade whereas all servers with only "new" data was
successfully upgraded.
Jari
Keith Ching wrote:
> mirrored databases.. different OS and my
here is my BioMaterials discriminators
mysql> select distinct discriminator from BioMaterials;
+---+
| discriminator |
+---+
| 1 |
| 2 |
| 3 |
| 4 |
+---+
4 rows in set (0.00 sec)
-keith
mirrored databases.. different OS and mysql versions
successful update from 2.1.2 -> 2.2.0 using mysql 5.0.18-standard on MacOSX
[86%] --Updating schema version: 25 -> 27...
[87%] --Updating schema version: 27 -> 28...
[87%] --Updating schema version: 28 -> 29...
[90%] Database updated s
I have successfully upgraded from 2.1.2 to 2.2. This is of course not
exactly the same upgrade as Chris.
Jari
Nicklas Nordborg wrote:
> Chris Wiita wrote:
>> I attempted a update to Base2.2 from a 2.1.1 installation. Executing
>> updatedb.sh worked until the "Updating database" step:
>
> I
Chris Wiita wrote:
> I attempted a update to Base2.2 from a 2.1.1 installation. Executing
> updatedb.sh worked until the "Updating database" step:
I really don't know why this is happening. The error message says
something about "Discriminator: 0" but we never use a 0, only the values
1, 2, 3
I attempted a update to Base2.2 from a 2.1.1 installation. Executing
updatedb.sh worked until the "Updating database" step:
--
[75%] Updating database...
[87%] --Updating schema version: 28 -> 29...12:06:13,579 ERROR
Update:1150 - updateToSchemaVersion29: FAILED
net.sf.basedb.core.B
