HP NonStop Data Transformation Engine ODBC Adapter Reference Guide

Transcription

1 HP NonStop Data Transformation Engine ODBC Adapter Reference Guide Abstract This manual provides information about using the HP NonStop Data Transformation Engine (NonStop DTE) ODBC adapter. Product Version NonStop Data Transformation Engine Version Updates (RVUs) N/A Part Number Published October 2004

2 Document History Part Number Product Version NonStop Data Transformation Engine NonStop Data Transformation Engine Published June 2004 October 2004

3 Contents About This Document Related References... 4 Chapter 1 - ODBC Adapter Overview... 6 System Requirements... 6 Chapter 2 - Database Columns and Types Item Type Properties... 7 Date and Time Formats... 8 Chapter 3 - Database Interface Designer Settings Database Definition Dialog Box Stored Procedures Native Call Syntax Chapter 4 - ODBC Adapter Commands Adapter Command Summary Adapter-specific Commands Adapter Commands for a Source GET > Source > Command Setting ID Execution Command DBLOOKUP or DBQUERY Functions GET Function Adapter Commands for a Target PUT > Target > Command Setting OD Execution Command PUT Function Chapter 5 - Overriding Column Attributes Defining Column Attribute Overrides Chapter 6 - Binding Values in DBLOOKUP/DBQUERY Limitation When Using ODBC Specifying the Data Type Chapter 7 - Configuring DSN for Event Server Startup Selecting the Startup Method Chapter 8 - Restrictions and Limitations Appendix A - Return Codes and Error Messages Index 3

4 About This Document This document contains detailed information about using the ODBC Adapter. For general information regarding using any of the Mercator Resource adapters, see the Resource Adapters Reference Guide. This document assumes that the reader knows the Windows environment, has used the Mercator Design Studio, and understands words such as mapping, type trees, and other basic Mercator terminology. Related References Related Reference Resource Adapters Reference Guide Database Interface Designer Reference Guide Execution Commands Reference Guide Functions and Expressions Reference Guide Getting Started Description Using adapters as map sources and map targets in general. Detailed information can be found in the reference guide for each specific adapter. Importing metadata into the databases and using adapters. Using executions commands to control how a map is run by the Command Server or through the Platform API. Creating component rules in the Type Designer and map rules in the Map Designer using expressions, functions, and reserved words. Describing Mercator products, the Integration Broker suite, the installation procedure, and system requirements. 4

5 About This Document Related References Related Reference Integration Flow Designer Reference Guide Description Using the Integration Flow Designer as a Design Studio companion and graphical facility to manage collections of related maps. Also graphically organizing these maps, based upon your requirements, into logical collections called systems. 5

6 Chapter 1 - ODBC Adapter This chapter introduces the Open DataBase Connectivity (ODBC) adapter. You can use the adapter with a Command Server, an Event Server, the Platform API, or with a map in a map rule. Overview Use the database adapters for ODBC to access and manipulate data contained in databases that are ODBC data sources. You can also install database adapters on additional systems for remote database connectivity. This chapter discusses the requirements for installing and running the database adapters for ODBC and provides the database-specific information required for using your specific adapters in your database host environment. System Requirements To install and run the ODBC database adapters Verify that you have installed any desired ODBC drivers and have configured your ODBC data source(s). For information about how to do this, refer to the ODBC documentation included with your driver(s). Verify that the ODBC environment variables are defined. For information about this, refer to your ODBC documentation. Note After you have initially run the setup program, if you make changes to your path and/or library path at a later date, you need to re-run this program. 6

