The following example illustrates how you might edit odbc.ini to connect to a Data Source database that consists of one or more flat files. The example also includes descriptions for each line item in parentheses. You can make a separate entry to connect to the OLAP Metadata Catalog database, which must be stored in a relational database.
Also included is an example of the QETXT.INI file. The example uses shows how you would configure three tables from the TBC database: Product, Region, Market, and an abbreviated version of Sales.
Integration Services does not support data source table names and column names that contain spaces or special characters, such as a period (.). See Integration Services Limits and Guidelines for a complete listing of the unsupported characters. |
You must use a relational database as your OLAP Metadata Catalog database and configure it as described in Editing the odbc.ini File. |
[ODBC Data Sources] tbc_ff=TBC flat file data source ... [tbc_ff] Driver=/EPM_ORACLE_HOME/common/ODBC/Merant/6.0/Drivers/ARtxt24.so (location of a driver) Description=DataDirect 5.2 TextFile(*.*) AllowUpdateAndDelete=0 (a variable edited by user) ApplicationUsingThreads=1 (a variable edited by user) CacheSize=64 (a variable edited by user) CenturyBoundary=20 (a variable edited by user) Database=/EPM_ORACLE_HOME/flat_files/stream (a data file location) DataFileExtension=TXT (a variable edited by user, default is TXT) DecimalSymbol=. (a variable edited by user, default is dot(.)) Delimiter=~ (a variable edited by user) FileOpenCache=0 (a variable edited by user) FirstLineNames=1 (a variable edited by user) IntlSort=1 (a variable edited by user) ScanRows=5 (a variable edited by user) TableType=Character (a variable edited by user) UndefinedTable=GUESS (a variable edited by user) [ODBC] IANAAppCodePage=4 InstallDir=products/common/ODBC/Merant/6.0 Trace=0 TraceDll=products/common/ODBC/Merant/6.0/Drivers/odbctrac.so TraceFile=odbctrace.out UseCursorLib=0
For more information on editing the ODBC.INI file in UNIX to configure a flat file data source see the DataDirect Connect ODBC Reference in PDF format in products/common/ODBC/Merant/6.0/books/odbcref.
The following is an example of the QETXT.INI file. The example shows how you would configure three tables from the TBC database: Product, Region, Market, and an abbreviated version of Sales.
[Defined Tables] PRODUCT.txt=Product REGION.txt=REGION SALESFACTSHORT.txt=SalesFactShort MARKET.txt=Market [Product] FILE=PRODUCT.txt FLN=1 TT=Comma Charset=ANSI DS=. FIELD1=PRODUCTID,NUMERIC,9,0,9,0, FIELD2=FAMILYID,NUMERIC,8,0,8,0, FIELD3=SKU,VARCHAR,6,0,6,0, FIELD4=SKUNAME,VARCHAR,18,0,18,0, FIELD5=CAFFIENATED,VARCHAR,11,0,11,0, FIELD6=OUNCES,NUMERIC,6,0,6,0, FIELD7=PKGTYPE,VARCHAR,7,0,7,0, FIELD8=INTRODATE,DATE,10,0,10,0,yyyy/m/d [REGION] FILE=REGION.txt FLN=0 TT=Comma Charset=ANSI DS= [SalesFactShort] FILE=SALESFACTSHORT.txt FLN=1 TT=Comma Charset=ANSI DS=. FIELD1=STATEID,NUMERIC,7,0,7,0, FIELD2=PRODUCTID,NUMERIC,9,0,9,0, FIELD3=SCENARIOID,NUMERIC,10,0,10,0, FIELD4=SUPPLIERID,NUMERIC,10,0,10,0, FIELD5=TRANSDATE,DATE,10,0,10,0,yyyy/m/d FIELD6=SALES,NUMERIC,7,2,6,0, FIELD7=COGS,NUMERIC,6,2,6,0, FIELD8=MARKETING,NUMERIC,11,2,9,0, FIELD9=PAYROLL,NUMERIC,9,2,7,0, FIELD10=MISC,NUMERIC,6,2,4,0, FIELD11=OPENINGINVENTORY,NUMERIC,18,2,16,0, FIELD12=ADDITIONS,NUMERIC,11,2,9,0, [Market] FILE=MARKET.txt FLN=1 TT=Comma Charset=ANSI DS=. FIELD1=STATEID,NUMERIC,7,0,7,0, FIELD2=REGIONID,NUMERIC,8,0,8,0, FIELD3=STATE,VARCHAR,13,0,13,0, FIELD4=POPULATIONID,NUMERIC,12,0,12,0,
For more information on creating the QETXT.INI file in UNIX to configure tables for a flat file data source see the DataDirect Connect ODBC Reference in PDF format in products/common/ODBC/Merant/6.0/books/odbcref.