Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

odbcinst(1) [centos man page]

odbcinst(1)						       unixODBC manual pages						       odbcinst(1)

odbcinst - An unixODBC tool for manipulating configuration files SYNOPSIS
odbcinst is a command line tool which has been created for allowing people who are developing the install scripts/RPMs for Drivers to be able to easily create/remove entries in odbc.ini and odbcinst.ini. This command line tool is a complement to the shared library of the same name ( This tool is a part of the odbcinst component of unixODBC. OPTIONS
ACTIONS -i Install (add section to config file) new OBJECT. -u Uninstall (remove section from config file) existing OBJECT. -q Query the config files and print the options for specified OBJECT. -j Prints current configuration of unixODBC, listing (among others) the paths to the configuration files. -c Calls SQLCreateDataSource -m Calls SQLManageDataSources --version Prints program version and exits. OBJECTS -d The ACTION affect drivers (and thus the odbcinst.ini configuration file). -s The ACTION affect data sources (and thus the user or system odbc.ini configuration file). OPTIONS -f FILE The FILE is template file, describing the configuration of installed OBJECT (only valid for the -i ACTION). -r Same as the -f OPTION, only take the standard input as the template file. -n NAME Specifies the NAME of the OBJECT. -v Turn off verbose mode. This turns off all information, warning and error messages. -l The specified data source is system-wide. Has any effect only with the -s OBJECT. -h The specified data source is user-specific. Has any effect only with the -s OBJECT. RETURN VALUES
This command returns zero on success and non-zero value on failure. FILES
/etc/odbinst.ini Configuration file containing all the database drivers specifications. See odbcinst.ini(5) for more details. /etc/odbc.ini System-wide data sources specifications. See odbc.ini(5) for more details. $HOME/.odbc.ini User-specific data sources specifications. See odbc.ini(5) for more details. SEE ALSO
odbcinst.ini(5), odbc.ini(5) AUTHORS
The authors of unixODBC are Peter Harvey <> and Nick Gorham <>. For the full list of contributors see the AUTHORS file. COPYRIGHT
unixODBC is licensed under the GNU Lesser General Public License. For details about the license, see the COPYING file. version 2.3.1 Wed 26 Jun 2013 odbcinst(1)

Check Out this Related Man Page

grass-odbc(1grass)						Grass User's Manual						grass-odbc(1grass)

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/ Setup = /usr/lib/ 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, 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 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)
Man Page

Featured Tech Videos