Best way to handle clob fields?

Hi Stefan,

Thanks for reaching out to Yellowfin Support.

This issue mostly occurs due to whenever You tried to perform an operation between two different datatypes, but the datatypes are not compatible(it means inconsistent) it shows the error as mentioned below.

Option 1 :

To correct this error, you can do one of the following:

• Not use the LIKE condition in your SQL (against the LONG datatype field).
• Consider modifying your table so that the supplier_name field is either a VARCHAR2 or CHAR field.
• Try writing a custom PLSQL function to convert a LONG to a VARCHAR2.

Option 2 :

To correct this error, you can do one of the following:

• Not use Oracle functions in your SQL (against the LONG datatype field).
• Consider modifying your table so that the supplier_name field is either a VARCHAR2 or CHAR field.
• Try writing a custom PLSQL function to convert a LONG to a VARCHAR2.

Regards,

Sri Vamsi

Hi Stefan,

Hope things are good on your end. Just wanted to check in to make sure you had what you needed here.

Regards,

Sri Vamsi

Hi Stefan,

I just want to touch base to see if you had chance to read through my response. If you can let me know that would be great.

Regards,

Sri Vamsi

Hi Stefan,

Thanks for your reply.

Unfortunately, there aren't any options in yellowfin. However, I've logged this Enhancement request on your behalf with the Product Team for further review.. Such requests will be reviewed by our Product Team and implemented based on feasibility, level of positive impact on the user experience, and votes from the community.

This post will be updated with any future information relevant to this process. Can I mark this ticket as completed.

Regards,

Sri Vamsi

Hi,

Sorry, but I have to ask again.

If I have a CLOB field in a view, then the content is shown to me in the data preview, the column type specified as varchar. Actually looks good (= varchar).

If I use this "Varchar (clob)" column in the report - without change, just display, I get the error message above from my question. Why actually and why then not in the view preview?
---
If I use a DB procedure in the view to change Clob to Varchar, I get the same error message already in the view and the preview shows no more data. Nevertheless the column works in the report.
Does this fit together for you?

;) Stefan

Hi Stefan,

Sorry for the delay in response.

Could you please share the error messages/logs you are getting while using "Varchar (clob)" column in the report.

Regards,

Sri Vamsi

Hi Stefan,

Can you please upload the entire log files in https://ftp.yellowfin.bi/files/ and specify the file name , this site is protected.

Regards,

Sri Vamsi

Hi Stefan,

The issue you are facing with CLOB fields in your Oracle data source is likely due to the large size of the data in those fields. In Oracle, a CLOB data type can store up to 4 GB of data, which is much larger than the maximum size of other data types like VARCHAR2.

When you are trying to view the data in the "Prepare" section of Yellowfin, it may be encountering issues with processing and displaying the large CLOB data.

One solution to this issue is to modify the SQL query used to retrieve the data from Oracle to only select the first few characters of the CLOB field, instead of the entire field. This will reduce the size of the data returned and may prevent the error you are encountering in the "Prepare" section of Yellowfin.

Another option is to create a view in Oracle that selects only the necessary columns and truncates the CLOB field to a smaller size. This view can then be used as the data source in Yellowfin.

Finally, if you are able to access and modify the database schema, you may consider changing the data type of the CLOB fields to a more appropriate data type if possible, such as VARCHAR2 or BLOB, depending on the data stored in the fields.

It's important to note that if you are able to view the data in reports, it means that the data is being retrieved and processed correctly, and the issue may only be related to the size of the data in the "Prepare" section of Yellowfin.

Regards,

Sri Vamsi

Hi Stefan,

I just want to touch base to see if you had chance to read through my response. If you can let me know that would be great.

Regards,

Sri Vamsi

Hi Stefan,

I'm going to go ahead and mark this ticket as Completed due to inactivity at this time. Feel welcome to reach out in the future.

Regards,

Sri Vamsi