Hyperion(r) SQL Interface Guide | Information Map | ||
Show | Previous | Next |
Hyperion(r) SQL Interface Guide | Information Map | ||
Hide | Previous | Next |
Hyperion(r) SQL Interface Guide | Information Map |
Show | Previous | Next |
Hyperion(r) SQL Interface Guide | Information Map |
Hide | Previous | Next |
You can use ODBC database drivers with Essbase other than the MERANT drivers provided with SQL Interface. For example, you can use a Microsoft ODBC driver to connect to Microsoft Access, or use an IBM ODBC driver to connect to IBM DB2/6000. Some non-MERANT ODBC drivers are tested with Essbase. For more information on tested and supported drivers and data sources, see the Essbase Installation Guide or the readme.txt file.
To use a non-MERANT driver, you need to:
This chapter contains the following topics that describe how to use non-MERANT ODBC drivers:
When you configure a MERANT driver, Essbase recognizes the basic configuration information for the driver, especially the name of the driver and whether the name and password are case-sensitive. However, when you use a non-MERANT driver, you must give Essbase the configuration information for the driver that you use.
You give Essbase the configuration information for your non-MERANT driver by creating a driver configuration file called esssql.cfg, which is an ASCII text file. Place this file in your ARBORPATH\BIN directory on OLAP Server. This is c:\hyperion\essbase\ if you installed Essbase in the default directory (/home/hyperion/essbase/ on UNIX platforms).
Note: If you do not create a configuration file, Essbase uses its own default values. You may not be able to connect to the SQL database using the default values.
The configuration file must contain at least some of the following configuration values for each non-MERANT ODBC driver that you use. Required values may be different for different drivers. See the online help for each driver or see the documentation for specific information.
This section contains information about what you need to include in the configuration file, and in one case, how to find it:
At a minimum, your configuration file must contain at least the DriverName for every non-MERANT ODBC driver that you use. Surround all values for each driver with brackets ( [ ] ). Leave one or more spaces between the configuration keyword and its corresponding value.
Use this template to help you create a configuration file:
[ | |
Description | |
DriverName | |
UserId | |
Password | |
Database | |
Server | |
Application | |
Dictionary | |
Files | |
SingleConnection | |
UpperCaseConnection | |
IsQEDriver | |
] |
Description of Driver is your description of the driver. Enclose the description in quotation marks (" "). The default value is " ".
DriverName is the file name of the non-MERANT ODBC driver and is required.
For all other configuration keywords, set Value to be either 1 or 0, according to is table:
The defaults apply if you do not specify the value for the driver. These defaults are different from the Essbase default values that apply if you do not create an esssql.cfg file.
Include configuration information for all the non-MERANT drivers in one configuration file. Enclose the values for each driver in brackets ( [ ] ).
Use this template to help you create a configuration file:
[ | |
Description | "Description of Driver " |
DriverName | DriverName |
... | |
] | |
[ | |
Description | "Description of Driver " |
DriverName | DriverName |
... | |
] |
To display the name of the drive, use this procedure:
The ODBC Data Source Administrator dialog box, User DSN tab appears:
Data sources that you have configured are in the User Data Sources list box. Drivers that have not been properly configured may also be in the User Data Sources list box. Ignore them.
For more information on the ODBC Administrator, see Configuring an MS Access Data Source on Windows.
On UNIX, the driver's name is in the .odbc.ini file. For more information on the .odbc.ini file, see Configuring a Data Source on UNIX.
The driver name for the Microsoft Access driver on Windows is ODBCJT32.DLL. This driver requires a database name, server name, application name, and dictionary (directory path). This driver is not a MERANT driver, so you must create a type its configuration file, esssql.cfg in ASCII-text format.
Use this example as a template:
[ | |
Description | |
DriverName | |
Database | |
Server | |
Database | |
Application | |
Dictionary | |
IsQEDriver | |
] |
Note: See Configuring an MS Access Data Source on Windows.
The driver name for the IBM DB2/6000 driver on AIX is DB2.0. This driver requires a user ID, password, and database name, but not a server name. This driver is thread-safe and case-sensitive. It is not a MERANT driver, so you must create a configuration file, esssql.cfg, in ASCII-text format.
Use this example as a template:
[ | |
Description | |
DriverName | |
UserId | |
Password | |
Database | |
SingleConnection | |
UpperCaseConnection | |
IsQEDriver | |
] |
Note: See Configuring an IBM DB2 Data Source on AIX.
Configure a non-MERANT data source in the same way that you configure a MERANT data source. See Configuring a Data Source for more information. The following sections tell you how to configure a Microsoft Access data source on Windows NT and an IBM DB2/6000 data source on AIX:
Note: Before you configure a non-MERANT data source, you must first configure the driver by creating an esssql.cfg configuration file. See Creating a Configuration File for Non-MERANT Drivers.
The following example describes how to configure a Microsoft Access data source on OLAP Server on Windows. Your data source and driver may differ, but the steps that you take to configure the data source are essentially the same. The example assumes:
On Windows, use the ODBC Administrator, ODBCAD32.EXE, to configure a non-MERANT data source, just as you use it to configure a MERANT data source.
This example uses the ORDERS.MDB file, which is installed with Microsoft Access, but you can use any .MDB file to test the data source configuration.
The Microsoft Access ODBC 32-bit database driver is also installed with Microsoft Access, but it can be installed in other ways. For Microsoft Access, you need to specify the data source name and database. You can also provide a description. Other ODBC drivers may require additional information. See the documentation for each driver, and online help, for what is required.
To configure the Microsoft Access data source:
The User DSN tab of the ODBC Data Source Administrator dialog box is displayed:
Data sources that you have previously configured are displayed in the User Data Sources list box. Drivers that have not been properly configured may also be in the User Data Sources list box. Ignore or remove them.
The Microsoft Access data source is in the User Data Sources list box, with other data sources that may or may not have been configured.
You can now load data from the Microsoft Access data source file that you chose into a Essbase database. For information on loading SQL data, see Loading SQL Data. For general information on loading data, see the Essbase Database Administrator's Guide.
Note: Remember that source files must be accessible to OLAP Server. They can be on the OLAP Server machine or on the network.
If you use AIX, you can connect to an IBM DB2/6000 data source using the IBM DB2/6000 ODBC driver. Consult the database administrator for information on configuration, authorization, binding, and other steps that may be required to connect to the data source.
Note: See Example: Creating a Configuration File for the IBM DB2 Driver on AIX.
Some non-MERANT drivers are not tested or supported for use with Essbase. The driver that you choose might not be specifically tested to work with Essbase. For information on qualified drivers and data sources, see the Essbase Installation Guide.
![]() Copyright © 2002 Hyperion Solutions Corporation. All rights reserved. http://www.hyperion.com |