My Oracle Support Banner

OEMM Oracle Database (via JDBC) Bridge Fails to Import a Database View when the View TEXT_LENGTH is Greater than 32768 Characters (Doc ID 2313485.1)

Last updated on SEPTEMBER 14, 2022

Applies to:

Oracle Enterprise Metadata Management - Version 12.2.1.1 to 12.2.1.1
Information in this document applies to any platform.

Symptoms

NOTE: In this article, values used in errors, examples, and images represent a fictitious sample for clarity.  These and any value placeholders including <> which surround the placeholders should all be replaced by the actual values used in your environment. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.

On Oracle Enterprise Metadata Management (OEMM) 12.2.1.1 version, when a TEXT_LENGTH for an Oracle Database View is greater than 32768, the Oracle Database (via JDBC) bridge does not harvest the entire view text. 

The import is not aborted and it completes successfully, but, the following messages are showed in the harvesting log:


When selecting the "View Statement" property in the OEMM Properties tab thru the OEMM web interface, it is possible to determine that the view text was cut off.

Below is snapshot of the "Properties" palette on the OEMM GUI interface where it is possible to verify the view text after the harvest into OEMM repository:




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.