Re: [Dspace-tech] "java.sql.SQLException: bad_dublin_core schema" after modifying input-forms.xml file.

helix84

unread,

Aug 26, 2015, 10:44:07 AM8/26/15

to abhishek.kulkarni, dspace-tech

Hi Abishek,

did you create your "iit" schema (in "Metadata Registry" while logged in as Admin) before you made the changes to input forms? From the message it seems the schema doesn't exist. Also make sure to add any metadata fields into that schema that you wish to use them in your input forms.

Regards,
~~helix84

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

abhishek.kulkarni

unread,

Aug 26, 2015, 10:44:07 AM8/26/15

to dspac...@lists.sourceforge.net

Hi,

I just installed DSpace 3.1 and customized input-forms.xml to suite the
requirement.
The modified form displays properly on step 1 of item submission, however
when clicked 'next' to proceed, it throws error as below: -

java.sql.SQLException: bad_dublin_core schema=iit, department null
at org.dspace.content.Item.update(Item.java:1640)
at org.dspace.content.WorkspaceItem.update(WorkspaceItem.java:517)
at org.dspace.submit.step.DescribeStep.doProcessing(DescribeStep.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
at org.mozilla.javascript.Context.call(Context.java:538)
at
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)
at
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803)
at
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)
at
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)

Am I missing something after modifying input-forms.xml file?

Please help.

Thanks,
Abhishek Kulkarni
Library Technology Group
Illinois Institute of Technology

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

helix84

unread,

Aug 26, 2015, 10:44:10 AM8/26/15

to Abhishek Kulkarni, dspace-tech

It's so easy that it's probably not even documented.

1) log in as site administrator

2) go to Administrative - Registries - Metadata

3) fill in Namespace (arbitrary URL) and Name ("iit"), click "Add new schema"

4) open the newly added schema

5) into "Field Name:" type your element and qualifier and click "Add new metadata field"

Regards,
~~helix84

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

On Wed, Apr 17, 2013 at 11:13 PM, Abhishek Kulkarni <akul...@hawk.iit.edu> wrote:

Hi Helix,

I missed the creation of metadata in entirety.
Can you please guide on how we go about it?
(Maybe, an already published article/ solution)

Thanks,
Abhishek

abhishek.kulkarni

unread,

Aug 26, 2015, 10:46:16 AM8/26/15

to dspac...@lists.sourceforge.net

Hi Helix,

I added the schema as mentioned in steps.
But now facing another exception.

java.sql.SQLException: bad_dublin_core schema=dc, embargo terms

at org.dspace.content.Item.update(Item.java:1640)
at org.dspace.content.WorkspaceItem.update(WorkspaceItem.java:517)
at org.dspace.submit.step.DescribeStep.doProcessing(DescribeStep.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)

org.apache.cocoon.ProcessingException: Error calling continuation
at processPage - resource://aspects/Submission/submission.js:507
at <map:call> - resource://aspects/Submission/sitemap.xmap:93:44
at <map:match> - resource://aspects/Submission/sitemap.xmap:92:61
at <map:select type="AuthenticatedSelector"> -
resource://aspects/Submission/sitemap.xmap:60:48

Have added embargo in metadata though.

Can we export existing metadata from dspace version 1.8 and import it into
version 3.1?

Thanks in advance.

-Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663312.html

helix84

unread,

Aug 26, 2015, 10:46:18 AM8/26/15

to abhishek.kulkarni, dspace-tech

It seems you have put "embargo terms" somewhere where you should have
put "embargo.terms" (with a dot).

Probably in input-forms.xml you put
<dc-element>embargo terms</dc-element>
<dc-qualifier></dc-qualifier>
instead of
<dc-element>embargo</dc-element>
<dc-qualifier>terms</dc-qualifier>

abhishek.kulkarni

unread,

Aug 26, 2015, 10:46:19 AM8/26/15

to dspac...@lists.sourceforge.net

Below is the screenshot of my input-forms.xml

<http://dspace.2283337.n4.nabble.com/file/n4663315/embargo.jpg>

Its same, as it should be in your reply.

-Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663315.html

helix84

unread,

Aug 26, 2015, 10:46:20 AM8/26/15

to abhishek.kulkarni, dspace-tech

On Mon, Apr 22, 2013 at 5:58 PM, abhishek.kulkarni
<akul...@hawk.iit.edu> wrote:
> Below is the screenshot of my input-forms.xml

OK, but in input-forms.xml you have dc.embargo.terms. In the
screenshot you sent me of your metadata registry you have
iit.embargo.terms. Unless you *also* have dc.embargo.terms, you can't
put it into input-forms.

