Tim, solved, thank you.
I wasn't aware that the "123456789" sitewide object existed in a database
before I added any content, even though I changed default handle straight
away after DSpace installation.
The command [dspace]/bin/dspace update-handle-prefix did the job.
Peter
W dniu wtorek, 2 października 2018 15:50:37 UTC+1 użytkownik Tim Donohue
napisał:
>
> Hello Peter,
>
> It sounds like the handle "0/0" doesn't exist in your 'handle'
> database table. Maybe when you originally installed DSpace you had a
> different handle prefix, and then swapped it out for "0"?
>
> In DSpace 6.x, all handles, including the "Site wide" handle (which is
> [handle-prefix]/0) are stored in that "handle" database table. In this
> situation, there should be a 'handle' in that table that *ends with* "/0",
> and points at your Site UUID (in the "site" table). My guess is you
> likely need to modify this handle to reset it to be "0/0", and then
> everything should work fine.
>
> (Just as a sidenote, this behavior changed between 5.x and 6.x. In 5.x,
> the Site object never really existed, and the "[handle-prefix]/0" handle
> was hardcoded into DSpace code. But, in 6.x, we modified that behavior to
> actually create the Site object and store its handle in the "handle"
> database table, alongside all other DSpace handles.)
>
> I hope that helps!
>
> Tim
>
> On Tue, Oct 2, 2018 at 6:47 AM admin >
> wrote:
>
>> Hi,
>>
>> I have a fresh DSpace 6.3 installation. I configured dummy handle "0"
>> and set up cron to perform full backup:
>> 30 5 * * * $DSPACE/bin/dspace packager -u -d -a -t AIP -e
>> em...@example.com -i 0/0 xxx/backup.zip
>>
>> The cron however sends the following report:
>>
>> Exception: Bad identifier/handle -- Cannot resolve handle "0/0"
>>
>> java.lang.IllegalArgumentException: Bad identifier/handle -- Cannot
>> resolve handle "0/0"
>>
>> at
>> org.dspace.app.packager.Packager.main(Packager.java:456)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>>
>> at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
>>
>> at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>>
>> I have only one empty community (ID: 1) in the repository so far, so that
>> may be a reason maybe? Nevertheless I wanted to resolve the issue before
>> filling it with collections/items.
>> As I understand from DSPace docs (
>> https://wiki.duraspace.org/display/DSDOC6x/AIP+Backup+and+Restore), I
>> can use "/0" to denote all repository items.
>>
>>
>> Best, Peter
>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> 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
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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.
