Re: question about restoring...
From the OP: I have a copy of the INNODB files for these two tables - is there a way to extract the table contents from these files short of a full import? I have to agree, that's quite ambiguous. Andy, is it a copy of the innoDB datafiles, or a database dump that you have ? In the latter case, it's reasonably simple to extract what you need; in the former case you're gonna have to try attaching them to a new instance - good luck with that. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: Oracle imports into MySQL
My quick suggestion for such a process would be to use SQL*NET formatting commands to create a well-formed CSV file, which you then import into MySQL using LOAD DATA INFILE. I'm not aware of any Oracle-specific import tools in MySQL. If anything, after the merger I would rather expect something that goes the other way round :-) On Thu, Nov 11, 2010 at 7:46 AM, Machiel Richards machi...@rdc.co.zawrote: Good day all I am hoping that someone has got some more answers for me on the topic as most of the websites which have not been very useful. All websites I have found thus far reffers to software that either needs to be bought or otherwise need to be run manually. One of our clients are currently running MySQL for their web based systems, however all other systems are running oracle. There is a current data load process from oracle that generates a dump file of specific data, goes through a convertion process, gets imported into a mysql runnign on VM to test import, then gets pushed to MySQL production. This process was put in place quite some time ago by developers. At some stage I read something about this process not being required from MySQL 5 onwards and data imports from oracle is less troublesome. The import process needs to run every 30 minutes and the current process is too troublesome. We are busy plannign a hardware migration for the systems and are also looking at improving these processes. Does anybody have experience with this to perhaps provide me with some info on how we can improve this import process? Any assistance will be appreciated. Regards Machiel -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: question about restoring...
If you just need specific records, you can use -w option of mysql to extract only the specifc records. Then you can run the dump file into another db. regards anandkl On Fri, Nov 12, 2010 at 2:35 PM, Johan De Meersman vegiv...@tuxera.bewrote: From the OP: I have a copy of the INNODB files for these two tables - is there a way to extract the table contents from these files short of a full import? I have to agree, that's quite ambiguous. Andy, is it a copy of the innoDB datafiles, or a database dump that you have ? In the latter case, it's reasonably simple to extract what you need; in the former case you're gonna have to try attaching them to a new instance - good luck with that. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: question about restoring...
Thanks, guys. I have copies of the innodb files. The boss went whole hog on using zfs for everything, so backups of files are readily available. Looks like I'll be having the db reconstituted... thanks again On 11/12/10 1:05 AM, Johan De Meersman wrote: From the OP: I have a copy of the INNODB files for these two tables - is there a way to extract the table contents from these files short of a full import? I have to agree, that's quite ambiguous. Andy, is it a copy of the innoDB datafiles, or a database dump that you have ? In the latter case, it's reasonably simple to extract what you need; in the former case you're gonna have to try attaching them to a new instance - good luck with that. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- Andy Wallace iHOUSEweb, Inc. awall...@ihouseweb.com (866) 645-7700 ext 219 -- There are two ways to build software: Make it so simple that there are obviously no bugs, or make it so complex that there are no obvious bugs. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
FW: [USN-1017-1] MySQL vulnerabilities
How come these kinds of notices are not sent to the mysql list? I realize this particular one is from Ubuntu, but the vulnerability is not ubuntu specific, it's mysql. Why aren't the mysql, er um, Oracle people more pro-active about letting us know these things? -Original Message- From: ubuntu-security-announce-boun...@lists.ubuntu.com [mailto:ubuntu-security-announce-boun...@lists.ubuntu.com] On Behalf Of Marc Deslauriers Sent: Thursday, November 11, 2010 7:49 AM To: ubuntu-security-annou...@lists.ubuntu.com Cc: full-disclos...@lists.grok.org.uk; bugt...@securityfocus.com Subject: [USN-1017-1] MySQL vulnerabilities === Ubuntu Security Notice USN-1017-1 November 11, 2010 mysql-5.1, mysql-dfsg-5.0, mysql-dfsg-5.1 vulnerabilities CVE-2010-2008, CVE-2010-3677, CVE-2010-3678, CVE-2010-3679, CVE-2010-3680, CVE-2010-3681, CVE-2010-3682, CVE-2010-3683, CVE-2010-3833, CVE-2010-3834, CVE-2010-3835, CVE-2010-3836, CVE-2010-3837, CVE-2010-3838, CVE-2010-3839, CVE-2010-3840 === A security issue affects the following Ubuntu releases: Ubuntu 6.06 LTS Ubuntu 8.04 LTS Ubuntu 9.10 Ubuntu 10.04 LTS Ubuntu 10.10 This advisory also applies to the corresponding versions of Kubuntu, Edubuntu, and Xubuntu. The problem can be corrected by upgrading your system to the following package versions: Ubuntu 6.06 LTS: mysql-server-5.05.0.22-0ubuntu6.06.15 Ubuntu 8.04 LTS: mysql-server-5.05.0.51a-3ubuntu5.8 Ubuntu 9.10: mysql-server-5.15.1.37-1ubuntu5.5 Ubuntu 10.04 LTS: mysql-server-5.15.1.41-3ubuntu12.7 Ubuntu 10.10: mysql-server-5.15.1.49-1ubuntu8.1 In general, a standard system update will make all the necessary changes. Details follow: It was discovered that MySQL incorrectly handled certain requests with the UPGRADE DATA DIRECTORY NAME command. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 9.10 and 10.04 LTS. (CVE-2010-2008) It was discovered that MySQL incorrectly handled joins involving a table with a unique SET column. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 6.06 LTS, 8.04 LTS, 9.10 and 10.04 LTS. (CVE-2010-3677) It was discovered that MySQL incorrectly handled NULL arguments to IN() or CASE operations. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 9.10 and 10.04 LTS. (CVE-2010-3678) It was discovered that MySQL incorrectly handled malformed arguments to the BINLOG statement. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 9.10 and 10.04 LTS. (CVE-2010-3679) It was discovered that MySQL incorrectly handled the use of TEMPORARY InnoDB tables with nullable columns. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 6.06 LTS, 8.04 LTS, 9.10 and 10.04 LTS. (CVE-2010-3680) It was discovered that MySQL incorrectly handled alternate reads from two indexes on a table using the HANDLER interface. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 6.06 LTS, 8.04 LTS, 9.10 and 10.04 LTS. (CVE-2010-3681) It was discovered that MySQL incorrectly handled use of EXPLAIN with certain queries. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 6.06 LTS, 8.04 LTS, 9.10 and 10.04 LTS. (CVE-2010-3682) It was discovered that MySQL incorrectly handled error reporting when using LOAD DATA INFILE and would incorrectly raise an assert in certain circumstances. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 9.10 and 10.04 LTS. (CVE-2010-3683) It was discovered that MySQL incorrectly handled propagation during evaluation of arguments to extreme-value functions. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 8.04 LTS, 9.10, 10.04 LTS and 10.10. (CVE-2010-3833) It was discovered that MySQL incorrectly handled materializing a derived table that required a temporary table for grouping. An authenticated user could exploit this to make MySQL crash, causing a denial of service. (CVE-2010-3834) It was discovered that MySQL incorrectly handled certain user-variable assignment expressions that are evaluated in a logical expression context. An authenticated user could exploit this to make MySQL crash, causing a denial of service. This issue only affected Ubuntu 8.04 LTS, 9.10, 10.04 LTS and 10.10. (CVE-2010-3835) It was discovered that MySQL incorrectly
Re: FW: [USN-1017-1] MySQL vulnerabilities
I suspect that that is because this is not a security list, but a general help list. If you want those things, you'll get them from either your vendor, bugtraq, or the mysql security-specific mailing list that undoubtedly exists somewhere. Don't ask me where, though - I'm not on it either :-) On Fri, Nov 12, 2010 at 8:02 PM, Daevid Vincent dae...@daevid.com wrote: How come these kinds of notices are not sent to the mysql list? I realize this particular one is from Ubuntu, but the vulnerability is not ubuntu specific, it's mysql. Why aren't the mysql, er um, Oracle people more pro-active about letting us know these things? -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
RE: FW: [USN-1017-1] MySQL vulnerabilities
my point exactly. there is NONE. and if you don't patch your mysql as needed, then you will need a lot more help when you're hacked. ;-p http://lists.mysql.com/ _ From: vegiv...@gmail.com [mailto:vegiv...@gmail.com] On Behalf Of Johan De Meersman Sent: Friday, November 12, 2010 12:18 PM To: Daevid Vincent Cc: mysql Subject: Re: FW: [USN-1017-1] MySQL vulnerabilities I suspect that that is because this is not a security list, but a general help list. If you want those things, you'll get them from either your vendor, bugtraq, or the mysql security-specific mailing list that undoubtedly exists somewhere. Don't ask me where, though - I'm not on it either :-) On Fri, Nov 12, 2010 at 8:02 PM, Daevid Vincent dae...@daevid.com wrote: How come these kinds of notices are not sent to the mysql list? I realize this particular one is from Ubuntu, but the vulnerability is not ubuntu specific, it's mysql. Why aren't the mysql, er um, Oracle people more pro-active about letting us know these things? -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Re: FW: [USN-1017-1] MySQL vulnerabilities
On Fri, Nov 12, 2010 at 4:12 PM, Daevid Vincent dae...@daevid.com wrote: my point exactly. there is NONE. and if you don't patch your mysql as needed, then you will need a lot more help when you're hacked. ;-p http://lists.mysql.com/ Daevid, You may want to read http://dev.mysql.com/tech-resources/articles/security_vulnerabilities.html You can send feedback there. Regards -- Gael Martinez