7 Chapter 2 - Database Columns and Types The Database Interface Designer and mtsmaker with the Type Tree Maker generate type trees for queries, tables, views, and stored procedures in an ODBCcompliant RDBMS (Relational Database Management System). Item types are created in a type tree that represents the data types of the columns of a query, table, view, or stored procedure. The Database Interface Designer and mtsmaker get information about columns by calling the ODBC Driver Manager that calls the ODBC driver for your RDBMS to describe the columns associated with a query, table, view, or stored procedure. The ODBC driver for the RDBMS has mapped the data types in each column to ODBC data types as appropriate. From the RDBMS, the ODBC Driver Manager returns the ODBC data type, length, and other information to the Database Interface Designer and mtsmaker. The ODBC data types are then mapped to types in a type tree. The Database Interface Designer and mtsmaker have no knowledge of the RDBMS-specific data types only the ODBC data types. Item Type Properties The following table lists the ODBC data types and the values of the item type properties to which they correspond when the type tree is generated. ODBC Data Type Interpret as Item Subclass, Presentation Length SQL_VARCHAR Character Text * SQL_CHAR Character Text * SQL_DECIMAL Character Number, Decimal * SQL_NUMERIC Character Number, Decimal * SQL_SMALLINT Character Number, Integer 6 SQL_INTEGER Character Number, Integer 11 SQL_REAL Binary Number, Float 4 SQL_FLOAT Binary Number, Float 8 7

8 Chapter 2 - Database Columns and Types Date and Time Formats ODBC Data Type Interpret as Item Subclass, Presentation Length SQL_DOUBLE Binary Number, Float 8 SQL_LONGVARCHAR Character Text * SQL_BIT Character Number, Integer * SQL_TINYINT Character Number, Integer 4 SQL_BIGINT Character Number, Integer 20 SQL_BINARY Binary Text * SQL_VARBINARY Binary Text * SQL_LONGVARBINARY Binary Text * SQL_DATE Character Date & Time * SQL_TIME Character Date & Time * SQL_TIMESTAMP Character Date & Time * SQL_INTERVAL_HOUR Character Text * SQL_INTERVAL_MINUTE Character Text * SQL_INTERVAL_SECOND Character Text * SQL_INTERVAL_YEAR_TO_MONTH Character Text * SQL_INTERVAL_DAY_TO_HOUR Character Text * SQL_INTERVAL_DAY_TO_MINUTE Character Text * SQL_INTERVAL_DAY_TO_SECOND Character Text * SQL_INTERVAL_HOUR_TO_MINUTE Character Text * SQL_INTERVAL_HOUR_TO_SECOND Character Text * SQL_INTERVAL_MINUTE_TO_SECOND Character Text * * The DBMS dictates the length of this type. Date and Time Formats When using columns defined as dates and times in ODBC databases, the format for both input and output is: Note Precision can be specified on output. For example, a precision of 4 would change a date of format from ccyy-mm-dd to ccyy. 8

9 Chapter 2 - Database Columns and Types Date and Time Formats date: ccyy-mm-dd time: timestamp: hh:mm:ss ccyy-mm-dd hh:mm:ss[.fff ] Note If the group format is fixed, the field is padded to 26 with trailing spaces. where cc = a two-digit century yy = a two-digit year mm = a two-digit month dd = a two-digit day hh = a two-digit hour mm = a two-digit minute ss = a two-digit second.fff = optional fractional seconds An example is :00:00 which specifies August 27, Note In the Generate Type Tree from dialog box, use the Represent date/time columns as text items check box to define whether to automatically format this information as Date & Time (which is with this check box disabled, the result of which is shown in the Item Subclass, Presentation column above) as a text string. When generated as a text string, it may be necessary to use either the TEXTTODATE or TEXTTOTIME function in a map rule to convert the text string to the date and time format required by the database. If you are generating new type trees, it is recommended that you disable this check box. The Represent date/time columns as text items check box is modal. After it has been disabled, it will remain disabled for all subsequent type tree generations, regardless of source. Therefore, you must be careful in determining this setting. 9

10 Chapter 3 - Database Interface Designer Settings When you define an ODBC database in the Database Interface Designer, in addition to the common settings available for all of the database adapters in the Database Definition dialog box, you need to enter the information specific to ODBC. Database Definition Dialog Box The ODBC adapter-specific settings are described in the following table: Setting Description Data Source Database Interface Designer Runtime The data source you defined in your development PC that is used by the Database Interface Designer to access the database information for designtime purposes The data source you defined in your ODBC database host platform to be used for access to the database for run-time (map execution) purposes both from the Map Designer and a Command Server Security User ID Password The user ID used to connect to the database The authorization password to connect to the DB2 subsystem 10