abhishek.kulkarni

unread,

Aug 26, 2015, 10:46:21 AM8/26/15

to dspac...@lists.sourceforge.net

Thanks Helix,

I see no embargo entry in dc schema.
Let me check after adding it into dc schema.

-Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663317.html

abhishek.kulkarni

unread,

Aug 26, 2015, 10:46:22 AM8/26/15

to dspac...@lists.sourceforge.net

It worked after adding couple of missing entries in 'dc' schema.

Thanks Helix!

-Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663318.html

helix84

unread,

Aug 26, 2015, 10:46:23 AM8/26/15

to abhishek.kulkarni, dspace-tech

On Mon, Apr 22, 2013 at 6:22 PM, abhishek.kulkarni
<akul...@hawk.iit.edu> wrote:
> It worked after adding couple of missing entries in 'dc' schema.

Yes, that should work, but the point was to add the "iit" fields to
input-forms, not create new "dc" fields. It's better practice in light
of upcoming changes to metadata schemas in DSpace - in general, you
shouldn't add new elements to "dc".

helix84

unread,

Aug 26, 2015, 10:47:04 AM8/26/15

to Abhishek Kulkarni, dspace-tech

Please, always CC dspace-tech.

It seems what you're doing is running the data export over an existing
database (with data).

What you should do instead is take the export (created using pg_dump),
import it into an empty database (you can create a separate database
for that purpose), let's call it "dspace_new" and then run the upgrade
scripts in the correct order:
[dspace-src]/dspace/etc/postgres/database_schema_17-18.sql
[dspace-src]/dspace/etc/postgres/database_schema_18-3.sql
These will upgrade the database format from 1.7 to 3, keeping the existing data.

Then simply point your dspace to the new database name (in dspac.cfg)
and restart it:
db.url = jdbc:postgresql://localhost:5432/dspace_new

Regards,
~~helix84

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

On Wed, Apr 24, 2013 at 4:47 PM, Abhishek Kulkarni
<akul...@hawk.iit.edu> wrote:
> Hello Ivan,
>
> Can you please help me out with importing postgres database?
> I have installed dspace 3.1 (fresh install) on new server and already have
> dspace 1.7 running on another server.
> I copied entire assetstore from 1.7 to 3.1 dspace.
> After copying, I tried searching for items in new dspace, and no results
> were thrown.
> Then, it struck me about DB import too.
> How do I import dspace1.7.sql dump into new dspace 3.1?
> I tried \i command but it threw all duplication errors as below: -
>
>
> psql:/home/guru/DBDump/new_dump.sql:301051: ERROR: duplicate key value
> violates unique constraint "metadataschemaregistry_pkey"
> DETAIL: Key (metadata_schema_id)=(1) already exists.
> CONTEXT: COPY metadataschemaregistry, line 1: "1
> http://dublincore.org/documents/dcmi-terms/ dc"
> psql:/home/guru/DBDump/new_dump.sql:354919: ERROR: duplicate key value
> violates unique constraint "metadatavalue_pkey"
> DETAIL: Key (metadata_value_id)=(128) already exists.
> CONTEXT: COPY metadatavalue, line 1: "128 23 3 Stewart,
> John L. \N 1 \N -1"
> psql:/home/guru/DBDump/new_dump.sql:466775: ERROR: insert or update on
> table "resourcepolicy" violates foreign key constraint
> "resourcepolicy_epersongroup_id_fkey"
> DETAIL: Key (epersongroup_id)=(67) is not present in table "epersongroup".
> psql:/home/guru/DBDump/new_dump.sql:466807: ERROR: insert or update on
> table "subscription" violates foreign key constraint
> "subscription_eperson_id_fkey"
> DETAIL: Key (eperson_id)=(38) is not present in table "eperson".
> psql:/home/guru/DBDump/new_dump.sql:466951: ERROR: insert or update on
> table "tasklistitem" violates foreign key constraint
> "tasklistitem_eperson_id_fkey"
> DETAIL: Key (eperson_id)=(340) is not present in table "eperson".
> psql:/home/guru/DBDump/new_dump.sql:467027: ERROR: insert or update on
> table "workflowitem" violates foreign key constraint
> "workflowitem_item_id_fkey"
> DETAIL: Key (item_id)=(3223) is not present in table "item".
> psql:/home/guru/DBDump/new_dump.sql:467197: ERROR: insert or update on
> table "workspaceitem" violates foreign key constraint
> "workspaceitem_item_id_fkey"
> DETAIL: Key (item_id)=(1708) is not present in table "item".
> psql:/home/guru/DBDump/new_dump.sql:467205: ERROR: multiple primary keys
> for table "bi_2_dis" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467213: ERROR: multiple primary keys
> for table "bi_2_dmap" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467221: ERROR: multiple primary keys
> for table "bi_4_dis" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467229: ERROR: multiple primary keys
> for table "bi_4_dmap" are not allowed
> ALTER TABLE
> ALTER TABLE
> psql:/home/guru/DBDump/new_dump.sql:467253: ERROR: multiple primary keys
> for table "bi_item" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467261: ERROR: multiple primary keys
> for table "bi_withdrawn" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467269: ERROR: multiple primary keys
> for table "bitstream" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467277: ERROR: multiple primary keys
> for table "bitstreamformatregistry" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467285: ERROR: relation
> "bitstreamformatregistry_short_description_key" already exists
> psql:/home/guru/DBDump/new_dump.sql:467293: ERROR: multiple primary keys
> for table "bundle2bitstream" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467301: ERROR: multiple primary keys
> for table "bundle" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467309: ERROR: multiple primary keys
> for table "checksum_history" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467317: ERROR: multiple primary keys
> for table "checksum_results" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467325: ERROR: multiple primary keys
> for table "collection2item" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467333: ERROR: multiple primary keys
> for table "collection_item_count" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467341: ERROR: multiple primary keys
> for table "collection" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467349: ERROR: multiple primary keys
> for table "communities2item" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467357: ERROR: multiple primary keys
> for table "community2collection" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467365: ERROR: multiple primary keys
> for table "community2community" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467373: ERROR: multiple primary keys
> for table "community_item_count" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467381: ERROR: multiple primary keys
> for table "community" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467389: ERROR: relation
> "eperson_email_key" already exists
> psql:/home/guru/DBDump/new_dump.sql:467397: ERROR: multiple primary keys
> for table "eperson" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467405: ERROR: multiple primary keys
> for table "epersongroup2eperson" are not allowed
> psql:/home/guru/DBDump/new_dump.sql:467413: ERROR: multiple primary keys
> for table "epersongroup2workspaceitem" are not allowed
>
>
>
> Please help.
>
> Thanks,
> Abhishek
>
>
>
> On Mon, Apr 22, 2013 at 11:48 AM, helix84 <hel...@centrum.sk> wrote:
>>
>> My point was that you should do this:
>>
>> <dc-schema>iit</dc-schema>

