KB17620: ‘Missing Right Parenthesis’ error message appears when manipulating tables from the Warehouse Catalog in MicroStrategy Developer 9.4.1/10.x

SYMPTOM:
Strategy Developer 9.4.1/10.x will display the following error message when trying to manage tables in the warehouse catalog.
 

 
Error adding Table(s) to the schema.
Database error <>: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. ORA-00907: missing right parenthesis.
Or:
 

 
Error processing table structure.
Database error <>: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. ORA-00907: missing right parenthesis.
Users are using the supported Strategy ODBC driver correctly.
 
TROUBLESHOOTING STEPS:
Follow these instructions to troubleshoot this issue:
 

1. Access the tool located at Start > Programs > Strategy > Tools > Diagnostics Configuration. (Alternate path: Inside Strategy Desktop > Tools menu > Diagnostics.)
2. Enable for that Machine Default, the Database classes > SQL Trace > Console log. Save, and restart Strategy Desktop 8.x.
3. Run the 'monitor.exe' from the Microsoft Windows Run command.
4. Reproduce warehouse catalog issue until the error message comes up.

The monitor log should show something like the following right before logging the 'missing right parenthesis' error:
 
3492: 2007-12-03 16:53:16.511-05:00 1315BC7011315BC90SELECT OWNER NAME_SPACE , TABLE_NAME TAB_NAME , COLUMN_NAME COL_NAME , DATA_TYPE DATA_TYPE , DATA_LENGTH DATA_LEN , DATA_PRECISION DATA_PREC , DATA_SCALE DATA_SCALE FROM ALL_TAB_COLUMNS WHERE TABLE_NAME in (``ADDRESS_MV``) AND OWNER in ( `SDW_MSTR_VMDB`, `SDW_MSTR_VMDB`) ORDER BY 1, 2
CAUSE:
This happens most likely after a warehouse database change, e.g. from Teradata to Oracle. The SQL instruction being used to read the warehouse catalog is not the right one.
 
ACTION:
Follow these instructions to solve this issue:
 

• In Strategy Desktop, open the Warehouse Catalog from the 'Schema' menu.
• Go to the Tools menu > Options > Catalog > Read settings > Settings, as shown in the image below.
  

• Note: User may want to save the SQL in this two boxes, before proceeding with this step. Set the defaults for both options available here as shown in the image below:
  

• Or revise the SQL shown here for errors if the default SQL is not desired.
   
  
• Click 'OK' button twice, save and close. The issue should now be fixed.