[CR #588134] If you have previously installed ETL Development, and you uninstall it to install ETL Development 4.9 for all users, when any user other than the one who installed it tries to connect to the repository, the demo database connects to the data source of the ETL Development 4.8 repository.
Workaround:
If the previous version of ETL Development was installed for all users, before upgrading, log in as each user and use the ODBC Data Source Administrator to delete the DEMO_Repository, ETLDEMO_DWH, ETLDEMO_GER, and ETLDEMO_US data sources. If you do not plan to uninstall the earlier version of ETL Development, you may want to rename the data sources instead of deleting them. For example: <old name_version number>.
See Chapter 4, “Upgrading,” in the ETL 4.9 Installation Guide.
If you have already installed the new version without renaming or deleting the old data sources, manually delete the old data sources. Follow the steps described in “Restoring the initial set of ODBC data sources of the demo repository,” in Chapter 3, “Postinstallation Tasks” in the ETL 4.9 Installation Guide.
Make sure that you specify the database files in the
user data location, not in the installation location.
If you encounter errors when trying to delete the old data sources, you can overwrite the entries for each user, as follows:
Save a copy of the userdata.conf file located in the etc folder of the installation directory.
Edit the userdata.conf file to replace all occurrences of “once” with “always” in the ODBC section.
For each user:
Log in to the machine and start ETL Development, then shut down the application.
Verify that the ODBC Data Source entries use SQL Anywhere 11 and point to the appropriate database files in your user data directory.
After all users have logged in to ETL Development, you can restore the original userdata.conf file.
See “Checking for a valid installation,” in Chapter 3, “Postinstallation Tasks” in the ETL 4.9 Installation Guide.
