About the mac weka connect to mysql - mysql

I have added java-connect-5.1.41.jar to the directory weka-oracle-jvm/content/java, but when I open DB and connect, it returns false and I get the error:
Unable to find a suitable driver to jdbc.
I have change the ./bash_profile:
export CLASSPATH = ".../weka.jar:/.../java-connect-5.1.41.jar"

I don't think you have downloaded the right file. If you're using MySQL, the file that you have to copy should be of the format "mysql-connector-java-version-bin.jar". The download link is here.
I have also posted a full work-around here. Do let me know if it works for you.

Related

windows could not start the MySQL. service on local computer. Error 2 : The system cannot find the file specified

I am not able to start the MySQL server on my Windows system. When I tried in services.msc to run, I got this error:
Starting it through the XAMPP control panel does not work either:
Can you help me to solve this?
Open windows services (Start->run ->Services.MSC)
Find service with name "Mysql Server" and check path, it should be something like that:
"C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51\bin\mysqld.exe" "--defaults-file=C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL\Data\my.ini" MySQL
Make sure that Mysql folder and executable file mentioned above exist by this path.
OR
Sometimes the file name of mysqld-nt.exe renamed to mysqld-nt.exe~ so rename it back to its original name and this may solve the problem.
Go to the path: C:Programs Files\MariaDB 10.2\data..
Lookout for my.ini file. Open the file and check the path for "datadir".
If that does not match to your installed directory then update it.
Your problem will be solved for sure.
I faced the same problem and solved it.
Just modify the registry editor value.
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/MySQL/ImagePath

FireDac error 314 - but DLLs are in program directory

I am getting when trying to access a MySql database :
[FireDac][Phys][MySQL]-314. Cannot load vendor library [libmysql.dll
or libmysqlld.dll]
This did not previously happen with this (unchanged) code, however, I have upgraded to Windows 10 and had to reinstall Delphi XE8, so it is obviously a system configuration matter.
In order to try to solve the problem, I copied both of those files into c:\windows\sysytem32.
When that did not seem to work, I copied them into \win32\debug, which is where the generated .EXE resides.
I imagine that I am doing something rather stupid, but can't see what.
The proper solution is to place the driver file (eg., libmysql.dll) in your application's folder, or to place the installation location in your FDDrivers.ini file:
[MySQL]
Vendor=<folder>\libmysql.dll
(Recent versions of the documentation seem to use VendorLib instead of Vendor in the INI file.)
See the RAD Studio documentation topics Configuring Drivers (FireDAC) and Connect to MySQL Server (FireDAC) for more information.
Let me to answer in two point.
Developing, live database connection!
Hope you have on your data module an "TFDPhysMySQLDriverLink" component.
Click this component and browse your LibMySQL.DLL into VendorLib. Should be work. But only in design time.
Runtime. Hopefully your DM created firstly in your project.
In the DM's OnCreate event, you have to disconnect your library (I always ran my project with no database connection) and replace your "TFDPhysMySQLDriverLink"'s Vendorlib to LibMySQL.DLL (which is copied your which is copied where the generated .EXE resided)
Have a nice day!

SAS MYSQL libname connection issue

Can anyone help with the following?
5 LIBNAME test1 mysql server='blah.blah.com' user='blah' password=XXXXXX;
ERROR: The SAS/ACCESS Interface to MYSQL cannot be loaded. The libmysql code appendage could not be
loaded.
ERROR: Error in the LIBNAME statement.
Am using SAS 9.3, and downloaded the latest MySQL client today (v5.2.47).
As per Usage Note 37512 I am not using the following statement either in my code, nor in the sasv9.cfg file:
options set=sasmyl mywin417;
Do you have a pointer to the MySQL library in your path variable?
data _null_;
format x $10000.;
x=sysget('path');
put x=;
run;
If a path to the MYSQL location is not in the list above, there are two options:
1 - update the path variable to point at the correct location (restart required): http://www.computerhope.com/issues/ch000549.htm#0
2 - presuming the correct location does not exist, you may not have the software correctly installed. Try installing from this location: http://dev.mysql.com/downloads/installer/
Another issue might be with the connector. This can be downloaded from http://dev.mysql.com/downloads/. A further step is to copy the libmysql.dll file from C:\Program Files\MySQL\MySQL Connector C 6.0.2 to C:\Windows\System32...
Another alternative is that your SAS installation is not licenced for SAS/Access Interface to MYSQL.
Solved the same problem just adding to path not bin, but lib directory. Also in this dir was libmysql.dll file
I was facing the same problem as well. I just put the libmysql.dll file into the System32 folder and it worked. Also could try the SysWOW64 if System32 does not help.

