HP Neoview ODBC Drivers Manual HP Part Number: 619332-001 Published: August 2010 Edition:
© Copyright 2010 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................9 Intended Audience.................................................................................................................................9 New and Changed Information in This Edition.....................................................................................9 Document Organization.....................................................................
API Functions..................................................................................................................................29 Data Types.......................................................................................................................................29 Restricted ODBC API Functions...........................................................................................................29 SQLBindParameter...............................................................
Unicode C and SQL Data Types...........................................................................................................48 Unicode Driver Behavior......................................................................................................................48 4 HP Neoview Unicode Driver for UNIX.......................................................................51 Unicode APIs...........................................................................................................
Index.................................................................................................................................
List of Tables 1-1 2-1 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 Release Considerations and Restrictions for Windows Driver.....................................................23 Release Considerations and Restrictions for HP Neoview ODBC Drivers for UNIX...................38 Connecting to a Data Source.........................................................................................................63 Obtaining Information About a Driver and Data Source.............
About This Document This manual describes how to configure HP Neoview ODBC drivers for Microsoft Windows and the HP Neoview ODBC drivers for UNIX (HP-UX, Linux, IBM AIX®, and Sun Solaris for SPARC®). The drivers enable applications developed for the Microsoft Open Database Connectivity (ODBC) application programming interface (API) to access the HP Neoview database.
Notation Conventions General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: SELECT Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required.
| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: {expression | NULL} … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: ATTRIBUTE[S] attribute [, attribute]... {, sql-expression}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times.
Neoview Customer Library The manuals in the Neoview customer library are listed here for your convenience. • Administration Neoview User Management and Security Administration Guide Information about security features on the Neoview platform, including user and role management for database and platform users, support for integration with Lightweight Directory Access Protocol (LDAP) directory servers, password encryption, and database security.
• Connectivity Neoview JDBC Type 4 Driver API Reference information about the HP Neoview JDBC Type 4 Driver API. Reference Neoview JDBC Type 4 Driver Programmer’s Reference Information about using the HP Neoview JDBC Type 4 driver, which provides Java applications on client workstations access to a Neoview database. Neoview ODBC Drivers Manual Information about using HP Neoview ODBC drivers on a client workstation to access a Neoview database. • Neoview ADO.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: pubs.comments@hp.com Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 HP Neoview ODBC Driver Overview for Windows Open Database Connectivity (ODBC) is a widely accepted application programming interface (API) for database access. It is based on the Call-Level Interface (CLI) specifications from X/Open and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language.
If you choose to port an ODBC 32–bit application to 64–bit, you must make code changes. For detailed information about the differences between 32–bit and 64–bit, ODBC code, please refer to the Microsoft Developer Network Online Library at http://msdn.microsoft.com/en-us/library/ ms716287.aspx. For installation instructions, see the README for the HP Neoview ODBC Driver for Windows, located at www.software.hp.com.
aware of each other. A connection in a connection pool can be used repeatedly by multiple components. NOTE: Connection pooling can be used by an ODBC application exhibiting ODBC 2.x behavior, as long as the application can call SQLSetEnvAttr. When using connection pooling, the application must not execute SQL statements that change the database or the context of the database, such as changing the database name, which changes the catalog used by a data source.
shared environment is found, the environment is returned to the application, and its reference count is incremented. The actual connection to be used is not determined by the Driver Manager until SQLConnect or SQLDriverConnect is called. 4. Calls SQLConnect or SQLDriverConnect to make the connection.
• • Password handling changes A new DLL in the installation package, to support password encryption Password encryption features are available on these platforms: • Windows 32-bit • Windows 64-bit This section discusses: • “Password Length” (page 19) • “Password Expiration” (page 19) • “Password Encryption” (page 19) • “Secure Login and Multiple-Role Support for Neoview ODBC Drivers” (page 21) • “Server Certificates” (page 21) Password Handling Changes for Release 2.5 As of release 2.
Passwords for platform-level users are encrypted in transit in the same way as LDAP user passwords and are stored on the Neoview platform in an encrypted form. Passwords for platform-level users have the following characteristics: • Minimum length of 8 bytes • Maximum length of 64 bytes NOTE: If you use 1024-bit keys, the combined length of the passwords for a platform user ID and cannot exceed 70 characters.
password, and the third is the brace that the ODBC driver will interpret as a delimiter and strip off. If you want the password to be Use this value in the connection string {4mica1]} “PWD={{4mica1]}}};” fOrB3}4& “PWD={fOrB3}}4&};” Secure Login and Multiple-Role Support for Neoview ODBC Drivers Logging On as a Database User Prior to logging on to the Neoview database as a database (LDAP) user, specify the connection attribute SQL_ATTR_ROLENAME to specify the role.
IMPORTANT: You must have write permission for the certificate directory. If you do not, the download fails and an error is returned. NOTE: The most common way to identify the home directory is the HOME environment variable. If that variable is not set on the workstation, the security framework uses the HOMEDRIVE and HOMEPATH environment variables. If those variables are not set either, an error is reported.
1. 2. Checks the location specified by SQL_ATTR_CERTIFICATE_DIR and SQL_ATTR_CERTIFICATE_FILE (or the corresponding values in the connection string or—in the case of the certificate directory—in the ODBC driver installation, MXODSN or odbc.ini file) to determine whether a certificate exists at that location. If the application did not specify a directory, the driver checks the user's home directory. If the application did not specify a filename, the driver assumes the name SYSTEM_NAME.
Table 1-1 Release Considerations and Restrictions for Windows Driver (continued) SQLSpecialColumns Function This function does not support pattern value arguments for table names, and returns an optimal set of columns that uniquely identifies a row in the table information for a specified table name. SQLStatistics Function This function does not support pattern value arguments for table names, and returns index information for a specified table name.
Neoview Platform Specific Extensions and Attributes Handling Larger Row Counts SQL_ATTR_ROWCOUNT64_PTR For 32-bit applications, when the number of rows affected by an UPDATE, INSERT, or DELETE operation exceeds 2,147,483,647 rows, SQLRowCount will return an error with a diagnostic message that an overflow occurred. In this case, an application can use the SQL_ATTR_ROWCOUNT64_PTR attribute in a SQLGetStmtAttr call to retrieve the actual rows affected into a 64-bit integer.
if (retcode == SQL_SUCCESS || retcode == SQL_SUCCESS_WITH_INFO) { /* Set the ODBC version environment attribute */ retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0); if (retcode == SQL_SUCCESS || retcode == SQL_SUCCESS_WITH_INFO) { /* Allocate connection handle */ retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc); if (retcode == SQL_SUCCESS || retcode == SQL_SUCCESS_WITH_INFO) { /* Set job id to 2468.
rc = SQLSetConnectAttr(hdbc, SQL_ATTR_APPLNAME, value, strlen(value)); . . . #include SQLHENV SQLHDBC SQLHSTMT SQLRETURN “hpsqlext.
• • • • • • • Query ID (SQL_CHAR) CPUTime (SQL_DOUBLE): An estimate of the number of seconds of processor time it might take to execute the instructions for this query. A value of 1.0 is 1 second. IOTime (SQL_DOUBLE): An estimate of the number of seconds of I/O time (seeks plus data transfer) to perform the I/O for this query. MsgTime (SQL_DOUBLE): An estimate of the number of seconds it takes for the messaging for this query.
Return: SQL_SUCCESS=0 Get Data All: "QueryID", "CPUTime", "IOTime", "MsgTime", "IdleTime", "TotalTime" "Cardinality" "MXID115000897212014649972695973_60_STMT_INFOSTATS ", 0.0986710164301648, 0.1023000010183761, 129.0 0.0980000013441895, 0.0980000013441895, 0.1023000010183761, 129.0 1 row fetched from 7 columns. Unsupported ODBC API Functions and Data Types API Functions This release of HP Neoview ODBC driver does not support the following ODBC 3.
2 HP Neoview ODBC Drivers Overview for UNIX Open Database Connectivity (ODBC) is a widely accepted application programming interface (API) for database access. It is based on the Call-Level Interface (CLI) specifications from X/Open and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language. ODBC is designed for maximum interoperability — that is, the ability of a single application to access different database management systems (DBMSs) with the same source code.
Driver components can be installed on any workstation running Linux, HP-UX, or IBM AIX®. These are the client components: MXODSN file Text file that contains client data sources. Sample program Run the sample program to verify a connection for HP Neoview ODBC Linux, HP-UX (32 and 64-bit), and IBM AIX® drivers. HP Neoview ODBC driver Is 3.0 compliant and implements a subset of the ODBC 3.51 APIs. Enables an ODBC client application to access the Neoview database.
Client Data Sources Client data sources reside on a client workstation. Each client data source is a logical name that identifies the attribute values used to connect to NDCS. Edit your data source configuration file (MXODSN) to add a new data source or change the data source configuration. NOTE: If an ODBC client tries to connect to a server data source that is stopped, NDCS rejects the connection. Setting the Client Character Set For UNIX ODBC Drivers, the default client character set is ISO88591.
UCS2 Translation The datasource attribute, UCS2Translation, controls whether the driver translates application data when inserting or retrieving data from UCS2 columns if the ISO mapping is ISO88591 and the client locale is the default. • If UCS2Translation is specified and set to 0, the driver does not translate application data. Use this setting to preserve the behavior of earlier versions of the drivers for UNIX. • If UCS2Translation is absent or has a value other than 0, translation occurs.
Password Expiration NDCS is configured to allow the driver to display password expiration warnings. If you receive a warning, you can continue your session, but you should change your password with NCI or HPDM as soon as possible. If you are using HPDM or NCI to connect and you get a password expiration warning, you are prompted to change your password and then log on to the session. Password Encryption Neoview clients require the user to present a password in order to log on.
• • You can configure the Neoview platform to notify you when your password will soon expire. You can change your LDAP password, using the NCI ALTER PASSWORD command described in the Neoview User Management and Security Administration Guide, provided that the grace count configured on the LDAP server has not been exhausted. NOTE: The Neoview platform does not provide means for a customer ODBC application to change the password of an LDAP user.
IMPORTANT: You must have write permission for the certificate directory. If you do not, the download fails and an error is returned. NOTE: The most common way to identify the home directory is the HOME environment variable. If that variable is not set on the workstation, the security framework uses the HOMEDRIVE and HOMEPATH environment variables. If those variables are not set either, an error is reported.
SQL_QUERY_TIMEOUT = SYSTEM_DEFAULT If you specify the directory in multiple ways—for example, if you specify it at installation and then specify a different value in the connection string: 1. The connection attribute has higher precedence than 2. The connection string, which has higher precedence than 3. The value specified during ODBC driver installation, or in the MXODSN or odbc.
Table 2-1 Release Considerations and Restrictions for HP Neoview ODBC Drivers for UNIX (continued) SQLStatistics Function This function does not support pattern value arguments for table names, and returns index information for a specified table name. SQLTables Function Returns all schemas defined in the SQL metadata. When SchemaName is: Returns all object types supported by SQL.
• • For information on the necessary data source configuration options, you will need to add to the respective configuration files (for example, to odbc.ini). You must configure the following data source attributes. For an example of configuration values, refer to the MXODSN file template provided with the installation. This is an example: DESCRIPTION = Default Data Source Catalog = CAT Schema = SCH DataLang = 0 FetchBufferSize = SYSTEM_DEFAULT Server = TCP:arc0101.caclab.cac.cpqcorp.
NOTE: If you reuse the same job ID over time, all work done under that ID is assumed to be related to the same job. Such reuse over a long period of time can result in undefined statistical aggregation, because some aged work statistics might have been archived and removed from the active statistics repository. Example In the following example, an application allocates environment and connection handles.
To use this feature, include the Neoview-specific header file called hpsqlext.h in your application, and specify the connection attribute SQL_ATTR_APPLNAME before the connection is established. Once the connection is established, you may not change the attribute value. Use the ODBC API SQLSetConnectAttr to set a connection attribute. Use the ODBC API SQLGetConnectAttr to retrieve the current value.
Compression is off by default. You can enable it: • By setting compression = 1 in either the MXODSN file or the odbc.ini file.: [TDM_Default DataSource] Description Catalog Schema DataLang FetchBufferSize Server SQL_ATTR_CONNECTION_TIMEOUT SQL_LOGIN_TIMEOUT SQL_QUERY_TIMEOUT Compression = = = = = = = = = = TDM_Default_DataSource NEO ODBC_SCHEMA 0 SYSTEM_DEFAULT TCP:wmb0101.tst.hp.com:3200 NO_TIMEOUT SYSTEM_DEFAULT SYSTEM_DEFAULT 1 • Or you can set compression = 1 in the connection string.
Example of INFOSTATS Suppose an application prepares a SELECT statement: “SELECT * FROM T1”. Use SQLGetCursorName to find the statement name. In this example, the returned statement name is SQL_CUR_3. To get statistics for “SELECT * FROM T1”, the application must allocate another statment handle and issue SQLExecDirect on INFOSTATS SQL_CUR_3. The statistics are returned as a result set. Use SQLFetch to retrieve the result.
Restricted ODBC API Functions SQLBindParameter The SQLBindParameter function has these restrictions: • • SQL_DEFAULT_PARAM is not supported for the pcbValue argument. The SQL_LEN_DATA_AT_EXEC(length) macro is not supported for the pcbValue argument.
3 HP Neoview Unicode Driver for Windows The HP Neoview Unicode driver allows an application to provide and retrieve Unicode data using an ODBC interface for access to the Neoview database. The driver translates as necessary between the client character set (locale) and the character encoding in the database. Applications that are not Unicode-enabled also work with Unicode driver.
of a function is identifiable by the suffix W. You can use any of these functions with the Neoview Unicode driver. Some ODBC API functions, for example SQLBindParameter , let you declare the data type of the argument in the function call. Such functions do not have different versions for Unicode and ANSI. For more information about ODBC functions that have Unicode versions, refer to the Microsoft Developer Online Library at http://msdn.microsoft.com/en-us/library/ms716246(VS.85).aspx.
• • • On insertion, if character data presented by a Unicode-enabled application exceeds the size of the database column, the Unicode driver truncates the data and reports an error to the client. On a fetch, if character data retrieved from the database exceeds the maximum length of the client's data buffer, the Unicode driver truncates the data and reports an error to the client. Error messages are in English. A Unicode application retrieves error messages in UTF-16 encoding in wide character buffers.
4 HP Neoview Unicode Driver for UNIX The HP Neoview Unicode driver allows an application to provide and retrieve Unicode data using an ODBC interface for access to the Neoview database. The driver translates as necessary between the client character set (locale) and the character encoding in the database. Applications that are not Unicode-enabled also work with Unicode driver.
Unicode also defines “wide” SQL data types.
5 Accessing Neoview SQL Data From Microsoft ODBC .NET Data Provider The Microsoft .NET framework is a Windows component that supports building and running applications and XML Web services. For more information about Microsoft .NET framework, see http://msdn.microsoft.com/en-us/netframework/default.aspx. Neoview Release 2.4 provides the ability to use the ODBC .NET Data Provider collection of classes.
Class Name Description OdbcPermission Enables the .NET Framework Data Provider for ODBC to help make sure that a user has a security level sufficient to access an ODBC data source. OdbcPermissionAttribute Associates a security action with a custom security attribute. OdbcRowUpdateEventArgs Provides data for the RowUpdated event. OdbcRowUpdatingEventArgs Provides data for the RowUpdating event. OdbcTransaction Represents an SQL transaction to be made at a data source. ODBC .
reader.Close() End Using End Sub ODBC .NET Environment Setup To set up the ODBC .NET environment, you must download and install the .NET framework SDK, version 3.5 or later from the Microsoft download website: http://msdn.microsoft.com/en-us/ netframework/default.aspx If you have not already done so, you must download and install Microsoft Visual Studio 2005 or newer from the Microsoft download website: http://msdn.microsoft.com/en-us/vs2005/ aa718332.
Sample Application Code Using ODBC .NET Data Provider To use the ODBC .NET Data Provider, the application must import the System.Data.Odbc namespace. For example, • Visual Basic imports System.Data.Odbc • C++ uses namespace System::Data • C# uses System.Data.Odbc The following source code samples demonstrate setting up (tear down) the connection to the data source. • Visual Basic Dim connString As String = "DSN=neo_datasrc;UID=userid,PWD=passWd" Dim myConn As New OdbcConnection(connString) ... myConn.
6 Configuring Client Data Sources If you are configuring client data sources on Linux, HP-UX, IBM AIX®, and Sun Solaris see “Configuring the Client Data Source on Linux, HP-UX, IBM AIX®, and Sun Solaris”. To configure client data sources on Windows, use the Microsoft ODBC Administrator to add, configure, and remove HP Neoview ODBC Driver data sources. For information about supported versions of Windows, see “Driver Components”.
3. 4. Select the data source name you want to reconfigure, and then click Configure. Each tab in the configuration view displays different fields in the data source configuration. Make the required changes. For more information about a tab, click Help. Configuring ODBC Client Data Sources for Update Operations To perform “update . . .
4. 5. 6. Select the Log file Path you want to use. Use the Browse button to locate the correct log file. Click Start Tracing Now. Click Apply then OK. Stop Tracing on a Client Data Source 1. Bring up the Microsoft ODBC Administrator: Start> Programs> HP ODBC 2.0> MS ODBC Administrator 2. 3. 4. Select the Tracing tab. Click Stop Tracing Now. Click Apply then OK. Enabling Connection Pooling The connection pooling mechanism is enabled by the client ODBC application.
6. Make the connection. Call SQLConnect or SQLDriverConnect. The driver manager uses the connection options and the SQL_ATTR_CP_MATCH attribute to determine which connection in the pool to assign to the application. 7. Set connection attributes.
ERROR, WARNING, and additional messages for CONFIG. The values are listed in the following table. Name Description ERROR Indicates some failed SQL calls and communications problems. WARNING Triggered by anything that generates a diagnostic record. CONFIG Provides details of configuration calls. INFO Provides details of what calls are made and other important markers. DEBUG Shows the detailed contents of many calls.
7 HP Neoview ODBC Drivers Conformance This section contains tables that describe the HP Neoview ODBC driver conformance to standard ODBC API functions and SQL conformance levels.
Table 7-2 Obtaining Information About a Driver and Data Source Function ODBC Version Supported by HP ODBC Description SQLDataSources 1.0 Yes Returns the list of available data sources. Implemented by the Driver Manager. SQLDrivers 2.0 Yes Returns the list of installed drivers and their attributes. Implemented by the Driver Manager. SQLGetInfo 1.0 Yes Returns information about a specific driver and data source. SQLGetFunctions 1.0 Yes Returns supported driver functions. SQLGetTypeInfo 1.
Table 7-5 Preparing SQL Requests Function ODBC Version Supported by HP ODBC Description SQLPrepare 1.0 Yes Prepares an SQL statement for later execution. SQLBindParameter 2.0 Yes Assigns storage for a parameter in an SQL statement. SQLGetCursorName 1.0 Yes Returns the cursor name associated with a statement handle. SQLSetCursorName 1.0 Yes Specifies a cursor name. SQLSetScrollOption 1.0 No Sets the option that controls cursor behavior.
Table 7-7 Retrieving Results and Information About Results (continued) Function ODBC Version Supported by HP ODBC Description SQLFetch 1.0 Yes Returns multiple result rows. SQLFetchScroll 3.0 Yes Supported for SQL_FETCH_NEXT attribute only. Returns scrollable result rows. SQLGetData 1.0 Yes Returns part or all of one column of one row of a result set (useful for long data values). SQLExtendedFetch 1.
Table 7-8 Obtaining Information About a Data Source’s System Tables (continued) Function ODBC Version Supported by HP ODBC Description SQLPrimaryKeys 1.0 Yes Returns a list of column names that make up the primary key for a table. See the “Release Considerations and Restrictions” (page 23) SQLProcedureColumns 1.0 Yes Returns the list of input and output parameters, as well as the columns that make up the result set for the specified procedures. SQLProcedures 1.
Table 7-9 Terminating a Statement (continued) Function ODBC Version Supported by HP ODBC Description SQLCancel 1.0 Yes Closes a cursor that has been opened on a statement handle. See the “SQLCancel Function” (page 24) SQLEndTran 3.0 Yes Commits or rolls back a transaction. Table 7-10 Terminating a Connection Function ODBC Version Supported by HP ODBC Description and Notes SQLDisconnect 1.0 Yes Closes the connection. SQLFreeHandle 3.
Table 7-11 Numeric Functions (continued) ODBC Function SQL Equivalent Function POWER POWER RADIANS RADIANS RAND RAND ROUND Not supported in this release. SIGN SIGN SIN SIN SINH SINH SQRT SQRT TAN TAN TANH TANH TRUNCATE Not supported in this release. Table 7-12 String Functions ODBC Function SQL Equivalent Function ASCII ASCII CHAR CHAR CONCAT CONCAT DIFFERENCE Not supported INSERT INSERT LCASE LOWER LEFT SUBSTRING LENGTH Supported, but no equivalent SQL function.
Table 7-13 Time and Date Functions ODBC Function SQL Equivalent Function CURDATE, CURRENT_DATE CURRENT_DATE CURTIME, CURRENT_TIME CURRENT_TIME DAY DAY EXTRACT EXTRACT DAYNAME Not supported DAYOFMONTH Not supported DAYOFWEEK DAYOFWEEK DAYOFYEAR DAYOFYEAR HOUR HOUR MINUTE MINUTE MONTH MONTH MONTHNAME MONTHNAME NOW Supported, but no equivalent SQL function.
Table 7-15 ODBC Data Types ODBC Data Type SQL Data Type Supported by HP ODBC CHAR(n) CHAR(n) Yes VARCHAR(n) VARCHAR(n) * Yes DECIMAL(p,s) DECIMAL(p,s) Yes NUMERIC(p,s)** NUMERIC(p,s) Yes SMALLINT SMALLINT Yes INTEGER INTEGER Yes REAL REAL Yes FLOAT(p) FLOAT(p) Yes DOUBLE PRECISION DOUBLE PRECISION Yes BIT Not supported No TINYINT Not supported No TINYINT UNSIGNED Not supported No BIGINT LARGEINT Yes BINARY(n) Not supported No VARBINARY(n) Not supported No LONG
Extended Numeric Precision Columns Extended numeric precision columns refer to columns which are defined as either NUMERIC(x,y) signed, where x > 18, or NUMERIC(x,y) unsigned, where x > 9. The Neoview ODBC drivers support the following conversions to and from extended numeric precision columns: • SQL_C_CHAR • SQL_C_FLOAT • SQL_C_DOUBLE Unsigned Data Types Unsigned data types are treated differently, according to the version of ODBC used, and whether the SQL_ATTR_MSACCESS_VERSION flag is set.
Transactions and Cursor Behavior with Multiple Statements AUTOCOMMIT is a connection-level attribute describing the semantics of transaction demarcation. AUTOCOMMIT ON defines the semantics where the underlying system automatically commits the current transaction at statement completion. COMMIT has secondary effects on open cursors, SELECT statements in an OPEN state, having position in a result set.
8 HP Neoview ODBC Drivers Messages HP Neoview ODBC Drivers Error Codes Timestamps for all driver error messages appear immediately following the SQL error text. HP Neoview ODBC Client Messages When an ODBC API call returns SQL_ERROR or SQL_SUCCESS_WITH_INFO, an associated SQLSTATE value can be obtained by calling SQLGetDiagRec with the appropriate arguments.
SQLSTATE Message 08S02 Transport layer error. 08001 No more NDCS servers available to connect. SQLSTATE Message 21001 Cardinality violation; insert value list does not match column list. 21002 Cardinality violation; parameter value list does not match column list. 21S01 Cardinality violation; insertion value list does not match column list. 21S02 Cardinality violation; parameter list does not match column list. 22001 String data right truncation.
SQLSTATE Message IM001 Driver does not support this function. IM009 Unable to load DLL. SQLSTATE Message S0001 Invalid table name; base table or view already exists. S0002 Invalid table name; table or view not found. S0011 Invalid index name; index already exists. S0012 Invalid index name; index not found. S0021 Invalid column name; column already exists. S0022 Invalid column name; column not found. SQLSTATE Message S1000 General error.
SQLSTATE Message S1094 Invalid scale value. S1095 Function type out of range. S1096 Information type out of range. S1097 Column type out of range. S1098 Scope type out of range. S1099 Nullable type out of range. SQLSTATE Message S1100 Uniqueness option type out of range. S1101 Accuracy option type out of range. S1102 Table type out of range. S1103 Direction option out of range. S1105 Invalid parameter type or parameter type not supported. S1106 Fetch type out of range.
Indicates that an error occurred during password processing. The following table lists possible errors and what you can do about them: Error Code and Text Description and Recovery [29713] Certificate file name is not found.
Error Code and Text Description and Recovery [29723] Directory name not found. The specified directory does not exist on the workstation. The CERTIFICATEDIR attribute, if present, must specify an existing directory. If you omit the CERTIFICATEDIR attribute, then the HOME environment variable or the HOMEDRIVE and HOMEPATH variables must identify an existing directory. [29702] Internal error: Session key generation These messages signify internal errors. Please report them to HP failed Support.
Indicates that an error occurred during password processing or certificate management operations. The following table lists possible errors and what you can do about them. Error Code and Text Description and Recovery [4400] Internal error [4401] No privileged segment [4405] No shared segment in security server [4410] Digest mismatch [4417] Error in shared segment These messages signify internal errors. Please report them to HP Support.
Index Symbols .NET data provider and Neoview ODBC driver, 54 classes, 53 sample application, 56 .
Date/Time values, partial, 72 DATETIME, 72 DAY function, 70 DAYNAME function, 70 DAYOFMONTH function, 70 DAYOFWEEK function, 70 DAYOFYEAR function, 70 DECIMAL data type, 71 DEGREES function, 68 descriptor fields, functions for setting and retrieving, 64 DIFFERENCE function, 69 Documents, related information, 11 DOUBLE PRECISION data type, 71 driver components of, 15, 31, 32 Unicode, 47 Unicode for UNIX, 51 Driver manager, Microsoft ODBC See Microsoft ODBC driver manager, 15, 32 E Encryption, 19, 35 error c
connection attributes for secure login and role selection, 36 ODBC driver for Windows password handling, 19 ODBC error codes, 78 ODBC for Windows Password braces as delimiters in .
SQLPrepare function, 65 SQLPrimaryKeys function, 23, 38, 67 SQLProcedureColumns function, 67 SQLProcedures function, 67 SQLPutData function, 65 SQLRowCount function, 65 SQLSetConnectAttr function, 64 SQLSetCursorName function, 65 SQLSetDescField function, 64 SQLSetDescRec function, 64 SQLSetEnvAttr function, 64 SQLSetPos function, 66 SQLSetScrollOption function, 65 SQLSetStmtAttr function, 64 SQLSpecialColumns function, 67 SQLStatistics function, 24, 39, 67 SQLTablePrivileges function, 67 SQLTables function
