Hi @Muhammad_Mustafa ,
This issue has previously occurred in my experience. To address it, begin by verifying the user configured in the iiq.properties file for database access. If you are using a database user other than the default IDENTITYIQ schema owner, ensure that appropriate synonyms are created in your schema for the newly introduced tables under the IDENTITYIQ schema.
This step is necessary due to the way SailPoint IdentityIQ utilizes Hibernate for object-relational mapping. Hibernate expects direct access to specific table names without fully qualifying them with the schema. As a result, missing synonyms can lead to errors during runtime or upgrade processes when the application attempts to query tables that are not directly visible to the configured user.