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

KB42776: Few out-of-the-box reports fail with the error "table or view does not exist" in MicroStrategy Enterprise Manager 9.x and 10.x, when the warehouse tables have a prefix.


Community Admin

• Strategy


In MicroStrategy Enterprise Manager 9.x- 10.x, when users execute the report "80. Top n users", the following error is received: "Table or view does not exist."

SYMPTOM
In Strategy Enterprise Manager 9.x- 10.x, when users execute the report "80. Top n users", the following error is received:
 
Sample Code/Error
Table or view does not exist.
 
It is noted that the Strategy Enterprise Manager warehouse tables have a prefix and the prefix has been correctly defined in the warehouse catalog. The SQL view of the report shows that the prefix is being used on all the tables, except the table EM_USER, as shown below.
 
Sample Code/Error
select a11.EM_USER_ID  EM_USER_ID,
 a13.EM_USER_NAME  EM_USER_NAME,
 sum(((a11.IS_REP_JOB_ID * 0) + 1))  WJXBFS1
from EMPROD_DAT.IS_REP_FACT a11
 join ZZMQ01 pa12
................
................
................
................
from EM_USER
group by EM_USER_ID) a13
 
 
 
CAUSE
The report "80. Top n users" accesses the table "EM_USER_View". "EM_USER_View" is not a warehouse table, but a logical view created within the Strategy metadata. Since the logical view definition does not specify the prefix, an error is received during report execution.
 
 
ACTION 
Edit the logical view "EM_USER_View" and specify the prefix as shown below.
 

ka04W000001MKpOQAW_0EM4400000029dg.jpeg

 
 
The following logical views exist in the Strategy Enterprise Manager 9.2.x - 9.3.0 project. If users have reports which access these logical views, the prefix should be specified in the respective view definitions to avoid seeing this error. 

  • EM_USR_GP_View
  • IS_DB_INST1_View
  • IS_OLAP_VIEW_REP

 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 6, 2017

Last Updated:

April 6, 2017