Oracle Database 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 Oracle Database 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: January 23, 2020.
New And Noteworthy
- Validated support for Oracle 18c. (71775)
- Set the default connection protocol to Oracle 12c with backwards compatibility for Oracle 11g. (56774)
- Added support for the Native Query Block using SQL. (54548)
- Added support for the Execute Block to run ExecuteNonQuery and ExecuteScalar SQL commands. ( 56044, 56045)
Note: Native Query, ExecuteNonQuery, and ExecuteScalar do not support executing Stored Procedures.
Closed Issues
8971
For an existing Oracle Connection, if the Connection dialog was opened and the Agent displayed in the Test field was not installed on a server with the Oracle client, an error occurred and the connection fields were inaccessible even when the correct Agent was selected later.
47608 / 47633 / 53503 / 69405 / 69919
Enhanced performance by implementing metadata caching to limit the number of times the Connector retrieves metadata. (Case # 58558, 66873, 68401, 01719015, 01728522, 01726999)
59466 / 61173
Replication Solutions where Oracle database was the target attempted to create tables more than once causing the initial replication to fail. (Case # 63631, 01723814)
74144
When there were multiple Views with the same name in different schemas, the Connector sometimes selected incorrect metadata generating errors similar to the following: (Case # 69350, 01729470)
ERROR: Exception Type : InvalidExecuteQueryException
Message : The following error has occurred in the Oracle Connector: ORA-00904: "VIEW1"."F2" invalid identifier
74522
Using a Replication Solution to replicate data to an Oracle Database where a source table had a Primary Key Field with a name over 23 characters long, failed after the first replication with errors similar to the following: (Case # 69515, 01729635, 01730223)
ORA-00904: "new_testentity2xxxxxxxxxxxxxxxxxxxxxxxxxxxxid": invalid identifier: Failed to delete existing record
Known Issues
SCORA-214
Summary: In a Query or Fetch Block, filtering records using equals to check whether two GUIDs contained in string fields of length 32 match, returns no records even if there are matching records. Using the same filter set to is not equal to returns all records including those where the two GUIDs do match.
Workaround: None.
SCORA-213
Summary: Operation results are not returned for operations that have run successfully nor are RecordsMatched values included for Fetch and For Each Child Blocks.
Workaround: None.
SCORA-212
Summary: Configuring an Oracle Database Connection with a UserName that is greater than 30 characters is not supported and generates errors similar to the following:
Connection test failed: Invalid value for key 'User ID'.
Workaround: Modify your User Name in Oracle Database to make it less than 30 characters.
SCORA-191
Summary: The field description displayed when hovering over a field on the Block Properties Fields tab displays the .NET data type instead of the native data type. For example, a field with native data type VARCHAR2(20) displays as System.String.
Workaround: None.
71773 / 70399
Summary: Number fields with a large number of digits to the right of the decimal point generate overflow errors. (Case # 67213)
Workaround: None.
Summary: Many Oracle databases have a large number of tables, views, stored procedures, etc. This large amount of data can cause a timeout error in TIBCO Scribe® Online similar to the error below, when trying to retrieve the complete list.
Error: The command request timed out.
Workaround: Create a User or Synonym that only has access to the specific objects you need to reference in TIBCO Scribe® Online. Configure the TIBCO Scribe® Online with that user.
March 2016 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
10529
When using Oracle as a target, translations for entity names that exceeded Oracle field size limitations were not always correct. (Case # 75809 )
10531
When running a Replication Services (RS) Solution to replicate the Competitor entity, a column heading was being removed from a lookup file when the replication ran. This caused the replication to fail and generated a " Column does not exist" error. (Case # 75809 )
Fall 2015
New And Noteworthy
The Oracle Connector was installed automatically with any Agent installation. In this release, the Oracle Connector has been moved to the TIBCO Scribe® Online Marketplace. (1802, 1809)
Closed Issues
There are no Closed Issues in this release.
October 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
8096
Oracle Connector was missing from the Connector drop-down list for Agents installed on Windows 64-bit computers. ( Case # 54713)
March 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6940
Using synonyms resulted in no tables shown when connecting using the Oracle Connector (Case # 49177)
