Thursday, December 9, 2010

DataStage Import Table Definition, ODBC Data Source

It is recommended to use Orchestrate Schema Definitions to import table definitions, which however is not available for MS SQL Server. An example to use orchdbutil GUI to import Oracle table definitions is shown below, which can only import one table at a time. Note the database server is the tnsnames entry configured.



Another way is to configure ODBC data source and use it to import table definitions. The file to configure the ODBC data source is $DSHOME/.odbc.ini:

An example for Oracle ODBC data source:
[Oracle-DSNAME]
QEWSD=2455147
Driver=/u/BASE/IBM/InformationServer/Server/branded_odbc/lib/VMora23.so
Description=DataDirect Oracle Wire Protocol driver
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=
LocalTimeZoneOffset=
LockTimeOut=-1
LogonID=
Password=
PortNumber=
ProcedureRetResults=0
SID=
UseCurrentSchema=1


An example for SQL Server ODBC data source:
[SQL-DSNAME]
Driver=/u/BASE/IBM/InformationServer/Server/branded_odbc/lib/VMmsss23.so
Description=DataDirect SQL Server Wire Protocol driver
Database=
Address=
QuotedId=No
AnsiNPW=No

And the uvodbc.config file under the project directory need to be configured by referencing the ODBC data sources:
......
[ODBC DATA SOURCES]
<ODBC_DATA_SOURCE>
DBMSTYPE = ODBC