Skip to main content

Data recovery in Yellowfin

So, while you’re working in Yellowfin, maybe your finger slips and you click delete, or it happens while you are thinking about something else.  However it happens, you’ve done the inevitable, you’ve deleted your SQL datasource.

 

After you quickly add it again, you realize that just re-adding it doesn’t restore your views or reports.    The CEO will be doing his regular daily review of the organization in 20 minutes and he starts with the reports.

 

No problem.

 

Fire up your SQL database client, open the Yellowfin database and manually edit the following tables.

 

Restoring your Datasource

Open the ‘ReportViewSource’ table and look for your deleted datasource.   You’ll find it because it will have ‘DELETED’ in the ‘AccessCode’ column.    Change the value from ‘DELETED’ to ‘UNSECURE’.   (You may need to change it to ‘ACCESSLEVEL’ if you had security applied to the datasource.)   While you’re at it, make note of the value for the record in the ‘SourceID’ column.    We’ll need it shortly.

 

Restoring your Views

Open the ‘ReportView’ table and look for your deleted views.  You can match them to the datasource by comparing the value in ‘SourceID’ to the number you wrote down while restoring the datasource.  To bring them back, change the value in ‘ViewStatusCode’ from ‘DELETED’ to ‘OPEN’.

 

Restoring your Reports

Open the ‘ReportHeader’ table and look for your deleted views.  Once again, you can match them using the ‘SourceID’ column to the number you wrote down while restoring the datasource.  To bring them back, change the value in ‘ReportStatusCode’ from ‘DELETED’ to ‘OPEN’.

 

Great, you’re all done.   Restart the Yellowfin engine and you will be good to go!

Comments

Popular posts from this blog

Fun Little Earthquake

It's 1:45pm EST in Ottawa, Ontario, Canada. We just had an earthquake.  Not strong enough to damage anything, but enough that I watched people run out of buildings. What a fun Wednesday.

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Lotus Trading Cards

I was painting the house last night, and my mind got to wandering... Bruce Elgort mentioned on Twitter last night that he was thinking of a VC fund for Lotus projects. So my mind wandered about that, and turned to how we present ourselves. I got to thinking that business cards are so ... old school. I think we need Trading Cards. So, here are the first few I've come up with.