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

KB287179: Error "ORA-00923:FROM keyword not found where expected" when executing report "Performance by Store" in MicroStrategy Developer 10.2 after Tutorial Metadata and Warehouse are moved to Oracle 12c database


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Error "ORA-00923:FROM keyword not found where expected" when executing report "Performance by Store" in MicroStrategy Developer 10.2 after Tutorial Metadata and Warehouse are moved to Oracle 12c database

SYMPTOM:
After Metadata and Warehouse for Tutorial Project are moved to Oracle 12c database using Project mover in Strategy 10.2, when report "Performance by Store" in Strategy Tutorial Project is executed, the error message pops out, as showed below.
Error: SQL Generation CompleteQueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQL ExecDirect. [42000:923: on SQLHANDLE][Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-00923: FROM keyword not found where expected
STEPS TO REPRODUCE:

  1. Move Metadata and Warehouse for Strategy Tutorial Project to Oracle 12c database using Project mover in Strategy 10.2.
  2. Run the report named "Performance by Store" in the path, Strategy Tutorial/ Public Object/ Reports/ Strategy Platform Capabilities/ Strategy Report Service/ Datasets/ Performance Management. The error pops out.
  3. Deleting alias for metric and attribute does not work​

CAUSE:
This is a defect in Strategy 10.2.
ACTION:
This is addressed in the 10.3 copy of the tutorial metadata so the error no longer happens, but the underlying resolution as to why the issue was happening is resolved in 10.6


Comment

0 comments

Details

Knowledge Article

Published:

June 7, 2017

Last Updated:

June 7, 2017