Server version name: Apache Tomcat/9.0.85 Operating System: Windows Server 2022 10.0 (amd64) Java: jdk-11.0.24 IdentityIQ: 8.5 (During 8.4p2 to 8.5 upgradation) Database: SQL Server 16.0 (SQL Server 2022)
During IdentityIQ 8.4p2 to IdentityIQ 8.5 upgradation/migration, getting following schema upgrade errors: DB script name:upgrade_identityiq_tables.sqlserver
Stack Trace:
Caution: Changing any part of an object name could break scripts and stored procedures.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 98]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 105]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Caution: Changing any part of an object name could break scripts and stored procedures.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 111]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Caution: Changing any part of an object name could break scripts and stored procedures.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 117]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 132]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 135]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Msg 15248, Level 11, State 1, Procedure sp_rename, Line 367 [Batch Start Line 138]
Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Msg 1913, Level 16, State 1, Line 143
The operation failed because an index or statistics with name 'spt_hac_app_name_ci' already exists on table 'identityiqah.spt_hist_account_capture'.
Msg 1913, Level 16, State 1, Line 146
The operation failed because an index or statistics with name 'spt_hist_pvr_deleted' already exists on table 'identityiqah.spt_policy_violation_remediation_capture'.
(1 row affected)
(1 row affected)
Completion time:2025-08-08TO7:34:29.6653439+04:00
I have validated this on my local MySQL setup. Tomorrow, I’ll attempt to fix it in the SQL Server script (upgrade_identityiq_tables.sqlserver) and provide you with an update.
The recommended syntax change worked fine and completed the migration in the Dev environment. A sanity check was performed after the migration, and everything looks good.
Note: For others who want to use this same index syntax fix, please consult the SailPoint support team for official confirmation. I will also wait for the SailPoint support team’s official confirmation before applying the same fix to the Stage environment upgrade/migration.
As a reminder, SailPoint Support does not offer advice on database indexing, so it is recommended that you review the documentation for IdentityIQ and consult with your DBA, who is the expert on database changes.
This is in regard to your comment referring the the SailPoint Support team for assistance:
Note: For others who want to use this same index syntax fix, please consult the SailPoint support team for official confirmation. I will also wait for the SailPoint support team’s official confirmation before applying the same fix to the Stage environment upgrade/migration.