check the version matrix before you proceed to upgrade, version compatibility should be there
Yes checked, versions are compatible.
Any insight related to sailpoint provided db upgrade script not updating system_version only schema_version got updated, would be helpful.
(Please refer to both the screenshots.)
Hej Sarkar,
after you have run the db upgrade script, you are expected to run the iiq upgrade command.
Upon successful execution of iiq upgrade you should be able to use iiq console again.
Thanks,
Renad
Hello Subhra,
The ran the last query that updates the database version.
This just an example, you can check in the upgrade script in database folder
Thanks.
Hi Renad,
Are you suggesting irrespective of database version mismatch, like below -
system_version : 8.3-45
schema_version : 8.4-87
Should I proceed with" iiq upgrade"? Will that work still?
Hi Shubham,
yes, I checked the upgrade script. There is nothing command for system_version (only command present for schema_version).
In my case schema_version already got updated, as expected.
Yes, that is exactly the command that you need to execute.
The issue is that your database version is already in the version 8.4.
The application itself is still in the 8.3pX. And that is the mismatch that happens.
Therefore when you execute the command iiq upgrade, also the application will be upgraded to 8.4
Br,
Renad
Hello Renad,
Message says the opposite regarding database only while launching iiq console, below sharing again -
“Error creating bean with name ‘versionChecker’ defined in class path resource [configBeans.xml]: Invocation of init method failed; nested exception is sailpoint.api.DatabaseVersionException: Application’s system version 8.4-104 does not match IdentityIQ database’s system version 8.3-45”
Please let me know, your suggestion.
Can you run this query in your database
select * from identityiq,spt_database_version
and show us the input here.
Thanks,
Renad
Based on the query results, you can see that the schema version was upgraded, but the system was not, which led to the mismatch.
By running the ./iiq upgrade command this issue should get resolved.
@sarkarS01, this happens when you do not run the iiq upgrade and your application and DB versions are different. Happened with me several times. Like Renad suggested, run the iiq upgrade from cmd and it will upgrade the db to the correct version. If not upgrading, check the db scripts and change it accordingly and then run the upgrade again.
Cheers!
@sarkarS01 I found this in you iiq.properties
dataSourceAccessHistory.username=identityiqah
dataSourceAccessHistory.password=
You do have provided the encrypted password, right? I mean just because you are sharing with us, you have not provided, right?
If no password set, use the below script
CREATE DATABASE identityiqah (If not already there)
GO
CREATE LOGIN identityiqah WITH password=‘Add your encrypted password here’
GO
@suyatra_sinha1992, yes I have already provided encrypted password in iiq.properties for “identityiqah” but it seems I am getting error related to that.
Separately able to connect to that db with that particular password as well.
Can you try to use the password in plaintext initially? It would sort out the issues, where you use the wrong encrypted key, which usually happen if just get the encrypted value from a different stage.
Br,
Renad
@rquku, I have tried both ways,
Keeping plain text password
keeping encrypted version (context.encrypt(“******”))
But both ways getting the same error.
Is there any additional setup needs to be done for password? Am I missing out on anything?
Thanks & Regards,
Subhra Sarkar
Hi @sarkarS01
Did you check user permission also check timeout.
Thanks,
Prakash
Completed upgrade, thanks to all for your suggestions!!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
