If you have run v8.0 or v8.1 of Jamf Pro, follow the instructions in this article before upgrading to v9.98. This will help determine whether your environment is affected by an issue that has no impact to functionality but causes increased error logging in your JSS when inventory records are updated.
First, run the following command and query to see if the unique key constraint exists in the serial_number field of the certificate_authority_issued table:
SHOW KEYS FROM certificate_authority_issued WHERE Non_unique=0 AND column_name='serial_number';
If "1 row in set" is returned, the constraint exists. If "empty set" is returned, the constraint does not exist, so do not proceed.
If the unique key constraint exists, do the following:
1. Back up your database.
2. Remove the constraint and the index to which it's attached by running the following command:
ALTER TABLE certificate_authority_issued DROP INDEX serial_number;
3. Put the index back into the database by running the following command:
CREATE INDEX serial_number ON certificate_authority_issued(serial_number);
When those steps are complete, you can upgrade to v9.98.