Release Notes > Connector and connectivity issues > Oracle Connector
  

Oracle Connector

Fixed issues

The following table describes fixed issues:
Issue
Description
SCAN-12628
Test Connection for catalog sources fails with the following error: "destination index -1 out of bounds for byte[128]"
(October 2024)
SCAN-11027
Metadata extraction jobs fail with the following error: InvalidInputException: Unable to parse script.
(October 2024)
CDGC-65601
When you run an Oracle catalog source job in an Azure environment, metadata extraction fails with the following error: ElasticsearchContentPublisher retry failed.
(July 2024)
CDGC-37509
Data profiling tasks for Oracle catalog sources fail if the source data contains a schema, table, or column name with a forward slash (/) in the name.
(July 2024)

Known issues

The following table describes known issues:
Issue
Description
SCAN-13543
You can't specify parameter values for an Oracle Data Integrator catalog source that includes mappings that are parameterized.
(November 2024)
SCAN-14516
When you run an Oracle Data Integrator catalog source job with a filter to include metadata from objects with names that contain regex special characters such as [, ], {, }, ^, ., |, +, and $, no objects are extracted. If this is the only filter included, then the job fails with the following error:
No graphs were provided by module(s) 'OdiCdgcReaderModule'
Workaround:
Replace the special characters with wildcards such as a question mark "?" or an asterisk "*".
(November 2024)