Cadet 3rd Class
Cadet 3rd Class
9430 views

SSC DB Seed Problem: Violation of PRIMARY_KEY constraint while migration

Jump to solution

Not exactly same as discussion opened by Enrico Frescura, "SSC DB Seed problem", but I also have problem with the SSC db seed process (HP Fortify Suite 4.42), while migrating SSC from 4.30 to 4.42 using configuration wizard. We got the following error while seeding HP_Fortify_Process_Seed_Bundled_2015_Q3.zip template:

Caused by: java.sql.BatchUpdateException: Violation of PRIMARY KEY constraint 'PK_CATPACKLOOKUP'. Cannot insert duplicate key in object 'dbo.catpacklookup'. The duplicate key value is (4857, Code Correctness: Class Does Not Implement equals).

    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1132) ~[sqljdbc4-2.0.jar:?]

    at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) ~[commons-dbcp-1.4.jar:1.4]

    at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) ~[commons-dbcp-1.4.jar:1.4]

    ....

and stuck on that seeding process, yet the we successfully execute the migration.sql. Full stacktrace is attached.

Previously, when installing HP Fortify 4.30 we use Q1 seed bundled, (eg. HP_Fortify_Process_Seed_Bundled_2015_Q1.zip). I've searched in this site and documentations, yet haven't found clue to to resolve this issue. Any suggestion?

Thanks.

0 Likes
1 Solution

Accepted Solutions
Vice Admiral
Vice Admiral

This error indicates that your database has a case-insensitive collation. This is not supported with 4.4x, so you will have to migrate the database to use a case-sensitive collation before proceeding with the upgrade.

That process is detailed beginning page 32 in the install and config document​ for SQL Server.

If you encounter any difficulties, I recommend opening a ticket with us to get dedicated help. Email fortifytechsupport@hpe.com or open a case with your portal account at https://support.fortify.com

-Josh

Fortify L3 Support Engineer

View solution in original post

0 Likes
2 Replies
Vice Admiral
Vice Admiral

This error indicates that your database has a case-insensitive collation. This is not supported with 4.4x, so you will have to migrate the database to use a case-sensitive collation before proceeding with the upgrade.

That process is detailed beginning page 32 in the install and config document​ for SQL Server.

If you encounter any difficulties, I recommend opening a ticket with us to get dedicated help. Email fortifytechsupport@hpe.com or open a case with your portal account at https://support.fortify.com

-Josh

Fortify L3 Support Engineer

View solution in original post

0 Likes
Cadet 3rd Class
Cadet 3rd Class

Hi Josh,

We did miss the SQL Server configuration at the beginning and too focus on migration procedure at page 145. These exception is gone after set the proper case-sensitive collation.

However we are facing new problem while seeding process. We have checked the prerequisite of installation procedure, yet have not found a clue. So, we decide to open a ticket instead. Thank you for your support.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.