I’m getting a bunch of these in the SMT Sync Report:
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
I probably won’t spend much time trying to figure out how to fix SMT however I’ll probably just rebuild.
[QUOTE=e972157;26694]I’m getting a bunch of these in the SMT Sync Report:
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
I probably won’t spend much time trying to figure out how to fix SMT however I’ll probably just rebuild.[/QUOTE]
Hello We figured out same issue on our SMT server. Server is SLES11SP3.
Downloading Product and Repository information
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
[QUOTE=jjouannet;27104]Hello We figured out same issue on our SMT server. Server is SLES11SP3.
Downloading Product and Repository information
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
DBD::mysql::db do failed: Duplicate entry ‘suse-linux-enterprise-server-sp1-10-online-i386’ for key ‘PRODUCTLOWER’ at /usr/lib/perl5/vendor_perl/5.10.0/SMT/SCCSync.pm line 675.
Any idea to solve this issue will be helpful.[/QUOTE]
I opened a Service Rrequest this morning about my instance of SMT producing that error when smt-sync is run. It was also producing lots more similar errors about other versions of suse-linux-enterprise-server. Less than two hours after raising the SR I was sent a link to PTF rpm which I was told would fix the issue, and it did. (The errors were still there on the first run of smt-sync after installing the update, but gone when I ran smt-sync the second time.) Given the speed with which I was sent a PTF I highly doubt it was created just for me. I suspect this is a known issue the fix for which is currently being provided to people who report the encountering the issue. I advise you raise a Service Request.