Sponsored Content
Operating Systems Linux Red Hat Missing dependencies updating unixODBC / MySQL Connector Post 302467084 by Bengbers on Thursday 28th of October 2010 07:34:16 AM
Old 10-28-2010
Missing dependencies updating unixODBC / MySQL Connector

I have installed mysql-connector-odbc-5.1.5-0.i386.rpm and libtools on my Fedora12 system.
Updating with yum says that there is nothing to update.
Updating with rpm -Uvh mysql-connector-odbc-5.1.7-0.i386.rpm fails with the same missing dependencies as for the 64-bit version.

Should I force installation with rpm --nodeps ?
 

3 More Discussions You Might Find Interesting

1. AIX

Install MySQL connector without local SQL database

Hello UNIX gurus, I need to install the mysql odbc connector with unixODBC on my AIX 5.3 machine. I have a mySQL database running on another server (Ubuntu 7.04). The SQL database works fine. The problem I am having is when trying to run ./configure for mysql-connector-odbc it seems to be looking... (1 Reply)
Discussion started by: raidzero
1 Replies

2. SuSE

How to resolve missing missing dependencies with opensuse 11.3 and 12.3?

Hello, This is a programming question as well as a suse question, so let me know if you think I should post this in programming. I have an application that I compiled under opensuse 12.2 using g77-3.3/g++3.3. The program compiles and runs just fine. I gave the application to a colleague who... (2 Replies)
Discussion started by: LMHmedchem
2 Replies

3. Red Hat

Yum - resolving missing dependencies that are not missing

I am trying to install VirtualBox on RHEL 5 but I need the 32 bit version for 32 bit Windows. When I run yum I get the following: sudo yum localinstall /auto/spvtg-it/spvss-migration/Software/VirtualBox-4.3-4.3.2_90405_el6-1.i686.rpm Loaded plugins: fastestmirror Setting up Local Package... (13 Replies)
Discussion started by: gw1500se
13 Replies
grass-odbc(1grass)						Grass User's Manual						grass-odbc(1grass)

NAME
grass-odbc - ODBC driver ODBC driver ODBC driver in GRASS Communication between GRASS and ODBC database for attribute management: | GRASS module | | ODBC Interface | | RDBMS | GRASS | DBMI driver | unixODBC | ODBC driver | PostgreSQL | Oracle | ... Supported SQL commands All SQL commands supported by ODBC. Operators available in conditions All SQL operators supported by ODBC. EXAMPLE
In this example we copy the dbf file of a SHAPE map into ODBC, then connect GRASS to the ODBC DBMS. Usually the table will be already present in the DBMS. Configure ODBC driver for selected database (manually or with 'ODBCConfig'). ODBC drivers are defined in /etc/odbcinst.ini. Here is example: [PostgreSQL] Description = ODBC for PostgreSQL Driver = /usr/lib/libodbcpsql.so Setup = /usr/lib/libodbcpsqlS.so FileUsage = 1 Create DSN (data source name). The DSN is used as database name in db.* modules. Then DSN must be defined in $HOME/.odbc.ini (for this user only) or in /etc/odbc.ini for (for all users) [watch out for the database name which appears twice and also for the PostgreSQL protocol version]. Omit blanks at the beginning of lines: [grass6test] Description = PostgreSQL Driver = PostgreSQL Trace = No TraceFile = Database = grass6test Servername = localhost UserName = neteler Password = Port = 5432 Protocol = 8.0 ReadOnly = No RowVersioning = No ShowSystemTables = No ShowOidColumn = No FakeOidIndex = No ConnSettings = Configuration of an DSN without GUI is described on http://www.unixodbc.org/odbcinst.html, but odbc.ini and .odbc.ini may be created by the 'ODBCConfig' tool. You can easily view your DSN structure by 'DataManager'. Con- figuration with GUI is described on http://www.unixodbc.org/doc/UserManual/ To find out about your PostgreSQL protocol, run: psql -V Now create a new database if not yet existing: db.createdb driver=odbc database=grass6test Now store the table 'mytable.dbf' (here: in current directory) into PostgreSQL through ODBC: db.connect driver=odbc database=grass6test db.copy from_driver=dbf from_database=./ from_table=mytable to_driver=odbc to_database=grass6test to_table=mytable Next link map to attribute table (now the ODBC table is used, not the dbf file): v.db.connect map=mytable.shp table=mytable key=ID database=grass6test driver=odbc v.db.connect -p Finally a test: Here we should see the table columns (if the ODBC connection works): db.tables -p db.columns table=mytable Now the table name 'mytable' should appear. Doesn't work? Check with 'isql ' if the ODBC-PostgreSQL connection is really established. Note that you can also connect mySQL, Oracle etc. through ODBC to GRASS. You can also check the vector map itself concerning a current link to a table: v.db.connect -p mytable.shp which should print the database connection through ODBC to the defined RDBMS. SEE ALSO
db.connect, v.db.connect, unixODBC web site, SQL support in GRASS GIS Last changed: $Date: 2011-02-07 18:59:50 +0100 (Mon, 07 Feb 2011) $ Help Index GRASS 6.4.2 grass-odbc(1grass)
All times are GMT -4. The time now is 12:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy