Datastage Environment Configuration For Netezza & Oracle

DATASTAGE ENVIRONMENT CONFIGURATION FOR NETEZZA AND ORACLE

Document Prepared By: RAYALA PRAPHULLA

Datastage Environment Configuration For Netezza & Oracle

1. Purpose Of The Document

This document describes the required steps to configure Netezza with Datastage. Netezza configuration is very important part of Datastage configuration and generally takes lot of time because unavailability of proper information. This document can be used to accelerate that whole process. In addition to Netezza configuration this document also comprises of information about other integral part of Datastage Environment Configuration like

After Successful Datastage installation setup, we need to configure the following. Configure ODBC Driver Configure Netezza Enterprise Stage Configure Oracle Stages Configure Orchadmin command

2. Configuring ODBC Driver

To Configure ODBC driver following three files to be modified .odbc.ini uvodbc.config Dsenv

All these 3 files are there in $DSHOME folder. These files to be updated as per the info provided below :

.odbc.ini File
The .odbc.ini files gives information about connecting to the database (wire protocol drivers) or the database client (non-wire protocol drivers). If your system uses a mix of drivers, your .odbc.ini file will contain a mix of entry types. EDIT .odbc.ini file from $DSHOME/.odbc.ini If you are using ODBC Stage to Read/Write to the Oracle Database. You must Fill the required fields .

[Oracle Wire Protocol]

Driver=/IIS_Apps/Server/branded_odbc/lib/VMora24.so Description=DataDirect Oracle Wire Protocol driver

Datastage Environment Configuration For Netezza & Oracle

ApplicationUsingThreads=1 ArraySize=60000 CachedCursorLimit=32 CachedDescLimit=0 CatalogIncludesSynonyms=1 CatalogOptions=0 DefaultLongDataBuffLen=1024 DescribeAtPrepare=0 EnableDescribeParam=0 EnableNcharSupport=0 EnableScrollableCursors=1 EnableStaticCursorsForLongData=0 EnableTimestampWithTimeZone=0 HostName=172.19.4.120 /* i.e Host IP of Oracle Server */ LocalTimeZoneOffset= LockTimeOut=-1 LogonID=readonly /* i.e User name to connect to Oracle Server */ Password=******** /* i.e Password to connect to Oracle Server */ PortNumber=1521 ProcedureRetResults=0 SID=CLIECONP UseCurrentSchema=1

If you are using ODBC Stage to Read/Write to the NETEZZA Database. You must Fill the required fields and add to the .odbc.ini. [NZSQL]
Driver Description Servername Port Database Username Password ReadOnly ShowSystemTables LegacySQLTables LoginTimeout QueryTimeout DateFormat NumericAsChar SQLBitOneZero StripCRLF = /usr/local/nz/lib64/libnzodbc.so = NetezzaSAL ODBC = 172.19.6.78 /* Host IP for Netezza Server */ = 5480 = DWH = admin /* i.e User name to connect to Oracle Server */ = ******* /* i.e User name to connect to Oracle Server */ = false = false = false =0 =0 =1 = false = false = false

You can Refer the sample odbc file under:

Datastage Environment Configuration For Netezza & Oracle

/IIS_Apps/Server/branded_odbc/

uvodbc.config File
Use the uvodbc.config file to specify the DSNs for the databases that you are connecting to through ODBC. If you are using ODBC Table Definitions method for importing metadata from databases.You need to add a DSN entry in the uvodbc.config file

/IIS_Apps/Server/DSEngine/uvodbc.config Below is the sample uvodbc.config file

[ODBC DATA SOURCES]

<localuv> DBMSTYPE = UNIVERSE network = TCP/IP service = uvserver host = 127.0.0.1 <NZSQL> DBMSTYPE = ODBC <Oracle Wire Protocol> DBMSTYPE = ODBC

A copy of the uvodbc.config file is also placed in each WebSphere DataStage project directory. For example, the default path for projects on Linux is /opt/IBM/WDIS/Server/Projects/. This is useful where you configure a data source that is known to some projects but not others. By default, WebSphere DataStage searches the current project directory for a uvodbc.config file and, if it finds one, uses this in preference to the file in $DSHOME. If you alter uvodbc.config after creating projects you should copy the edited file to the project directories.

Note:
Netezza dont have any inbuilt Import plugin for importing metadata. All the NZ metadata import operations can be done only through ODBC Table Definitions method.

dsenv file

Datastage Environment Configuration For Netezza & Oracle

The WebSphere DataStage server has a centralized file for storing environment variables called dsenv in $DSHOME. $DSHOME identifies theWebSphere DataStage installation directory. The default directory is /opt/IBM/InformationServer/Server/DSEngine. Make sure that the following paths are added to dsenv file. ODBCINI=/IIS_Apps/Server/DSEngine/.odbc.ini export ODBCINI NZ_ODBC_INI_PATH=/opt/odbc64v51 export NZ_ODBC_INI_PATH NETEZZA=/usr/local/nz export NETEZZA export NZ_HOST=172.19.6.89 /* Host IP of Netezza Server */ ORACLE_HOME=/oraclient/app/oracle/product/11.2.0/client_1 export ORACLE_HOME SQLPATH=$ORACLE_HOME/bin; export SQLPATH ORACLE_SID=CLIECONP; export ORACLE_SID export TNS_ADMIN=/oraclient/app/oracle/product/11.2.0/client_1/network/admin PATH=$ORACLE_HOME/bin:$PATH;export PATH LIBPATH=$LIBPATH:$ORACLE_HOME/lib; export LIBPATH You might need to add new environment variables as you configure WebSphere DataStage to connect to different databases using plug-ins or ODBC drivers. Any environment variables you need for interactive use of ODBC drivers to make a connection to an ODBC data source must be added to the dsenv file. This lets the WebSphere DataStage server inherit the proper environment for ODBC connections. For a connection using a wire protocol driver, there are no changes required to dsenv. For a connection using a non-wire protocol driver, you generally need to specify the following information in the dsenv file:

environment variables required by the database client software database home location database library directory the PATH environment variable

Note: Stop and restart the WebSphere DataStage server whenever you edit dsenv.

Datastage Environment Configuration For Netezza & Oracle

3. Configuring ODBC Table Definitions Import

To Configure ODBC Table definitions Import, follow the steps suggested under uvodbc.config section to add the corresponding DSN entries.

4. Configuring Netezza Enterprise Stage

Netezza Enterprise Stage uses NZ ODBC driver to perform its operations. To configure NZ enterprise Stage, you need to configure the odbc.ini file present under /opt/odbc64v51/odbc.ini path and add all the NZ paths suggested under dsenv file section above Below is the sample odbc.ini file

[ODBC Data Sources]

NZSQL = NetezzaSQL [NZSQL] Driver Description Servername Port Database Username Password ReadOnly ShowSystemTables LegacySQLTables LoginTimeout QueryTimeout DateFormat NumericAsChar SQLBitOneZero

= /usr/local/nz/lib64/libnzodbc.so = NetezzaSQL ODBC = 172.19.6.78 = 5480 = DWH = datastage_user = datastage123 = false = false = false =0 =0 =1 = false = false

5. Configuring Oracle Enterprise Stage

To configure Oracle Connector and Oracle Enterprise stages, you need to add the corresponding paths listed in dsenv file section The Path to tnsnames.ora file is under /oraclient/app/oracle/product/11.2.0/client_1/network/admin Update the tnsnames.ora file with the correct TNS entries

Datastage Environment Configuration For Netezza & Oracle

Below is the sample TNS entries

DWHV890.WORLD = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = V8901P-VIP)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = V8901P-VIP)(PORT = 1525)) ) (CONNECT_DATA = (SERVICE_NAME = DWHIUSA) (SERVER = DEDICATED) ) ) SAEO.CLIECONP = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.19.4.120)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = 172.19.4.120)(PORT = 1525)) ) (CONNECT_DATA = (SERVICE_NAME = CLIECONP) (SERVER = DEDICATED) ) ) REPORTS.BSCS = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.19.4.157)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = 172.19.4.157)(PORT = 1525)) ) (CONNECT_DATA = (SERVICE_NAME = REPORT) (SERVER = DEDICATED) ) )

6. Configuring Orchadmin command To configure orchadmin command you need to export the below paths: You can configure them either in dsenv or .profile files

Datastage Environment Configuration For Netezza & Oracle

export PATH=$APT_ORCHHOME/bin:$PATH export APT_CONFIG_FILE=/IIS_Apps/Server/Configurations/default.apt