Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[wlrutherford]

Reindex is complete. Browse counts are lower on new system.

I was hoping it was just a new way of indexing but I found an author who 
shows up on the old site but not the new
one. If I copy/paste the file handle to the new system I'm directed to the 
file so the files are on the new system, and
even in the right place, the system just doesn't where/how to find them 
unless told explicitly.

So now I'm poking through the webapps hierarchy (and PostgreSQL tables) to 
find where browse and search
specifications get converted into file handles.



On Wednesday, March 28, 2018 at 12:52:03 PM UTC-8, helix84 wrote:
>
> The Access Rights Awareness feature was added around DSpace 3. Usually 
> what people upgrading from an older version are surprised to see is DSpace 
> showing lower item counts than before for users who are not logged in.
>
>
> https://wiki.duraspace.org/display/DSDOC6x/Discovery#Discovery-AccessRightsAwareness
>
> https://jira.duraspace.org/browse/DS-1229
>
> Assuming that the reindex is complete (which you'd see running in 
> dspace.log), compare item counts in Browse by Title or Browse by Issue 
> Date. Then log in as administrator and compare them again, they should be 
> equal.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[helix84]

The Access Rights Awareness feature was added around DSpace 3. Usually what
people upgrading from an older version are surprised to see is DSpace
showing lower item counts than before for users who are not logged in.

https://wiki.duraspace.org/display/DSDOC6x/Discovery#Discovery-AccessRightsAwareness

https://jira.duraspace.org/browse/DS-1229

Assuming that the reindex is complete (which you'd see running in
dspace.log), compare item counts in Browse by Title or Browse by Issue
Date. Then log in as administrator and compare them again, they should be
equal.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[wlrutherford]

Curiouser and curiouser...

After one of my changes introduced weird formatting errors to the webpage I 
rolled back an earlier version.
On inspection I saw it was reporting even more records than before 
(differences of 123, 70, 0 from what I
was expecting). This was great news.
But an hour later when I checked again the differences had increased to the 
figures I noted before! What
happened? None of the dspace cron scripts were due to run for >12hrs so I 
doubt they were involved.

I've hunted for records which are missing on the new system to see if 
there's an obvious reason why they
were dropped. We did find a difference in the number of fields in one of 
the tables but I don't know if that's
even related to this issue.

What exactly is the difference between the old database format and the new? 
We haven't introduced any
modifications that I'm aware of so there must be another reason migration 
is partially failing for us.

