KB273557: After altering the Database connection using the script from Command Manager in MicroStrategy 9.4.1, the changes do not get applied to the reports unless the database instance is opened in Developer.

SUMMARY:
This issue has been classified as a defect by Strategy. The impact is from the Strategy 9.4.1 product when altering a Database Connection using the script from Command Manager.  A workaround for this issue is available in the following document.
 
SYMPTOM:
There is a script in Command Manager in order to alter a Database Connection, however, after using this in order to make some changes to the Database Connection, it will be noticed that the changes are not applied unless the Database instance is opened in Developer.
 
STEPS TO REPRODUCE:

1. Run the following script for the Tutorial environment in order to modify the DSN being used for the Database Connection “Data”:

ALTER DBCONNECTION 'Data' ODBCDSN 'DSN'

 

1. Go to Developer and make sure all the cached Database connections are deleted.
2. Run any report that is not cached in the Strategy Tutorial project or clear the cache of the report and run it.
3. Notice that the report is still running against the 'Tutorial_Data' DSN, since no error is shown and the report runs correctly.

CAUSE:
This is a known issue in Strategy Developer 9.4.1.
 
ACTION:
Currently this issue is still being reviewed for feasibility by our Technology team and it is not scoped for any upcoming scheduled Strategy release.
 
WORKAROUND:

1. Open up the Database Instance that uses that Database connection in Developer
2. Notice the DSN for the DB connection seems to have been changed.
3. Click Ok in the Database Connection and Database Instance editors.
4. Go and try to run the report again, and notice this time it does error out, as expected and is running against the DSN that was chosen in the script in Command Manager.

 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE22998.