In certain situations, when users attempted to restart monitoring on a large number of database instances, monitoring would fail to start and DPA would log messages such as "Task has been rejected by TaskExecutor." This issue has been resolved.

Resolution/Work-around: For a complete list of the database types and versions supported for the DPA repository, see the System Requirements for your version of DPA.

Resolution/Work-around:

1. Open the following file in a text editor:

   <DPA-install-dir>\iwc\tomcat\ignite_config\iwc\security\sqlauth.xml

2. Look for invalid XML such as the following (shown in red):

   <entry key="sql.authentication.password">
   <![USER_PASSWORD]]<
>/entry>

3. Reenter the password enclosed in CDATA, and edit the XML so that it is valid. For example:

   <entry key="sql.authentication.password">
  <![CDATA[MyPasswordWith<SpecialCharacters>]]>
</entry>

4. Save the file.

   Changes take effect immediately. The password in the sqlauth.xml file is encrypted the first time DPA prompts a user to enter it.

Resolution/Work-around: Change the property separator in the COND table in the DPA repository database from & to ;. For details, see this article.

Resolution/Work-around:

1. Create the repository user manually and specify that the mysql_native_password plugin be used to authenticate that user. For example:

   CREATE USER 'userName'@'localhost' IDENTIFIED WITH mysql_native_password BY 'userPassword';

   You can verify user creation by querying the mysql.user table:

   select user,host,plugin from mysql.user;

2. Grant the required privileges to the user. See the GRANT statements in the script available through the Repository Creation Wizard.
3. On step 2 of the Repository Creation Wizard, select Provide the repository user. Then enter the user name and password of the user you created.

Resolution/Work-around: Open the alert definition and save it again, without making any changes. Saving the alert definition updates the name on the Alert Status tab.

Resolution or Workaround: Disregard the values that are incorrect on your version of SQL Server. You can also disable the collection of a metric that shows incorrect data.

Resolution/Work-around:

1. Create the monitoring user manually and specify that the mysql_native_password plugin be used to authenticate that user. For example:

   CREATE USER 'userName'@'localhost' IDENTIFIED WITH mysql_native_password BY 'userPassword';

   You can verify user creation by querying the mysql.user table:

   select user,host,plugin from mysql.user;

2. Grant the required privileges to the user. See the GRANT statements in the script available through the Register Instance Wizard.
3. On step 2 of the Register Instance Wizard, select I'll create the database user. Then enter the user name and password of the user you created.