>> <dc-element>embargo</dc-element>
>> <dc-qualifier>terms</dc-qualifier>
>>
>>

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:47:06 AM8/26/15

to Ivan Masár, dspace-tech

Thanks Helix!

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:47:07 AM8/26/15

to Ivan Masár, dspace-tech

Should I run update-sequences.sql present in /dspace/dspace-3.1-release/dspace/etc/postgres too

after running: - (i) database_schema_17-18.sql & (ii) database_schema_18-3.sql ?

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:47:09 AM8/26/15

to Ivan Masár, dspace-tech

Hi Ivan,

I created new db, dspace_new and performed all the steps as mentioned successfully.

However, I am still not getting search results after searching for any keyword in dspace.

Also, on item submission I faced the following exception after the 'Grant license' step.

java.lang.RuntimeException: Error while attempting to create identifier for Item id: 3490

	at org.dspace.identifier.VersionedHandleIdentifierProvider.register(VersionedHandleIdentifierProvider.java:117)
	at org.dspace.identifier.IdentifierServiceImpl.register(IdentifierServiceImpl.java:80)
	at org.dspace.content.InstallItem.installItem(InstallItem.java:67)
	at org.dspace.content.InstallItem.installItem(InstallItem.java:44)
	at org.dspace.workflow.WorkflowManager.archive(WorkflowManager.java:724)
	at org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:656)
	at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:416)
	at org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:634)
	at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:407)
	at org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:597)
	at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:395)
	at org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:556)
	at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:383)
	at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:336)
	at org.dspace.workflow.WorkflowManager.start(WorkflowManager.java:179)
	at org.dspace.submit.step.CompleteStep.doProcessing(CompleteStep.java:96)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
	at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
	at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
	at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
	at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
	at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
	at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
	at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
	at org.mozilla.javascript.Context.call(Context.java:538)
	at org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)

However, the uploaded item is reflected in the list of Unfinished submissions.

Can you please let me know, if I have made a mistake in any step?

Thanks,

Abhishek

abhishek.kulkarni

unread,

Aug 26, 2015, 10:47:11 AM8/26/15

to dspac...@lists.sourceforge.net

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
at
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
at org.mozilla.javascript.Context.call(Context.java:538)
at
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)

