Not logged in : Login
(Sponging disallowed)

About: Configuration of the Multi-Tier "Enterprise" Edition Generic Client ODBC Drivers, on Linux or Unix-like OS (DB2)     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:HowTo, within Data Space : data.openlinksw.com associated with source document(s)
QRcode icon
http://data.openlinksw.com/describe/?url=http%3A%2F%2Fdata.openlinksw.com%2Foplweb%2Fuda%2Fhowto%2FGenericLinuxMulti-TierDB2GenericODBCClientConfigurationGuide%23this

Configuration of the Multi-Tier "Enterprise" Edition Generic Client ODBC Drivers, on Linux or Unix-like OS (DB2)

AttributesValues
description
  • Configuration of the Multi-Tier "Enterprise" Edition Generic Client ODBC Drivers, on Linux or Unix-like OS (DB2)
described by
title
  • Configuration of the Multi-Tier "Enterprise" Edition Generic Client ODBC Drivers, on Linux or Unix-like OS (DB2)
hasDatabaseFamily
hasOperatingSystemFamily
category
  • Configuration Guide
relatedLink
text
    1. Open the file $OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi.
    2. Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
    3. [OpenLink]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = localhost:5000
      ServerType      = Oracle 8.1.x
      Database        = 
      Options         = 
      Username        = 
      Password        = 
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DSN
        
    4. Example DB2 Data Source:
    5. [db2]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = requestbroker_hostname:5000
      ServerType      = DB2
      Database        = test
      Options         = 
      Username        = db2inst1
      Password        = db2inst1
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DB2 Connection
        
    6. Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
    7. Use the iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
    8. # cd OPENLINK_INSTALL
      # . ./openlink.sh
      # iodbctest db2
      iODBC Demonstration program
      This program shows an interactive SQL processor
      Driver Manager: 03.52.0507.0105
      Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
      SQL>You should now be able to issue SQL statements directly against the target database.
      
    9. Additional Information:
    10. The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.

      That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.

    1. Open the file $OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi.
    2. Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
    3. [OpenLink]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = localhost:5000
      ServerType      = Oracle 8.1.x
      Database        = 
      Options         = 
      Username        = 
      Password        = 
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DSN
        
    4. Example DB2 Data Source:
    5. [db2]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = requestbroker_hostname:5000
      ServerType      = DB2
      Database        = test
      Options         = 
      Username        = db2inst1
      Password        = db2inst1
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DB2 Connection
        
    6. Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
    7. Use the iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
    8. # cd OPENLINK_INSTALL
      # . ./openlink.sh
      # iodbctest db2
      iODBC Demonstration program
      This program shows an interactive SQL processor
      Driver Manager: 03.52.0507.0105
      Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
      SQL>You should now be able to issue SQL statements directly against the target database.
      
    9. Additional Information:
    10. The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.

      That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.

    1. Open the file $OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi.
    2. Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
    3. [OpenLink]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = localhost:5000
      ServerType      = Oracle 8.1.x
      Database        = 
      Options         = 
      Username        = 
      Password        = 
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DSN
        
    4. Example DB2 Data Source:
    5. [db2]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = requestbroker_hostname:5000
      ServerType      = DB2
      Database        = test
      Options         = 
      Username        = db2inst1
      Password        = db2inst1
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DB2 Connection
        
    6. Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
    7. Use the iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
    8. # cd OPENLINK_INSTALL
      # . ./openlink.sh
      # iodbctest db2
      iODBC Demonstration program
      This program shows an interactive SQL processor
      Driver Manager: 03.52.0507.0105
      Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
      SQL>You should now be able to issue SQL statements directly against the target database.
      
    9. Additional Information:
    10. The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.

      That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.

    1. Open the file $OPENLINK_INSTALL/bin/odbc.ini with a suitable text editor such as vi.
    2. Locate and edit the [OpenLink] section, which is a sample OpenLink Generic ODBC data source (DSN) created during the installation process—Sample DSN as created by installer:
    3. [OpenLink]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = localhost:5000
      ServerType      = Oracle 8.1.x
      Database        = 
      Options         = 
      Username        = 
      Password        = 
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DSN
        
    4. Example DB2 Data Source:
    5. [db2]
      Driver          = /OPENLINK_INSTALL/lib/oplodbc.so
      Host            = requestbroker_hostname:5000
      ServerType      = DB2
      Database        = test
      Options         = 
      Username        = db2inst1
      Password        = db2inst1
      FetchBufferSize = 99
      ReadOnly        = no
      DeferLongFetch  = no
      JetFix          = no
      Description     = Sample DB2 Connection
        
    6. Presuming the OpenLink Request Broker is already running on the target machine, you are now ready to test the connection.
    7. Use the iodbctest tool, which is packaged with the HTTP-based OpenLink ODBC Administrator, as follows:
    8. # cd OPENLINK_INSTALL
      # . ./openlink.sh
      # iodbctest db2
      iODBC Demonstration program
      This program shows an interactive SQL processor
      Driver Manager: 03.52.0507.0105
      Driver: 06.02.1217 OpenLink Generic ODBC Driver (oplodbc.so)
      SQL>You should now be able to issue SQL statements directly against the target database.
      
    9. Additional Information:
    10. The bitness of the Generic ODBC Driver is determined by the bitness of your ODBC client application.

      That is, if your ODBC client application is 32-bit, then the Generic ODBC Driver component MUST also be 32-bit.

type
schema:step
is topic of
Faceted Search & Find service v1.17_git122 as of Jan 03 2023


Alternative Linked Data Documents: iSPARQL | ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3330 as of Apr 5 2024, on Linux (x86_64-generic-linux-glibc25), Single-Server Edition (30 GB total memory, 26 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software