Parsed Console Output Error in Hudson

im running Hudson continuous integration for db unit.
when i run the job the console output is displaying the SUCCESS, but then why do the Parsed Console Output keep returning this error:
ERROR:Failed to parse console log :
log-parser plugin ERROR: Cannot parse log: Can't read parsing rules file:
i already installed the parse-log plugin & i already restarted the Hudson..
i installed the plugin using remote PC
any help and suggestion is appreciated. Thanks!
1) Place the Parser Rule File in the JENKINS_HOME location.
2) Configure that log parser console output in the Global COnfiguration settings and Name it.
3) Add this option in the Post Build Actions and Select the Name
ok silly me..
i forgot to configure the global configuration in hudson that link to the parser rule file..
problem solved.
I'm posting this in case anyone else has a specific case of this problem. This issue started when upgrading from 1.509.2 to 1.554.3... I had the parsing rules file in the win\system folder which was a known issue when running Jenkins as a service. Well I guess they fixed it by this version. I moved the parsing rules back into Jenkins Home folder and it worked fine again.

how to connect mysql databases in weka?

i want to use my mysql databases in weka in order to analysis data.
i download the mysql-connector-java-5.0.8-bin.jar and put that in weka folder in my program Files folder, and add this path to system variable path, but when i open the weka explorer and click the openDB, i don't know what should i write in the url textbox,
i don't know completely what should i do?
the error that i saw is:
problem connecting to database:
no suitable driver found for!
please give me a total guidance, thanks in advance.
add mysql-connector-java-5.1.12-bin.jar to CLASSPATH .
or put it in weka folder, navigate to weka installation folder and run command :
%java_home%/bin/java -Xmx300M -cp ".;weka.jar;mysql-connector-java-5.1.12-bin.jar;" weka.gui.GUIChooser
then click open DB and
fill in the proper user+password
put the url: jdbc:mysql://localhost:3306/DATABASENAME
Click Execute. The result window should show the results now.
For Weka 3.7.10, the classpath system environment variable is not took into account (at leat under Windows 7). The only working approach for me was to modify the RunWeka.ini file from the Weka installation folder as follows: the cp= setting was modified to:
cp=%CLASSPATH%;d:/Programs/jdbc/mysql-connector-java-5.1.26/mysql-connector-java-5.1.26-bin.jar
whereas only the %CLASSPATH%; setting was originally provided. Does not make much sense, but in worked.
find some introduction to WEKA and the environment variable:
http://weka.wikispaces.com/CLASSPATH
Copy mysql-connector-java-X.X.XX-bin.jar to /usr/share/java/
unizip /usr/share/java/weka.jar
edit: /usr/share/java/weka/experiment/DatabaseUtils.props
add:
jdbcDriver=com.mysql.jdbc.Driver
jdbcURL=jdbc:mysql://localhost:3306/test (with your server)
add shell
export CLASSPATH=/usr/share/java/mysql-connector-java-X.X.XX-bin.jar:
export CP=/usr/share/java/mysql-connector-java-X.X.XX-bin.jar::/usr/share/java/:/usr/shared/java/weka.jar
execute weka:
java -cp $CP -Xmx500m weka.gui.explorer.Explorer
Ready