[Dspace-tech] PSQLException OID ### does not exist

2009-04-02 Thread Ron Stevenhaagen
 Message: 2

 Date: Wed, 01 Apr 2009 21:01:58 -0700

 From: Kim Griggs kim.gri...@oregonstate.edu

 Subject: [Dspace-tech] PSQLException OID ### does not exist

 To: dspace-tech@lists.sourceforge.net

dspace-tech@lists.sourceforge.net

 Message-ID: c5f986c6.a42c%kim.gri...@oregonstate.edu

 Content-Type: text/plain;  charset=US-ASCII

 

 We are upgrading to 1.4.2 to 1.5. Java 1.5. Postgres 8.1.

 

 After running the indexer we are getting internal errors on the high
level

 browse by pages. The error is:

 

 org.postgresql.util.PSQLException: ERROR: relation with OID 54778762

 does not exist

 

 Oddly the community level browse bys work.

 

 I read that it might be a postgres thing and upgrading to 8.3 might fix
it.

 Before I go through that I am looking for confirmation.

 

 Has anyone seen this problem and how did you fix it?

 

 Thanks.

 

Hi Kim

 

You need to stop the handle-server, tomcat, and then postgres in that order.
Then just restart them in the reverse order. Wait 30 seconds for each
command to complete before executing the next command. Example:

 

1.) svcadm disable handle-server

2.) svcadm disable dspace

3.) svcadm disable postgres

 

4.) svcadm enable postgres

5.) svcadm enable dspace

6.) svcadm enable handle-server

 

This is how I resolved this issue. 

 

Ron Stevenhaagen

 Technical Specialist

 Information Technology Services

 Queens University

 Kingston Ontario

 

 

 

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


[Dspace-tech] PSQLException OID ### does not exist

2009-04-01 Thread Kim Griggs
We are upgrading to 1.4.2 to 1.5. Java 1.5. Postgres 8.1.

After running the indexer we are getting internal errors on the high level
browse by pages. The error is:

org.postgresql.util.PSQLException: ERROR: relation with OID 54778762
does not exist

Oddly the community level browse bys work.

I read that it might be a postgres thing and upgrading to 8.3 might fix it.
Before I go through that I am looking for confirmation.

Has anyone seen this problem and how did you fix it?

Thanks.


--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech