date:20180129

RE: [dspace-tech] Internal system error DSpace

2018-01-29 Thread prosentientsystems

Tomcat is trying to create your solr index folders but does not have 
permissions for  /dspace/solr , so SOLR fails startup – causing UI problems in 
the interface.

 

If you give tomcat appropriate write permissions you should be able to restart 
the tomcat service and let the folders get initialized.

 

Regards Edmund

 

From: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] On 
Behalf Of Leidy Madroñero
Sent: Saturday, 27 January 2018 7:34 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Internal system error DSpace

 

good afternoon 

 

I find an internal error of the system that I have not been able to solve yet, 
I check each different documentation and I make the corresponding 
installations, but nothing gives a good result. I want to attach my 
installation step by step so that you can observe it and they can help me in 
case I'm missing some configuration or doing a step wrong. I have the same 
problem: Internal system error. I also attach the error captures. I hope to get 
some help.

 

Thank you for your attention.

 

a greeting

Jessica

Installation:

  

 

 

  

 

  

 

 

 

The installation was done by guiding me in:

 

https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace

 

https://www.researchgate.net/publication/320719874_Instalacion_de_Dspace_62_en_Linux

 

http://repositorio.iaen.edu.ec/bitstream/24000/3721/1/MANUAL%20DE%20INSTALACI%C3%93N%20DE%20DSPACE%20VERSI%C3%93N%205.4.pdf

 

  

 

 

  



 

  

 

-- 
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.

-- 
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] Database Migration 4.2->5.6 Issue

2018-01-29 Thread Terry Brady

Scott,

I do not have those views in my installation.

select schemaname,viewname from pg_catalog.pg_views where schemaname no
t in ('information_schema','pg_catalog');
 schemaname |viewname
+
 public | community2item
 public | dcvalue
(2 rows)

I also did a scan of the DSpace 5 code base and I do not find the string
"v_files".

I suspect those views are there for support purposes or they are a vendor
add-on.

Terry

On Mon, Jan 29, 2018 at 9:47 AM, Scott Renton  wrote:

> Hi folks,
>
> I see this was mentioned before in http://dspace.2283337.n4.
> nabble.com/Upgrade-3-2-to-5-4-database-problem-td4680533.html
>
> Basically, we are migrating from 4.2 to 5.6, and have hit database
> migrations problems between the 5.0.2014.09.25 and 5.0.2014.09.26 stages.
> Just like the above problem, it was down to stats related views: the first
> two it complained about (v_stats_workflow and stats.v_workflow) had only 6
> lines in each, so I cheerfully hived them off and dropped. I'm now through
> to my next problem:
>
> Caused by: org.postgresql.util.PSQLException: ERROR: cannot drop table
> bundle column name because other objects depend on it
>
>   Detail: view stats.v_files depends on table bundle column name
>
> view stats.v_files_coll depends on view stats.v_files
>
> view stats.v_files_comm depends on view stats.v_files
>
> view stats.v_item2bitstream depends on table bundle column name
>
>
> These views have a lot more in them. I'm all for dropping them, but
> wondered if anyone could advise on implications. I guess they are dspace
> generated- this is one of our least configured sites, so I'm guessing
> they've happened through user interaction rather than anything we've done.
> The one site we have that has gone to 5.6 didn't have these views.
>
>
> Cheers
>
> Scott
>
> --
> 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.
>



-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
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] Database Migration 4.2->5.6 Issue

2018-01-29 Thread Tim Donohue

Hi Scott,

Those views are not generated by DSpace (as far as I'm aware).  Searching
Github does not show them in our codebase (and all views created by DSpace
are documented in our SQL database scripts).  So, my best guess is that
these were locally created, or someone installed a custom Statistics plugin
in your DSpace that uses those?  I notice they all start with "stats.", so
that's why I wonder if these are related either to a third-party plugin, or
were created locally to help run some detailed statistics on your DSpace.

That's my best guess.  If they are from a plugin, then hopefully someone
else on this list will recognize these names and report back.

In any case, I don't see any harm to your DSpace in deleting them.  But,
obviously, you may want to check to see if anyone knows why they were
created in the first place.

Tim

On Mon, Jan 29, 2018 at 2:19 PM Scott Renton  wrote:

> Hi folks,
>
> I see this was mentioned before in
> http://dspace.2283337.n4.nabble.com/Upgrade-3-2-to-5-4-database-problem-td4680533.html
>
> Basically, we are migrating from 4.2 to 5.6, and have hit database
> migrations problems between the 5.0.2014.09.25 and 5.0.2014.09.26 stages.
> Just like the above problem, it was down to stats related views: the first
> two it complained about (v_stats_workflow and stats.v_workflow) had only 6
> lines in each, so I cheerfully hived them off and dropped. I'm now through
> to my next problem:
>
> Caused by: org.postgresql.util.PSQLException: ERROR: cannot drop table
> bundle column name because other objects depend on it
>
>   Detail: view stats.v_files depends on table bundle column name
>
> view stats.v_files_coll depends on view stats.v_files
>
> view stats.v_files_comm depends on view stats.v_files
>
> view stats.v_item2bitstream depends on table bundle column name
>
>
> These views have a lot more in them. I'm all for dropping them, but
> wondered if anyone could advise on implications. I guess they are dspace
> generated- this is one of our least configured sites, so I'm guessing
> they've happened through user interaction rather than anything we've done.
> The one site we have that has gone to 5.6 didn't have these views.
>
>
> Cheers
>
> Scott
>
> --
> 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] Import directory cleanup?

2018-01-29 Thread Matt Ralston

Hi - we've been running DSpace 6.2 for a couple of months in test and I am 
trying to get a handle on how everything works.  My users have been using 
the batch import feature to add new content, and I noticed that the 
imports/batchupdate folder doesn't seem to be cleared after successful 
import, even after a couple of months.  I don't see an obvious way to clear 
this using DSpace's command line tools - is the expectation that we clear 
this directory from the file system?  Or am I missing something?

Any help or direction would be appreciated.

-- 
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] Database Migration 4.2->5.6 Issue

2018-01-29 Thread Scott Renton

Hi folks, 

I see this was mentioned before 
in 
http://dspace.2283337.n4.nabble.com/Upgrade-3-2-to-5-4-database-problem-td4680533.html

Basically, we are migrating from 4.2 to 5.6, and have hit database 
migrations problems between the 5.0.2014.09.25 and 5.0.2014.09.26 stages. 
Just like the above problem, it was down to stats related views: the first 
two it complained about (v_stats_workflow and stats.v_workflow) had only 6 
lines in each, so I cheerfully hived them off and dropped. I'm now through 
to my next problem:

Caused by: org.postgresql.util.PSQLException: ERROR: cannot drop table 
bundle column name because other objects depend on it

  Detail: view stats.v_files depends on table bundle column name

view stats.v_files_coll depends on view stats.v_files

view stats.v_files_comm depends on view stats.v_files

view stats.v_item2bitstream depends on table bundle column name


These views have a lot more in them. I'm all for dropping them, but 
wondered if anyone could advise on implications. I guess they are dspace 
generated- this is one of our least configured sites, so I'm guessing 
they've happened through user interaction rather than anything we've done. 
The one site we have that has gone to 5.6 didn't have these views.


Cheers

Scott

-- 
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] Database error when trying to edit epersons (oracle - ORA-00932: inconsistent datatypes: expected -

2018-01-29 Thread Tim Donohue

Hi Don,

This stacktrace tells me that the issue you are having is *not* the same as
the issue that Francis is happening (despite the similar error messages).

Based on the error stack below, the error you  see is coming from the
"EPerson.searchResultCount()" method, specifically the SQL on this line:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/eperson/EPerson.java#L438


However, the error reported by Francis (and described in DS-3649:
https://jira.duraspace.org/browse/DS-3649), was coming from the
"EPerson.findAll()" method on this line:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/eperson/EPerson.java#L518

So, I'm not surprised that the fix Tom provided won't work on your system.
As it is fixing the latter method, and not the former one.

It looks to me like your error is resulting from a similar/related problem
though, that a CLOB data type cannot be used in "comparison conditions"
[1], and the SQL in that "searchResultCount()" method uses LOWER() on a
CLOB data type.

So, I think, based on Tom's previous recommendation, you'd need to replace
the "text_value" fields with "dbms_lob.substr(text_value, 0, 4000)" on
these two lines:
* Select statement here:
https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace-api/src/main/java/org/dspace/eperson/EPerson.java#L441
* And select statement here:
https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace-api/src/main/java/org/dspace/eperson/EPerson.java#L442


That's my best guess here. It sounds to me like we need to take a closer
look at *all* the methods in this EPerson class, and ensure they are
updated similarly.

- Tim

[1] https://docs.oracle.com/cd/B19306_01/server.102/b14200/conditions002.htm


On Fri, Jan 26, 2018 at 1:05 PM Donald Bynum  wrote:

> I made the change as suggested.  Did a rebuild.  That resulted in a new
> additions-5.5.jar (which makes sense since the updated java module was in
> additions.  Same error.  Here is the log entry (sorry it so lengthy):
>
> 2018-01-26 13:55:13,555 ERROR org.dspace.storage.rdbms.DatabaseManager @
> SQL query single Error -
> java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes:
> expected - got CLOB
>  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
>  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
>  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
>  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
>  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
>  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
>  at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)
>  at
> oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:886)
>  at
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1175)
>  at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1296)
>  at
> oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)
>  at
> oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3657)
>  at
> oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1495)
>  at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>  at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>  at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>  at
> org.dspace.storage.rdbms.DatabaseManager.query(DatabaseManager.java:295)
>  at
> org.dspace.storage.rdbms.DatabaseManager.querySingle(DatabaseManager.java:342)
>  at org.dspace.eperson.EPerson.searchResultCount(EPerson.java:438)
>  at
> org.dspace.app.xmlui.aspect.administrative.eperson.ManageEPeopleMain.addBody(ManageEPeopleMain.java:118)
>  at
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223)
>  at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>  at com.sun.proxy.$Proxy110.startElement(Unknown Source)
>  at
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
>  at
> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
>  at
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:240)
>  at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:498)
>  at
>

