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

KB7846: How to obtain Oracle 9.x dumps for use by MicroStrategy to troubleshoot issues


Community Admin

• Strategy


Often times, for effective troubleshooting, MicroStrategy Technical Support requires a copy of the users' metadata tables or statistics tables or even specific warehouse tables. This article outlines guidelines for obtaining such information when the database is Oracle.

Often times, for effective troubleshooting, Strategy Technical Support requires a copy of the users' metadata tables or statistics tables or even specific warehouse tables. This document outlines guidelines for obtaining such information when the database is Oracle.
 
NOTE: The information provided in this document is only Strategy's recommendation for getting Oracle dumps to be used only by Strategy. It should not be construed or interpreted as explicit advice for procuring Oracle dumps per se or anything else.
 
NOTE:
 

  • The Oracle Original Export Utility is no longer supported as explained in KB310758: How to provide an Oracle database backup to MicroStrategy Technical Support for troubleshooting purposes

 

  1. Try to obtain a user mode dump
    Oracle database allows export of:
    1. One or more tables (Table-mode export)
    2. All objects of a user (User-mode export)
    3. The whole database (Full database export)
  2.  
    Strategy's recommendation is to get a user mode export. However, if the user owns many more tables than the required ones -- metadata tables or statistics tables or any specific warehouse tables -- then it may be easier to export individual tables (Table-mode export).
    For both user mode and table mode export, please do obtain the name of the table owner (user).
    A full database export contains all the users of the source database, including SYS and SYSTEM. For Strategy's use for troubleshooting, getting a dump file of full database export is not necessary, as only the relevant metadata or statistics tables or specific warehouse tables are important.
     
  3. Do File Transfer Protocol (FTP) in BINARY mode
    Sometimes an FTP is done between platforms with different operating systems, to obtain the dump. It is recommended that the FTP be done in BINARY mode and not in ASCII mode. This is because different characters may have different meaning in different operating systems.
     
  4. Obtain the export parameters, if needed
    If non-default parameters have been used to export the dump, please obtain the export parameters and the export command used, if possible.
     
  5. Obtain information about the source database parameters
    Obtain information about the database parameters that include language and codepage. To do so, obtain the results of the following query:
    SELECT * FROM NLS_DATABASE_PARAMETERS
     
  6. Do not get an export of the System's schema
    If the metadata or statistics tables are in the System's schema, do not get an export of the System's schema. Either export the tables individually (Table-mode export) or transfer the tables to a different schema (user space) and get a user mode export of that space.
     
  7. Obtain the export log file

 
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.


Comment

0 comments

Details

Knowledge Article

Published:

May 24, 2017

Last Updated:

May 24, 2017