Difference: DpmSrmv2Support (3 vs. 4)

Revision 42007-03-14 - SophieLemaitre

Line: 1 to 1
 
META TOPICPARENT name="DataManagementDocumentation"

DPM upgrade to >= 1.6.0

Line: 70 to 70
 Issuing rollback() for database handle being DESTROY'd without explicit disconnect().
Changed:
<
<

Corrupted database

>
>

Error on rename

 
Changed:
<
<
The following error Error on rename is due to a corrupted database.
>
>
We believe the following error Error on rename is due to a bug in Mysql.
 
failed: Error on rename of './dpm_db/#sql-4083_25' to './dpm_db/dpm_pool' (errno: 150) at UpdateDpmDatabase.pm line 118.
Line: 81 to 81
 

You should:

Changed:
<
<
  • restore the database using the Mysql dump you created before running the script,
  • run the script again.
>
>
  • drop the foreign key
  • run the script again
  • re-create the foreign key

mysql> use dpm_db;
mysql> alter table dpm_fs drop foreign key fk_fs;

$ ./dpm_support_srmv2.2 --db-vendor MySQL --db localhost --user dpm --pwd-file /tmp/pwd --dpns-db cns_db --dpm-db dpm_db --verbose 

mysql> alter table dpm_fs add CONSTRAINT fk_fs FOREIGN KEY (poolname) REFERENCES dpm_pool (poolname); 
 

SRMv2.2 daemon

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback