Error "Table 'schema_version' already has a primary key defined" when trying to apply Incidents database

Article:TECH28790  |  Created: 2007-04-16  |  Updated: 2007-04-17  |  Article URL http://www.symantec.com/docs/TECH28790
Article Type
Technical Solution

Issue



When trying to apply the Incidents database from Configuration > Server Settings > Notification Server Settings > Incident Settings, the following error is shown.

The operation did not complete successfully, table 'schema_version' already has a primary key defined, see previous errors.


Environment



Upgrading to Helpdesk 6.0.297

Cause



A Primary Key was already manually created for the schema_version table using Enterprise Manager. (The primary key name had a random number appended to the end.) The Helpdesk upgrade checked for the existence of the known primary key name and was not able to find the key name expected, so it is trying to create it; however, the table already had a primary key (there can only be one) by a different name which prevented the creation of the new primary key.

Solution



Remove the manually created primary key from the schema_version table and reapply the Incident settings.

Legacy ID



34327


Article URL http://www.symantec.com/docs/TECH28790


Terms of use for this information are found in Legal Notices