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

KB232548: Unable to use Command Manager commands "ALTER DBCONNECTION" or "ALTER DBLOGIN" to alter Data Import Database Instances


Community Admin

• Strategy


Unable to use Command Manager commands "ALTER DBCONNECTION" or "ALTER DBLOGIN" to alter Data Import Database Instances

SUMMARY:
In Strategy, a Database instances can be created through the Data Import feature in Strategy Web. When creating the DSN Database Connection in Web, the database connection and database login are given default names, whereas outside of this feature the user specifies these values.
Different properties of a database instance, including Data Import database instances, can be modified manually through the Database Instance Editor in Developer, including the database connection name and login information.  Command Manager scripts are available to modify different aspects of a database connection, database instance, and database login.  However, certain commands do not work for database instances created through Data Import.
 
SYMPTOM:
When attempting to run one of the following commands:
 


ALTER DBCONNECTION


ALTER DBLOGIN

 
to alter Data Import database instances, the following errors result, respectively:

ka04W000000OgqrQAC_0EM440000002C90.jpeg
ka04W000000OgqrQAC_0EM440000002C92.jpeg


DBConnection ‘XXXXX.conn' not found.


DBLogin 'XXXXX.login' not found.

 
 
STEPS TO REPRODUCE:

  • Create a new DSN Database Connection through Data Import in Web
ka04W000000OgqrQAC_0EM440000002C93.jpeg
  • In Developer, right click on the database instance and select "Edit." Note that the Database connection is given the default name "Test_DSN.conn."
ka04W000000OgqrQAC_0EM440000002C8y.jpeg
  • Select that connection and click "Modify..." Note that the database login name is given the default name "Test_DSN.login"
ka04W000000OgqrQAC_0EM440000002C91.jpeg
  • In Command Manager, execute the following commands and the errors noted in the SYMPTOM section will occur:


ALTER DBCONNECTION "Test_DSN.conn" NAME "Test_Connection";


ALTER DBLOGIN "Test_DSN.login" NAME "Test_Login";

 
CAUSE:
For Data Import Database Instances, ALTER DBLOGIN and ALTER DBCONNECTION commands do not work because the user does not have the ability to initially choose the name for the DBConnection and DBLogin.  The default names that Strategy creates (DSN_NAME.conn and DSN_NAME.login) are not working properly with the Command Manager commands to modify the names.  Commands affecting parameters that the user first specifies, such as the ALTER DBINSTANCE command, work correctly.
 
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:
Alter the DBConnection and DBLogin fields manually in the Database Instances Editor.
 
 
The Strategy Internal Reference Number for the issue discussed in this technical note is 1010522.


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017