SYMPTOM:
Per the steps below it can be observed that the Strategy Engine checks authentication against a project's primary database instance before submitting queries that only hit tables in the non-primary database instance:
1) Create an empty (non-Microsoft Access) test database with a sample table in it. For this example, the table will be referred to as TestTable. Create a DSN to this database using Strategy Connectivity Wizard on a 10.10 Windows machine with Strategy Developer installed.
2) Create either a 2 tier or 3 tier connection to the Strategy Tutorial metadata. Create a new DB Instance, connection, and login, choosing the DSN created in step (1). Choose the appropriate database connection type and type in anything login user name and password. Note that for this test, the login info specified here is intentionally invalid.
3) Create a brand new project in the same project source as Strategy Tutorial project. For now don't add any new tables to it through the project creation editor.
4) After the project is created, right click the project name > Project Configuration > Database instances. Set the primary DB Instance to be the one created in step (2). Then in the panel below, check the boxes for that db instance and for "Tutorial Data" db instance. Click OK to close project configuration.
5) Unload and reload the new project if in 3-tier for the new DB instance configuration to take effect. Disconnect and reconnect to project source.
6) Open WH catalog for the new project and an error will be thrown since the login for primary db instance is incorrect - but open WH catalog anyway. In the drop down menu, select "Tutorial Data" db instance and read the WH catalog. Import any lookup table (LU_GENDER for example) into the project. Save and close WH catalog.
7) Update schema. Create a new attribute from one of the columns on the table that was imported. Update schema again.
8) Create a new report, place this attribute on it, and run the report. The report should error saying the login info is invalid, and it will show that the DSN and login info for the primary DB instance are being submitted, instead of the login info for Tutorial WH, even though we specifically imported the table from the Tutorial WH and the LU_GENDER table is mapped to Tutorial Data DB instance in WH catalog.
CAUSE:
This is a known issue with the Strategy 9.x - 10.x Engine.
ACTION:
Make sure that the primary database instance has valid login information for the database that it points to.
Strategy will continue to investigate and post updates as soon as they are available.
KB414053
