March 2015 - discuss - lists.mariadb.org

[Maria-discuss] New Question: MS-SQL Server Change tracking
by AskMonty KB 18 Mar '15

18 Mar '15

Hello, A new question has been asked in "Moving to MariaDB" by peterhorwood. Please answer it at http://mariadb.com/kb/en/ms-sql-server-change-tracking/ as the person asking the question may not be subscribed to the mailing list. -------------------------------- I'm looking at having our product add MariaDB as a database we support. Currently we only support MS-SQL. One issue I'm wondering about is change tracking. Does MariaSQL have anything like the SQL Server (2008 and newer) Server change tracking? Or do I need to 'roll my own' using insert/update/delete triggers? -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/ms-sql-server-change-tracking/

1 0

[Maria-discuss] Sysbench compile error for MariaDB under Centos 6.4
by Fay Hou 18 Mar '15

18 Mar '15

Thank you for your time. I do see the libmysqlclient installed. []# find / -name libmysqlclient_r* /usr/lib64/libmysqlclient_r.so.15 /usr/lib64/libmysqlclient_r.so.15.0.0 /usr/lib64/libmysqlclient_r.so.16.0.0 /usr/lib64/libmysqlclient_r.so.16 /usr/lib64/libmysqlclient_r.a But, I got error when I compile "make". Any ideas? libtool: link: gcc -W -Wall -Wextra -Wpointer-arith -Wbad-function-cast -Wstrict-prototypes -Wnested-externs -Winline -funroll-loops -Wundef -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wcast-align -pthread -O2 -ggdb3 -o sysbench sysbench.o sb_timer.o sb_options.o sb_logger.o db_driver.o sb_percentile.o -L/usr/local/lib tests/fileio/libsbfileio.a tests/threads/libsbthreads.a tests/memory/libsbmemory.a tests/cpu/libsbcpu.a tests/mutex/libsbmutex.a scripting/libsbscript.a drivers/mysql/libsbmysql.a -L/usr/lib64/mysql -lmysqlclient_r scripting/lua/src/liblua.a -ldl -lrt -lm -pthread /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `mysql_get_ssl_cipher': (.text+0x2159): undefined reference to `SSL_get_current_cipher' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `send_client_reply_packet': (.text+0x2a68): undefined reference to `SSL_get_peer_certificate' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `send_client_reply_packet': (.text+0x2a80): undefined reference to `X509_get_subject_name' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `send_client_reply_packet': (.text+0x2a94): undefined reference to `X509_NAME_oneline' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `send_client_reply_packet': (.text+0x2aa3): undefined reference to `X509_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `send_client_reply_packet': (.text+0x2cbc): undefined reference to `ERR_error_string_n' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `mysql_close': (.text+0x35f4): undefined reference to `SSL_CTX_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(client.c.o): In function `mysql_get_ssl_cipher': (.text+0x2162): undefined reference to `SSL_CIPHER_get_name' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(mysql_async.c.o): In function `my_ssl_read_async': (.text+0xcdf): undefined reference to `SSL_read' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(mysql_async.c.o): In function `my_ssl_read_async': (.text+0xd0e): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(mysql_async.c.o): In function `my_ssl_write_async': (.text+0xd8f): undefined reference to `SSL_write' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(mysql_async.c.o): In function `my_ssl_write_async': (.text+0xdbe): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(vio.c.o): In function `vio_end': (.text+0x5a7): undefined reference to `ERR_remove_state' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(vio.c.o): In function `vio_end': (.text+0x5ac): undefined reference to `ERR_free_strings' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(vio.c.o): In function `vio_end': (.text+0x5b1): undefined reference to `EVP_cleanup' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(vio.c.o): In function `vio_end': (.text+0x5b7): undefined reference to `CRYPTO_cleanup_all_ex_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosocket.c.o): In function `vio_is_connected': (.text+0xe86): undefined reference to `SSL_pending' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x3b): undefined reference to `SSL_new' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x4f): undefined reference to `SSL_clear' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x57): undefined reference to `SSL_get_session' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x62): undefined reference to `SSL_SESSION_set_timeout' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x6d): undefined reference to `SSL_set_fd' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x81): undefined reference to `SSL_ctrl' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0xab): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0xef): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0xfc): undefined reference to `SSL_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x159): undefined reference to `SSL_get_fd' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `ssl_do': (.text+0x199): undefined reference to `ERR_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_read': (.text+0x1f1): undefined reference to `SSL_read' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_read': (.text+0x207): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_write': (.text+0x2e1): undefined reference to `SSL_write' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_write': (.text+0x2f7): undefined reference to `SSL_get_error' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_close': (.text+0x3b8): undefined reference to `SSL_set_quiet_shutdown' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_close': (.text+0x3c0): undefined reference to `SSL_shutdown' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_delete': (.text+0x407): undefined reference to `SSL_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `sslaccept': (.text+0x447): undefined reference to `SSL_accept' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `sslconnect': (.text+0x467): undefined reference to `SSL_connect' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viossl.c.o): In function `vio_ssl_has_data': (.text+0x4ac): undefined reference to `SSL_pending' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x63): undefined reference to `SSL_load_error_strings' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x8a): undefined reference to `TLSv1_server_method' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x92): undefined reference to `SSL_CTX_new' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0xae): undefined reference to `SSL_CTX_set_cipher_list' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0xc5): undefined reference to `SSL_CTX_load_verify_locations' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0xe5): undefined reference to `SSL_CTX_set_default_verify_paths' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x103): undefined reference to `SSL_CTX_get_cert_store' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x116): undefined reference to `X509_STORE_load_locations' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x12b): undefined reference to `X509_STORE_set_flags' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x15f): undefined reference to `SSL_CTX_use_certificate_chain_file' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x17c): undefined reference to `SSL_CTX_use_PrivateKey_file' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x191): undefined reference to `SSL_CTX_check_private_key' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x19e): undefined reference to `DH_new' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x1b9): undefined reference to `BN_bin2bn' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x1d1): undefined reference to `BN_bin2bn' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x1fd): undefined reference to `SSL_CTX_ctrl' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x205): undefined reference to `DH_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x221): undefined reference to `TLSv1_client_method' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x268): undefined reference to `SSL_library_init' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x26d): undefined reference to `OPENSSL_add_all_algorithms_noconf' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x2d6): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x2e3): undefined reference to `SSL_CTX_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x32d): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x3ad): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x42d): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x465): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x47a): undefined reference to `DH_free' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLFd': (.text+0x4ad): undefined reference to `ERR_get_error_line_data' /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libmysqlclient_r.a(viosslfactories.c.o): In function `new_VioSSLConnectorFd': (.text+0x514): undefined reference to `SSL_CTX_set_verify' under Centos 6.4

