OpenLink Universal Data Access (UDA) Wiki
Documentation and guidance on installing, configuring and trouble-shooting UDA
Advanced Search
Help?
Location: / Dashboard / UdaWikiWeb / UdaWikiWebIndex / UDAInstallConfig / InstallConfigODBC / SingleTierLiteInstallDocs / SingleTierLiteInstallMac / InstallPostgreSQLLiteOSX

Installation and Configuration of the Single-Tier "Lite" Edition ODBC Driver for PostgreSQL Data Sources, for Mac OS X


Review Preinstallation Documentation: Pre-Installation Requirements

Installation

  1. The OpenLink ODBC Driver for PostgreSQL for Mac OS X is distributed in a single disk image (.dmg) file, which contains a Macintosh Installer mpkg.





  2. Double-click the mpkg to start the installation process.





  3. You will encounter a warning message that will ask you if you are sure that you want to install the software. Click Continue.





  4. The installer will display a Welcome message. Click "Continue."





  5. The next screen will display the Read Me file, including any last- minute updates to these documents. Please read carefully and click "Continue" when finished.





  6. The next screen will display the License Agreement for the OpenLink Single-Tier Driver for ODBC. Please read and click "Continue."





  7. You will be prompted to "Agree" to continue the installation or "Disagree" to abort.





  8. You will be asked to select a Destination Volume. Generally, this should be your Mac OS X boot volume. Click on the desired disk icon and then click "Continue."





  9. You may now choose the Easy Install, or if you are an experienced user, you may Customize which components are installed. OpenLink generally recommends the Easy Install.
  10. If you have installed OpenLink or iODBC components in the past, click "Upgrade" to continue; otherwise, click "Install."





  11. If you chose the custom option, select which of the following components to install.





  12. You must have an Administration username and password to install the OpenLink driver. Enter your Mac OS X Username and Password.





  13. You will be shown a graphical progress bar as the Installation progresses, followed by System Optimization.
  14. You will need to locate the license file. Click "Try or Buy License" to obtain evaluation or commercial licenses from the OpenLink Web site. Click "Use Existing License" to select a license on the local file system.





  15. When the process is complete, you will be told that the software was successfully installed. Click "Close" and your new database driver for ODBC is ready for use.




Configuration

  1. To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:





  2. Click the System DSN tab:





  3. Click the Add button. Then, select the OpenLink PostgreSQL Lite Driver from the list of available drivers. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.





  4. Click Finish.
  5. The Data Source tab prompts for information that identifies the PostgreSQL database server and listen port. It also requests a name for your Data Source. You may also supply an optional description for your Data Source Name.





    • DSN - A brief and meaningful title for your Data Source Name
    • Description - An optional description for your Data Source Name
    • Hostname - The hostname or IP of the server on which PostgreSQL runs
    • Port number - The TCP port on which PostgreSQL listens
  6. Click Continue.
  7. The Connection Tab takes a combination of required and optional parameters to make a connection to the target database:





    • Username - A PostgreSQL username
    • Row Buffer Size - This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
    • Hide Login Dialog - Suppresses the ODBC "Username" and "Password" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
    • Read Only connection - Specifies whether the connection is "Read-only." Make sure the checkbox is unchecked to request a "Read/Write" connection.
    • Database - A valid PostgreSQL database
    • SQL_DBMS Name - Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath for which the return the value should be "SQL Server".
  8. Click Continue.
  9. Click Continue to view additional preferences that can be set for the connection.





    • Initialization SQL - Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
    • Cursor Sensitivity - Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database.
    • Max Rows Override - Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.
    • Disable ODBC transactions - Disable ODBC transaction management. All transactions will be automatically committed. This prevents palloc() failures with out-of-memory errors when doing really big transactions such as exporting 10000 records from MS/Access.
    • Defer fetching of long data - Defers fetching of LONG (BINARY, BLOB etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in query do not include LONG data fields.
    • Enable HSODBC (Oracle Heterogeneous Service) fix -
    • Disable AutoCommit - Changes the default commit behaviour of the OpenLink driver. The default mode is AutoCommit (box unchecked).
    • Multiple Active Statements Emulation - Enables use of Multiple Active statements in an ODBC application even if the underlying database does not allow this, as it is emulated in the driver.
  10. Click the Finish button to save your new Data Source Name.

Next...

Powered By Virtuoso