While trying to install latest moodle version, I've got blocking message regarding the need to use Barracuda Format for InnoDB.
I've already the ITOP (https://www.combodo.com/itop-193) application installed, then I would like to know if there is any risk on changing from Antelope to Barracuda.
I've read the mariadb documentation (https://mariadb.com/kb/en/innodb-file-format/), but I was not able to understand if I can face potential issues with the databases that where created with Antelope format.
Related
We are using a Self-Hosted Integration Runtime for Azure Data Factory.
On that machine there was installed an Exasol ODBC driver of version 6. We wanted to upgrade the driver, deleted an old one and installed a new driver of version 7.
Weird thing is that now in Exasol logs we can see that Data Factory is sometimes connecting via driver version 7, and sometimes via driver version 6.
I made an experiment and deleted Exasol ODBC driver from the machine completely. After that Data Factory still was able to connect to Exasol using the driver I just deleted.
Looks like drivers' DLLs are cached somewhere. What can it be?
Update 1
I captured following actions in Process Monitor when Data Fatory connected to Exasol with ODBC driver of version 6:
Where these C:\Config.Msi\3739be5*.rbfASolution-6.1\ODBC\ DLLs may come from? There is no C:\Config.Msi\ directory on the machine.
Update 2
I noticed that when I test connection via Microsoft Integration Runtime Configuration Manager on the machine or in Data Factory Linked Service, then connection is always performed with ODBC driver of version 7.
But when I test connection via Data Factory Dataset, then in some cases connection is done with ODBC driver of version 6.
You could check the registry but clean at your own risk. An alternative might be the SysIternals tools, Process Monitor or Process Explorer which might help you get to the bottom of this. Install them on the SHIR VM if you are allowed to. Process Explorer in particular is a bit like SQL Profiler (if you've ever used that) so will be able to tell you which registry keys external processes are using. It will give you a lot a lot of information so you will have to make judicious use of timestamp and filtering. The proposed steps:
Start a trace using Process Monitor
Start a pipeline using the Exasol driver
Wait til it completes (or at least you know it has started)
Stop the Process Monitor trace Spend time going through the millions
of records it has captured, trying to filter down, or search for your
process
An alternative would be to build a clean SHIR and install only the new driver. Then swap it in for the old one. You may have to get the new SHIR added to the firewall if this is an issue for you.
Honestly I would propose both of these approached in parallel for a production problem. Procmon / Process Explorer can be quite labour and time expensive but should help you get to the bottom of the issue. Building a cleaner SHIR is probably a safer option in the long-term, but requires new infrastructure.
It may sound silly, but rebooting the server where SHIR is working solved the problem.
We noticed, that this server was running for more than 30 days, and decided to reboot it. Maybe restarting Integration Runtime service itself would also help, but we didn't do it.
Thanks to everyone for you help.
As part of the open-source software on PASE for i, MariaDB is available in the ibm repository. However, it seems like the MariaDB Connector/ODBC is not available.
Following the Building MariaDB Connector/ODBC From the Git Repository instructions does not work, since it appears that PASE is not supported. Forking it and modifying the source + build toolchain to work in PASE seems like a potential (but unattractive) option.
Is there a MySQL ODBC driver that can be used instead? Have I missed an available package? I also noticed that Zend / Seiden / etc have discussed using PHP with MySQL / MariaDB on PASE for i, how is PHP connecting to MariaDB in that case?
IBM does not currently provide an ODBC interface for connecting to MariaDB. Most high level languages provide a MySQL/MariaDB interface which does not require the client libraries (eg. PyMySQL).
I have recently installed eucalyptus on a Ubuntu 10.04. Everything works fine until I get to the user interface. Whenever I try to get to the store tab I get the following error:
Error 60: server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
I have been doing some research and tried to update the certificate, make changes to the /usr/lib/python2.7/dist-packages/imagestore/lib/fetch.py but none of these solutions worked.
I am really stuck and do not know what to do.
I cannot help resolve the issue on Ubuntu and I suspect the Euca version involved is way out date. If you are willing to work on CentOS then you've got two great options
FastStart - this is an awesome bundle of Eucalyptus and CentOS. I use this to spin up a new cloud after each release, including the pre-release of 3.3. Total time to new cloud is roughly 35 minutes.
http://www.eucalyptus.com/download/faststart
Package downloads - This is your standard install method and the only option to pick if you're trying to build a large cloud.
http://www.eucalyptus.com/download/eucalyptus
BTW - if you are looking to build a large cloud I also recommend you check out the Reference Architectures. These are Eucalyptus deployment blueprints based on lots of real-world, customer environments. http://eucalyptus.com/eucalyptus-cloud/reference-architectures
If you have other questions, I hope we see you on IRC. It's the #eucalyptus channel on freenode: http://webchat.freenode.net/?channels=eucalyptus
Hope this helps
I recently dug up a very old SQL Anywhere database. I have it installed and it kind of works, its only the distributed side of the data, so everything's running via dbeng50 and ODBC.
I would like to migrate this data to MySQL. Is there a way to do this? I attempted to view the data using an ODBC tool but I kept getting error messages saying the ODBC driver doesn't support the version of ODBC behavior.
I guess the database is too old (it's from 1997) - that put's at it SQL Anywhere version 5.
Its also difficult to find the old SQL tools that would help me access these.
Is it possible to use the .db file with a newer version?
Any help or guidance at all would be appreciated.
I have created a simple database using SQLite (actually PySQLite). It works fine when I'm querying or writing to the database from the local machine (ie program and database file on the windows machine drive). However when I copy the database file to my network drive (a time capsule), then Windows machines, although they can see the files and have full read/write access to the drive, give me a "SQL Error: database is locked" even when performing a simple select!
Queries work fine over the network from Macs.
There is no fancy multi-access going on - only one machine has the database open. Seems like some weird Mac networking issue. Happens in either the Python program, or in the SQLite3 command line. I am using SQLite 3.6.14.2.
Anybody seen this problem? Any way of fixing it? Don't really want to get heavy with MYSQL because this is a simple single-user program, but i'd like to use it from multiple machines.
Thanks.
I don't know if it can be done on MAC, on Debian I have to mount the samba directory with the nobrl option.
From mount.cifs(8):
nobrl
Do not send byte range lock requests to the server. This is
necessary for certain applications that break with cifs
style mandatory byte range locks (and most cifs servers do
not yet support requesting advisory byte range locks).
Read the sqlite FAQ: http://www.sqlite.org/faq.html#q5
"People who have a lot of experience
with Windows tell me that file locking
of network files is very buggy and is
not dependable. If what they say is
true, sharing an SQLite database
between two or more Windows machines
might cause unexpected problems."
So it doesn't work on Windows, it doesn't tell about MAC.
Possibly it fails to lock the file over the network, I think you use SMB protocol so the bugginess comes with the package. If you would like to use SQLite over the network see SQLite Network for alternatives.
I've had a similar problem and I solved it by installing a newer sqlite version. Since Python 2.6 the problem has disappeared too because it uses a newer sqlite dll.
Thank you Carlos. Cherrytree depends on SQLite, and for some reason it recently stopped working with my samba-mounted SQLite database file, complaining about a locked database. Adding "nobrl" to my ubuntu fstab entry solved the problem.
//192.168.3.122/Files /mnt/Files cifs username=public,password=asdf,rw,noperm,nobrl 0 0