3 5

[Maria-discuss] Error Message spelling mistake
by Rhys Campbell 16 Mar '15

16 Mar '15

I feel like a bit of a pedant reporting this... "Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Error: connecting slave requested to start from GTID 1-1-7, which is not in the master's binlog. Since the master's binlog contains GTIDs with higher sequence numbers, it probably means that the slave has diverged due to executing extra errorneous transactions'" Errorneous should be erroneous Rhys Campbell Database Administrator TradingScreen, Inc. 23 York House, 5th Floor London WC2B 6UJ Email: rhys.james.campbell(a)googlemail.com<mailto:rhys.james.campbell@googlemail.com> Follow TradingScreen on Twitter<http://twitter.com/#!/TradingScreen> , Facebook<http://www.facebook.com/pages/TradingScreen/214046251945650> and our blog Trading Smarter<tradingsmarter.tradingscreen.com> This message is intended only for the recipient(s) named above and may contain confidential information. If you are not an intended recipient, you should not review, distribute or copy this message. Please notify the sender immediately by e-mail if you have received this message in error and delete it from your system.

3 2

[Maria-discuss] Stored Procedure debugger from Peter Gulutzan and Trudy Pelzer
by Alexander Barkov 13 Mar '15

13 Mar '15

Hi, Peter Gulutzan and Trudy Pelzer announced their GUI debugger for stored procedures. Sources, binaries and a demo are available here: http://ocelot.ca/blog/blog/2015/03/02/the-ocelotgui-debugger/ This is a great news. Greetings.

