8.4p1 - Patching is not working

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.

I recently upgraded from 8.1 to 8.4 and moving to 8.4p1. While patching I am getting below message ,
“IdentityIQ expected system version [8.4-105] does not match current database value [8.4-104].”

DB Scripts are run already and system version is 8.4-104 and schema version is 8.4-88.

Am I missing anything?

Thanks
Priyanka Jain

Can you check if the version that is there in the DB is what was present in this DB script.

This is just to verify that your DB script ran and completed propery.

Hi @ashutosh ,

Below is the DB Script for 8.4P1 and I see the same schema version is set in the DB as well.

update identityiqah.spt_hist_database_version set schema_version=‘8.4-88’ where name=‘main’;
GO


– ACCESS HISTORY upgrade end


– This is necessary to maintain the schema version. DO NOT REMOVE.

USE identityiqUAT
GO

– DO NOT REMOVE OR MODIFY BLOCK
– CONTEXT-SWITCH: dataSource
– DO NOT REMOVE OR MODIFY BLOCK

update identityiq.spt_database_version set schema_version=‘8.4-88’ where name=‘main’;

Before doing patch were you able to check SailPoint login either via console or via UI ?

Thanks

Prianka, execute just the update to the version table. and execute a command to commit the changes.

That should solve your issue.

1 Like

@priyanka_jain
What is your system version at DB level

select * from identityiq.spt_database_version

I did executed the update and below is the version

have you done the iiq patch 8.4p1 on the IIQ Console?

Getting below error,

C:\Sailpoint\Apache Software Foundation\Tomcat 9.0\webapps\ROOT\WEB-INF\bin>iiq console
IdentityIQ expected system version [8.4-105] does not match current database value [8.4-104].

Hi @priyanka_jain ,

You updated DB to 8.4-104 but the error was for 8.4-105 as per version error. So, did you missed to update correct version or it is intentional only?

Thanks

1 Like

Can you run a "Commit Changes " on your database? commit; or something like that.

theres two database versions now,

did you updated booth?

update identityiqah.spt_hist_database_version set schema_version = '8.4-88' where name = 'main';

--
-- ACCESS HISTORY upgrade end
--

USE identityiq;

-- DO NOT REMOVE OR MODIFY BLOCK
-- CONTEXT-SWITCH: dataSource
-- DO NOT REMOVE OR MODIFY BLOCK

--
-- This is necessary to maintain the schema version. DO NOT REMOVE.
--
update identityiq.spt_database_version set schema_version = '8.4-88' where name = 'main';
2 Likes

@priyanka_jain my thoughts on below

USE identityiqUAT
GO

– DO NOT REMOVE OR MODIFY BLOCK
– CONTEXT-SWITCH: dataSource
– DO NOT REMOVE OR MODIFY BLOCK

update identityiq.spt_database_version set schema_version=‘8.4-88’ where name=‘main’;

In above U used identityiqUAT and below u are updating identityiq. Can you check ?

update identityiqUAT.spt_database_version set schema_version=‘8.4-88’ where name=‘main’;
1 Like

if you have different schema created for non-prod env other then default one for example default is idenityiq , please make sure you replace all the identityiq with <identityiqUAT> before executing any script . Also i would say check if the iiq.properties file have a same schema details.

2 Likes

@priyanka_jain : Kindly check Mr @ipobeidi comment as I also did the same mistake once and forgot to commit the changes.

Thanks everyone for all your inputs. The issue was due to the schema was pointing to dbo instead of identityiq. Once the DB team fixed it, the patching ran successfully,.

Thanks
Priyanka

Good to know that it worked .

@priyanka_jain how did you resolved your error. Can you brief about it?

Thanks.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.