.
On Tuesday, March 13, 2018 at 5:09:51 PM UTC-8, wlruth...@alaska.edu wrote:
>
> Yes, I checked browse by author, title, and subject. All were off a bit: 
> by 288, 182, and 11 records respectively. But I hadn't
> applied custom themes and *perhaps* some of the configuration changes. 
> I'm sure the customized themes can wait but I'll
> double-check that all of the configuration settings are being set 
> correctly. I also hadn't noticed any errors in the logs but I
> did skim them pretty quickly to verify I was seeing (thousands of) 
> re-ingest notices. I'll go through the logs with a finer comb.
>
> Thanks for the possible gotchas.
>
>
> On Tuesday, March 13, 2018 at 10:24:06 AM UTC-8, Tim Donohue wrote:
>>
>> Hi,
>>
>> Have you checked your DSpace logs to see if there were any errors 
>> reported there, either from the 'dspace database migrate', or from the 
>> full site reindex (over the weekend)?  That'd be the first place I'd 
>> recommend checking if there are missing items.
>>
>> More on checking logs for errors at: 
>> https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error
>>
>> Also, I'd recommend comparing the number of items listed in "Browse by 
>> Title" between the two versions (DSpace 3.6 and 5.5).  That will give you 
>> better information on whether all the Items have been updated/upgraded 
>> successfully. It sounds like you are comparing the numbers in "Browse by 
>> Author"...and while those should pretty much match up, it is possible that 
>> DSpace 5 has reindexed your author information in such a way that it 
>> removed some duplicates that may have existed in DSpace 3.  
>>
>> You also may wish to verify that any configurations from your old DSpace 
>> (version 3.6) have been brought forward into DSpace 5.5. So, for example, 
>> if you customized Browse by Author settings (in dspace.cfg) to also use 
>> extra fields (not just "dc.contributor.author"), then you should verify 
>> that DSpace 5 is using those same fields (if it is not, then its author 
>> count would be lower).
>>
>> That's just a couple of ideas that come to mind. Hopefully one of them 
>> will help you start to figure out what may be going on.  As always, let us 
>> know if you have further questions or figure out more of what may be 
>> happening.
>>
>> Good luck,
>>
>> Tim
>>
>> On Tue, Mar 13, 2018 at 12:37 PM  wrote:
>>
>>> I gave it the weekend to be sure it was done then manually ran 'dspace 
>>> database migrate' again. If returned much quicker but nothing
>>> had changed. Of the 5105 author records I expected it found 4817. I 
>>> guess that's not bad. If I knew a way to tell what it's not finding
>>> it might not be too much work to just reentering them by hand. But so 
>>> far I haven't turned up what is different between the two copies.
>>>
>>>
>>> On Thursday, March 8, 2018 at 9:19:00 AM UTC-9, Tim Donohue wrote:
>>>
 Hello,

 While I'm not certain this is the case, it *sounds* like the behavior 
 you are seeing is related to a full reindex of the site.

 After any database upgrade (via `dspace database migrate`), DSpace will 
 trigger a full reindex of your site the next time you start up Tomcat (or 
 whatever servlet container you are using). This full reindex may take some 
 time (minutes or even hours, depending on the amount of content), but it 
 runs in the backend. A reindex is required for major upgrades, as often 
 the 
 database structure changes, and your search/browse indexes then need to be 
 updated based on those changes.

 You may wish to check your DSpace log files to see if you are seeing 
 messages related to individual Items being "indexed".  If so, this is the 
 reindex processing each file, and once it is complete all your records 
 should reappear in the search/browse.  While it is reindexing you still 
 can 
 use the site, but not all records may appear (they each will appear as 
 they 
 are reindexed).

 And just to clarify, 

[dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[Jose Miguel Ravasi]

Hola lo que puedo aportar es el procedimiento que hice para migrar de 
Dspace 4.2 hacia 6.2
Por si les es util.
Saludos

Jose M Ravasi
Facultad de Ingenieria
Universidad Nacional de Mar del  Plata


*Procedimiento migrar BD postgres *

*DSPACE 4.2 a Dspace 6.x*

Siempre tener presente esta secciòn 
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace



Realizado en Ubuntu 16.04

Puede realizarce desde el phppgadmin (interface web de administración del 
postgres) ó por linea de comando desde terminal.

Debe crearse el usuario/rol dspace, la base de datos dspace, con la 
codificación UTF-8, hacer propietario de la bd a dspace y crear la 
extensión pgcryto

Se espera que usted sepa la contraseña del rol/usuario postgres 

psql Template1 -U postgres

alter user postgres with password ‘admin’;

devuelve ALTER ROLE

\q para salir



Desde terminal ingrese comando: 

sudo createuser -U postgres -d -A -P dspace

passw NEW ROLE 123456 (o la pasww que usted desee, recordar que esta se usa 
luego en el local.cfg

sudo su – postgres

puede pedir password del usuario postgres

createdb -E UNICODE dspace (crea la bd)

psql -U postgres -d dspace (entrar al shell para dar permisos)



ALTER ROLE dspace WITH PASSWORD ‘123456’;

devuelve ALTER ROLE

ALTER DATABASE dspace OWNER TO dspace; (hace propietario a de bd a dspace)

devuelve ALTER ROLE

GRANT ALL PRIVILEGE ON DATABASE dspace TO dspace; (dar privilegios sobre bd)

devuelve ALTER ROLE

CREATE EXTENSION pgcrypto; (crear extensión pgcrypto)

\l (lista las bd y sus propietarios)

\q salir



En carpeta [dspace-target]/bin/dspace database info

Devuelve versión de la bd y otras aspectos, no debe aparecer error

Detener el Tomcat (systemctl stop tomcat o similar)

Desde [dspace-source]/dspace/target/dspace-installer/ant update

*Ingresar los registros *de la bd desde un archivo sql generado en el 
postgres del Dspace 4.2. Para generar el sql con los registros debe hacer

- desde terminal

pg_dump U[databaseuser] f [backupfilelocation/namefile] [databasename]

a saber

pg_dump U dspace f /home/dspace/rinfi42.sql dspace



Volviendo al paso Ingresar los registros debe hacer desde terminal

psql -U dspace -W -h localhost dspace < rinfi42.sql

Pide contraseña del usuario/ro dspace 123456 en nuestro caso

Devuelve lineas que informan del import de datos y tablas

En carpeta [dspace-target]/bin/dspace database info

Devuelve la info en fomato de tabla e informa al final

BD compatible con Dspace version 4.0

all upgrades *after* version 4,0 will be run during next migration

If you’ d like to upgrade now, simply run “dspace database migrate”

En carpeta [dspace-target]/bin/dspace database migrate

trabaja un rato 

En carpeta [dspace-target]/bin/dspace database info

Ya no debe informar de error

Copiar la carpeta assetstore del original a mi nuevo [dspace-target]

Rearrancar el Tomcat

The database migration should also *automatically trigger* your 
metadata/file registries to be updated (based on the config files in 
[dspace]/config/registries/).  However, if this update was NOT triggered, 
you can also manually run these registry updates (they will not harm 
existing registry contents) as follows:





[dspace]/bin/dspace 
registry-loader-metadata[dspace]/config/registries/dcterms-types.xml

[dspace]/bin/dspace registry-loader -metadata 
[dspace]/config/registries/dublin-core-types.xml



[dspace]/bin/dspace registry-loader -metadata 
[dspace]/config/registries/eperson-types.xml 



[dspace]/bin/dspace registry-loader -metadata 
[dspace]/config/registries/local-types.xml



[dspace]/bin/dspace registry-loader -metadata 
[dspace]/config/registries/sword-metadata.xml



[dspace]/bin/dspace registry-loader -metadata 
[dspace]/config/registries/workflow-types.xml





El miércoles, 7 de marzo de 2018, 21:17:03 (UTC-3), wlruth...@alaska.edu 
escribió:
>
>
> While upgrading our repository we initially built DSpace-6.0 but it was 
> unable to fully ingest
> the legacy postgres database used by the older DSpace-3.1 system. We were 
> told we'd need
> to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade to 
> DSpace-6.0.
>
> So we built a DSpace-3.6 system and it was able to read the DSpace-3.1 
> database. We then
> built a DSpace-5.5 system with a copy of the entire database. All seemed 
> well at first but on
> closer inspection it's doing the same thing as our original DSpace-6.0 
> system - ignoring most
> of the database. The manual says DSpace will automatically fix the 
> database or that the
> 'dspace database migrate' command will accomplish this. Neither seems to 
> have had any
> effect. I'm scanning through logfiles to see if it silently told me that 
> something went wrong.
>
> I know other DSpace users have successfully upgraded from DSpace-3.x to 
> DSpace-6.0 so
> that's encouraging. Am I missing a step? Do I have install DSpace-4.x 
> before DSpace-5.x?
>
> Thank you for any help you can provide.
>
>
>
>

-- 
You received this message 

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[wlrutherford]

Yes, I checked browse by author, title, and subject. All were off a bit: by 
288, 182, and 11 records respectively. But I hadn't
applied custom themes and *perhaps* some of the configuration changes. I'm 
sure the customized themes can wait but I'll
double-check that all of the configuration settings are being set 
correctly. I also hadn't noticed any errors in the logs but I
did skim them pretty quickly to verify I was seeing (thousands of) 
re-ingest notices. I'll go through the logs with a finer comb.

Thanks for the possible gotchas.


On Tuesday, March 13, 2018 at 10:24:06 AM UTC-8, Tim Donohue wrote:
>
> Hi,
>
> Have you checked your DSpace logs to see if there were any errors reported 
> there, either from the 'dspace database migrate', or from the full site 
> reindex (over the weekend)?  That'd be the first place I'd recommend 
> checking if there are missing items.
>
> More on checking logs for errors at: 
> https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error
>
> Also, I'd recommend comparing the number of items listed in "Browse by 
> Title" between the two versions (DSpace 3.6 and 5.5).  That will give you 
> better information on whether all the Items have been updated/upgraded 
> successfully. It sounds like you are comparing the numbers in "Browse by 
> Author"...and while those should pretty much match up, it is possible that 
> DSpace 5 has reindexed your author information in such a way that it 
> removed some duplicates that may have existed in DSpace 3.  
>
> You also may wish to verify that any configurations from your old DSpace 
> (version 3.6) have been brought forward into DSpace 5.5. So, for example, 
> if you customized Browse by Author settings (in dspace.cfg) to also use 
> extra fields (not just "dc.contributor.author"), then you should verify 
> that DSpace 5 is using those same fields (if it is not, then its author 
> count would be lower).
>
> That's just a couple of ideas that come to mind. Hopefully one of them 
> will help you start to figure out what may be going on.  As always, let us 
> know if you have further questions or figure out more of what may be 
> happening.
>
> Good luck,
>
> Tim
>
> On Tue, Mar 13, 2018 at 12:37 PM  
> wrote:
>
>> I gave it the weekend to be sure it was done then manually ran 'dspace 
>> database migrate' again. If returned much quicker but nothing
>> had changed. Of the 5105 author records I expected it found 4817. I guess 
>> that's not bad. If I knew a way to tell what it's not finding
>> it might not be too much work to just reentering them by hand. But so far 
>> I haven't turned up what is different between the two copies.
>>
>>
>> On Thursday, March 8, 2018 at 9:19:00 AM UTC-9, Tim Donohue wrote:
>>
>>> Hello,
>>>
>>> While I'm not certain this is the case, it *sounds* like the behavior 
>>> you are seeing is related to a full reindex of the site.
>>>
>>> After any database upgrade (via `dspace database migrate`), DSpace will 
>>> trigger a full reindex of your site the next time you start up Tomcat (or 
>>> whatever servlet container you are using). This full reindex may take some 
>>> time (minutes or even hours, depending on the amount of content), but it 
>>> runs in the backend. A reindex is required for major upgrades, as often the 
>>> database structure changes, and your search/browse indexes then need to be 
>>> updated based on those changes.
>>>
>>> You may wish to check your DSpace log files to see if you are seeing 
>>> messages related to individual Items being "indexed".  If so, this is the 
>>> reindex processing each file, and once it is complete all your records 
>>> should reappear in the search/browse.  While it is reindexing you still can 
>>> use the site, but not all records may appear (they each will appear as they 
>>> are reindexed).
>>>
>>> And just to clarify, you no longer need to upgrade from one major 
>>> version to the next.  So, you should not need to upgrade from DSpace 3 to 5 
>>> to 6.  You can now *directly* upgrade from any prior release to DSpace 6 
>>> (even from DSpace 1.0 -> 6.0 would work).  The only requirement is that you 
>>> need to make sure your database backend is upgraded first, to a compatible 
>>> release.  So, for example, if you are running a very old version of 
>>> Postgres or Oracle, you'd want to upgrade that database backend to a recent 
>>> version (as required by DSpace 6), and then you should be able to upgrade 
>>> directly to DSpace 6 per the upgrade instructions at: 
>>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>>>
>>> Hopefully that helps! If you have further questions, feel free to ask 
>>> them on this list.
>>>
>>> Tim
>>>
>>> On Thu, Mar 8, 2018 at 12:04 PM  wrote:
>>>
>> Interesting... It looks like the number of records has updated itself 
 since yesterday.
 Perhaps the automatic database migration is working, just slowly. I'll 
 watch it.


 On Wednesday, 

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[Tim Donohue]

Hi,

Have you checked your DSpace logs to see if there were any errors reported
there, either from the 'dspace database migrate', or from the full site
reindex (over the weekend)?  That'd be the first place I'd recommend
checking if there are missing items.

More on checking logs for errors at:
https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error

Also, I'd recommend comparing the number of items listed in "Browse by
Title" between the two versions (DSpace 3.6 and 5.5).  That will give you
better information on whether all the Items have been updated/upgraded
successfully. It sounds like you are comparing the numbers in "Browse by
Author"...and while those should pretty much match up, it is possible that
DSpace 5 has reindexed your author information in such a way that it
removed some duplicates that may have existed in DSpace 3.

You also may wish to verify that any configurations from your old DSpace
(version 3.6) have been brought forward into DSpace 5.5. So, for example,
if you customized Browse by Author settings (in dspace.cfg) to also use
extra fields (not just "dc.contributor.author"), then you should verify
that DSpace 5 is using those same fields (if it is not, then its author
count would be lower).

That's just a couple of ideas that come to mind. Hopefully one of them will
help you start to figure out what may be going on.  As always, let us know
if you have further questions or figure out more of what may be happening.

Good luck,

Tim

On Tue, Mar 13, 2018 at 12:37 PM  wrote:

> I gave it the weekend to be sure it was done then manually ran 'dspace
> database migrate' again. If returned much quicker but nothing
> had changed. Of the 5105 author records I expected it found 4817. I guess
> that's not bad. If I knew a way to tell what it's not finding
> it might not be too much work to just reentering them by hand. But so far
> I haven't turned up what is different between the two copies.
>
>
> On Thursday, March 8, 2018 at 9:19:00 AM UTC-9, Tim Donohue wrote:
>
>> Hello,
>>
>> While I'm not certain this is the case, it *sounds* like the behavior you
>> are seeing is related to a full reindex of the site.
>>
>> After any database upgrade (via `dspace database migrate`), DSpace will
>> trigger a full reindex of your site the next time you start up Tomcat (or
>> whatever servlet container you are using). This full reindex may take some
>> time (minutes or even hours, depending on the amount of content), but it
>> runs in the backend. A reindex is required for major upgrades, as often the
>> database structure changes, and your search/browse indexes then need to be
>> updated based on those changes.
>>
>> You may wish to check your DSpace log files to see if you are seeing
>> messages related to individual Items being "indexed".  If so, this is the
>> reindex processing each file, and once it is complete all your records
>> should reappear in the search/browse.  While it is reindexing you still can
>> use the site, but not all records may appear (they each will appear as they
>> are reindexed).
>>
>> And just to clarify, you no longer need to upgrade from one major version
>> to the next.  So, you should not need to upgrade from DSpace 3 to 5 to 6.
>> You can now *directly* upgrade from any prior release to DSpace 6 (even
>> from DSpace 1.0 -> 6.0 would work).  The only requirement is that you need
>> to make sure your database backend is upgraded first, to a compatible
>> release.  So, for example, if you are running a very old version of
>> Postgres or Oracle, you'd want to upgrade that database backend to a recent
>> version (as required by DSpace 6), and then you should be able to upgrade
>> directly to DSpace 6 per the upgrade instructions at:
>> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>>
>> Hopefully that helps! If you have further questions, feel free to ask
>> them on this list.
>>
>> Tim
>>
>> On Thu, Mar 8, 2018 at 12:04 PM  wrote:
>>
> Interesting... It looks like the number of records has updated itself
>>> since yesterday.
>>> Perhaps the automatic database migration is working, just slowly. I'll
>>> watch it.
>>>
>>>
>>> On Wednesday, March 7, 2018 at 3:17:03 PM UTC-9, wlruth...@alaska.edu
>>> wrote:


 While upgrading our repository we initially built DSpace-6.0 but it was
 unable to fully ingest
 the legacy postgres database used by the older DSpace-3.1 system. We
 were told we'd need
 to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade
 to DSpace-6.0.

 So we built a DSpace-3.6 system and it was able to read the DSpace-3.1
 database. We then
 built a DSpace-5.5 system with a copy of the entire database. All
 seemed well at first but on
 closer inspection it's doing the same thing as our original DSpace-6.0
 system - ignoring most
 of the database. The manual says DSpace will automatically fix the
 database or that the

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[wlrutherford]

I gave it the weekend to be sure it was done then manually ran 'dspace 
database migrate' again. If returned much quicker but nothing
had changed. Of the 5105 author records I expected it found 4817. I guess 
that's not bad. If I knew a way to tell what it's not finding
it might not be too much work to just reentering them by hand. But so far I 
haven't turned up what is different between the two copies.

On Thursday, March 8, 2018 at 9:19:00 AM UTC-9, Tim Donohue wrote:
>
> Hello,
>
> While I'm not certain this is the case, it *sounds* like the behavior you 
> are seeing is related to a full reindex of the site.
>
> After any database upgrade (via `dspace database migrate`), DSpace will 
> trigger a full reindex of your site the next time you start up Tomcat (or 
> whatever servlet container you are using). This full reindex may take some 
> time (minutes or even hours, depending on the amount of content), but it 
> runs in the backend. A reindex is required for major upgrades, as often the 
> database structure changes, and your search/browse indexes then need to be 
> updated based on those changes.
>
> You may wish to check your DSpace log files to see if you are seeing 
> messages related to individual Items being "indexed".  If so, this is the 
> reindex processing each file, and once it is complete all your records 
> should reappear in the search/browse.  While it is reindexing you still can 
> use the site, but not all records may appear (they each will appear as they 
> are reindexed).
>
> And just to clarify, you no longer need to upgrade from one major version 
> to the next.  So, you should not need to upgrade from DSpace 3 to 5 to 6.  
> You can now *directly* upgrade from any prior release to DSpace 6 (even 
> from DSpace 1.0 -> 6.0 would work).  The only requirement is that you need 
> to make sure your database backend is upgraded first, to a compatible 
> release.  So, for example, if you are running a very old version of 
> Postgres or Oracle, you'd want to upgrade that database backend to a recent 
> version (as required by DSpace 6), and then you should be able to upgrade 
> directly to DSpace 6 per the upgrade instructions at: 
> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>
> Hopefully that helps! If you have further questions, feel free to ask them 
> on this list.
>
> Tim
>
> On Thu, Mar 8, 2018 at 12:04 PM  
> wrote:
>
>> Interesting... It looks like the number of records has updated itself 
>> since yesterday.
>> Perhaps the automatic database migration is working, just slowly. I'll 
>> watch it.
>>
>>
>> On Wednesday, March 7, 2018 at 3:17:03 PM UTC-9, wlruth...@alaska.edu 
>> wrote:
>>>
>>>
>>> While upgrading our repository we initially built DSpace-6.0 but it was 
>>> unable to fully ingest
>>> the legacy postgres database used by the older DSpace-3.1 system. We 
>>> were told we'd need
>>> to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade to 
>>> DSpace-6.0.
>>>
>>> So we built a DSpace-3.6 system and it was able to read the DSpace-3.1 
>>> database. We then
>>> built a DSpace-5.5 system with a copy of the entire database. All seemed 
>>> well at first but on
>>> closer inspection it's doing the same thing as our original DSpace-6.0 
>>> system - ignoring most
>>> of the database. The manual says DSpace will automatically fix the 
>>> database or that the
>>> 'dspace database migrate' command will accomplish this. Neither seems to 
>>> have had any
>>> effect. I'm scanning through logfiles to see if it silently told me that 
>>> something went wrong.
>>>
>>> I know other DSpace users have successfully upgraded from DSpace-3.x to 
>>> DSpace-6.0 so
>>> that's encouraging. Am I missing a step? Do I have install DSpace-4.x 
>>> before DSpace-5.x?
>>>
>>> Thank you for any help you can provide.
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[Tim Donohue]

Hello,

While I'm not certain this is the case, it *sounds* like the behavior you
are seeing is related to a full reindex of the site.

After any database upgrade (via `dspace database migrate`), DSpace will
trigger a full reindex of your site the next time you start up Tomcat (or
whatever servlet container you are using). This full reindex may take some
time (minutes or even hours, depending on the amount of content), but it
runs in the backend. A reindex is required for major upgrades, as often the
database structure changes, and your search/browse indexes then need to be
updated based on those changes.

You may wish to check your DSpace log files to see if you are seeing
messages related to individual Items being "indexed".  If so, this is the
reindex processing each file, and once it is complete all your records
should reappear in the search/browse.  While it is reindexing you still can
use the site, but not all records may appear (they each will appear as they
are reindexed).

And just to clarify, you no longer need to upgrade from one major version
to the next.  So, you should not need to upgrade from DSpace 3 to 5 to 6.
You can now *directly* upgrade from any prior release to DSpace 6 (even
from DSpace 1.0 -> 6.0 would work).  The only requirement is that you need
to make sure your database backend is upgraded first, to a compatible
release.  So, for example, if you are running a very old version of
Postgres or Oracle, you'd want to upgrade that database backend to a recent
version (as required by DSpace 6), and then you should be able to upgrade
directly to DSpace 6 per the upgrade instructions at:
https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace

Hopefully that helps! If you have further questions, feel free to ask them
on this list.

Tim

On Thu, Mar 8, 2018 at 12:04 PM  wrote:

> Interesting... It looks like the number of records has updated itself
> since yesterday.
> Perhaps the automatic database migration is working, just slowly. I'll
> watch it.
>
>
> On Wednesday, March 7, 2018 at 3:17:03 PM UTC-9, wlruth...@alaska.edu
> wrote:
>>
>>
>> While upgrading our repository we initially built DSpace-6.0 but it was
>> unable to fully ingest
>> the legacy postgres database used by the older DSpace-3.1 system. We were
>> told we'd need
>> to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade to
>> DSpace-6.0.
>>
>> So we built a DSpace-3.6 system and it was able to read the DSpace-3.1
>> database. We then
>> built a DSpace-5.5 system with a copy of the entire database. All seemed
>> well at first but on
>> closer inspection it's doing the same thing as our original DSpace-6.0
>> system - ignoring most
>> of the database. The manual says DSpace will automatically fix the
>> database or that the
>> 'dspace database migrate' command will accomplish this. Neither seems to
>> have had any
>> effect. I'm scanning through logfiles to see if it silently told me that
>> something went wrong.
>>
>> I know other DSpace users have successfully upgraded from DSpace-3.x to
>> DSpace-6.0 so
>> that's encouraging. Am I missing a step? Do I have install DSpace-4.x
>> before DSpace-5.x?
>>
>> Thank you for any help you can provide.
>>
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Database migration DSpace-3.6 to DSpace-5.5

[wlrutherford]

Interesting... It looks like the number of records has updated itself since 
yesterday.
Perhaps the automatic database migration is working, just slowly. I'll 
watch it.


On Wednesday, March 7, 2018 at 3:17:03 PM UTC-9, wlruth...@alaska.edu wrote:
>
>
> While upgrading our repository we initially built DSpace-6.0 but it was 
> unable to fully ingest
> the legacy postgres database used by the older DSpace-3.1 system. We were 
> told we'd need
> to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade to 
> DSpace-6.0.
>
> So we built a DSpace-3.6 system and it was able to read the DSpace-3.1 
> database. We then
> built a DSpace-5.5 system with a copy of the entire database. All seemed 
> well at first but on
> closer inspection it's doing the same thing as our original DSpace-6.0 
> system - ignoring most
> of the database. The manual says DSpace will automatically fix the 
> database or that the
> 'dspace database migrate' command will accomplish this. Neither seems to 
> have had any
> effect. I'm scanning through logfiles to see if it silently told me that 
> something went wrong.
>
> I know other DSpace users have successfully upgraded from DSpace-3.x to 
> DSpace-6.0 so
> that's encouraging. Am I missing a step? Do I have install DSpace-4.x 
> before DSpace-5.x?
>
> Thank you for any help you can provide.
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.