Issue 12162 - Remote ODBC connection fails
Summary: Remote ODBC connection fails
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-09 15:24 UTC by assengar
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description assengar 2003-03-09 15:24:34 UTC
Hi,

I've been trying use a remote data source for bibliographic entries. I am using
openoffice.org version 1.0.1 on redhat 8.0 on a laptop. My remote database is on
a mysql server (192.168.1.2) located in an internal home-based lan. The server
is also a workstation and I have redhat 8.0 and openoffice on that one too. The
workstation/server is able to access the local mysql database via odbc just
fine. But the laptop can't. I can connect to the database from the laptop using:
'mysql -h 192.168.1.2 -u medline -p' without any problems.  

Here is my /etc/odbc.ini:
[MySQL-medline]
Description   = MySQL database medline
Driver     = MySQL
Server     = 192.168.1.2
Database    = medline
Port      = 3306
Socket     =
Option     =
Stmt      =


Here is /etc/odbcinst.ini:
[MySQL]
Description   = ODBC Driver for MySQL
Driver     = /usr/lib/libmyodbc.so
Setup      = /usr/lib/libodbcmyS.so
FileUsate    = 1
CPTimeout    =
CPReuse     =


My installed packages on the laptop are: mysql-3.23.55a-4, MyODBC-2.50.39-7, and
unixODBC-2.2.2-3.

There is a documented bug with redhat 8.0 and remote mysql logins. I corrected
for the bug by adding 'set-variable=thread_stack=265k' under [mysqld] in
/etc/my.cnf.  This allowed the remote mysql connection via mysql client. 

I then was able to test the ODBC connection: 'isql MySQL-medline medline medline
-v' and this works too. 

In openoffice, I go to tools > data sources... and add a new datasource. I pick
ODBC and my MySQL-medline database name shows up in the list. I am able to
select it. Then I click on the ODBC tab and type in my username and check the
password required box. When I go to the tables tab, openoffice asks for my
password which I enter after which the entire app crashes and disappears off my
screen. It's a clean crash as there are no leftover processes or memory usage
that I can see.

I did a google search and discovered others with this problem, but no solutions
were posted. I'm not sure if it's a RH8.0 specific problem or not. Also as far
as I can tell there is no bug reports here either. If I'm mistaken, please send
me the link to the report.

One workaround would be to run a mysql server on the laptop and manually copy
the databases back and forth between the workstation and the laptop. That's a
pain. If you have a patch or better workaround I'd appreciate it. 

Thanks,

Ameet
Comment 1 dnwilson 2003-03-10 21:02:01 UTC
Thsi seems to be a database issue rather than a bibliographic one 
Comment 2 Frank Schönheit 2003-03-11 08:47:08 UTC
assengar, do you have a chance to try this with the latest snapshot of
OOo (http://www.openoffice.org/dev_docs/source/644/)?
Comment 3 assengar 2003-03-13 13:13:55 UTC
Ok, the 644 snapshot has solved my data source issues. I can now
connect to a remote mysql server and access the data. But, I also had
to recompile the MyODBC package from redhat. Their pre-built binary
does not work with their updated mysql and unixODBC packages. (True
for redhat 8.0 at least).

Here's the new problem:

I go to Tools > Bibliographic Database and choose my remote database
as my datasource. My tables are a bit different than the openoffice
default structure, so I edit the table to assign my columns
appropriately.  To add a citation into my document, I go to Insert >
Indexes and Tables > Bibliographic entry... and that's where a new
crash occurs and I get a popup window that states:

'an unrecoverable error has occured...saving etc...'

I can see the list of short_names from my database in the background
which is good. 

I also get the following error at my prompt:

$ sh: line 1: crash_report: command not found
$ Aborted

Any thoughts?
Comment 4 Frank Schönheit 2003-03-13 16:00:23 UTC
> Ok, the 644 snapshot has solved my data source issues.

great :)

> Here's the new problem:
> ...
> Any thoughts?

yes: file a new issue :). Sorry, sounds harsh, but can we please
separate this into another issue, as it seems to be another problem?
Tracking and understanding issues which changed their content is
always a pain, so I'd like to stay with "one problem - one issue".
Thanks :)
Comment 5 Frank Schönheit 2003-04-29 13:17:43 UTC
marking this as FIXED in reaction to the submitter's:

> Ok, the 644 snapshot has solved my data source issues.
Comment 6 Frank Schönheit 2003-04-29 13:17:55 UTC
closing
Comment 7 hans_werner67 2004-02-02 12:57:09 UTC
change subcomponent to 'none'