The migration Database Technical Support dashboard migration utility can successfully migrate one type of database agent (e.g. Oracle) but not a different type of database agent (e.g. SQL Server).
An error similar to the following is printed in the FMS log file
INFO [forge-startup] com.quest.nitro.service.cartridge.api.CartridgeManager - Successfully re-enabled cartridge: DB_Oracle-5_7_5_50 on startup.
...
INFO [forge-startup] com.quest.nitro.service.cartridge.api.CartridgeManager - Successfully re-enabled cartridge: DB_SQL_Server-5_7_5_10 on startup.
...
INFO [forge-startup] com.quest.nitro.service.cartridge.api.CartridgeManager - Successfully re-enabled cartridge: DB_Global_View_UI-5_9_2_1 on startup.
...
-------
WARN...com.quest.qsi.fason.framework.installer.exceptions.InstallerServiceException: Failed to list FglAMs. Reason: Function not found:system:dbwc_spi20repository_installer_apis.listFglAMs.
...
...
Caused by: java.io.FileNotFoundException: WCFResource system:dbwc_spi20repository_installer_apis:wcf.xml not found.
...
WARN ...id=system:dbwc_mssql_database20agents20migration.CheckIfThereAtLeast2Fglams name="'Check if there at least 2 fglams'...java.lang.NullPointerException: Cannot invoke method set() on null object
CAUSE 1
SPI Repository database cartridge is not enabled
CAUSE 2
Oracle and SQL Server cartridges were not at the same version level.
The Oracle and SQL Server cartridges both can use PI (Performance Investigator) on the same FMS. Their cartridge versions should be at the same level because they depend on the same SPIRepsitory cartridge.
CAUSE 3
Corrupt view in the SPIRepository cartridge.
RESOLUTION 1
RESOLUTION 2
RESOLUTION 3
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center