However, the uploaded item is reflected in the list of Unfinished
submissions.
Can you please let me know, if I have made a mistake in any step?

Thanks,
Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663372.html

helix84

unread,

Aug 26, 2015, 10:47:14 AM8/26/15

to Abhishek Kulkarni, dspace-tech

On Wed, Apr 24, 2013 at 6:14 PM, Abhishek Kulkarni <akul...@hawk.iit.edu> wrote:

I created new db, dspace_new and performed all the steps as mentioned successfully.

I made a mistake, here's how you should run the database upgrade scripts:

psql dspace_new < [dspace-src]/dspace/etc/postgres/database_schema_17-18.sql
psql dspace_new < [dspace-src]/dspace/etc/postgres/database_schema_18-3.sql

but you say you've managed to do that.

Should I run update-sequences.sql present in /dspace/dspace-3.1-release/dspace/etc/postgres too

There's no harm in running update-sequences.sql, but do that only while Tomcat is down.

However, I am still not getting search results after searching for any keyword in dspace.

You have to run [dspace]/bin/dspace index-init, and if you're using Discovery also [dspace]/bin/dspace update-discovery-index. But this is all described in the official documentation about upgrading, you should read and follow it completely:

https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+1.7.x+to+1.8.x

https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+1.8.x+to+3.x

Also, on item submission I faced the following exception after the 'Grant license' step.

java.lang.RuntimeException: Error while attempting to create identifier for Item id: 3490
	at org.dspace.identifier.VersionedHandleIdentifierProvider.register(VersionedHandleIdentifierProvider.java:117)

I'm not sure about that, maybe it will be fixed when you follow the upgrading docs above.

You should also look into dspace.log, find this line and post it here. The equivalent line from log is almost the same but it contains an important extra piece of information. You should include even more lines, especially including the "Caused by" line.

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:47:14 AM8/26/15

to Ivan Masár, dspace-tech

Thanks for speedy response Ivan.

I will follow the steps mentioned and get back.

Many thanks !

-Abhishek

abhishek.kulkarni

unread,

Aug 26, 2015, 10:47:17 AM8/26/15

to dspac...@lists.sourceforge.net

Search started working after I refreshed the indexes.
However, I wasn't successful in refreshing Discovery.
Faced exception: -

Exception: java.net.ConnectException: Connection refused
org.dspace.discovery.SearchServiceException: java.net.ConnectException:
Connection refused
at
org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:418)
at org.dspace.discovery.IndexClient.main(IndexClient.java:119)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Maybe, I might not be using it in DSpace, and hence the connection refused
exception.
I went forward and started tomcat to check search functionality.
It was working but the problem of item submission at last step 'Grant
License' persists.

Entire exception from log file: -

2013-04-24 12:36:56,225 ERROR
org.dspace.identifier.VersionedHandleIdentifierProvider @
akul...@hawk.iit.edu:session_id=412F900F3FBB16BBC0F53E41F3F66F35:Error
while attempting to create handle:Item id\colon; 3491
java.lang.RuntimeException: ERROR: permission denied for relation
versionitem
at org.dspace.versioning.VersionHistoryDAO.find(VersionHistoryDAO.java:73)
at
org.dspace.versioning.VersioningServiceImpl.findVersionHistory(VersioningServiceImpl.java:126)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.retrieveVersionHistory(VersionedHandleIdentifierProvider.java:625)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.mint(VersionedHandleIdentifierProvider.java:250)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.register(VersionedHandleIdentifierProvider.java:82)

at
org.dspace.identifier.IdentifierServiceImpl.register(IdentifierServiceImpl.java:80)
at org.dspace.content.InstallItem.installItem(InstallItem.java:67)
at org.dspace.content.InstallItem.installItem(InstallItem.java:44)
at org.dspace.workflow.WorkflowManager.archive(WorkflowManager.java:724)
at org.dspace.workflow.WorkflowManager.doState(WorkflowManager.java:656)
at org.dspace.workflow.WorkflowManager.advance(WorkflowManager.java:416)

Caused by: java.lang.RuntimeException: ERROR: permission denied for relation
versionitem
at org.dspace.versioning.VersionDAO.findByItemId(VersionDAO.java:82)
at org.dspace.versioning.VersionHistoryDAO.find(VersionHistoryDAO.java:53)
... 226 more
Caused by: org.postgresql.util.PSQLException: ERROR: permission denied for
relation versionitem
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2103)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)

2013-04-24 12:36:56,233 ERROR
org.dspace.identifier.VersionedHandleIdentifierProvider @
akul...@hawk.iit.edu:session_id=412F900F3FBB16BBC0F53E41F3F66F35:Error
while attempting to create handle:Item id\colon; 3491

