Hi Arthy,
Are you running more than one MCP Client?
My guess is you have run into the bug I reported here:
https://github.com/archivematica/Issues/issues/752
The clue to me here is that 128 is the default batch size, so one batch completes, but others fail.
--
Sean
From:
archiv...@googlegroups.com <archiv...@googlegroups.com> on behalf of arth...@gmail.com <arth...@gmail.com>
Date: Tuesday, December 28, 2021 at 5:50 AM
To: archivematica <archiv...@googlegroups.com>
Subject: [archivematica] Normalization errors with ""An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.""
Caution: This message was sent from outside the University of Manitoba. |
--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
archivematic...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/archivematica/a2fd4a8a-913e-49a9-8dd5-f8635e11f440n%40googlegroups.com.
Hi Arthy,
After reading #1111, I’ll also share a separate issue I reported related to database update timing issues and how Ingest can be started too early if you have thousands of files.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/df4d950c-7dbb-4709-88d5-a7bea4efec9cn%40googlegroups.com.