[Primex_software] transferred database from clondb1 to primexdb

[Mark M. Ito]

  Folks,

I had to redo this transfer. Some table attributes did not make the 
transfer when using the "compatible" switch.

This time the switch was not used to make the dumps from clondb1. Rather 
a script was used to strip out incompatible keywords in the dump. Find a 
copy of the script attached.

The new versions of the dumps are in 
/mss/home/marki/primex/primex_db_xfer_3. The backups of the original 
state on primexdb are the same files as those stored in primex_db_xfer_2.

   -- Mark

On 10/14/2010 11:30 AM, Mark M. Ito wrote:
>  Folks,
>
> On 10/13/2010 05:25 PM, Mark M. Ito wrote:
>> I did a mass transfer of several of our database tables from the online
>> server, clondb1, to the offline server, primexdb. If any of you notice
>> problems. Please let me know: 504-0664.
>
> Some details on yesterday's database transfer.
>
> 6 databases were transferred from clondb1 to primexdb:
>
> 1. primex
> 2. primex_calib
> 3. primex_calib_user
> 4. primex_cluster
> 5. primex_connections
> 6. primex_online
>
> The dump from clondb1 was done logged onto clon00 (not necessary, but 
> sufficient). A compatibility option was necessary to create a dump 
> acceptable to mysql 4.0.13, the version being run on primexdb.
>
>   mysqldump --compatible=mysql40 -hclondb1 -uprimex_user 
> <database-name> > <mysql-dump-file>
>
> The dump files were called clondb1_<database-name>_2010-10-13.sql
>
> These dumps were loaded these onto primexdb while logged into primexdb:
>
>   mysql -hlocalhost -udbmanager -p<password> <databasename> < 
> <mysql-dump-file>
>
> In these loads, the old version pre-existing on primexdb was dropped 
> as first step in dump file.
>
> All operations on primexdb were done with /usr/local/mysql/bin first 
> in the PATH. This guaranteed compatibility with the version of mysql 
> being run by the mysql server.
>
> __Backups__
>
> Backups of primexdb were done both before and after loading the 
> databases from clondb1. The sizes of the resulting dumps are 
> approximately the same for each database.
>
> The backups created before the load were called 
> primexdb_<database_name>_2010-10-13.sql . Those created after the load 
> were called loaded_<database_name>_2010-10-13.sql .
>
> __Storage of dump files__
>
> All of the above mentioned dump files are in the tape library in the 
> directory /mss/home/marki/primex/primex_db_xfer_2 . (There is also a 
> primex_db_xfer directory; those files have compatibility problems).
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: restore.sh
Type: application/x-shellscript
Size: 253 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/primex_software/attachments/20101018/3df6c3cd/attachment.bin