OLE DB 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 OLE DB 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.3.1

Released February 13, 2020.

New And Noteworthy

Closed Issues

55946 / 56088 / 57205 / SCOLEDB-101

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)

63464 / SCOLEDB-97

For OLEDB 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.

57205 / SCOLEDB-1

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)

Known Issues

55946 / 56504 / 56897 /SCOLEDB-84 / SCOLEDB-88

Summary: For each record being inserted into a target database, the Create and Update/Insert Blocks are executing a “Select from target table” command with no where clause causing all records to be returned. (Case # 62412, 62615, 01722683, 01722883)

Workaround: Contact Support for hotfix 56088.

Fall 2015 Release

New And Noteworthy

The OLE DB Connector was installed automatically with any agent installation. In this release, the OLE DB Connector has been moved to the TIBCO Cloud™ Integration - Connect Marketplace. (1802, 1809)

Closed Issues

There are no Closed Issues in this release.

March 2012 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

5941 / 5942

Invalid column name 0' when using the new OLE-DB connector as source — The error message "invalid column name '0'" appeared as a fatal error in the Execution History. This occurred when running an Integration app that used an OLE DB connector as a source and defined a filter with a SQL “tinyint” data type and setting the value to 0.

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.

Related Topics

Release Notes And Known Issues