I finally figured out the problem. The owner of the versionhistory and versionitem tables and versionhistory_seq and versionitem_seq sequences was changed from dspace to postgres, effectively preventing us from adding any new items to DSpace or from backing up the database.
Does anybody have any suggestions as to how to harden DSpace? Thank you for all your help. Alain -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of helix84 Sent: Wednesday, March 27, 2013 12:25 PM To: Alain Tschanz Cc: [email protected] Subject: Re: [Dspace-tech] Cannot create items after upgrading to DSpace 3.0 On Wed, Mar 27, 2013 at 5:20 PM, Alain Tschanz <[email protected]> wrote: > None of the 104 items have a resource_id, but they do have a handle_id, > handle and resource_typ_id. To remove those items from our database do I just > delete the handles from the handle table? Ah, in that case, yes. It is safe to delete handles without resource_id. I thought you had resource_ids with NULL handles. IIRC, your situation happens when you remove an item that has a handle assigned. Anyway, before you do any change in the database, first do a backup. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
