Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Release Notes for October 2025
  3. Administrator
  4. API Center
  5. API Manager
  6. API Portal
  7. Application Integration
  8. B2B Gateway
  9. B2B Partners Portal
  10. Business 360 Console
  11. CLAIRE GPT
  12. Cloud Data Integration for PowerCenter (CDI-PC)
  13. Data Governance and Catalog
  14. Data Ingestion and Replication
  15. Data Integration
  16. Data Marketplace
  17. Data Profiling
  18. Data Quality
  19. Data Validation
  20. Human Tasks
  21. Integration Hub
  22. MDM - Customer 360 SaaS
  23. MDM - Product 360 SaaS
  24. MDM - Reference 360
  25. MDM - Supplier 360 SaaS
  26. Metadata Command Center
  27. Monitor
  28. Multidomain MDM SaaS
  29. Operational Insights

Release Notes

Release Notes

Oracle Connector

Oracle Connector

Fixed issues

The tables in this section describe recent fixed issues for Oracle connector in
Metadata Command Center
. Not all monthly releases include fixed issues.
November 2024 fixed issues
Issue
Description
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'
(November 2024)
October 2024 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]"
SCAN-11027
Metadata extraction jobs fail with the following error:
InvalidInputException: Unable to parse script.
July 2024 fixed issues
Issue
Description
CDGC-65601
When you run an Oracle catalog source job in an Azure environment, metadata extraction fails with the following error:
ElasticsearchContentPublisher retry failed
.
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.

0 COMMENTS

We’d like to hear from you!