cannot open view - system error inconsistency

Stefan Hall shared this problem 17 months ago
Resolved

After editing and saving a view, it can no longer be opened - "process stopped in order not to endanger consistency".

How can I fix this, the view is complex and I have invested a lot of time?

;) Stefan

ErrorMessage from log

ERROR (MIViewProcess) - [53] [EB7E622A] [/MIPreViewEdit.i4] View Problem Management(124537) was being loaded and the available field list was empty. Aborting with Inconsistency Error.ERROR (MIViewProcess) - [53] [EB7E622A] [/MIPreViewEdit.i4] Inconsistency Error detected. Aborting to maintain View integrity.

Best Answer
photo

Hi Stefan,

Thanks for reaching out.

Could you please help me with the following:

1. When did the issue started? After making any change to view/data source schema? or if any abrupt disconnection of data source?

2. /info,jsp of the environment.

3. Could you please enable DEBUG logging and replicate the issue? Once we have the replicated the issue, kindly share a screenshot of error message in the UI(if any) and also the debug logs from the same time (along with time stamp of error replication). We may upload the compressed logs to FTP: https://ftp.yellowfin.bi/ and help me with the name of the file uploaded.


I suspect it could be related to DISCONNECTED fields, could you please check if there are any? as per the article(Step 3) : https://community.yellowfinbi.com/knowledge-base/article/how-to-fix-fields-missing-from-step-2-of-view-builder-and-reports


Thanks,

Deepak

Replies (4)

photo
1

Hi Stefan,

Thanks for reaching out.

Could you please help me with the following:

1. When did the issue started? After making any change to view/data source schema? or if any abrupt disconnection of data source?

2. /info,jsp of the environment.

3. Could you please enable DEBUG logging and replicate the issue? Once we have the replicated the issue, kindly share a screenshot of error message in the UI(if any) and also the debug logs from the same time (along with time stamp of error replication). We may upload the compressed logs to FTP: https://ftp.yellowfin.bi/ and help me with the name of the file uploaded.


I suspect it could be related to DISCONNECTED fields, could you please check if there are any? as per the article(Step 3) : https://community.yellowfinbi.com/knowledge-base/article/how-to-fix-fields-missing-from-step-2-of-view-builder-and-reports


Thanks,

Deepak

photo
1

Hi Deepak,

very good information!

With the right search term "DISCONNECT", I could have found the article myself. I had tried with part of the error message.


But anyway, I was able to "fix" the fields and the view works again. Thanks a lot ;)

---

A question about the linked article:

Depending on your issue and release of Yellowfin we may suggest the inclusion of an extra DB parameter 'NEVERDISCONNECTFIELDS'

We have now had this error 2 times in a short time and connection problems could not be detected. (YF 9.8.0.1)

What is the "dark side" of this parameter, what is the risk?


;) Stefan

photo
1

Hi Stefan,

Thanks for the update. I am glad that it helped with our issue.

The only scenario I could think off is: if we have a data source where the fields are often changed / for some reason they get corrupted YF would still try to display those fields (may be showing wrong fields/results). If the data source/views fields wouldn't change then we can add the NEVERDISCONNECTFIELDS.

Please let me know if that helps.

Regards,

Deepak

photo
1

Hi Deepak,

perfect, now I have a good basis for decision. Currently, I will not add the parameter and wait to see if the problem occurs again. In this case I have a solution and set the parameter.

Happy New Year!
;) Stefan

photo
photo
1

Hi Stefan,

Thanks for the update.

I will go ahead and mark this as completed.

Happy New Year to you too :)

Deepak

Leave a Comment
 
Attach a file