Helix, review all data base updates and all was applied, but the problem 
persist.

Some other idea.

Please and thanks
-----Mensaje original-----
De: [email protected] [mailto:[email protected]] En nombre de helix84 
Enviado el: miƩrcoles, 24 de julio de 2013 16:17
Para: Luis Rojas C. (CATIE)
CC: [email protected]
Asunto: Re: [Dspace-tech] RV: Problen send to repository

On Wed, Jul 24, 2013 at 5:47 PM, Luis Rojas C. (CATIE) <[email protected]> 
wrote:
> java.lang.RuntimeException: ERROR: permission denied for relation 
> versionitem

Hi Luis,

it seems that you haven't run the database_schema_18-3.sql upgrade script as 
your postgres "dspace" role. There are some examples how to fix that here:
http://stackoverflow.com/questions/15520361/permission-denied-for-relation

However, this likely means you also didn't run the other database upgrade 
scripts as the "dspace" role, either. Therefore you may expect some of the 
other new features in 1.5.0 - 3.0 to misbehave. Check all commands executed 
there, especially CREATE TABLE, but perhaps also CREATE INDEX and CREATE 
SEQUENCE and fix the permission issues.

It might be easier just to drop them and re-run the upgrade scripts as the 
correct role. You'll have to judge that for yourself.

Regards,
~~helix84

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



------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to