11 Chapter 3 - Database Interface Designer Settings Stored Procedures Native Call Syntax The following is an example of the Database Definition dialog box with the ODBC-specific settings. Stored Procedures Native Call Syntax A stored procedure can be accessed from within a map by specifying the native call syntax in the following: a query that is specified in an input card the first argument in a DBQUERY or DBLOOKUP function This argument does not need to be a literal. The arguments to the stored procedure may be determined at map execution time. the SQL Statement adapter command (-STMT) in DBQUERY, DBLOOKUP, or GET functions For information about using DBLOOKUP or DBQUERY, refer to or about using the syntax for device-independent calls to access return values and output adapter commands, refer to the Database Interface Designer Reference Guide. For example, a call to a stored procedure using ODBC in a DBLOOKUP might be: DBLOOKUP ("{call MyAddNameProc('" + Name:Column + "',-1)}", "mydb.mdq", "MyDB") Note String literals must be contained within single quotation marks; adapter arguments must be separated by commas. 11

12 Chapter 4 - ODBC Adapter Commands This chapter describes the functions and usage of the ODBC adapter commands and their options. Note For information about command syntax notation, refer to Getting Started. Adapter Command Summary The following is a summary of the adapter commands that can be used to specify data sources and targets. The applicability of many of the commands depends upon whether you are specifying a source or target, whether a database/query file (.mdq) is used, and the situations in which the usage of the command applies. Adapter commands can be used in GET > Source > Command or PUT > Target > Command settings in the Map Designer and Integration Flow Designer, using GET, PUT, DBLOOKUP, or DBQUERY function calls, or overriding a data source or target using execution commands in a RUN function or on the command line. Adapter-specific Commands The following section lists and describes those adapter commands that are ODBCspecific database parameters. For a complete listing of all database adapter commands, refer to the Resource Adapters Reference Guide. -DBTYPE -ROWCNT -SOURCE 12

13 Chapter 4 - ODBC Adapter Commands Adapter Command Summary Database Adapter Type (-DBTYPE) Use the Database Adapter Type adapter command (-DBTYPE) to specify the database adapter type. -DBTYPE ODBC Option ODBC Description The database adapter type is ODBC. Row Count (-ROWCNT) Note This command must be specified if the original card is not a database and no database is specified using the Database/Query adapter command (-MDQ) and the Database Name adapter command (-DBNAME). Use the Row Count adapter command (-ROWCNT) to specify the number of rows to be retrieved per fetch. -ROWCNT row_count Option row_count Description This is the number of rows to be retrieved per fetch. The time to fetch is optimized in accordance with the increase in the number of rows to retrieve. Therefore, a significant performance improvement may be gained by retrieving as many rows as possible in a single fetch. Note The number of rows retrieved is limited only by the amount of memory installed on the querying PC. The default for the number of rows to be retrieved per fetch for the ODBC adapter is one row. 13

14 Chapter 4 - ODBC Adapter Commands Adapter Commands for a Source Data Source (-SOURCE) Use the Data Source adapter command (-SOURCE) to specify the ODBC data source. -SOURCE datasource Option datasource Description Specify the ODBC data source. Adapter Commands for a Source This summary shows the syntax of the adapter commands that can be used when defining a data source using an.mdq file or without using an.mdq file, including both the required and optional adapter commands in the following situations: using a GET > Source > Command setting in the Map Designer and Integration Flow Designer overriding a data source using the Input Source Override Database execution command (-ID) using a RUN function or on the command line using a DBLOOKUP, DBQUERY, or GET function in map or component rules GET > Source > Command Setting Use the Map Designer or Integration Flow Designer to specify Database as the value for the GET > Source setting and enter the database adapter commands as desired for the Command setting. With Database/Query File [-DBTYPE ODBC] [-SOURCE datasource] [-STMT SQL_statement] [-FILE [directory]] [-VAR name=value ] [-USER user_id] [-CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]] Without Database/Query File -DBTYPE ODBC -SOURCE datasource -STMT SQL_statement [-FILE [directory]] [-VAR name=value ] [-USER user_id] [-CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]] 14

