Feedback
Did this article resolve your question/issue?

   

Article

"Optional feature not implemented" error received when cursor transaction isolation level "Read committed" is used with Teradata ODBC driver

Information

 
Title"Optional feature not implemented" error received when cursor transaction isolation level "Read committed" is used with Teradata ODBC driver
URL NameOptional-feature-not-implemented-with-Teradata-driver
Article Number000180929
EnvironmentProduct: Connect for ODBC Teradata driver
Version: 7.1
OS: all supported platforms
Database: Teradata
Application: all supported applications
Question/Problem Description
The below error is seen when cursor transaction isolation level "Read committed" is used. 
Steps to Reproduce
Clarifying Information
Call SQLSetConnectAttr(SQL_TXN_READ_COMMITTED=2).
Error Message[DataDirect][ODBC Teradata Client driver]Optional feature not implemented
Defect Number
Enhancement Number
Cause
Teradata only supports isolation levels 0 (read uncommitted) and 3 (serializable).
Resolution
Use isolation levels 0 (read uncommitted) or 3 (serializable) instead.
Workaround
Notes
Last Modified Date2/28/2017 12:36 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.