RE: [dspace-tech] Issue with database migration 6.3 to 7.4

[Cameron, Jacob]

Hi Mohammad,

I’ve actually done that prior to this and still get a large number of errors no 
matter whether I import using psql or pg_restore for an sql or plain text dump.

I’m wondering if I need to upgrade from 9.6 to 13 in Postgres before it’ll fix 
it.  I’m sure I had to do that when I went from 1.8.3 to 6 originally. I could 
be wrong.  That was along time ago.  But I have something about that in old 
notes from that upgrade.

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com  On Behalf Of 
Mohammad S. AlMutairi
Sent: January 27, 2023 5:21 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Issue with database migration 6.3 to 7.4

Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to 
phish...@uleth.ca.

Hi all,

@Tim, I think Jacob issue is caused by the way he dumped his old database and 
the way he tried to restore it.  Those " thousands of invalid command /N" 
should've not shown up if the database was dumped in a custom binary format and 
the new server database was cleaned (emptied) or even recreated before 
restoring the old database int it using pg_restore (It's a must to use 
pg_restore for any binary format dumps). There is a good chance for him to able 
to migrate unless he is affected by the known issue you mentioned.

https://www.pgadmin.org/docs/pgadmin4/6.18/backup_dialog.html

Regards
On Friday, January 27, 2023 at 11:04:41 PM UTC+3 Tim Donohue wrote:
Hi Sean,

This issue is a known issue which some sites encounter during the upgrade to 
DSpace 7 if they have previously ignored migrations which never ran during a 
past 5.x ->6.x upgrade​.  Essentially, to summarize, there are two "5.7" 
migrations which can fail during the upgrade to 7.x... these migrations are 
obsolete​ and can be skipped over.

There's a thread discussing this on dspace-tech here, along with "workarounds" 
to skip the two problematic 5.7 migrations: 
https://groups.google.com/g/dspace-tech/c/PlOA1WMvd4M/m/eBVE5RfhBgAJ

There's also a fix for this coming in the 7.5 release.  In 7.5 (due Feb 20) we 
have a new "./dspace database skip" command which can be used to skip 
problematic migrations.  See the PR at 
https://github.com/DSpace/DSpace/pull/8611

So, you are not the first person to hit this migration bug. An easier fix is 
coming in 7.5... but in the meantime, you can use the dspace-tech link above to 
workaround the issue if you want to upgrade immediately to 7.4.

Tim

From: dspac...@googlegroups.com  on behalf of 
Cameron, Jacob 
Sent: Friday, January 27, 2023 12:46 PM
To: Sean Carte 

Cc: DSpace Technical Support 
Subject: RE: [dspace-tech] Issue with database migration 6.3 to 7.4


I’ve tried importing with the postgres account, using an elevated command 
prompt, in pgadmin and they are all giving the same errors.  It’s still 
failing.  I’m at a loss now.  There’s a ton of tables missing when it finishes 
importing.



--

Jake Cameron, BCS(UNB)

Systems Support Specialist III

Information Systems and Technical Services University of Lethbridge Library

Phone:(403)329-2756

This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.



From: Sean Carte 
Sent: January 27, 2023 12:31 AM
To: Cameron, Jacob 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] Issue with database migration 6.3 to 7.4



Caution: This email was sent from someone outside of the University of 
Lethbridge. Do not click on links or open attachments unless you know they are 
safe. Suspicious emails should be forwarded to phis...@uleth.ca.



Hi Jacob



I had a similar problem with a database I was trying to import: many /N invalid 
commands. I gave my user superuser privileges and was able to import the dump 
without those errors.



Sean



On Thu, 26 Jan 2023 at 23:06, Cameron, Jacob  wrote:

Hi Everyone,

I exported my DSpace 6.3 database, imported it on the new server running 7.4.  
There were thousands of 

[dspace-tech] Re: Statistics not updating

[Wally Grotophorst]

Fixed it.  Problem was I didn't have "solr-statistics-server" predefined in 
config/modules/solr-statistics.cfg which broke subsequent URL creation 
making my solr server URL look like this:   https://localhost:8983//solr 
 (double //'s).   Added this to my local.cfg and things started working as 
you'd expect:

solr-statistics.server = http://localhost:8983/solr/statistics


On Monday, January 30, 2023 at 2:16:46 PM UTC-5 Wally Grotophorst wrote:

> Exported data from production 6.3 system and built a 7.4 instance that's 
> working well in most respects.  However, statistics don't show any 
> activity.  I exported a few CSV files from our 6.3 system and imported them 
> into the 7.4 version...those stats show up.  However,  if I download one of 
> the documents shown in the stats, the "usage" number does not increment. 
>  Still shows the activity only from the imported stat CSV files.
>
> Do I have to run a job to get these to update or is it a real-time sort of 
> thing?  If you download a document, should I expect the statistics to bump 
> up by one right then?
>
> Any assistance appreciated.  Still learning my way around DSpace 7 :)
>
> - Wally Grotophorst
> George Mason University
>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/cc65ce2f-a805-4edd-aa49-211e8b3db8a0n%40googlegroups.com.

[dspace-tech] Re: The feedback mail page may only be invoked from another DSpace page Error Feedback form

[Saad Itani]

Hello, is it possible to completely disable the feedback form? or redirect 
it to an authorized page? in dspace 6.4?

On Monday, July 11, 2022 at 7:05:17 PM UTC+3 Tim Donohue wrote:

> This is expected behavior from DSpace 6.3.  It's required by DSpace to 
> avoid spammers using your Feedback form to send you spam.  So, as a basic 
> spam protection, you can only invoke that form from another page within 
> DSpace.
>
> Tim
>
> On Friday, July 1, 2022 at 3:36:23 AM UTC-5 phiri...@gmail.com wrote:
>
>> How to solve this issue in DSpace 6.3 stated above:
>> The feedback mail page may only be invoked from another DSpace page Error 
>> Feedback form
>>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/1323d182-52f8-4e6a-828e-83f0e03f8187n%40googlegroups.com.