Re: SPARC to x64 Transition
This is confirmed working on a small test set with MySQL 4.1.22
transitioning from SPARC to X64. Thanks everyone!
-Aaron
Here's the test set we used:
CREATE TABLE `test_innodb` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`bigint` bigint(11) DEFAULT NULL,
`float` float DEFAULT NULL,
`double` double DEFAULT NULL,
`deci` decimal(6,2) DEFAULT NULL,
`var` varchar(255) DEFAULT NULL,
`datetime` datetime DEFAULT NULL,
`timestamp` timestamp NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP,
big_unsigned bigint unsigned,
float_unsigned float unsigned,
int_unsigned int unsigned,
PRIMARY KEY (`id`),
KEY `deci` (`deci`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=latin1;
insert into `test_innodb` values
('1' ,'9223372036854775807' ,'321.123' ,'123132321.213213' ,'12.20'
,'somehcar' ,'2009-02-10 10:44:10' ,'2009-02-17 10:46:05' ,(400 *
400) ,444.888 ,123456) ,
('2' ,'-9223372036854775807' ,'-67498.7' ,'-6.84616419684968e+17' ,'-0.84'
,'somevarchar' ,'2009-02-05 10:45:12' ,'2009-02-17 10:46:12' ,(500 *
300) ,444.888 ,123456) ,
('3' ,'0' ,'0.0' ,'0.0' ,'0.0' ,NULL ,'-00-00 00:00:00' ,'2009-02-17
10:46:12' ,(0) ,0.0 ,0);
On Mon, Feb 16, 2009 at 8:26 AM, Heikki Tuuri heikki.tu...@oracle.comwrote:
Aaron,
I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from
a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though
obviously one is x86 and the other is SPARC). Is it possible to simply
copy
the data files from one host to the other or is a full mysqldump/import
necessary to preserve data integrity?
If a file copy doesn't work, why specificially would it fail?
Thanks,
-Aaron
you can simply copy the files, whether InnoDB or MyISAM. As far as I know,
all modern processors use the same floating point format. And all integer
and other data structures are platform independent in MyISAM and InnoDB.
Best regards,
Heikki
Innobase/Oracle
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=aaronb...@gmail.com
Re: SPARC to x64 Transition
Aaron, I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though obviously one is x86 and the other is SPARC). Is it possible to simply copy the data files from one host to the other or is a full mysqldump/import necessary to preserve data integrity? If a file copy doesn't work, why specificially would it fail? Thanks, -Aaron you can simply copy the files, whether InnoDB or MyISAM. As far as I know, all modern processors use the same floating point format. And all integer and other data structures are platform independent in MyISAM and InnoDB. Best regards, Heikki Innobase/Oracle -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
SPARC to x64 Transition
All, I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though obviously one is x86 and the other is SPARC). Is it possible to simply copy the data files from one host to the other or is a full mysqldump/import necessary to preserve data integrity? If a file copy doesn't work, why specificially would it fail? Thanks, -Aaron
Re: SPARC to x64 Transition
On Feb 13, 2009, at 11:41 AM, Aaron Blew wrote: All, I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though obviously one is x86 and the other is SPARC). Is it possible to simply copy the data files from one host to the other or is a full mysqldump/ import necessary to preserve data integrity? I have done straight data directory copy from server to server before (granted they were both SPARC machines) and had no problem. Off-hand, I can't think of any reason why it wouldn't work between SPARC x86, both running the same Solaris version, especially if they're both running the same version of mySQL. I would suggest doing a test copy, if possible to see what happens. Kurt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: SPARC to x64 Transition
It actually depends on your table types. With MyISAM it is no problem, but with InnoDB you are looking at a dump-and-restore.. Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Fri, Feb 13, 2009 at 6:23 PM, Kurt Cypher kurt.cyp...@wright.edu wrote: On Feb 13, 2009, at 11:41 AM, Aaron Blew wrote: All, I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though obviously one is x86 and the other is SPARC). Is it possible to simply copy the data files from one host to the other or is a full mysqldump/import necessary to preserve data integrity? I have done straight data directory copy from server to server before (granted they were both SPARC machines) and had no problem. Off-hand, I can't think of any reason why it wouldn't work between SPARC x86, both running the same Solaris version, especially if they're both running the same version of mySQL. I would suggest doing a test copy, if possible to see what happens. Kurt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=li...@olindata.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: SPARC to x64 Transition
I'm not sure that is true. I haven't seen a case where the architecture matters. I think the floating-point format is the big issue; as far as I've seen, even InnoDB stores its data in an endian-neutral manner. I am not familiar enough with the SPARC architecture to know whether it uses IEEE standard floating-point format, but if it does, I think the files should copy fine. And that's assuming there are even any float columns -- maybe this is all textual or integer data. I would suggest to the original author to create a trivial example database with representative data types, then shut it down and copy it to the new architecture. Start mysqld on the copied files, and see what happens. That's likely to be better than any of us experts guessing about it. A 3.5TB copy is not a reasonable test; a 3.5TB dump and restore should be the absolute *last* resort. Baron On Fri, Feb 13, 2009 at 5:04 PM, Walter Heck li...@olindata.com wrote: It actually depends on your table types. With MyISAM it is no problem, but with InnoDB you are looking at a dump-and-restore.. Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Fri, Feb 13, 2009 at 6:23 PM, Kurt Cypher kurt.cyp...@wright.edu wrote: On Feb 13, 2009, at 11:41 AM, Aaron Blew wrote: All, I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though obviously one is x86 and the other is SPARC). Is it possible to simply copy the data files from one host to the other or is a full mysqldump/import necessary to preserve data integrity? I have done straight data directory copy from server to server before (granted they were both SPARC machines) and had no problem. Off-hand, I can't think of any reason why it wouldn't work between SPARC x86, both running the same Solaris version, especially if they're both running the same version of mySQL. I would suggest doing a test copy, if possible to see what happens. Kurt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=li...@olindata.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=ba...@xaprb.com -- Baron Schwartz, Director of Consulting, Percona Inc. Our Blog: http://www.mysqlperformanceblog.com/ Our Services: http://www.percona.com/services.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
