Configuring data source names on UNIX systems

Neither the ODBC Administrator or the odbcconfig utility is available on UNIX systems. On UNIX, you must edit the odbc.ini file to set environment variables, to configure, add, or change data source names, and to add or change drivers.

If you are using Oracle OCI direct connection, you do not need to configure data source names on UNIX. You connect Integration Services to both an OLAP Metadata Catalog database and a Data Source database when you access them in Integration Services Console. This process is described in Connecting to Integration Server and Connecting to data sources.

Configuring environment variables

On UNIX systems, you must set environment variables to enable access to ODBC core components. See Configuring the environment on UNIX for information about using shell scripts created by the installation program to set the required variables.

Oracle OCI: If you are using Oracle OCI drivers, you must set environment variables for the database client software as described in Updating the environment for the database client.

Teradata: If you are using Teradata drivers, you must set environment variables to point to the location of the installed drivers as specified in Updating the environment for the database client.

Note:
Use the env command to verify environment settings.

Editing the odbc.ini file

You configure data source names for a Data Source database or OLAP Metadata Catalog database in an odbc.ini file. In one section of the file, add a name and description for the ODBC data source. In a separate, newly created section of the file, provide the ODBC driver path, file name, and all other required driver settings.

The installation program installs a sample odbc.ini file in the HYPERION_HOME/common/ODBC/Merant/4.2 directory. The file contains generic ODBC connection and configuration information for supported ODBC drivers. Use the file as a starting point to map the ODBC drivers that you use to the Data Source database and OLAP Metadata Catalog database.

DB2 Universal Database: For each server computer to which you are connecting using the DataDirect Wire Protocol driver, you must create a bind package. DataDirect supplies a program that creates the bind package for you. See Creating DB2 bind packages for DataDirect Wire Protocol driver connections for instructions on using the program supplied by DataDirect.

Teradata: When configuring a data source name, the data source description must be set to tdata.sl (HP-UX) or tdata.so (AIX and Solaris). Specific examples for AIX, HP-UX, and Solaris operating systems are shown in Examples of ODBC settings for Teradata

Note:
If you use a file other than the odbc.ini file (located by default in $HYPERION_HOME/common/ODBC/Merant/4.2), be sure to set the ODBCINI environment variable to the name of the file that you use.

To add an ODBC data source to an odbc.ini file:

  1. On the computer running Integration Server, open the odbc.ini file by using a text editor such as vi.
  2. Locate the section starting with [ODBC Data Sources] and add a new line with the data source name and description; for example:
    mydata=data source for analysis

    To minimize confusion, the data source name can match the name of the database in the RDBMS.

  3. Add a new section to the file by creating a new line with the new data source name enclosed in brackets; for example:
    [mydata]
  4. On the lines following the data source name, add the full path and file name for the ODBC driver required for this data source and any other required ODBC driver information.

    Use the examples shown in the following sections as guidelines for specific RDBMSs.

    Note:
    Make sure that the ODBC driver file actually exists in the location that you specify for the Driver= setting.
  5. When you finish editing odbc.ini, save the file and exit the text editor.

For information about the odbc.ini file and the ODBC driver settings for each RDBMS, see the DataDirect Connect for ODBC Reference in PDF format and the Readme files in the $HYPERION_HOME/common/ODBC/Merant/4.2/docs directory. This manual is also installed with the DB2 OLAP Server documentation. For information about vendor-supplied ODBC driver settings, refer to the installation documentation for the vendor-supplied ODBC drivers.

Examples of ODBC settings for DB2 Universal Database

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, such as db2data on DB2 UDB Version 7.1 (on AIX), using a DataDirect Wire Protocol driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

Use the vi $ODBCINI command to edit the odbc.ini file and insert the following statements:

[ODBC Data Sources]
db2data=DB2 Source Data on AIX
...
[db2data]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARdb218.so
IpAddress=isaix7
Database=tbd7a7n
TcpPort=50000
Package=PACK4A
Action=REPLACE
QueryBlockSize=8
CharSubTypeType=SYSTEM_DEFAULT
ConversationType=SINGLE_BYTE
CloseConversation=DEALLOC
UserBufferSize=32
MaximumClients=35
GrantExecute=1
GrantAuthid=PUBLIC
OEMANSI=1
DecimalDelimiter=PERIOD
DecimalPrecision=15
StringDelimiter=SINGLE_QUOTE
IsolationLevel=CURSOR_STABILITY
ResourceRelease=DEALLOCATION
DynamicSections=32
Trace=0
WithHold=0

Example of ODBC settings for DB2 UDB for z/OS and OS/390

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, such as os390 on DB2 UDB for z/OS and OS/390 Version 7, using a DataDirect Wire Protocol driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

Use the vi $ODBCINI command to edit the odbc.ini file and insert the following statements:

[ODBC Data Sources]
os390= Source data on DB2 UDB for z/OS and OS/390
...
[os390]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARdb219.so
Collection=DATADIRECT00
Database=
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=isaix21
IsolationLevel=CURSOR_STABILITY
Location=DALLAS
Package=PACK42
PackageOwner=
TcpPort=446
WithHold=1
Note:
To use DB2 OLAP Integration Server with DB2 UDB for z/OS and OS/390, you must add an entry to the eis.cfg file after you configure the data source name for the source database. See Adding a configuration file entry for DB2 UDB for z/OS and OS/390 for more information.

Example of ODBC settings for Informix

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, such as ifxdata on Informix Version 9.3 (on HP-UX), using a DataDirect Version 4.2 ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

