KB295480:“ORA-20000: Unable to analyze TABLE” error occurs when running MicroStrategy Enterprise Manager data load against an Oracle database

SUMMARY
This issue has been classified as a defect by Strategy. The impact is limited to Strategy Enterprise Manger 10.0 - 10.2 against an Oracle database, when running the data load option to update database statistics. A workaround is available in the current document. A solution/code fix for this issue is available in Strategy Secure Enterprise 10.3.
 
SYMPTOM
In Strategy 10.0 - 10.2, during an Enterprise Manager data load with the data load option 'Update Database Statistics' option enabled, the following error message is seen in the data load error logs (MAENTMgr.xml)

[Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-20000: Unable to analyze TABLE "AAABBB"."CT_EXEC_TYPE", insufficient privileges or does not exist
ORA-06512: at "SYS.DBMS_STATS", line 23818
ORA-06512: at "SYS.DBMS_STATS", line 23880
ORA-06512
at com.Strategy.maem.connections.database.DatabaseConnection.executeStatement(Unknown Source)
at com.Strategy.maem.dataload.admin.ScriptBasedCommand.executeCommand(Unknown Source)
at com.Strategy.maem.dispatcher.command.BaseCommand.execute(Unknown Source)
at com.Strategy.maem.dispatcher.command.BaseCommand.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Execute Query failed. ^M

Following entries are caught in the DSSerrors.log:

[PID:1268][THR:3964][Database Classes][Error] Execute Query failed. 
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HY000:20001: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-20001: AAABBB is an invalid identifier
ORA-06512: at "SYS.DBMS_STATS", line 20337
ORA-06512: at "SYS.DBMS_STATS", line 20360
ORA-06512: at line 1 Connection String: DSN=AAABBB;UID=XXXXX;HOST=XX.XX.XX.XX;PORT=1522;SID=orcl112;. SQL Statement: BEGIN DBMS_STATS.GATHER_TABLE_STATS ('AAABBB' , 'IS_SESSION_STATS' , CASCADE => TRUE); DBMS_STATS.GATHER_TABLE_STATS ('AAABBB' , 'IS_PROJ_SESS_STATS' , CASCADE =>

Note: The DSN name AAABBB is used to qualify the tables instead of schema-name.
CAUSE
This is a known issue with data load in Strategy Enterprise Manager 10.0 - 10.2. 
 
ACTION
This issue has been fixed in Strategy Secure Enterprise 10.3. Upgrade to this version to take advantage of the fix.
WORKAROUND
On Windows operating systems, locate the file 'Upd_Stat_Table_Stats_Ora.sql' located at <install_drive>:\Program Files (x86)\MicroStrategy\Enterprise Manager\Scripts as well as the file 'Upd_Fact_Table_Stats_Ora.sql'. Update the file so that the wildcard '%SCHEMANAME%' in all the commands is replaced with a static schema name.
 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE29575.