D'oh. Very simple problem: I didn't allocate a large enough disk to my
virtual machine. Here we go again...
Cheers
Ben
On 20/02/12 14:45, Sam Skipsey wrote:
> Hi Ben,
>
> So, no, there's been tracking of the schema version in all versions of
> DPM back to something like 1.5 (although the format of the table has
> changed).
>
> People have seen the problem with schema_version_dpm having the "wrong"
> column names, which is covered in the DPM Install page on the gridpp wiki.
>
> For ease of use, that advice is copied below:
>
>
> Schema Update
>
> This is performed automatically by YAIM or you can run the script that
> YAIM runs from /opt/glite/yaim/functions. It only adds tables so should
> be quick and harmless.
>
> Some people experienced a problem where the update said:
>
> INFO: Upgrading DPNS schema from 300 to 310
> DBD::mysql::db do failed: Unknown column'major' in'field
> list' at ./cns-db-300-to-310 line 19.
>
> The solution applied was to run the following SQL commands and then
> rerun the update
>
> ALTER TABLE schema_version CHANGE major_number major INTEGER(11);
> ALTER TABLE schema_version CHANGE minor_number minor INTEGER(11);
> ALTER TABLE schema_version CHANGE patch_number patch INTEGER(11);
>
> [edit
> <https://www.gridpp.ac.uk/w/index.php?title=DPM_Install&action=edit§ion=14>]
>
>
> Interestingly, though, this issue was with the dpns schema (which is
> called schema_version, not schema_version_dpm).
> You *should* have a schema_version_dpm, with probably version 3.0.0 if
> you're moving from 1.7.3 to 1.8.0+
>
> I hope this helps.
>
> Sam
>
>
> P.S.
> For reference, my schema_version_dpm in my DPM looks like:
>
> mysql> select * from schema_version_dpm;
> +-------+-------+-------+
> | major | minor | patch |
> +-------+-------+-------+
> | 3 | 2 | 0 |
> +-------+-------+-------+
> 1 row in set (0.00 sec)
>
> On 20 February 2012 14:06, Ben Waugh <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> Hi All,
>
> I have moved the database from my old (v1.7.3) DPM head node onto a
> newer server with DPM v1.8.2. YAIM is not able to update the schema
> because there is no table "schema_version_dpm" in the database "dpm_db".
>
> Is this because this information was only added in later DPM
> versions? Do I have to run some other script before running YAIM, or
> can I just create and populate "schema_version_dpm" by hand?
>
> Thanks,
> Ben
>
> --
> Dr Ben Waugh Tel. +44 (0)20 7679
> 7223 <tel:%2B44%20%280%2920%207679%207223>
> Dept of Physics and Astronomy Internal: 37223
> University College London
> London WC1E 6BT
>
>
--
Dr Ben Waugh Tel. +44 (0)20 7679 7223
Dept of Physics and Astronomy Internal: 37223
University College London
London WC1E 6BT
|