Failure to Upgrade to SailPoint IIQ version 8.4

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

Version 8.4

Share all details related to your problem, including any error messages you may have received.

We are upgrading IIQ from version 8.1 to 8.4. We have successfully completed the process up until IIQ 8.3. When we started upgrading to IIQ 8.4, we encountered the following error when we are trying to run the upgrade command “iiq upgrade”

Invalid object name ‘spt_database_version’. com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name ‘spt_database_version’.

Anyone has seen this issue before or might know how to potentially fix it? We already checked the schema version and followed the steps in this article but still same error: Error: Invalid object name 'spt_database_version' - Compass

2

Can you provide the full error message?

3

Are you sure you followed all DB related steps before upgrade to 8.4? There were quite significant changes to the DB including creation of completly new database for access history.

4

The error message is not related to the new database. We have followed all the DB related steps and the new Access History database has been successfully created with no issues. iiq.properties has been properly updated as well.

5

image
image1504×559 289 KB

6

Check if your iiq.properties file is pointing to the correct database

7

@Medo1

I was receiving the same error. Nightmare for me because I had completed all of the processes. How I solved it was by properly adjusting the iiq.properties file.

Check identityiq_ah database’s url is correct and the user identityiq_ah(default name) is configured to access the database identityiq_ah.

1 Like
8

Database URL for AH is the same as identityiq. This is DEV so we are using the same server for both. We are also using the same user “identityiq” to connect to both databases. We added the required permissions to access both DBs. We also double checked the iiq.properties, and it all looked good.

9

Using the same SQL Server Login for both schemas could be an issue. I am pretty when the logins are created, they are set with a default schema and if that is not set I believe it causes issues.

1 Like
10

If thats not a problem please add here your iiq.properties for verification

11

Hi @Medo1,

Change the database name and credentials like below and try.

dataSourceAccessHistory.username=identityiqah
dataSourceAccessHistory.password=Update Password

MySQL/Aurora (without SSL)

dataSourceAccessHistory.url=jdbc:mysql://IP/identityiqah?useServerPrepStmts=true&tinyInt1isBit=true&useSSL=false&characterEncoding=UTF-8&serverTimezone=UTC&allowPublicKeyRetrieval=true
dataSourceAccessHistory.driverClassName=com.mysql.cj.jdbc.Driver
sessionFactoryAccessHistory.hibernateProperties.hibernate.dialect=org.hibernate.dialect.MySQL57Dialect

12

Is it an issue to use the same user? or we can use the same user as long as we set the default schema and grant the required permissions? because we did.

13

I am not 100% sure if this is actually an issue. Looking at SQL Server Management Studio now, I can see a Login can have multiple databases set in their User Mappings where the default schema can be set.

Have you been upgrading SQL Server as you are going through IIQ versions as well? It seems like you are possibly using Java 17 along with SQL Server JDBC v4 (sqljdbc4.jar) based on the logs. That is a really old version of the SQL Server JDBC driver. I definitely recommend using a later version if possible. You could be running into some compatibility issues as you are going up in versions.

1 Like
14

Thank you, I tried with the new driver and it is still throwing the same error.

LogMessageErrorIIQ8_4Upgrade_NewDriver
LogMessageErrorIIQ8_4Upgrade_NewDriver1295×445 22.6 KB

15

I am using MSSQL not MySQL.

16

Can you confirm if both databases have spt_database_version tables?

1 Like
17

Actually only identityiq database has that table. The new database identityiqah has a similar one but with a different name by simply adding ah.

18

Thank you Patrick. The issue was with using 2 different users. We also had some other configuration issues, but the main issue was trying to use 2 different users.

1 Like