FIX: Cubes and Databases No Longer Visible from OLAP Manager

Article translations Article translations
Article ID: 272006 - View products that this article applies to.
This article was previously published under Q272006
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 11261 (PLATO_7x)
Expand all | Collapse all

On This Page

SYMPTOMS

All databases and cubes are no longer visible in OLAP Manager and the Repository table, OLAPObjects, is empty. This only occurs on OLAP systems that have migrated the repository to SQL Server 7.0.

CAUSE

This occurs because the SELECT INTO/Bulk Copy option is not set for the repository database in SQL Server 7.0.

WORKAROUND

After the problem occurs, you can browse the OLAPObjects_bak table in the OLAPRep database to see if any records exist. If records do exist, inspect the LastUpdated column to see if the rows are current enough to restore. If the records are current copy the records into the OLAPObjects table.

If there are no records or the records are too old in the OLAPObjects_bak table, you must restore the repository database from a backup.

STATUS

Microsoft has confirmed this to be a problem in SQL Server OLAP Services version 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server OLAP Services version 7.0. For information about how to download and install the latest SQL Server OLAP Services Service Pack, see the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=F62F45E9-24ED-4FA6-BD74-8A26606F96D8
For more information, contact your primary support provider.

MORE INFORMATION

The repository in OLAP Services contains three tables:
  • OLAPObjects
  • OLAPObject_bak
  • Server
When OLAP Services attempts to backup or recover the repository, OLAP Services uses a SELECT INTO statement to move all the records to and from the OLAPObjects_bak table. After the copy of the records, OLAP Services drops the OLAPObjects table, and then re-creates the table. If the Select Into/Bulk Copy option is not set, the records can not be copied to or from the .bak table and the repository data is lost.

This is not a problem on Microsoft SQL Server 2000 because the Select Into/Bulk Copy option is set by default.

NOTE: Microsoft strongly recommends that you set the SQL Insert/Bulk Copy option on the OLAP repository database immediately after you migrate the repository. Microsoft also strongly recommends that you backup the OLAP repository on a regular basis.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
275050 BUG: OLAP Databases Missing in OLAP Manager with Migrated Repository Database

Properties

Article ID: 272006 - Last Review: February 28, 2014 - Revision: 4.1
APPLIES TO
  • Microsoft SQL Server OLAP Services
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbolap700sp3fix KB272006

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com