[ODBC Data Sources]
ifxdata=Informix 9.3 Source Data on HP-UX
...
[ifxdata]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARifcl18.so
Description=Informix9.3 ODBC Driver
Database=ifxdata
HostName=ishp4
PortNumber=1526
ServerName=informixhost

Example of ODBC settings for Oracle

If an installation uses Oracle onames instead of tnsnames, use the Oracle OCI interface instead of ODBC and connect directly to relational data sources when they are accessed in Integration Services Console.

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, oradata, on Oracle 9i (on Solaris), using a DataDirect Version 4.2 ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

[ODBC Data Sources]
oradata=Oracle9i Source Data on Solaris
...
[oradata]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARora18.so
Description=my oracle source
HostName=oraclehost
SID=tbc1
PortNumber=1521
Note:
Run ivtestlib to verify that the environment is set to run the correct ODBC driver file. For example, run ivtestlib and paste the path and file name that follow Driver= in the odbc.ini file that you edited.

Example of ODBC settings for SQL Server

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, such as sqldata, on SQL Server 2000 (on HP-UX), using a vendor-supplied ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

[ODBC Data Sources]
sqldata=SQL Server 2000 Source Data on HP-UX
...
[sqldata]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARmsss18.so
Description=SQL Server 2000 Driver
Database=sqldata
Address=isqa17,1433
QuotedId=No
AnsiNPW=No

Example of ODBC settings for Sybase

The following example illustrates how you might edit odbc.ini to connect to a Data Source database, such as sybdata, on Sybase Version 12 (on HP-UX), using a DataDirect Version 4.2 ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database.

sybdata=Sybase 12.0 Source Data on HP-UX
...
[sybdata]
Driver=
%HYPERION_HOME%/common/ODBC/Merant/4.2/lib/ARase18.so
Description=Sybase 12.0 ODBC Driver
Database=sybdata
NetworkAddress=issol5,4200

Examples of ODBC settings for Teradata

AIX: The following example illustrates how you might edit odbc.ini to connect to a Data Source database, tbc, on Teradata (on AIX), using the Teradata ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database. The data source description in [ODBC Data Sources] must be set to tdata.so.

[ODBC Data Sources]
tbc=tdata.so
...
[tbc]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R4
DBCName=139.64.140.45
DefaultDatabase=tbc
UseXViews=Yes

HP-UX: The following example illustrates how you might edit odbc.ini to connect to the same Data Source database, tbc, on Teradata (on HP-UX), using the Teradata ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database. The data source description in [ODBC Data Sources] must be set to tdata.sl.

[ODBC Data Sources]
tbc=tdata.sl
...
[tbc]
Driver=/usr/odbc/drivers/tdata.sl
Description=NCR 3600 running Teradata V2R4
DBCName=139.64.140.45
DefaultDatabase=tbc
UseXViews=Yes

Solaris: The following example illustrates how you might edit odbc.ini to connect to the same Data Source database, tbc, on Teradata (on Solaris), using the Teradata ODBC driver. You can make a separate entry to connect to the OLAP Metadata Catalog database. The data source description in [ODBC Data Sources] must be set to tdata.so.

[ODBC Data Sources]
tbc=tdata.so
...
[tbc]
Driver=/usr/odbc/drivers/tdata.so
Description=NCR 3600 running Teradata V2R4
DBCName=139.64.140.45
DefaultDatabase=tbc
UseXViews=Yes

Creating DB2 bind packages for DataDirect Wire Protocol driver connections

In the UNIX environment, you must create a bind package for each connection between DB2 OLAP Integration Server and a DB2 UDB database that you make using the MERANT Wire Protocol driver. Without a bind package for each connection, the Wire Protocol driver will not work properly. MERANT supplies a command line program to create the bind packages.

To create a bind package for a connection using the MERANT Wire Protocol Driver for DB2 UDB:

  1. On the computer running Integration Server, open a command shell window.
  2. In the command shell window type:

    bind19 dsn

    Replace dsn with the data source name for which you are creating this bind package. For example, to create a bind package for the data source name TBC, type:

    bind19 TBC
    Note:
    You are prompted for a user name and password if this information is not stored in the system information file.

    If successful, a message is displayed stating that the package was created and bound.

    For troubleshooting information, access the DataDirect Web site at http://www.datadirect-technologies.com and select the Product Documentation link.

  3. Repeat step 2 for all bind packages you want to create.
  4. When all bind packages are created, close the command shell window.

Adding a configuration file entry for DB2 UDB for z/OS and OS/390

If you are using IBM DB2 UDB for z/OS and OS/390, you must add an entry to the eis.cfg file to support DB2 OLAP Integration Server functionality. You must add entries for each data source name for DB2 UDB for z/OS and OS/390 that you configured in Configuring DataDirect Wire Protocol drivers.

Note:
For DB2 UDB for z/OS and OS/390, you configure data source name for the Data Source database only. You cannot configure a data source name for the OLAP Metadata Catalog database. OLAP Metadata Catalog functionality is not supported in DB2 UDB for z/OS and OS/390.

To add an entry for DB2 UDB for z/OS and OS/390 to the eis.cfg file:

  1. On the computer running the server component of DB2 OLAP Integration Server, use a text editor to open eis.cfg.
  2. Add a new line for DB2 UDB for z/OS and OS/390 using the data source name or names you configured in Configuring DataDirect Wire Protocol drivers.

    Add separate lines for each data source name configured for DB2 UDB for z/OS and OS/390. The syntax is:

    [DS:dsn:390]

    For example, using the sample application database, TBC, the following is the entry to the eis.cfg file:

    [DS:TBC:390]
  3. Save and close eis.cfg.