java.lang.RuntimeException: Error while attempting to create identifier for

Item id: 3491
at
org.dspace.identifier.VersionedHandleIdentifierProvider.mint(VersionedHandleIdentifierProvider.java:262)
at
org.dspace.identifier.VersionedHandleIdentifierProvider.register(VersionedHandleIdentifierProvider.java:82)

-Abhishek

--
View this message in context: http://dspace.2283337.n4.nabble.com/java-sql-SQLException-bad-dublin-core-schema-after-modifying-input-forms-xml-file-tp4663226p4663379.html

helix84

unread,

Aug 26, 2015, 10:47:19 AM8/26/15

to abhishek.kulkarni, dspace-tech

On Wed, Apr 24, 2013 at 7:47 PM, abhishek.kulkarni
<akul...@hawk.iit.edu> wrote:
> Search started working after I refreshed the indexes.
> However, I wasn't successful in refreshing Discovery.
> Faced exception: -
>
> Exception: java.net.ConnectException: Connection refused
> org.dspace.discovery.SearchServiceException: java.net.ConnectException:
> Connection refused
> at
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:418)
> at org.dspace.discovery.IndexClient.main(IndexClient.java:119)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> Maybe, I might not be using it in DSpace, and hence the connection refused
> exception.

You're right, Discovery it not enabled by default, so if you didn't
enable it, you don't have to worry about update-discovery-index not
working.

> java.lang.RuntimeException: ERROR: permission denied for relation
> versionitem

Yes, this is the actual error. The "versionitem" tables and some other
related stuff were created by the database_schema_18-3.sql upgrade
script. According to the error message, you don't have the permission
to access this new table. So you probably run psql <
database_schema_18-3.sql as a different database user (role) than the
rest of your dspace tables. The easiest solution at this point would
be to drop your upgraded database and do the import and upgrade steps
again, this time using the correct databse user (role). You will know
what the correct user should be by looking at "db.username" in
dspace.cfg.

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:47:20 AM8/26/15

to Ivan Masár, dspace-tech

Will do as mentioned and get back..

Thanks,

Abhishek

Abhishek Kulkarni

unread,

Aug 26, 2015, 10:49:03 AM8/26/15

to Ivan Masár, dspace-tech

Hi Ivan,

Am facing with following problem after turning ON Discovery feature.

INFO [main] (DSpaceKernelInit.java:52) - Created new kernel: DSpaceKernel:org.dspace:name=ffc05c8f-416f-499b-a722-04c872402ab9,type=DSpaceKernel:lastLoad=null:loadTime=0:running=false:kernel=null
INFO [main] (ConfigurationManager.java:1224) - Loading from classloader: file:/dspace/config/dspace.cfg
INFO [main] (ConfigurationManager.java:1224) - Using dspace provided log configuration (log.init.config)
INFO [main] (ConfigurationManager.java:1224) - Loading: /dspace/config/log4j.properties
Exception: Error executing query
org.dspace.discovery.SearchServiceException: Error executing query

at org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:418)
at org.dspace.discovery.IndexClient.main(IndexClient.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:183)
Caused by: org.apache.solr.client.solrj.SolrServerException: Error executing query
at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:95)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:118)
at org.dspace.discovery.SolrServiceImpl.getSolr(SolrServiceImpl.java:106)
at org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:388)
... 6 more
Caused by: org.apache.solr.common.SolrException: Not Found

Not Found

request: http://localhost/solr/search/select?q=search.resourcetype:2 AND search.resourceid:1&wt=javabin&version=2
at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:435)
at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:244)
at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:89)
... 9 more

Also, page load after server startup is taking lot of time and when check logs, it shows same exception.

Can you please help out?

-Abhishek Kulkarni
Illinois Institute of Technology

On Wed, Apr 24, 2013 at 1:29 PM, helix84 <hel...@centrum.sk> wrote:

Hilton Gibson

unread,

Aug 26, 2015, 10:49:04 AM8/26/15

to Abhishek Kulkarni, dspace-tech

HI

Your input-forms.xml is badly formed.

Try re-installing the old version or the original version, if it works, then check your custom form with an xml editor.

Cheers

hg

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--

Hilton Gibson

Systems Administrator

JS Gericke Library

Room 1025C

Stellenbosch University

Private Bag X5036

Stellenbosch

7599

South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

http://library.sun.ac.za

http://scholar.sun.ac.za

http://ar1.sun.ac.za

http://aj1.sun.ac.za

Reply all

Reply to author

Forward