|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
dspace dsrun org.dspace.browse.IndexBrowse -r -f
all the browse related tables, view and index are removed except for the communities2item table that is not cleaned.
You can easly fix this running the following sql:
delete from communities2item;
if you re-enable a dbms browse (postgres or oracle) just need to re-run the
dspace dsrun org.dspace.browse.IndexBrowse -r -f
and the communities2item will be re-populated.
For DSpace 4.0 a patch will be post shortly to make this further step (sql delete) unnecessary to allow smooth switch to SOLRBrowseDAOs