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

Post a Comment

Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control
Post a Comment
Read more

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.
5 comments
Read more

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "jvm.properties" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X
3 comments
Read more