Symptoms:
Internal Error 500 after the publishing of the SVM 3rd party packages. The package gets published but unable to edit the published packages.
Diagnosis: The following issues appear when the sps_packages table is missing/not complete or the SVM on-premise has been updated to latest version but the following table sps_packages have not been updated correctly. Please follow the below steps to verify the issue.
Log in to your DB server
mysql -u root -p
Check the ca.csi_pdb_info table if you are on the latest version of SVM-on-premise.
select * from ca.csi_pdb_info;
Please Note: If you already at the latest version. then follow the solution steps otherwise, first try to update your SVM on-premise to the latest version.
Solution:
Select the private DB which ends with your server customer-id.
use ca_cust-id;
select the count of sps_packages table and check if have any count value.
select count(*) from sps_packages;
If the count is Zero then execute the below commands.
drop table sps_packages;
CREATE TABLE `sps_packages` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`account_id` int(11) NOT NULL,
`guid` char(36) NOT NULL,
`xmlText` mediumtext DEFAULT NULL,
`package_type` tinyint(4) DEFAULT NULL,
`product_id` int(11) DEFAULT NULL,
`product_name` varchar(255) DEFAULT NULL,
`vendor_name` varchar(100) DEFAULT NULL,
`secure_version` varchar(255) DEFAULT NULL,
`min_version` varchar(100) DEFAULT NULL,
`patched_version` varchar(255) DEFAULT NULL,
`architecture` tinyint(3) unsigned NOT NULL DEFAULT 0,
`version_rule_id` int(11) DEFAULT NULL COMMENT 'Version Rule Id to keep track of the packages/solutions related to the insecure installation',
`sps_params` varchar(500) DEFAULT NULL,
`created_at` datetime DEFAULT NULL,
`vpm_id` int(11) DEFAULT 0,
PRIMARY KEY (`id`),
UNIQUE KEY `guid` (`guid`),
KEY `guid_idx` (`guid`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
