EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB310758: How to provide an Oracle database backup to MicroStrategy Technical Support for troubleshooting purposes


Community Admin

• Strategy


Summary

 
Strategy Technical Support may request your Strategy Metadata repository to continue troubleshooting issues that are specific to schema configurations, upgrades or specific sets of data. This article is meant to provide guidance to Strategy Administrators as well as Database Administrators on how to provide an Oracle Database backup of the Strategy related repositories.  
 

Pre-requisites

 
In most enterprises it will be necessary to involve the appropriate Database Administrator to make sure that all commands are run properly and with general best practices. This article is meant to be a guide to make the process simple and allow the import process to be faster.
 

Prepare the dump

 
Using the Datapump export utility to perform the export is the recommended way for all Oracle databases on version 11 and above. Oracle does not support the original export utility for any recent versions. Using the original export may result in an unsuccessful import when the dump is received by Strategy Technical Support. Refer to the following Oracle article for more information:
Original Export utility is no longer supported for exports on Oracle 11 and above.
 
To perform a Datapump export follow these general recommendations:
1. Provide only the schemas that contain data relevant to Strategy. It is common to have different schemas in the same Database server for the Metadata repository, Enterprise Manager Statistics and History List. If Strategy Technical support requests the Metadata repository only, export the schema that contains the Strategy Metadata tables. This can be accomplished with the SCHEMAS modifier in the Datapump export command.
 
2. Generate an export log when performing the Datapump export. This log provides useful information like the schema name that needs to be imported, confirms the entire contents and size of the export tables.
 
3. Use parallel exports only when necessary. Datapump exports allow for parallel files to be exported for a faster process. It is not recommended to export in parallel small dumps, generally if the size of the database is less than 5GB.
 
A sample Datapump export command is included below for general reference, the complete Datapump export documentation is available in the official Oracle Website Datapump Export:
 
 


expdp system/#####@orcl112 schemas=METADATA directory=DMP dumpfile=METADATA.dmp logfile=METADATA.log

 
Note: Adjust all the parameters above to the locations that apply in the environment in question. In this case the Strategy Metadata repository tables were present in the METADATA schema.
 

Files to provide

 
The following two files are highly recommended to allow a successful import:
1. The dump files with a .dmp extension : Datapump is the recommended method to export Oracle databases. The original export utility is no longer supported in Oracle version 11 and above, see the previous section for more details.
2. The export log generated during the datapump export: If it is not possible to provide the export log providing the exported schema will help speed up the import process.
 

Third-Party Software Warning

Oracle Databases and export utilities are not property of Strategy and will not be troubleshooted by the Strategy Technical Support team. For support on these technologies contact your Database Administrator or Oracle Support.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017