"Failed to save ASP for DB agents" popup when changing SQL PI repository password (4378844)

A popup with the message "Failed to save ASP for DB agents" popup appears when changing a SQL PI repository password for Oracle agents. This has not been found with the SQL Server agent but be present for agents of other domains including Azure SQL and MySQL PI.

A message similar to the following is printed in the FMS log file

ERROR   [dgcnwsbqhq-3] script.system:dbwc_spi20repository_installer_apis.changeRepositoryCredentials - Failed to save ASP for agent AGENTNAME, message=Field spircStorageUseSSl is not found.

Coding issue

Workaround

Recreate the PI connection from the Oracle agents, configuring it to use the new password.

1. Disconnect the PI extension from all of the Oracle agents by selecting all of the Oracle agents with PI using the repository from Global View (Databases dashboard), clicking Settings then Administration, and then selecting the agent checkboxes and Disable in the SQL Performance Investigator panel
2. Delete the DB_Oracle_SPI_Repository agent from Agent Status 
3. Add the PI extension back to one Oracle agent to recreate the SPI agents by Navigating to the Global View (Databases) dashboard, clicking Settings then Administration, and then selecting the agent checkbox and Enable in the SQL Performance Investigator panel. Fill in any of the necessary connection details when prompted in the popups. (If the PI repository password was previously updated for SQL Server agents with PI, then the password field will greyed out and the user can click Next to continue)
   1. When prompted in the schema creation popup to confirm the repository database path locations, choose the existing PI database in the pulldown option at the bottom of the popup.
4. Navigate to PI, wait a couple minutes to make sure the data is collecting and extend the range to one week or more to look at historical data
5. Add the PI extension the rest of the database agents by navigating to the Global View (Databases) dashboard, selecting the other DB agents, clicking Settings then Administration, and then selecting the agent checkbox and Enable in the SQL Performance Investigator panel. 

Status

This issue has been found to no longer occur in the Oracle 7.3.0.10 cartridge. The issue appears to have been fixed as part of changes made for defect FOG-9647 in which a Windows user could not connect to a SQL PI repository.