Apache OpenOffice (AOO) Bugzilla – Issue 14691
unable to add MySQL data source then crash 1.1beta
Last modified: 2006-05-31 14:29:06 UTC
unable to add MySQL data source Open Writer or Calc |Tools|DataSources...|click New Data Source|name as test|select MySQL|click MySQL tab|Use existing MyODBC connector|click to add path gave error "could not load program library libodbc.so ...." I symlinked libodbc.so.1.0.0 to libodbc.so and got one stage further to Choose a data source|Organize and got a similar error "could not load program library libodbcinst.so...." Symlinked /usr/lib/libodbc*.so.1.0.0 to /usr/lib/libodbc*.so but the error remained - see screendump Tried again Tools|Data Sources...| Add new Data Source|name as test|select MySQL|click MySQL tab| Use connector J3|MySQL tab| enter values at <host>:<3306>/<DBNAME> **not immediately intuitive what is required here**|click Tables tab| enter pwd| -- error "No connection could be established......" screenshot Confirmed mysql was running and that I had a valid user/pwd pair and 3306 was open Reproduced this problem in both modes several times and then clicked help to check the syntax of the data entry in the <host>:<3306>/<DBNAME> box and got unrecoverable error. 1st crash I have had with 1.1 beta :-( unlike 1.01, 1.02 This is the first bug Ive added -- is this enough/too much info?
Created attachment 6311 [details] jdbc error
*** Issue 14692 has been marked as a duplicate of this issue. ***
> This is the first bug Ive added -- is this enough/too much info? There's rarely such a thing like "too much info". As long as _one_ issue focusses on _one_ problem (which is the case here), every bit of information which may remotely help to reproduce the problem is appreciated. Only a bug which can be reproduced can be fixed, and information is strictly necessary for reproducing. But while we're at it (: What about your linux distribution?
OS is SuSE 8.1 with stock SuSE kernel 2.4.19-4GB hardware is Athlon2000+ 384Mb RAM
Can you give us a stack dump of the crash happening in OOo1.1beta2? See http://kegel.com/openoffice/#dump (or wait for OOo1.1rc1, which will have a built-in crash logger) Thanks!
I'm adding the "oooqa" keyword & setting the priority to P1 from P3.
There are known issues with UnixODBC. Please upgrade to UnixODBC-2.2.6 from http://www.unixodbc.org Also, that symlink trick really wasn't kosher :-) If you can reproduce this problem with UnixODBC-2.2.6 and OpenOffice.org1.1.0rc4, please reopen this issue; for now, I'm marking it 'invalid' to reflect the fact that it's probably a bug in your unixodbc. BTW, if you haven't seen them, there are some (slightly outdated) guides on using MySQL and OpenOffice at redhat 7.3: http://www.unixodbc.org/doc/OOoMySQL.pdf redhat 9: http://www.unixodbc.org/doc/OOoMySQL9.pdf
so I close this issue
change subcomponent to 'none'