Workaround
This workaround has been logged as hotfix FDH-58 and is applicable for SQL Server v5.9.7.21/v5.9.7.20 and Oracle/Azure v5.9.7.20. After applying the workaround below, the database cartridges will be able to deploy the SQL PI repository on an Azure SQL Managed Instance via the setup wizard.
FMS
Backup the WCF module
Open a command line on the FMS and run the following two commands. Replace "foglight" in each line with the foglight administrator account username and password.
- {fms_home}/bin/fglcmd.bat -usr foglight -pwd foglight -port 8080 -cmd util:uiexport -m "system:dbwc_spi20repository_installer_apis" -f repository_installer_api_old.zip
- {fms_home}/bin/fglcmd.bat -usr foglight -pwd foglight -port 8080 -cmd util:uiexport -m "system:dbwc_spi20repository_installer" -f repository_installer_old.zip
Import the WCF module into the FMS from a command line on the FMS
- Copy repository_installer_api.zip and repository_installer.zip to the folder {fms_home}/bin
- Execute following command to import WCF module:
{fms_home}/bin/fglcmd -usr foglight -pwd foglight -cmd util:uiimport -f repository_installer.zip
{fms_home}/bin/fglcmd -usr foglight -pwd foglight -cmd util:uiimport -f repository_installer_api.zip
Deploy the jar file to the FMS
Backup the jar file spi-common-utils-1.16.0.jar from the jar folder.
- Using SqlServer as an example, you can backup the jar from \state\cartridge.exploded\DB_SQL_Server-5_9_7_21\DB_SQL_Server-APIs-5_9_7_21
Replace the jar file spi-common-utils-1.16.0.jar in following paths:
- SQL Server
{fglam_home}\state\cartridge.exploded\DB_SQL_Server-5_9_7_21\DB_SQL_Server-APIs-5_9_7_21
{fglam_home}\state\cartridge.exploded\DB_SQL_Server_UI-5_9_7_21\NPA-JARs-5_9_7_21
{fglam_home}\state\cartridge.exploded\SPIRepository-1_16_0\SPIRepository-APIs-1_16_0 - Oracle
{fglam_home}\cartridge.exploded\DB_Oracle-5_9_7_20\DB_Oracle-FMS-APIs-5_9_7_20
{fglam_home}\state\cartridge.exploded\DB_Oracle_UI-5_9_7_20\jarComponent-5_9_7_20
{fglam_home}\state\cartridge.exploded\SPIRepository-1_16_0\SPIRepository-APIs-1_16_0 - Azure SQL DB
{fglam_home}\state\cartridge.exploded\DB_Azure-5_9_7_20\DB_Azure-APIs-5_9_7_20
{fglam_home}\state\cartridge.exploded\DB_Azure_UI-5_9_7_20\SPI-JARs-5_9_7_20
{fglam_home}\state\cartridge.exploded\SPIRepository-1_16_0\SPIRepository-APIs-1_16_0
Then Restart the FMS
FglAM
Deploy jar file on FglAM
Backup the jar file spi-common-utils-1.16.0.jar from the path mentioned in next step.
For Foglight Agent Managers deployed with database agents and Foglight Agent Managers deployed with a Domain manager agent, replace the jar file spi-common-utils-1.16.0.jar in the path:
- SQLServer:
{fglam_home}\agents\DB_SQL_Server\5.9.7.21-5.9.7.21-20210125-1021\lib - Oracle:
{fglam_home}\agents\DB_Oracle\5.9.7.20-5.9.7.20-20201127-1841\lib - Azure:
{fglam_home}\agents\DB_Azure_Database\5.9.7.20-5.9.7.20-20201127-1836\lib
Then restart the FglAM
Status
This issue has been logged as defect FOG-620 and has been fixed in the 6.0.0.10 and higher releases of the Foglight Database cartridges.