5 8

[Maria-discuss] Enabling feedback pluging for MariaDB 10.1.4
by Michael Widenius 12 Mar '15

12 Mar '15

Hi! We had originally planned to enable the feedback plugin by default for the Alpha and Beta stages of MariaDB 10.1, but we forgot to do this for the alpha so I suggested Sergei today that we should enable it for the beta period of MariaDB 10.0 We agreed that before doing this we would have a discussion on the maria developer list to explain why we would like to do this. The reason we would like to enable it is to get information about which features people are testing and using in MariaDB 10.1, so that we can concentrate our testing and bug fixing during the beta phase for those areas that people are actually using. This would help our development work a lot and would also help us to plan for MariaDB 10.2 development. Anyone will be able to disable the feedback plugin by adding: --feedback=OFF to their my.cnf file. In MariaDB 10.1 gamma/release we would make it default OFF again. We will of course inform everyone about this change, including how to disable the feedback, in the MariaDB changelog and release notes. We do of course hope that as many as possible will have it on, even after gamma, to help us with our development work! Information about the MariaDB feedback plugin and the statistics it provides can be found at: http://mariadb.org/feedback_plugin https://mariadb.com/kb/feedback-plugin As most MariaDB users should know, the feedback is totally anonymous and no private or sensitive information is being sent. Any comments, suggestions or recommendations? Regards, Michael Widenius Creator of MySQL and MariaDB

12 19

[Maria-discuss] MariaDB Galera Cluster 10.0.17 and 5.5.42 now available
by Daniel Bartholomew 11 Mar '15

11 Mar '15

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.17 & 5.5.42 Both are Stable (GA) releases. See the Release Notes and Changelog for details. - - Links - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MariaDB Galera Cluster 10.0.17 - Release Notes: https://mariadb.com/kb/en/mariadb-galera-cluster-10017-release-notes/ - Changelog: https://mariadb.com/kb/en/mariadb-galera-cluster-10017-changelog/ - Downloads: https://downloads.mariadb.org/mariadb-galera/10.0.17 MariaDB Galera Cluster 5.5.42 - Release Notes: https://mariadb.com/kb/en/mariadb-galera-cluster-5542-release-notes/ - Changelog: https://mariadb.com/kb/en/mariadb-galera-cluster-5542-changelog/ - Downloads: https://downloads.mariadb.org/mariadb-galera/5.5.42 About MariaDB Galera Cluster: - https://mariadb.com/kb/en/what-is-mariadb-galera-cluster/ APT and YUM Repository Configuration Generator: - https://downloads.mariadb.org/mariadb/repositories/ - - MariaDB Webinars - - - - - - - - - - - - - - - - - - - - - - - - - There are several upcoming MariaDB-focused webinars and many previously held ones available to watch on an on-demand basis at: - https://mariadb.com/news-events/webinars - - MariaDB Books - - - - - - - - - - - - - - - - - - - - - - - - - - There is an ever-growing library of MariaDB books available to help you get the most out of MariaDB. See the MariaDB Books page for details and links: - https://mariadb.com/kb/en/mariadb/books/ - - User Feedback plugin - - - - - - - - - - - - - - - - - - - - - - - MariaDB includes a User Feedback plugin. This plugin is disabled by default. If enabled, it submits basic, completely anonymous MariaDB usage information. This information is used by the developers to track trends in MariaDB usage to better guide development efforts. If you would like to help make MariaDB better, please add "feedback=ON" to your my.cnf or my.ini file! See http://mariadb.com/kb/en/user-feedback-plugin for more information. - - Quality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The project always strives for quality, but in reality, nothing is perfect. Please take time to report any issues you encounter at: - http://mariadb.org/jira - - Support MariaDB - - - - - - - - - - - - - - - - - - - - - - - - - - If you would like to contribute to the MariaDB Foundation, please see the "contributing" and "donations" pages. We also have merchandise available in a cafepress store. All proceeds go to support the MariaDB Foundation. - https://mariadb.com/kb/en/contributing - https://mariadb.org/en/donate/ - http://www.cafepress.com/mariadb We hope you enjoy MariaDB! -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb

1 0

[Maria-discuss] GSOC 2015 :UDFs returning arrays
by Delveri chick 11 Mar '15

11 Mar '15

Hi My name is Blessing Atie and i would love to participate in the Google summer of code 2015 under Mariadb. I am interested in the project UDF returning arrays. I have build mariadb from source and and i also ran the test suites. I am currently studing the sql/sql.** files to understand UDF's and i also downloaded some ebook on mysql internals and mysql plugin development which im reading while hoping to find a breakthrough on this project in them. I would love to know if there are any bugs related to this task on JIRA I could work on as a means of preparing for the project. Please give me the link. Regards

5 14

[Maria-discuss] New Question: Looking for a stable version of ODBC connector for Linux
by AskMonty KB 05 Mar '15

05 Mar '15

Hello, A new question has been asked in "MariaDB Connector/ODBC" by namkyungkim. Please answer it at http://mariadb.com/kb/en/looking-for-a-stable-version-of-odbc-connector-for… as the person asking the question may not be subscribed to the mailing list. -------------------------------- Hi all, I am looking for a stable version of ODBC connector for Linux. I am kindly asking you when I can have a chance to download it. Thank you and regards, -------------------------------- To view or answer this question please visit: http://mariadb.com/kb/en/looking-for-a-stable-version-of-odbc-connector-for…

1 0

[Maria-discuss] mariadb 10.0.17 keeps crashing
by Gabriel Sosa 04 Mar '15

04 Mar '15

