Skip to end of metadata
Go to start of metadata

Purpose

To help SAP Contact Center Administrators understand the options/steps used to manage issues raised by MS Analysis Services, which causes missing information in the SCC Online Reporting.
In this document, I will provide some instructions on how to re-build the OLAP database(s) in the event DTE or a full process failure.

Overview

In some cases, you may be instructed by SAP Product Support to re-create the OLAP database(s) because of some falure either running the DTE (Data Transformation) process or by running either the "XXX:Reporting OLAP database management" from the "SQL Management Studio" suite (under the SQL Server Agent -> Jobs section).
Here are some errors you may see in the DTE logs:

  • Error ErrorCode="3238985734" Description="XML parsing failed at line 1, column 0: A document must contain exactly one root element.
  • Error ErrorCode="3239313436" Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\D:\ProgramFiles\Microsoft SQLServer\MSAS10_50.BCMPRD\OLAP\Data\BCM_OLAP.0.db\CubCSSContacts.0.cub\Fact Call Statistic.5647.det.xml

Some errors when trying to run the "XXX:Reporting OLAP database management " job:

  • The database with the name of 'BCM_OLAP' already exists in the 'XXXBCMR1' server. at Microsoft.AnalysisServices.Xmla.XmlaClient.CheckForSoapFault(XmlReader

    reader, XmlaResult xmlaResult, Boolean throwIfError) at Microsoft.AnalysisServices.Xmla.XmlaClient.CheckForError(XmlReader reader, XmlaResult xmlaResult, Boolean throwIfError) at Microsoft.AnalysisServices.Xmla.XmlaClient.SendMessage(BooleanendReceivalIfException, Boolean readSession, BooleanreadNamespaceCompatibility).... The step failed.

Process

    1. Perform a backup of the OLAP database.
      1. Connect to MSSQL Analysis Services:
      2. Backup the existing Database used for this reporting.


      3. Delete the database and verify the deletion was successful:


        NOTE:
        If there is any errors deleting the DB, then try renaming the database manually from the folder itself.
        *** For example:
        Rename "D:\SQL_DatabasesMSAS10_50.BCMSQL\DATA\BCM_OLAP.0.db"  to  "D:\SQL_DatabasesMSAS10_50.BCMSQL\DATA\BCM_OLAP.0.db_copy".  Then delete the DB manually using MSSQL Management Studio.
      4. To avoid any unwanted errors in DTE, it is recommended to also stop/disable the Reporting Data Transformation Process SQL job (from MSSQL Management Studio). Please remember to start/enable this after the below steps have been completed. 
    2. Upgrade your Reporting database server VU:
      1. Launch SAP CCrt IA (Infrastructure Administrator) and connect to HAC and go into Deployment mode.
      2. Inactivate the VU at the Virtual Unit Level.
      3. Now at the HAC level, expand the VU and select the Software item, then select "Upgrade All Software".
      4. The VU should show Bolded, right-click and select "Apply Changes to System".

      5. Verify the newly created OLAP database has been successful.
      6. If you are using Contact Center Feature pack 13 and up and the OLAP database is still not created, then:
        1. In the Infrastructure Administrator (IA), navigate to the Reporting Database VU
        2. Go to the "Variables for Reporting Database Server" and expand the block
        3. Make sure the "Microsoft Reporting Services in use" option is checked, if not, check it and repeat the process to recreate the OLAP DB
        4. Run  the "XXX:Reporting OLAP database management" job to check if the error persists or not

Note:

NOTE:
The above ""XXX:Reporting OLAP database management" job will run a "Full process" OLAP database and update the bookkeeping for DTE, which is necessary to avoid duplicate entries. This job is not designed for daily use, only for periodical maintenance and for solving trouble cases. My recommendation is that you schedule this job to run once or twice monthly if possible and preferably when there is no other jobs running at that scheduled time.
  • If running the above job returns errors or if the original error is not resolved, then please run the "Full process" manually with the following steps:

Important Notes/KBAs

Wiki Page: How to re-collect data for statistics (Online Reporting)
SAP Note 1961095: How to use the CopyLogData tool to copy data from the history database over to the staging database
SAP Note 1753539: BCM 7.0 Required information and logs for troubleshooting 
SAP Note 1753607: BCM 7.0 How to change server and client loglevels

 

 

  • No labels