• Topic
  • Discussion
  • UdaWikiWeb.InstallOracleExpressOSX(Last) -- Owiki? , 2016-08-19 15:00:24 Edit owiki 2016-08-19 10:00:24

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


    Review Preinstallation Documentation: Pre-Installation Requirements

    Installation

    Note: The software must be installed as a user with Administrative privileges on the machine.
    1. The Single-Tier "Express" Edition ODBC Driver for Oracle Data Sources is distributed as a Disk Image (.dmg) file:
    2. Double-click the disk image 'mul6eora.dmg' to access the installer .mpkg file:





    3. Double-click the .mpkg file to run the installer and follow the instructions to complete the installation:





    4. This is the Welcome dialog for the OpenLink ODBC Driver for Oracle (Express Edition):





    5. Review the ReadMe file for installation requirements and known issues:





    6. Read the software license agreement:





    7. Agree to the software license agreement before continuing your installation:





    8. Select a destination volume for the driver installation:





    9. Choose to perform a custom or default installation of the driver:





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





    11. After the driver has been installed, you will be prompted for a license file --





      NOTE -- If a correctly named file already exists in $OPL_LICENSE_DIR, /Library/Application Support/openlink/bin/, you will not see this dialog. If the existing file is not valid (evaluation has expired, it's for a different OS, it permits insufficient processor cores, etc.), you will need to manually apply a valid license file after installation is completed.


      NOTE -- In some environments, this dialog may be hidden by the Installer.app or other windows on your Mac. Please minimize, hide, and/or move windows until you can see and act on this dialog. If you do not answer this dialog, the installation will not complete properly, and the driver will not function as desired.


      • If a license file already exists on the machine, select the 'use existing' option. (Previously generated license files may be re-downloaded from your ODS-Briefcase data space.)
      • If you need to obtain a new trial or permanent license file, select the 'try or buy' option, which will load a relevant web page:





        • If you've already tested the driver and verified that it works for you, you can click on the 'Shop' link to purchase a full license.
        • If you haven't tested the driver yet, please register and/or log in to the OpenLink Web site, and click on the 'download license' button to generate and download a new trial license file.





    12. Select the license file that you want to use for the installation:





    13. The installation is complete:




    Configuration

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





    2. Click the Add button:





    3. Select the OpenLink Oracle Driver (Express Edition) v6.0 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. Provide a suitable DSN name and optional description for the Data Source:





    5. The Connection tab takes the minimum parameters required to make a connection to the target database:





      • Host: This is the fully qualified hostname or IP address of the machine hosting the DBMS you wish to access, e.g., dbms-server.example.com, or 192.168.155.123. Any hostname which can be resolved by your local DNS is acceptable.
      • Port: The port on which the Oracle instance listens.
      • SID (Service Name): The Oracle System Identifier that refers to the instance of the Oracle database running on the server.
      • User Name: A valid Oracle user.
      • The advanced button displays additional, optional parameters that can be configured.
        Name Description
        NetworkProtocol Sets the network protocol for connections. Default is 'tcp'. Can be set to all possible protocols Net8 supports. Only needed for JDBC OCI driver.
        MaxStatements Specifies the value of the maxStatements property. This will be the size of the application cache which will be used by both implicit and explicit caching.
        ImplicitCachingEnabled Sets the value of the implicitCachingEnabled property, which enables or disables the implicit cache. Note that this is independent of the cache size set with setMaxStatements().
        ExplicitCachingEnabled Sets the value of the explicitCachingEnabled property, which enables or disables the explicit cache. Note that this is independent of the cache size, set with setMaxStatments().

    6. Click continue to proceed to the Options tab. This tab contains optional parameters that are not required for basic ODBC connectivity:





      • 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.
      • Drop Catalog from Meta calls - Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.
      • No support of quoted identifier - If set, the call SQLGetInfo for 'SQL_IDENTIFIER_QUOTE_CHAR' will return a space (" "). It can be used if the DBMS doesn't support quoted SQL like select * from "account."
      • Drop Schema from Meta calls - Enable this option to have the schema-name not appear for tables, views, and procedures when requesting database meta-data.
      • SQLStatistics disabled - Check this box to have SQLStatistics() return an empty resultset. Use this if the underlying database does not support retrieval of statistics about a table (e.g. what indexes it has).
      • No support of search string escape - If set, the call SQLGetInfo for 'SQL_LIKE_ESCAPE_CLAUSE' will return a space (" "). It can be used if the DBMS doesn't support SQL escape patterns.
      • Patch of NULL size of SQL_CHAR - If set, this option overrides the size of SQL_CHAR column type returned by the database with the value set in the text box (in bytes). With a default value of 0, the driver uses the size returned by the 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".
    7. Click continue to proceed to the Preferences tab. This tab contains optional parameters that are not required for basic ODBC connectivity:





      • 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 Autocommit - Changes the default commit behaviour of the OpenLink driver. The default mode is AutoCommit (box unchecked).
      • Disable Rowset Size Limit - Disables a limitation enforced by the cursor library. This limitation is enforced by default. It prevents the driver from claiming all available memory in the event that a resultset generated from an erroneous query is very large. The limit is normally never reached.
      • 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.
      • 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.
      • Always include VIEWS in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see VIEWs in the graphical query builder. This option is redundant when Always include alltypes is ticked.
      • Always include alltypes in table list - This switch is needed for Microsoft Excel and Query, Stata, and some other tools which explicitly request only TABLEs from the back-end DBMS. Tick this box if you also need to see SYSTEM TABLEs, VIEWs, SYSTEM VIEWs, SYNONYMs, GLOBAL TEMPORARYs, ALIASes, and/or LOCAL TEMPORARYs in the graphical query builder. Note: the TABLE list will be much longer than when this box is not ticked, and SYSTEM objects will be sorted to the top of the list, due to typical naming conventions.
    8. Click on the 'Test Data Source' button to make a connection to the database to verify connectivity:





    9. Enter a valid username and password for the database:





    10. A successful connection to the database has been made:




    Next...


    Referenced by...