15 Chapter 4 - ODBC Adapter Commands Adapter Commands for a Source -ID Execution Command Use the Input Source Override - Database execution command (-ID) to designate a database as the source or you can override one or more of the adapter command settings or database definitions in a RUN function or on the command line. Note The following adapter commands are shown using a single quotation mark, which is the Windows syntax. For non-windows platforms, use two single quotation marks followed by one single quotation mark and end with one single quotation mark followed by two single quotation marks. The Source in the Compiled Map is a Database With Database/Query File '[-MDQ mdq_file -DBNAME database_name] [-QUERY query_name -STMT SQL_stmt] [-FILE [directory]] [-VAR name=value ] [-USER username] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]' Without Database/Query File '-DBTYPE ODBC -SOURCE datasource -STMT SQL_statement [-FILE [directory]] [-VAR name=value ] [-USER user_id] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]' The Source in the Compiled Map is Not a Database With Database/Query File '-MDQ mdq_file -DBNAME database_name] -QUERY query_name -STMT SQL_stmt] [-FILE [directory]] [-VAR name=value] [-USER username] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]' Without Database/Query File '-DBTYPE ODBC -SOURCE datasource -STMT SQL_statement [-FILE [directory]] [-USER user_id] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]' 15

16 Chapter 4 - ODBC Adapter Commands Adapter Commands for a Target DBLOOKUP or DBQUERY Functions The DBLOOKUP and DBQUERY functions can be used in component rules in the Type Designer and map rules in the Map Designer when creating a map that can be used with a database. With Database/Query File DBLOOKUP ("SQL_statement", "-MDQ mdq_file -DBNAME database_name [-USER username] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]") Without Database/Query File DBQUERY ("SQL_statement", "-DBTYPE ODBC -SOURCE datasource [-USER username] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]") GET Function The GET function returns the data from the source adapter. With Database/Query File GET ("DB", "-MDQ mdq_file -DBNAME database_name -QUERY query_name -STMT SQL_stmt [-FILE [directory]] [-VAR name=value ] [-USER username] [-CCARD -CSTMT [number]] [-ROWCNT row_count] [{-TRACE -TRACEERR}[+] [full_path]]") Without Database/Query File GET "DB", "-DBTYPE ODBC -SOURCE datasource -STMT SQL_stmt [-FILE [directory]] [-USER username] [-ROWCNT row_count] [-CCARD -CSTMT [number]] [{-TRACE -TRACEERR}[+] [full_path]]") Adapter Commands for a Target This summary shows the syntax of the adapter commands that can be used when defining a data target using an.mdq file or without using an.mdq file, including both the required and optional adapter commands in the following situations: using a PUT > Target > Command setting in the Map Designer and Integration Flow Designer overriding a data source using the Output Source Override Database execution override (-OD) using a RUN function or on the command line using the PUT function in map or component rules 16

17 Chapter 4 - ODBC Adapter Commands Adapter Commands for a Target PUT > Target > Command Setting Use the Map Designer or the Integration Flow Designer to specify Database as the value for the PUT > Target setting and enter the adapter commands as desired for the Command setting. With Database/Query File [-DBTYPE ODBC] [-SOURCE datasource] [-PROC procedure_name -TABLE table_name] [-USER user_id] [-CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]] Without Database/Query File -DBTYPE ODBC -SOURCE datasource -PROC procedure_name -TABLE table_name [-USER user_id] [-CSTMT [number]] [-DELETE] [{-TRACE -TRACEERR}[+] [full_path]] -OD Execution Command Use the Output Source Override - Database execution command (-OD) to designate a database as a target or you can override one or more of the adapter command settings or database definitions in a RUN function or on the command line. Note The following adapter commands are shown using a single quotation mark, which is the Windows syntax. For non-windows platforms, use two single quotation marks followed by one single quotation mark and end with one single quotation mark followed by two single quotation marks. The Target in the Compiled Map is a Database With Database/Query File '[-MDQ mdq_file -DBNAME database_name] [-PROC procedure_name -TABLE table_name] [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] [-BADDATA[+] full_path] Without Database/Query File '-DBTYPE ODBC -SOURCE datasource -PROC procedure_name -TABLE table_name [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] 17

