HYPERION® ESSBASE® – SYSTEM 9 RELEASE 9.3.1
SQL INTERFACE GUIDE Essbase SQL Interface Guide, 9.3.1 Copyright © 1998, 2007, Oracle and/or its affiliates. All rights reserved. Authors: Rosemary Peters The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Contents
Chapter 1. Introducing Essbase SQL Interface ...... 5 Understanding Essbase SQL Interface ...... 5 Preparing for Using SQL or Relational Data Sources ...... 6
Chapter 2. Configuring a Data Source ...... 7 Configuring a Data Source on Windows ...... 7 Configuring a Data Source on UNIX ...... 7 Editing the odbc.ini File for Changes ...... 8 Example: Editing odbc.ini for DB2 ...... 8
Chapter 3. Preparing Multiple-Table Data Sources ...... 9 Understanding Multiple-Table Preparation ...... 9 Understanding Two Methods for Multiple-Table Data Preparation ...... 9 Choosing a Preparation Method ...... 11 Understanding Security Requirements ...... 11 Preparing Data from Multiple Tables ...... 11
Chapter 4. Loading SQL Data ...... 13 Understanding Data Loading ...... 13 Using Substitution Variables ...... 13 Understanding the Rules for Substitution Variables ...... 14 Creating and Using Substitution Variables ...... 14 Loading Relational Data Using Essbase SQL Interface ...... 14 Summary of Steps ...... 14 Creating the Data Load Rules File ...... 15 Selecting the SQL Data Source ...... 15 Creating SQL Queries (optional) ...... 15 Loading the Data ...... 16
Chapter 5. Using Non-DataDirect ODBC Drivers ...... 17 Configuring a Non-DataDirect Driver ...... 17 Creating a Configuration File for Non-DataDirect Drivers ...... 18 Including the Minimum Required Contents ...... 18
Contents iii Finding a Driver Name on Windows ...... 20 Finding a Driver Name on UNIX ...... 20 Configuring Non-DataDirect Data Sources ...... 21 Support for Non-DataDirect Drivers ...... 21
Appendix A. Enabling Faster Data Loads from Teradata Data Sources ...... 23 Installing Required Teradata Software ...... 23 Setting Up the Environment for Using Export Operator ...... 23 Loading Teradata Data Using Teradata Parallel Transporter ...... 24
Index ...... 25
iv Contents Introducing Essbase SQL 1 Interface
In This Chapter Understanding Essbase SQL Interface...... 5 Preparing for Using SQL or Relational Data Sources ...... 6
Use this chapter to learn about Essbase SQL Interface and prepare for loading data with it.
Understanding Essbase SQL Interface To enable building outline dimensions and loading values from SQL and relational database sources, Oracle's Hyperion® Essbase® – System 9 provides the Essbase SQL Interface feature. You can execute SQL statements on data before loading. For example, using SQL statements to specify the data to retrieve enables you to load summary data instead of the entire contents of the source database.
Note: You do not need Essbase SQL Interface for spreadsheet or text file data sources which you can load using Oracle's Essbase® Administration Services, MaxL, or ESSCMD. See the Hyperion Essbase - System 9 Database Administrator's Guide and the Essbase Technical Reference.
Essbase SQL Interface works with Administration Services to retrieve data, as follows: 1. Using Administration Services you write a SELECT statement in SQL . 2. Essbase SQL Interface passes it to the SQL or relational database server. For non-SQL data sources, Essbase SQL Interface converts SQL statements to requests for data that the source understands. 3. Essbase SQL Interface interprets the records received from the SQL, or relational database server using the rules defined in the data load rules file. (For more information on data load rules files, see Chapter 4, “Loading SQL Data.”) 4. Essbase SQL Interface loads the interpreted, summary-level data into the database.
Understanding Essbase SQL Interface 5 Preparing for Using SQL or Relational Data Sources Essbase SQL Interface is installed during the Essbase Server installation. See the Hyperion Essbase - System 9 Installation Guide for information about initial configuration tasks.
➤ To prepare for using SQL or relational data sources: 1 Configure the ODBC driver and point it to its data source. See Chapter 2, “Configuring a Data Source.” 2 If data is in multiple tables, prepare the data by doing either of these actions:
● Create one table or view in the SQL database before using Essbase SQL Interface.
● Join the tables during the data load by entering a SELECT statement in Administration Services. See “Understanding Multiple-Table Preparation” on page 9 for instructions. 3 Check the data source connection by using Data Prep Editor in Administration Services Console to open the SQL source file. See Chapter 4, “Loading SQL Data.” 4 Create a rules file to tell Essbase SQL Interface how to interpret the SQL data to be used with the Essbase database. See Chapter 4, “Loading SQL Data.” After these steps are complete, you can load data or build dimensions. See Chapter 4, “Loading SQL Data” for instructions.
6 Introducing Essbase SQL Interface 2 Configuring a Data Source
In This Chapter Configuring a Data Source on Windows ...... 7 Configuring a Data Source on UNIX...... 7
Before you can access data using Essbase SQL Interface, you must configure the operating system for each data source and the driver it requires. Essbase installation provides DataDirect ODBC drivers. This chapter describes procedures for configuring Windows and UNIX. For information about configuring non-DataDirect ODBC drivers, see Chapter 5, “Using Non-DataDirect ODBC Drivers .” For a complete list of supported ODBC drivers, see Hyperion Essbase - System 9 Installation Guide.
Note: For detailed, driver-specific information on each of the DataDirect drivers, see the DataDirect Connect for ODBC Reference. The location of this reference varies depending on the platform. Typically it is within the \$HYPERION_HOME\common\ ... \books\odbc\odbcref\ directory.
Configuring a Data Source on Windows On Windows, use the ODBC Administrator to configure the data source.
➤ To configure the ODBC Administrator: 1 Start the ODBC Administrator by opening the Windows Control Panel and double-clicking the Administrative Tools icon, then double-clicking the Data Sources icon. 2 Choose a data source, or add one, and then enter the required information about the driver. For detailed instructions, see the documentation from the ODBC provider.
Configuring a Data Source on UNIX After installing Essbase, execute the inst-sql.sh file to enable Essbase SQL Interface. The odbc.ini file is created in $HYPERION_HOME/common/ODBC/Merant/x.x/odbc.ini.
Configuring a Data Source on Windows 7 ➤ To configure a data source on UNIX: 1 In the UNIX user home directory, ensure the .odbc.ini link is set to $HYPERION_HOME/common/ODBC/ Merant/x.x/odbc.ini. and remove the link if it is to a different location.
● Correct the link if it is to a different location.
● Create the link if it is missing. 2 Edit the odbc.ini file to add a description of the data source. See “Editing the odbc.ini File for Changes” on page 8 and “Example: Editing odbc.ini for DB2” on page 8.
Editing the odbc.ini File for Changes If you add data sources or change driver products or data sources you may need to edit the odbc.ini file because the odbc.ini file contains ODBC connection and configuration information such as data source name and driver product name. Specific information varies per platform.
Example: Editing odbc.ini for DB2 The following example illustrates how you might edit the .odbc.ini file on an Essbase running on AIX, to connect to a DB2 8.2 database named “tbc_data,” using an ODBC data source named db2data that invokes the DataDirect 5.2 Wire Protocol driver. Use the vi command to edit the .odbc.ini file and insert the following statements: [ODBC Data Sources] tbcdata=DB2 Source Data on AIX ... [tbcdata] Driver=/home/hyperion/hyperion/common/odbc/Merant/5.2/lib/ARdb222.so Database=tbcdata IpAddress=isaix7 TcpPort=50000
8 Configuring a Data Source Preparing Multiple-Table Data 3 Sources
In This Chapter Understanding Multiple-Table Preparation ...... 9 Preparing Data from Multiple Tables...... 11
This chapter describes how to prepare relational data in multiple tables for loading into Essbase.
Understanding Multiple-Table Preparation Use this section to understand the two methods available for preparing multi-table data:
● “Understanding Two Methods for Multiple-Table Data Preparation” on page 9
● “Understanding Security Requirements” on page 11
● “Choosing a Preparation Method” on page 11
Understanding Two Methods for Multiple-Table Data Preparation If data is in multiple tables, create a single table or a view of the data either by:
● Creating one table or view in the SQL database before using Essbase SQL Interface:
Understanding Multiple-Table Preparation 9 See “Choosing a Preparation Method” on page 11 for instructions.
● Joining the tables by entering a SELECT statement in Administration Services Console during the data load-dimension build task:
See “Preparing Data from Multiple Tables” on page 11 for instructions.
10 Preparing Multiple-Table Data Sources Choosing a Preparation Method An SQL database server reads from a single table and maintains a single view more efficiently than it processes a multiple-table SELECT statement. Therefore, creating a single table or view before you use Essbase SQL Interface greatly reduces the amount of processing time the SQL server.
Understanding Security Requirements Data load-dimension build preparation requires specific permissions:
● (For either preparation method) SELECT access privileges to all tables containing the relevant data.
● (For creating a single table or view in the relational database source) CREATE access privileges in the SQL database to create a single table or view. Ask the SQL Database Administrator for the appropriate CREATE privileges. If you cannot obtain CREATE privileges, use Administration Services to join tables during the data load.
Preparing Data from Multiple Tables
➤ To prepare data from multiple tables: 1 Obtain the required privileges:
● SELECT access to tables where relevant data is stored
● CREATE access to create a single table or view to join multiple-table data before using Essbase SQL Interface 2 Use one of these methods to prepare data from multiple tables:
● Create a single physical table or virtual table (view) based on data from multiple tables in the source database.
● Create a SELECT statement in Administration Services Console that joins the tables: a. Identify the tables and columns (or fields) containing the data that you want to load into Essbase. b. Select File > Open SQL in Administration Services Console to display Open SQL Data Sources. See “Opening an SQL Database” in Essbase Administration Services Online Help. c. Write a SELECT statement that joins the tables. See “ Selecting the SQL Data Source” on page 15 and “Creating SQL Queries (optional)” on page 15.
Note: Essbase passes the SELECT statement to the database without verifying the syntax.
Preparing Data from Multiple Tables 11 12 Preparing Multiple-Table Data Sources 4 Loading SQL Data
In This Chapter Understanding Data Loading ...... 13 Using Substitution Variables...... 13 Loading Relational Data Using Essbase SQL Interface...... 14 Loading the Data...... 16
This chapter describes how to use Oracle's Essbase® Administration Services to load data and build dimensions from SQL data sources.
Understanding Data Loading You can load the data or build outline dimensions after you have configured the data source and prepared the multiple-table data for loading.
➤ To load the data: 1 If you plan to use substitution variables, create them. See “Using Substitution Variables” on page 13 for instructions. 2 Create a rules file. See “Loading Relational Data Using Essbase SQL Interface” on page 14. 3 Load data into the Essbase database. See “Loading the Data” on page 16.
Using Substitution Variables Substitution variables enable you to use the same rules file for different data sources. You can use substitution variables in SQL strings and data source names. A substitution variable can apply to all applications and databases on Essbase Server, or a substitution variable can be used for a particular application or database. You can also define a substitution variable for the data source name (DSN) and specify in the rules file the substitution variable name. Understand the rules for substitution variable use in Essbase SQL Interface before you create and use them:
Understanding Data Loading 13 Understanding the Rules for Substitution Variables Remember these rules when you create substitution variables:
● The value of the substitution variable should be valid and appropriate SQL. Essbase does not validate the value.
● Be especially careful when you use quotation marks or single quotes. Different source databases have different conventions about when to use them.
● Whether or not you use a substitution variable, be sure that no regular SQL operators in SELECT, FROM, or WHERE clauses start with the ampersand (&), because that is the Essbase identifier for substitution variables.
Creating and Using Substitution Variables
➤ To create and use a substitution variable, use the following procedure: 1 Create the substitution variable using the instructions in “Managing Substitution Variables” in Essbase Administration Services Online Help. 2 To open the SQL data source when you edit the rules file select File > Open SQL from the menu. (See “Creating a Rules File” in Essbase Administration Services Online Help.) Specify substitution variables in the resulting Open SQL Data Sources dialog box.
● To specify a substitution variable for the DSN, select Substitution Variables and select the substitution variable from the list.
● To specify substitution variables in the query, use the substitution variable instead of a “field=value” string in the Select, From, or Where box. Remember to type the ampersand (&) in front of the substitution variable name. 3 Click OK/Retrieve to retrieve the data for the rules file.
Note: Be sure to set the desired value for the substitution variables before you use the rules file for a data load or dimension build.
Loading Relational Data Using Essbase SQL Interface To load SQL data into the Essbase database, you must create and use a data load rules file. Data load and dimension build rules are a set of operations that Essbase performs on data it loads as values in an Essbase database or builds as members in an Essbase outline. The operations are stored in a rules file. The rules file can also reject invalid records in the data source.
Summary of Steps 1. Create a data load rules file.
14 Loading SQL Data 2. Select your SQL data source. See “ Selecting the SQL Data Source” on page 15 for instructions. 3. If you plan to create SQL queries in Essbase, see “Creating SQL Queries (optional)” on page 15.
Creating the Data Load Rules File
➤ To create a data load rules file, see Creating a Data Load Rules File in Essbase Administration Services Online Help.
Selecting the SQL Data Source When you create a rules file you must specify a data source.
➤ To select a SQL data source: 1 In Administration Services Console, open Data Prep Editor or an existing rules file. 2 Choose File > Open SQL. 3 In Select Database, enter the Essbase Server, application, and database. and click OK. 4 In Open SQL Data Sources, select the data source or select the substitution variable and enter required information. (See “Opening an SQL Database” in Essbase Administration Services Online Help for details.) 5 Click OK/Retrieve. 6 In SQL Connect, enter the user name and password for the source database and click OK. Note the following facts about data source files:
● The data source file must be configured on the server computer.
● On UNIX platforms, you have defined the path for the SQL data source file in the .odbc.ini file.
● On Windows, if you have not defined the path for the SQL source file in the ODBC Administrator, you can type the path in the Database text box of the Define SQL dialog box.
● If you do not define a path, Essbase looks for the data source file in the directory from which you are running Essbase Server.
Creating SQL Queries (optional) Instead of creating a table or view to select data for the retrieval, you can write a SELECT statement when you perform the data load.
Note: Creating a SELECT statement in Essbase is usually slower than creating a table or view in the source database.
Loading Relational Data Using Essbase SQL Interface 15 The SQL Statement text box in the Open SQL Data Sources dialog box has Select, From, and Where text boxes to help you write SQL queries. You can specify multiple data sources, filter the display of records, and specify the desired order and grouping of records that will appear in Data Prep Editor.
Loading the Data
➤ To use SQL or relational data with an Essbase database, see Performing a Data Load or Dimension Build in Essbase Administration Services Online Help.
16 Loading SQL Data Using Non-DataDirect ODBC 5 Drivers
In This Chapter Configuring a Non-DataDirect Driver...... 17 Creating a Configuration File for Non-DataDirect Drivers...... 18 Configuring Non-DataDirect Data Sources ...... 21 Support for Non-DataDirect Drivers ...... 21
You can use drivers other than the DataDirect drivers provided with Essbase. Some non- DataDirect ODBC drivers are tested with Essbase. For detailed information on tested and supported drivers and data sources, see the Hyperion Essbase - System 9 Installation Guide.
➤ To use a non-DataDirect driver: 1 Configure the driver for all drivers and data sources. 2 Configure the data source if you are using Teradata. This chapter contains the following topics that describe how to use non-DataDirect ODBC drivers:
Configuring a Non-DataDirect Driver When you configure a DataDirect 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-DataDirect driver, you must give Essbase the configuration information for the driver that you use. You give Essbase the configuration information for your non-DataDirect driver by creating a driver configuration file called esssql.cfg, which is a text file. Place this file in your ARBORPATH\BIN directory on Essbase Server. This is c:\Hyperion\AnalyticServices\ if you installed Essbase in the default directory (/home/hyperion/analyticservices/ on UNIX platforms).
Note: If you do not create a configuration file, Essbase uses the default values. You may not be able to connect to the SQL database using the default values.
Configuring a Non-DataDirect Driver 17 Creating a Configuration File for Non-DataDirect Drivers For non-DataDirect drivers, you create a configuration file: $ARBORPATH/bin/ esssql.cfg. The configuration file must contain at least some of the following configuration values for each non-DataDirect 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:
● “Including the Minimum Required Contents” on page 18
● “Finding a Driver Name on Windows” on page 20
● “Finding a Driver Name on UNIX” on page 20
Including the Minimum Required Contents At a minimum, the configuration file must contain at least the DriverName for every non- DataDirect 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 "Description of Driver "
DriverName DriverName
UserId Value
Password Value
Database Value
Server Value
Application Value
Dictionary Value
Files Value
SingleConnection Value
UpperCaseConnection Value
IsQEDriver Value
]
Description of Driver is your description of the driver. Enclose the description in quotation marks (" "). The default value is " ".
18 Using Non-DataDirect ODBC Drivers DriverName is the file name of the non-DataDirect ODBC driver and is required. For all other configuration keywords, set Value to be either 1 or 0, according to the following table:
Configuration Information Value Description
UserId 1 User ID required
0 User ID not required Default: 0
Password 1 Password required
0 Password not required Default: 0
Database 1 Database name required
0 Database name not required Default: 0
Server 1 Server name required
0 Server name not required Default: 0
Application 1 Application name required
0 Application name not required Default: 0
Dictionary 1 Dictionary name required
0 Dictionary name not required Default: 0
Files 1 Files name required
0 Files name not required Default: 0
SingleConnection 1 Driver not thread-safe One active connection allowed Default: 1 Recommendation for DataDirect drivers: 1
0 Driver thread-safe Multiple active connections allowed Caution! Specifying 0 (multiple active connections allowed) for DataDirect or non-DataDirect drivers may lead to instability
UpperCaseConnection 1 Driver not case-sensitive Connection information is converted to uppercase
0 Driver case-sensitive Connection information is unchanged Default: 0
IsQEDriver 1 Driver is a DataDirect driver You can specify configuration information for DataDirect drivers (for example, if you have a later version of a DataDirect driver which Essbase does not yet support)
0 Driver is a non-DataDirect driver Default: 0
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-DataDirect drivers in one configuration file. Enclose the values for each driver in brackets ( [ ] ).
Creating a Configuration File for Non-DataDirect Drivers 19 Use this template to help you create a configuration file:
[
Description "Description of Driver "
DriverName DriverName
...
]
[
Description "Description of Driver "
DriverName DriverName
...
]
Finding a Driver Name on Windows
➤ To display the name of the drive, use this procedure: 1 Start the ODBC Administrator using any method from step 1 in “Configuring a Data Source on Windows” on page 7. The ODBC Data Source Administrator dialog box appears. Data sources that you have configured are in the User Data Sources list box. Drivers that have not been properly configured may also appear in the User Data Sources list box. Ignore them. 2 Select the Drivers tab. 3 Obtain the file name of the driver by scrolling to the right. For example, the file name for the Microsoft Access Driver is ODBCJT32.DLL. 4 Select the driver, and click OK.
Finding a Driver Name on UNIX On UNIX, the driver name is in the .odbc.ini file. For more information on the .odbc.ini file, see “Configuring a Data Source on UNIX” on page 7.
20 Using Non-DataDirect ODBC Drivers Configuring Non-DataDirect Data Sources The procedure for configuring non-DataDirect data sources is similar to that for configuring DataDirect data sources. See Chapter 2, “Configuring a Data Source.” For specific instructions on configuring a non-DataDirect data source, please reference your ODBC documentation.
Note: Before you configure a non-DataDirect data source, you must first configure the driver by creating an esssql.cfg configuration file. See “Creating a Configuration File for Non- DataDirect Drivers” on page 18.
Support for Non-DataDirect Drivers Some non-DataDirect drivers are not tested or supported for use with Essbase. The driver that you choose might not be specifically tested to work with Oracle's Hyperion® Essbase® – System 9 . For information on qualified drivers and data sources, see the Hyperion Essbase - System 9 Installation Guide.
Configuring Non-DataDirect Data Sources 21 22 Using Non-DataDirect ODBC Drivers Enabling Faster Data Loads A from Teradata Data Sources
In This Appendix Installing Required Teradata Software ...... 23 Setting Up the Environment for Using Export Operator...... 23 Loading Teradata Data Using Teradata Parallel Transporter...... 24
You can use Teradata Parallel Transporter from Teradata Tools and Utilities to significantly improve data load performance. With this method, ODBC is used to extract the database schema; then Teradata Parallel Transporter retrieves the data. This method is tested for Teradata Parallel Transporter Export Operator release 8.2 and Teradata 3.6 ODBC and is supported for the following platforms: 32-bit and 64-bit AIX, 32-bit HP-UX, Red Hat Linux, 32-bit and 64-bit Solaris, 32-bit Windows, and 64-bit Windows Intel and AMD.
Installing Required Teradata Software The customer is responsible for having the correct Teradata license and ODBC version installed and configured on the Essbase Server computer. See the Teradata documentation for installation instructions.
● From Teradata Tools and Utilities install Teradata Parallel Transporter Export Operator, Shared ICU Libraries for Teradata, Teradata GSS Client, and CLI. (For Linux installations, select libraries built by GCC 3.3.)
● Install the Teradata ODBC driver.
Setting Up the Environment for Using Export Operator Follow the instructions in Chapter 2, “Configuring a Data Source.” In addition, perform the following tasks:
● Add an entry to the hosts file for the Teradata database; for example: 172.27.24.181 tera2db tera2cop1
● Configure a system ODBC DSN for $TELAPI$
Installing Required Teradata Software 23 ● For UNIX operating systems, ensure needed environment variable paths are defined in the appropriate location. (The Windows installation automatically updates needed environment variables):
❍ TD ODBC driver
❍ CLIv2
❍ TD GSS
❍ Shared ICU
❍ TPT export operator files
❍ DataDirect ODBC driver
● In addition, in the appropriate path for the operating system, set the following variables for Teradata Parallel Transporter. (For details, see the “Code Samples” appendix in Teradata Parallel Transporter Application Programming Interface Programmer Guide); for example, for Solaris SPARC:
❍ export LD_LIBRARY_PATH =
❍ export NLSPATH =
❍ (If CLI is not installed in the default directory) export COPERR =
Loading Teradata Data Using Teradata Parallel Transporter Follow the instructions in Chapter 4, “Loading SQL Data.” When you open the SQL data source, select the desired data source name with the prefix $TELAPI$ that you defined as the ODBC DSN. For the SQL statement, define a native Teradata query in the SQL SELECT, FROM, and WHERE statements. Do NOT include carriage returns or line feeds in these statements. Each entry must be in a single statement. See the relevant Teradata documentation for native Teradata SQL query rules.
24 Enabling Faster Data Loads from Teradata Data Sources ABCDEF I JKLMNOPRSTUVW
Index
A SQL records, 5 Administration Services Console data sources joining tables, 10 non-MERANT, 21 loading SQL data, 13 paths, 15 SELECT statement, 10, 11 selecting, 15 ARBORPATH, 17 DB2, example odbc.ini file, 8 dialog boxes B Define SQL, 11 ODBC Data Source Administrator, 20 BIN directory, 17 dimensions, building, 5 building Essbase dimensions, 5 directories BIN, 17 C data sources, default, 15 cfg (.CFG) file, creating, 17 driver configuration file, 17 choosing, a driver, 7 driver configuration file configuration file, for non-MERANT drivers, 18 creating, 17, 18, 19 configuring default values, 17, 19 data sources in BIN directory, 17 non-MERANT, 21 keyword values, 19 overview, 7 required values, 18 non-MERANT drivers, 17, 19 syntax, non-MERANT drivers, 19 converting SQL statements, 5 drivers CREATE privileges, 11 choosing in ODBC Administrator, 7 creating description of, 18 data load rules file, 14 file names, 20 driver configuration file, 17, 18, 19 naming, 18 security privileges for single table or view, 11 non-DataDirect, 17 single table or view, 9, 11 non-MERANT, 21 password, 17 D UNIX, names, 20 data load preparation, 9 E load preparation methods, 11 Essbase SQL, mapping, 14 default values for drivers, 17, 19 data load rules file loading data into, 13 creating, 14 outline, mapping data to, 14 definition, 14 esssql.cfg, 17, 18, 19
Index 25 ABCDEF I JKLMNOPRSTUVW
examples, odbc.ini files, 8 non-MERANT data source, configuring, 21 F drivers tested, 17, 21 files, .CFG (configuration), 17 O I ODBC Administrator, 7 ODBC drivers installed ODBC drivers, listed, 20 file names, 20 interpreting SQL records, 5 non-DataDirect, 17 tested, 17 J UNIX, names, 20 joining tables, 10 odbc.ini file Administration Services:Administration Services, DB2 example, 8 10 ODBCJT32.DLL, 20 SELECT statement, 11 outline loading data, 16 K keywords, driver configuration file, 19 P passing L SELECT statements, 11 SQL statements, 5 loading data passwords for driver, 17 data load rules, 14 paths from single table, 9 esssql.cfg, 17 into outline, 16 for data sources, 15 joining tables, 10, 11 processing time, 11 overview, 6, 13 preparing for, 9 summary level data, 5 R using Administration Services, 13 relational data, loading:, 5. See also data requesting non-SQL data, 5 M mapping SQL data to an Essbase outline, 14 S Microsoft Access, ODBC driver for, 20 security privileges, 11 multidimensional databases SELECT statement, 11 building Essbase dimensions, 5 joining tables, 10 loading data into, 5 processing time, 11 multiple tables selecting SQL data sources, 15 joining, 10, 11 spreadsheet data sources, 5 loading from, 9 SQL data preparing, 9 joining tables, 10 loading, 5 N mapping, 14 selecting source, 15 non-DataDirect SQL databases drivers single tables in, 9 configuring, 17
26 Index ABCDEF I JKLMNOPRSTUVW
SQL databases, single tables in, 11 SQL queries, 15 SQL server, 11 SQL statements, 5 summary data, loading, 5
T tables creating, 9 efficiency, 11 joining, 10, 11 loading from, 9 SQL databases, 9 Teradata data source, using Teradata Export Operator, 23 tested drivers, 17 non-MERANT drivers, 21 text file data sources, 5
U UNIX environments, odbc.ini file, 20
V views, 11 creating, 9 SQL databases, 9
W Windows 2000/XP environments, configuring data sources, 7
Index 27 ABCDEF I JKLMNOPRSTUVW
28 Index