How can I dismiss the profiling error message in Data Preparation?

Jim English-Oracle

Creating a dataset using Oracle DB tables. After creating the Definition and clicking OK, I'm getting an error

There was an error profiling your dataset. Click the Profile button to run the profile again. Error code = 17010

Clicking Profile gives the same error. I've disabled the Toggle Quality Tiles and Use Sample Data options in the lower right corner. However, I can't dismiss the profile error and move to the Data Preparation screen. I'm stuck at the error message can't save or edit.

Luis E. Rivas -Oracle

@Jim English-Oracle - what is most likely the cause of the error is reserved words in the object names. Have you tried going to the ADW connection and going to the advanced tab and selecting Double Quotes as the quoting identifier and trying again? The issue should be resolved after this - let me know if it doesn't.

User_90353

Hello,

I had the same problem. I tried removing special characters or spaces first, but that didn't help. What finally helped was that I adjusted the length of the column names. Apparently there is some limitation from Oracle. I hope this helps someone.

Cheers!

Jakub

Jim English-Oracle

Also, while the Profiling, the message 'You can start editing this dataset table in metadata view' with a Start Editing button appears. Clicking the button gives the Profile Error message. There seems no way to disable profiling.

TetyanaH-Oracle

Hi Jim,

Since you can't disable profiling, check if the following MOS document helps to resolve the error:

OAC Errors Profiling Dataset - Error Occurs While Calling Remote Service & [JDSError: 115] Invalid Database Name (Doc ID 2815980.1)

- Make sure that column names in the source View do not have any special characters or spaces. You can replace space or dot (if any) with underscore character (_).

Example: "City Name" => "City_Name" , "City.Name" => "City_Name"

--Test if using column names with all UPPER CASE works.

If above is not applicable and data set creation still fails, please consider opening a Service Request with Oracle Support to investigate further.

Thanks,

Tetyana