18 Chapter 4 - ODBC Adapter Commands Adapter Commands for a Target With Database/Query File [{-TRACE -TRACEERR}[+] [full_path]]' Without Database/Query File [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]]' The Target in the Compiled Map is Not a Database With Database/Query File '-MDQ mdq_file -DBNAME database_name -PROC procedure_name -TABLE table_name [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]]' Without Database/Query File '-DBTYPE ODBC -SOURCE datasource -PROC procedure_name -TABLE table_name [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]]' PUT Function Use the PUT function to pass data to the target adapter. With Database/Query File PUT ("DB", "-MDQ mdq_file -DBNAME database_name -PROC procedure_name -TABLE table_name [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-UPDATE [OFF ONLY]] [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]]") Without Database/Query File PUT ("DB", "-DBTYPE ODBC -SOURCE datasource -PROC procedure_name -TABLE table_name [-USER username] [-CCARD -CSTMT [number]] [-DELETE] [-BADDATA[+] full_path] [{-TRACE -TRACEERR}[+] [full_path]]") 18

19 Chapter 5 - Overriding Column Attributes When using the Database Interface Designer to generate a type tree for a query, table, view, or stored procedure, you may want to specify how columns are to be interpreted, rather than relying upon the interpretation of a particular database driver. These column overrides are saved in the.mdq file. When generating a type tree with the ODBC adapter and enabling the Override Column Definitions check box in the Generate Type Tree from dialog box for a query, table, view, or stored procedure, the Column Datatype Specification dialog box appears. Any overrides you specify in these dialog boxes are saved when the.mdq file is saved. Note The generated type tree with overrides is represented in the Navigator with an icon having black spheres (instead of blue, red, and green). If a tree is regenerated at a later date for the same query, table, view, or stored procedure within a database, you are prompted to confirm whether the previously defined overrides should be applied to the new tree. Note The following steps and dialog boxes show how to define column override attributes for a table or view. However, the steps and dialog boxes for a stored procedure are very similar and should follow the same process. Defining Column Attribute Overrides The following procedure describes how to define column attribute overrides for a: table or stored procedure query To define column attribute overrides for a table (or stored procedure) 1 In the Database Interface Designer, open the.mdq file. 2 In the Navigator, select the database containing the table for which you want to generate a type tree with column attribute overrides. 19

20 Chapter 5 - Overriding Column Attributes Defining Column Attribute Overrides 3 From the Database menu, select either Generate Tree From > Table or Generate Tree From > Procedure, depending upon the one you are generating. Either the Generate Type Tree from Tables or Generate Type Tree from Procedures dialog box appears, depending upon your selection. An example of the Generate Type Tree from Tables dialog box follows. For more information about the type tree generation dialog boxes, refer to the Database Interface Designer Reference Guide. 4 Select one or more tables, views, or procedures for which you want to generate a type tree. 5 Enter a name for the type tree file (.mtt) or Click (Browse) to select a type tree. 6 Enable one of the Type options to specify how you want the newly generated types to be saved. 7 From the Row group format list, enable Delimited or Fixed. 20

21 Chapter 5 - Overriding Column Attributes Defining Column Attribute Overrides 8 Accept the default values for the Group options fields (Delimiter, Terminator, and Release) or change as desired. 9 To specify how columns are to be interpreted, enable the Override column definitions check box as opposed to relying on the interpretation of the database driver. 10 Click Generate. The Column Datatype Specification dialog box appears, an example of which follows. 11 From the Tables/Views list, select the table or view containing the column or columns for which you want specify an override. 12 From the Columns list, select the column for which you want to specify an override. 13 Specify the Subclass, Interpret as, Presentation, and Length values for the selected column as desired. For more information about setting these attributes, refer to the Type Designer Reference Guide. Note In most cases, the specified length should not be shorter than the default length because this may result in data truncation errors. 14 Repeat Steps for each column for which you want to specify an override. 21

22 Chapter 5 - Overriding Column Attributes Defining Column Attribute Overrides 15 When finished, click OK. To define column definition overrides for a query 1 In the Database Interface Designer, open the.mdq file. 2 In the Navigator, select the query for which you want to generate a type tree. 3 From the Queries menu, choose Generate Tree. The Generate Type Tree from Query dialog box appears, an example of which follows. For details about the type tree generation dialog box, refer to the Database Interface Designer Reference Guide. 4 Enter a name for the type tree file (.mtt) or Click to select a type tree. 5 To specify the way you want to save the newly generated types, enable one of the Type options check boxes. 6 From the Row group format list, enable either Delimited or Fixed. 22

