Difference between revisions of "SUNScholar/Indexes/Purge"
Jump to navigation
Jump to search
m |
m |
||
| Line 2: | Line 2: | ||
'''[[SUNScholar/Indexes|Back to Indexes]]''' | '''[[SUNScholar/Indexes|Back to Indexes]]''' | ||
</center> | </center> | ||
| − | |||
==<font color="red">'''OLD INDEX PURGE'''</font>== | ==<font color="red">'''OLD INDEX PURGE'''</font>== | ||
<font color="red">'''Check that you have a backup of the database before doing any purging. You have been warned.'''</font> | <font color="red">'''Check that you have a backup of the database before doing any purging. You have been warned.'''</font> | ||
Revision as of 09:44, 5 August 2016
Back to Indexes
Contents
OLD INDEX PURGE
Check that you have a backup of the database before doing any purging. You have been warned.
For DSpace =>5.X
A new command has been introduced with DSpace =>5.X. See below for an example.
$HOME/bin/dspace index-db-browse -f -d
See step 11 of: https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace
For DSpace <=4.X
Step 1 - Remove "communities2item" table
Login into the server as the dspace user and then type the following;
sudo -i
su - postgres
psql dspace
DELETE from communities2item;
\q
exit
exit
exit
Step 2 - Remove all "bi_" tables
I used pgadmin to do a "cascade drop" of all the bi_* tables, where bi = browse index.
