After upgrade from DSpace 3.3 to 5.2 I run "dspace -f -d -v" and get this
output:

 

Using DSpace installation in: C:\DSPACE

Creating browse indexes for DSpace

init complete (15 ms)

Deleting browse tables

Deleting old indices

Checking for bi_1

Checking for bi_1_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_2

Checking for bi_2_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_3

Checking for bi_3_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_4

Checking for bi_4_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_5

Checking for bi_5_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_6

Checking for bi_6_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_7

Checking for bi_7_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_8

Checking for bi_8_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_9

Checking for bi_9_dis

... doesn't exist; but will carry on as there may be something that
conflicts

Checking for bi_10

Checking for bi_10_dis

... doesn't exist; no more tables to delete

Browse tables deleted

Started: 1434210155527

Ended: 1434210155871

Elapsed time: 0 secs (344 msecs)

 

I have a problems with "dspace cleanup -v", there is some bitstream ids,
that cannot be deleted. What should I do?

------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to