23 Chapter 5 - Overriding Column Attributes Defining Column Attribute Overrides 7 Accept the default values for the Group options fields (Delimiter, Terminator, and Release) or change as desired. 8 To specify how columns are to be interpreted, enable the Override column definitions check box as opposed to relying on the interpretation of the database driver. 9 Click OK. The Column Datatype Specification dialog box appears, an example of which follows. 10 From the Columns list, select the column for which you want to specify an override. 11 Specify the Subclass, Interpret as, Presentation, and Length values for the selected column as desired. For more information about setting these attributes, refer to the Type Designer Reference Guide. Note In most cases, the specified length should not be shorter than the default length because this may result in data truncation errors. 12 Repeat Steps for each column for which you want to specify an override. 13 Click OK. 23

24 Chapter 6 - Binding Values in DBLOOKUP/DBQUERY When using a DBLOOKUP or DBQUERY function, use the Bind facility to submit similarly constructed SQL statements to the database server so that the statements are syntactically identical. By binding a value to a placeholder in the SQL statement, the actual syntax of the statement can be made static, which may improve performance. For more information about using bind values in database functions, refer to the Database Interface Designer Reference Guide. Limitation When Using ODBC When binding values using ODBC, a limitation exists because ODBC cannot determine the data type of the column to which the value is being bound at the time the SQL statement is executed. Therefore, the data type of the value being passed must be explicitly specified. Because of this ODBC limitation, the ODBC database adapter determines the data type of the value according to the following rule: If the value contains only numeric characters or numeric characters with a decimal point, the value is assumed to be numeric; otherwise, the value is assumed to be text. This rule provides the expected results in most cases; however, there may be some situations in which the rule may not apply and it may be necessary to specify the exact data type. For example, if the value is a text field consisting solely of numeric characters, the value is incorrectly interpreted as numeric unless correctly specified. Specifying the Data Type To override the default behavior and to explicitly specify the data type, a data type indicator must precede the bind value. The syntax for this is: :bind([t N D],value) 24

25 Chapter 6 - Binding Values in DBLOOKUP/DBQUERY Specifying the Data Type The following table lists the data type indicators and the relationship between each data type indicator and the ODBC data types. Data Type Indicator T or TEXT N or NUM or NUMBER D or DATE ODBC data type SQL_CHAR SQL_NUMERIC SQL_DATETIME Note For information about item formats and interpretation, refer to Item Type Properties. As an example of specifying a data type, to bind a date value to a statement, you must specify that the value be of data type DATETIME. The SQL statement would be entered as: DBLOOKUP("select Age from Person where DateOfBirth=:bind([DATE]," + DateItem:Row + ")", "DB.mdq", "MyDB") If the [DATE] data type indicator is not specified, the trace file from the database adapter displays the following error message: Message: [Microsoft][ODBC Microsoft Access 97 Driver] Data type mismatch in criteria expression. 25

26 Chapter 7 - Configuring DSN for Event Server Startup Note This information also applies to establishing a Windows-based data source name for the Informix adapter. For information about how to configure a DSN for Unix, refer to your Unix documentation. Using ODBC, data sources are configured in the ODBC Data Source Administrator applet in the Control Panel as system sources (System DSN) that are visible to all users and NT services on the system, or to user sources (User DSN) that are visible only to you (the current user). Note For Windows 2000, access this (ODBC Data Source Administrator) applet by selecting Administrative Tools in the Control Panel, then Data Sources (ODBC). Based upon each data source configuration, the data source is allowed access only if the logon account is correctly specified. A system data source can be accessed only when using a system account logon, which is the default. A user data source can be accessed only when using a user account logon that must be specified. When using the NT Event Server and access to ODBC data sources is required, the Event Server must be started from the Services applet with the correct logon (either system or user account) that allows access to the data sources required by the Event Server during run-time. For more information about this and using the Windows 2000 machine, refer to the Event Server Reference Guide. For example, if a data source is defined as a system source in the System Data Sources list on the System DSN tab, the Event Server must be started using the System Account logon, which is the default. 26

