Postrequisites
Deployment of reports
After any upgrade, you need to redeploy all the standard reports.
Additionally, in the case of Omada Identity v14.0.4 (Update 4), in the tblApplicationSetting table of the ODW database, the ES database user (e.g., srvc_omada) should be assigned as the [ValueStr] of the ssrsServiceAccount [Key].
Deprecated components
After installing the software, run the SystemInfo.sql script in the ES database.
This script is located in the Omada Identity installation folder at C:\ProgramFiles\Omada Identity Suite\Enterprise Server\Sql scripts.
This script creates a stored procedure (spSystemDiagnostics) that produces information about the Omada Identity system that is usable for diagnostics and bug investigation. The stored procedure should be executed with text output.
The script can, for example, detect the use of deprecated components that require special attention when upgrading, including:
- Use of deprecated access modifiers.
- Use of deprecated code methods.
- Other issues that should be handled if reported (for example, issues related to data objects with mandatory fields that have empty values).
Update database
Rerun the CreateObjects.OISAudit.sql or add the i.[_VERSIONID] column manually to [dbo].[Identity_MasterData] view on the ES Archive DB.
Make sure that any of the views [Context_MasterData_Custom], [Identity_MasterData_Custom] and [Resource_MasterData_Custom] also output the [_VERSIONID] column. Otherwise, the import will fail.