ODBC Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector For ODBC for more information.
Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.
Version 1.4.0
Released March 19, 2025
New And Noteworthy
-
This update introduces the Disable Prepend Schema field for greater control over the metadata. By default, the value is set to false and the schemas are prepended. Set this field to true to remove the schema prefix. (SCODBC-226)
-
The Execute block is introduced to run SQL Command methods. Use ExecuteNonQuery for SQL statements that do not return results and ExecuteScalar for SQL statements that return a single value.
Note: ExecuteNonQuery and ExecuteScalar do not support executing stored procedures.
Closed Issues
SCODBC-331
The TIBCO Scribe® Online Connector for _____ ODBC update fails with the following error: (Case #02134799)
ERROR [42S02] [SAP][ODBC Driver][SQL Anywhere]Table 'tlc_crm_pers' not found
SCODBC- 217, 328
Operations such as INSERT or UPDATE on the NUMBER, FLOAT INT, or INTEGER datatypes fail with a CAST error. (Case #02197563)
SCODBC-216
On not selecting a tablename in order by clause, MySQL Query with Net Change fails. (Case #02182924)
SCODBC-215
When performing the DELETE operation in SQL, Sybase, or ETC as a non-DBA user, the delete statements do not include a schema name. (Case #02134799)
Known Issues
SCODBC-349
Summary: On inserting a record with Unicode and ASCII symbols, the data displays correctly in the table but shows as ???????? in the query block preview.
Workaround: None.
SCODBC-177
Summary: In some cases, if an ODBC driver fails to delete a record in a target datastore, the failure exception is not recognized by the Connector and the processed record may be counted as successful in the execution history.
Workaround: Try using a different ODBC driver.
57424
Summary: When using the ODBC Connector to connect to NetSuite, Lookup Blocks return all records if no matching criteria is specified instead of the default maximum of two.
Workaround: None.
56679 / 73074 / SCODBC-205
Summary: ODBC connections that use Iseries drivers generate errors similar to the following when attempting to update/insert data. (Case # 62378,66933, 01722649, 01727059, 01883713)
ERROR [42000] [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0104 - Token DEFAULT was not valid. Valid tokens: : <INTEGER>.
Workaround: None.
39521 / 39522 / SCODBC-10 / SCODBC-11
Summary: In some cases, Delete and Update operations fail if you are using a database with multiple schemas.
Workaround: Make sure that the schema that should be used is the default schema for the user credentials on the ODBC Connection dialog.
30931 / SCODBC-169
Summary: PostgreSQL ODBC connections are not supported.
Workaround: Use the PostgreSQL Connector instead. See TIBCO Scribe® Online Connector For PostgreSQL.
Version 1.3.1
Released February 13, 2020.
New And Noteworthy
- Added a EULA specifically for this Connector that can be accessed from the License Information section of the Connector Help.
- Rebranded the Connector as a TIBCO Scribe® Online Connector.
- Enhanced logging used for diagnostics. (SCODBC-9)
Closed Issues
63464 / SCODBC-113
For ODBC connections to SQL Server, using a Query Block and Lookup Block that connect to different tables in the same database caused errors similar to the following: (Case # 64700, 01724855)
Connection is busy with results for another command.
40686 / 40691 / 41324 / SCODBC-29
Net Change was not supported for some ODBC drivers. If Net Change was used, a fatal error similar to the following was generated: (Case # 57703, 01718238)
The following error has occurred in the ODBC Connector: ERROR [42000] [Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in query expression '``Companies``.`LastModifiedDate`'.
55946 / 56088 / 57205 / SCODBC-12
For each record being inserted into a target database, the Create and Update/Insert Blocks were executing a “Select from target table” command with no WHERE clause, causing all records to be returned. (Case # 62412, 62615, 01722683, 01722883)
Fall 2015 Release
New And Noteworthy
The ODBC Connector was installed automatically with any Agent installation. In this release, the ODBC Connector has been moved to the TIBCO Scribe® Online Marketplace. (1802, 1809)
Closed Issues
There are no closed issues in this release.
June 2014 Release
New And Noteworthy
There are no new features for this release.
Closed Issues
8707
ODBC Connections to a Progress DB 10.1C data source were not getting closed after a map ran, causing maps to fail once the maximum number of permitted connections was reached. (Case # 59303)
August 2013 Release
New And Noteworthy
There are no new features for this release.
Closed Issues
7727
Fatal Error: SQL Query timeout expired (Case # 51132)
July 2012 Release
New And Noteworthy
There are no new features for this release.
Closed Issues
6291
AS400 DB2 ODBC – We encountered an issue where some ODBC drivers that do not support index metadata yielded overflow errors when using arithmetic operations, among others. We fixed this issue and improved logging for invalid property metadata. (Case # 46736)
6374
Unable to see Entities using Oracle ODBC Connection – This issue manifested itself across SQL, ODBC, and OLEDB connectors in cases where two entities were reported with the same name but different cases, and a third entity, even, may exist with the same name and a numeric suffix (e.g., account, Account, Account2). This has been fixed such that we will be able to list these entities in the field lists without stack errors. (Case # 47001)
May 2012 Release
New And Noteworthy
For ODBC connectors, you can now choose to process the data in tables associated with a single schema. If left blank, TIBCO Scribe® Online will use all schemas for this Connection.
If you specify a single schema, you must refresh the metadata for this Connection after you create or edit it. Refreshing the metadata ensures that TIBCO Scribe® Online displays the expected tables in the Connections tab of the Create/Edit Map page.
Closed Issues
There are no closed issues in this release.
March 2012 Release
New And Noteworthy
There are no new features for this release.
Closed Issues
6005
ODBC and OLEDB connectors were not recognizing 24 hour clock for last mod dates — Entities are replicated every time for any map using OLE DB or ODBC as a source connection that has a Last Modified Date field defined. This was due to the fact that date-time values were erroneously not utilizing the 24-hour clock.