27 Chapter 7 - Configuring DSN for Event Server Startup Selecting the Startup Method However, if your ODBC data sources are defined as user data sources and are listed in the User Data Sources list on the User DSN tab of the ODBC Data Source Administrator applet, you must change the Startup options for the Event Server so that the logon is specified for the user account. This allows the Event Server to have access to the data sources associated with the user account that are required during Event Server run-time. Selecting the Startup Method Note Because of differences in operating systems, there are two separate procedures for selecting the startup method for the Event Server according to operating system as listed below: Windows NT Windows 2000 To select the startup method for the Event Server (Windows NT) 1 From the Start menu, select Settings > Control Panel. 2 Open the Services applet. 27

28 Chapter 7 - Configuring DSN for Event Server Startup Selecting the Startup Method 3 From the Services applet, select Mercator Event Server and click the Startup button. The Service dialog box appears, an example of which follows. 4 Enable This Account and click (Browse) to select the user account under which the DSN was created. 5 Enter values for the selected user account in the Password and Confirm Password fields. The Event Server will use these values to log on to the system and access the user data sources. 6 Click OK. To select the startup method for the Event Server (Windows 2000) 1 From the Start menu, select Settings > Control Panel. 2 Select Administrative Tools. 3 Open the Services applet. The Services dialog box appears. 4 In the Name column, double-click Mercator Event Server. The Mercator Event Server Properties dialog box appears, an example of which follows. 28

29 Chapter 7 - Configuring DSN for Event Server Startup Selecting the Startup Method 5 Click the Log On tab. The Log On tabbed page appears, an example of which follows. 29

30 Chapter 7 - Configuring DSN for Event Server Startup Selecting the Startup Method 6 Enable This account and click to select the user account under which the DSN was created. 7 Enter values for the selected user account in the Password and Confirm password fields. The Event Server will use these values to log on to the system and access the user data sources. 8 Click OK. 30

31 Chapter 8 - Restrictions and Limitations The Database Interface Designer and database adapters offer options and functions for accessing and manipulating data contained within a database. However, there is one restriction for this adapter: database triggers are not supported. You cannot use a data source as an input event trigger for the Event Server. 31

32 Appendix A - Return Codes and Error Messages Return codes and messages are returned when the particular activity completes. Return codes and messages may also be recorded as specified in the audit logs, trace files, execution summary files, etc. For information about error codes and messages returned by database-specific adapters, see Appendix A - Return Codes and Error Messages > Database-specific Adapter Messages in the Resource Adapters Reference Guide. Various troubleshooting tools are available in case you encounter problems while using the database adapters. For example, if you attempt to run a map that uses the adapter and encounter problems or do not receive the expected results, use the following adapter troubleshooting tools: adapter audit log (.log) adapter trace file (.mtr) 32

33 Index..log file, 32.mtr, 32 A audit log, 32 B Bind facility limitations, 24 binding example of, 25 C column attribute overrides, 19 for queries, 22 for tables and stored procedures, 19 commands Data Source (-SOURCE), 14 Database Adapter Type (-DBTYPE), 13 for a source, 14 for a target, 17 list of, 12 Row Count (-ROWCNT), 13 summary, 12 D data types, 7 database definition ODBC-specific settings, 10 Date & Timeformat, 9 DBLOOKUP or DBQUERY functions, 16 bind limitations when using ODBC, 24 -DBTYPE adapter command, 13 Driver Manager for ODBC, 7 E error messages, 32 Event Server startup, 26 examples binding using ODBC, 25 native call for stored procedures, 11 execution commands -ID, 15 -OD, 17 F format data type, 7 date and time, 9 functions DBLOOKUP/DBQUERY, 16 GET, 16 PUT function, 18 G GET > Source > Command setting, 14 GET function, 16 I -ID execution command, 15 Input Source - Override - Database execution command (-ID), 15 item formats, 7 L log file, 32 N native call for stored procedures, 11 O -OD execution command, 17 Output Source Override - Database execution command (-OD), 17 P PUT > Target > Command setting, 17 PUT function, 18 Q query defining attribute overrides for, 22 R RDBMS, 7 related references, 4 restrictions and limitations, 31 return codes, 32 -ROWCNT adapter command, 13 rules for binding, 24 33

34 Index S S -SOURCE adapter command, 14 stored procedures using native call, 11 syntax for binding, 24 system requirements, 6 table T defining attribute overrides for, 19 troubleshooting, 32 type trees generating from a view, 20, 21 V views generating a type tree, 20 34