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

KB35742: "Table or view does not exist" and "Ignoring failed drop table SQL execution. DROP TABLE TMP_0319" errors appear in the DSSErrors.log and MACfgWiz.xml files when upgrading a metadata using the MicroStrategy Configuration Wizard


Community Admin

• Strategy


When upgrading a metadata through the MicroStrategy Configuration Wizard, users notice the warning and error below appear several times in both the DSSErrors.log and MACfgWiz.xml log file.

SYMPTOM:
When upgrading a metadata through the Strategy Configuration Wizard, users notice the warning and error below appear several times in both the DSSErrors.log and MACfgWiz.xml log file:
 
DSSErrors.log


Table or view does not exist Connection String: DSN=XXX;UID=XXX;HOST=XXX;PORT=XXX;SID=XXX;. SQL Statement: DROP TABLE TMP_0319.

 
MACfgWiz.xml

Ignoring failed drop table SQL execution. DROP TABLE TMP_0319

 

 
CAUSE:
Before the upgrade process starts, the Strategy Configuration Wizard needs to check that the user used to login to the metadata database has enough privileges to write and drop tables in the database. To do so, it creates a temporary table with name TMP_0319. However, before the table is created, the Configuration Wizard issues a query to drop it in case it already exists in the database, this query will always result in the error message described in this document.
 
Therefore, users should not be concerned by seeing this error in the log files, unless the upgrade process fails and displays the error in the Configuration Wizard graphical interface. In this case, users should make sure they are connecting to the correct schema, and that the user has enough privileges to create and drop tables and triggers.


Comment

0 comments

Details

Knowledge Article

Published:

July 14, 2017

Last Updated:

July 14, 2017