Hello, I've been a proudly user of mariadb 5.5.x for a long time now but given the nice feature setI decided to give mariadb 10.x a try. I took one of our current slaves running mariadb 5.5.x (on centos 6.5) and followed the upgrade steps using yum and ran *mysql_upgrade*. The upgrade ran without any trouble...then I moved a huge table (about 1B records right now) from InnoDB to TokuDB. Now, every couple of hours I find that the replication is far behind the master and the reason is because this server keeps checking tables marked as crashed.... I can't seems to find any indicator of OOM killer in the system logs NOR anything related to that in the mysql log, the only clue I have is: --------------- *150303 10:08:57 mysqld_safe Number of processes running now: 0* *150303 10:08:57 mysqld_safe mysqld restarted* 150303 10:08:58 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. 150303 10:08:59 [Warning] option 'innodb-status-file': boolean value 'ib_status' wasn't recognized. Set to OFF. 150303 10:08:59 [Warning] option 'innodb-autoextend-increment': unsigned value 10485760 adjusted to 1000 150303 10:08:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages 150303 10:08:59 [Note] InnoDB: The InnoDB memory heap is disabled 150303 10:08:59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 150303 10:08:59 [Note] InnoDB: Memory barrier is not used 150303 10:08:59 [Note] InnoDB: Compressed tables use zlib 1.2.3 150303 10:08:59 [Note] InnoDB: Using Linux native AIO 150303 10:08:59 [Note] InnoDB: Using CPU crc32 instructions 150303 10:08:59 [Note] InnoDB: Initializing buffer pool, size = 6.0G 150303 10:08:59 [Note] InnoDB: Completed initialization of buffer pool 150303 10:08:59 [Note] InnoDB: Highest supported file format is Barracuda. 150303 10:08:59 [Note] InnoDB: Log scan progressed past the checkpoint lsn 14178608217047 150303 10:08:59 [Note] InnoDB: Database was not shutdown normally! 150303 10:08:59 [Note] InnoDB: Starting crash recovery. 150303 10:08:59 [Note] InnoDB: Reading tablespace information from the .ibd files... 150303 10:09:05 [Note] InnoDB: Restoring possible half-written data pages 150303 10:09:05 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 14178613459456 InnoDB: Doing recovery: scanned up to log sequence number 14178618702336 InnoDB: Doing recovery: scanned up to log sequence number 14178623945216 InnoDB: Doing recovery: scanned up to log sequence number 14178629188096 InnoDB: Doing recovery: scanned up to log sequence number 14178634430976 InnoDB: Doing recovery: scanned up to log sequence number 14178639673856 InnoDB: Doing recovery: scanned up to log sequence number 14178644916736 ...... ...... ...... ...... 150303 10:09:14 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 16433109, file name slave-bin.852141 InnoDB: Last MySQL binlog file position 0 16784214, file name /var/lib/mysql/log/bin/slave-bin.005211 150303 10:09:34 [Note] InnoDB: 128 rollback segment(s) are active. 150303 10:09:34 [Note] InnoDB: Waiting for purge to start 150303 10:09:34 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-72.0 started; log sequence number 14178834821658 Tue Mar 3 10:09:36 2015 TokuFT recovery starting in env /var/lib/mysql/data/ Tue Mar 3 10:09:36 2015 TokuFT recovery scanning backward from 1330297 Tue Mar 3 10:09:36 2015 TokuFT recovery bw_end_checkpoint at 1330297 timestamp 1425395277901416 xid 1330281 (bw_newer) Tue Mar 3 10:09:36 2015 TokuFT recovery bw_begin_checkpoint at 1330281 timestamp 1425395273487081 (bw_between) Tue Mar 3 10:09:36 2015 TokuFT recovery turning around at begin checkpoint 1330281 time 4414335 Tue Mar 3 10:09:36 2015 TokuFT recovery starts scanning forward to 1330297 from 1330281 left 16 (fw_between) Tue Mar 3 10:09:36 2015 TokuFT recovery closing 14 dictionaries Tue Mar 3 10:09:36 2015 TokuFT recovery making a checkpoint Tue Mar 3 10:09:36 2015 TokuFT recovery done 150303 10:09:36 [Note] Recovering after a crash using /var/lib/mysql/log/bin/slave-bin --------------- The odd thing is that the 5.5.x version was working just fine (since about a year) in the same hardware...nothing changed in that front. Any clue? Thank you in advance

4 9

[Maria-discuss] Questions on image data should be stored in database or not?
by Peter Boston 04 Mar '15

04 Mar '15

I don't know the following questions are valid here or not. I just hope I get some help from experienced experts here. I am planning to use MariaDB on 64bit Linux for a new medical application project. I have to store lots of images. The size of one image is about 263KB. There are about 50 images per patient. It's about 14MB. I have two options here for these image data: Option A: store them in file system and have their location linked in database table; Option B: store them in database in a separated table as BOLB with a unique id; I know there are lots of implementations go with Option A. My concern about Option A is the security and backup. I have to do them separately. Do you have any good idea how to do them? For Option B, I am worry about the size of that table and the database. I read somewhere saying the BOLB and TEXT columns in a table are not stored "inline" and will not be counted to the table size. Where I can find the detailed information about this? Oracle has a special way to handle this situation and is pushing save images into database. Is there a similar mechanism in MariaDB? How about compress a series of images for a patient in Option B? Is it worthy to scarify perform for gaining some spaces? Eventually the data size will be very big, what are the options for me to cleanup and archive old data, including the image data? Thanks, Peter

3 4