Changes between Version 41 and Version 42 of ReleaseNotes/gLite-3.2

Timestamp:

Feb 15, 2011, 10:05:23 AM (13 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

ReleaseNotes/gLite-3.2

@@ -51 +51 @@
 gLite 3.2 update 21, delivered as part of version [milestone:gLite-3.2.0-4 3.2.0-4] of QWG templates, brings DPM and LFC 1.8 which are major DPM and LFC upgrades requiring a database schema change. The schema change is not deployed by QWG templates. '''The schema upgrade script must be run manually''' with the following commands:
 {{{
-# For LFC, the script is in /opt/lcg/share/DPM/cns-db-300-to-310
+# For LFC, the script is in /opt/lcg/share/LFC/cns-db-300-to-310
 cd /opt/lcg/share/DPM/cns-db-300-to-310
-# First check the current schema version
+# First check the current schema version (in case of failure, see comment below)
 ./cns_db_300_to_310 --db-vendor MySQL --user root --pwd-file /tmp/pwd --db-host localhost --db cns_db --show-version-only
 # If less than `3 1 0`, upgrade the schema
@@ -65 +65 @@
  * LFC : `DPM-name-server-mysql`
 
-
-''Note: the upgrade script is provided by the new DPM/LFC rpms. If you want to upgrade the database before updating DPM, you need to retrieve the script from the new version.''
-
-Also note that it may happen (both DPM and LFC) that the column names indicating the schema version may not match what is expected. In this case, running the script with `--show-version-only` results in a failure to query the version. To fix it, connect to the MySQL database and enter the following commands:
+Also note that it may happen (both for DPM and LFC) that the column names indicating the schema version may not match what is expected. In this case, running the script with `--show-version-only` results in a failure to query the version. To fix it, connect to the MySQL database and enter the following commands:
 {{{
 use cns_db;