Ok thanks David, the first error has gone but the second not.... For your info I was able to set only at 4000 RHNPACKAGECHANGELOG "TEXT" column value (5000 oracle say isn't possible) but I think this is sufficient.. Now remains to understand why the second error persists... Have you some other idea? What can I do? <div class="gmail_quote">2009/7/24 David Nutter <<a href="mailto:davidn@bioss.sari.ac.uk">davidn@bioss.sari.ac.uk</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, Jul 24, 2009 at 10:01:30AM +0200, Tommaso Rossetto wrote: > *Hi all, > > when I launch rhnpush I get this error message :* *snip* <div class="im"> > Error pushing base/CentOS/setroubleshoot-2.0.5-3.el5.noarch.rpm: Error > 500Error Message: > ORA-12899: value too large for column > "SPACEWALK"."RHNPACKAGECHANGELOG"."TEXT" (actual: 3002, maximum: 3000) > Error Class Code: 54 > Error Class Info: > Package Upload Failed due to uniqueness constraint violation. > Make sure the package does not have any duplicate dependencies or > does not already exists on the server (500) > Waiting 2 seconds and trying again... </div>The above should be easy to fix - just increase the size of the column "TEXT" in table RHNPACKAGECHANGELOG. Offhand, and untested, this will probably be a command like: ALTER TABLE RHNPACKAGECHANGELOG MODIFY (TEXT VARCHAR2(5000)); My knowledge of oracle is minimal so the above command may be wrong. Even if it succeeds it may have bad effects so use at your own risk. <div class="im"> > Error Message: > ORA-00001: unique constraint (SPACEWALK.RHN_CNP_CID_NID_UQ) violated > ORA-06512: at "SPACEWALK.RHN_CHANNEL", line 916 > ORA-06512: at line 1 > Error Class Code: 23 > Error Class Info: Could not update database entry. > > xargs: rhnpush: exited with status 255; aborting </div>Here follows some wild speculation: I think that constraint ensures that package IDs are unique on the spacewalk server. Possibly the previous error is leaving some kind of uncompleted upload which is causing the constraint to be violated but once the push session ends the failed uploads have their transactions rolled back leaving no visible evidence such as a half uploaded package visible on the spacewalk website. Consequently if you fix the first error, the second may go away too. End of wild speculation. Regards, -- David Nutter Tel: +44 (0)131 650 4888 BioSS, JCMB, King's Buildings, Mayfield Rd, EH9 3JZ. Scotland, UK Biomathematics and Statistics Scotland (BioSS) is formally part of The Scottish Crop Research Institute (SCRI), a registered Scottish charity No. SC006662 <div><div></div><div class="h5"> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </div></div></blockquote></div> -- Tommaso Rossetto vicolo I Maggio , 13 Maserada sul Piave - 31052 (TV)