Difference: DpmSrmv2Support (2 vs. 3)

Revision 32007-03-09 - SophieLemaitre

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

DPM upgrade to >= 1.6.0

Line: 56 to 56
 ./dpm_support_srmv2.2 --db-vendor MySQL --db localhost --user dpm --pwd-file /tmp/pwd --dpns-db cns_db --dpm-db dpm_db --verbose
Added:
>
>

Troubleshooting

Existing indexes

Don't worry if you get the following "error" output, it is harmless. It will appear if the G_PFN_IDX and P_PFN_IDX indexes already exist. In this case, you can consider that the migration script has been successfully run.

failed to query and/or update the DPNS/DPM databases : DBD::mysql::db do failed: Duplicate key name 'G_PFN_IDX' at UpdateDpmDatabase.pm line 264.
Issuing rollback() for database handle being DESTROY'd without explicit disconnect().
Issuing rollback() for database handle being DESTROY'd without explicit disconnect().

Corrupted database

The following error Error on rename is due to a corrupted database.

failed: Error on rename of './dpm_db/#sql-4083_25' to './dpm_db/dpm_pool' (errno: 150) at UpdateDpmDatabase.pm line 118.
Issuing rollback() for database handle being DESTROY'd without explicit disconnect().
Issuing rollback() for database handle being DESTROY'd without explicit disconnect().

You should:

  • restore the database using the Mysql dump you created before running the script,
  • run the script again.
 

SRMv2.2 daemon

A new daemon - supporting SRMv2.2 - has to run.

 
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