Re: [dspace-tech] REST 5 vs 6

2018-01-29 Thread Terry Brady

The REST 6 API supports more authentication methods than the REST 5 API.

The following endpoints (bottom of this note) were added to REST 6.  I
believe that the other endpoints are unchanged.

The identifiers passed to REST endpoints in DSpace 6 are UUID's instead of
integers.

Terry

Hierarchy

   - GET /hierarchy - Return hierarchy of communities and collections in
   tree form. Each object is minimally populated (name, handle, id) for
   efficient retrieval.

Metadata and Schema Registry

   - GET /registries/schema - Return the list of metadata schemas in the
   registry
   - GET /registries/schema/{schema_prefix} - Returns the specified
   metadata schema
   - GET /registries/schema/{schema_prefix}/metadata-fields/{element} -
   Returns the metadata field within a schema with an unqualified element name
   - GET
   /registries/schema/{schema_prefix}/metadata-fields/{element}/{qualifier} -
   Returns the metadata field within a schema with a qualified element name
   - POST /registries/schema/ - Add a schema to the schema registry
   - POST /registries/schema/{schema_prefix}/metadata-fields - Add a
   metadata field to the specified schema
   - GET /registries/metadata-fields/{field_id} - Return the specified
   metadata field
   - PUT /registries/metadata-fields/{field_id} - Update the specified
   metadata field
   - DELETE /registries/metadata-fields/{field_id} - Delete the specified
   metadata field from the metadata field registry
   - DELETE /registries/schema/{schema_id} - Delete the specified schema
   from the schema registry

Query/Reporting Tools

   - GET /reports - Return a list of report tools built on the rest api
   - GET /reports/{nickname} - Return a redirect to a specific report
   - GET /filters - Return a list of use case filters available for quality
   control reporting
   - GET /filtered-collections - Return collections and item counts based
   on pre-defined filters
   - GET /filtered-collections/{collection_id} - Return items and item
   counts for a collection based on pre-defined filters
   - GET /filtered-items - Retrieve a set of items based on a metadata
   query and a set of filters


On Mon, Jan 29, 2018 at 7:31 AM, Monika Mevenkamp  wrote:

> All Y’all:
>
> How much does the REST API change between version 5 and version 6 ?
> AKA: does the functionality that is available in 5 move forward to 6
> unchanged  ?
>
> Monika
>
> 
> Monika Mevenkamp
> mo.me...@gmail.com
>
> http://mo-meven.tumblr.com/
> http://mcmprogramming.com/mo.meven/
>
>
>
> --
> 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.
>



-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
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] REST 5 vs 6

2018-01-29 Thread Monika Mevenkamp

All Y’all: 

How much does the REST API change between version 5 and version 6 ? 
AKA: does the functionality that is available in 5 move forward to 6 unchanged  
? 

Monika 

 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



-- 
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] Internal system error DSpace

Re: [dspace-tech] Database Migration 4.2->5.6 Issue

Re: [dspace-tech] Database Migration 4.2->5.6 Issue

[dspace-tech] Import directory cleanup?

[dspace-tech] Database Migration 4.2->5.6 Issue

Re: [dspace-tech] Database error when trying to edit epersons (oracle - ORA-00932: inconsistent datatypes: expected -

Re: [dspace-tech] REST 5 vs 6

[dspace-tech] REST 5 vs 6

8 matches

Site Navigation

Mail list logo

Footer information