Problem with scripts after PostGreSQL upgrade

Hi...

I just upgraded from PostGReSQL 7.2.3 to 8.3 (I am using DSpace 1.4.2).

I have a number of PERL scripts that I run that get data from the
PostGreSQL database.  These scripts use the DBI connect command:
$dbh = DBI->connect('DBI:Pg:dbname=dspace', 'xxxxx', '');

This worked under the old PostGreSQL but under the new one, I get this error:

install_driver(Pg) failed: Can't load
'/usr/local/lib/perl5/site_perl/5.8.7/sun4-solaris/auto/DBD/Pg/Pg.so' for
module DBD::Pg: ld.so.1: list_users.pl: fatal: libpq.so.2: open failed:

Do I need to get new libraries for the new PostGreSQL?
****************************************
George Kozak
Coordinator
Web Development and Management
Digital Media Group
501 Olin Library
Cornell University 14853
gsk5@...
607-255-8924

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: Problem with scripts after PostGreSQL upgrade

You need the libraries for 8.3 (and possibly you will have to rebuild the
DBD::Pg against these, I'm not sure. At least you have to have the
libraries).

**********************
Urban Andersson
Digital library
University of Gothenburg
Sweden

> Hi...
>
> I just upgraded from PostGReSQL 7.2.3 to 8.3 (I am using DSpace 1.4.2).
>
> I have a number of PERL scripts that I run that get data from the
> PostGreSQL database.  These scripts use the DBI connect command:
> $dbh = DBI->connect('DBI:Pg:dbname=dspace', 'xxxxx', '');
>
> This worked under the old PostGreSQL but under the new one, I get this
> error:
>
> install_driver(Pg) failed: Can't load
> '/usr/local/lib/perl5/site_perl/5.8.7/sun4-solaris/auto/DBD/Pg/Pg.so' for
> module DBD::Pg: ld.so.1: list_users.pl: fatal: libpq.so.2: open failed:
>
> Do I need to get new libraries for the new PostGreSQL?
> ****************************************
> George Kozak
> Coordinator
> Web Development and Management

Service Provider Grid

DSpace Community -

DSpace Foundation has posted a new reference on www.dspace.org for  
service providers:   
http://www.dspace.org/index.php?option=com_content&task=view&id=548&Itemid=174

These companies/individuals have been vetted by the foundation and can  
provide assistance with repository design, development,  
installation/configuration, integration, customization, hosting,  
training and analysis.

It is our goal to keep the information current -- please let us know  
if you find discrepancies.  We would like to expand this list of  
service providers, so if you have any recommendations of whom we  
should be talking to, let us know.

Thank you!

Valorie Hollister
Community Outreach Manager
DSpace Foundation

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: javascript.evaluator.exception

This fixed it! Thanks a lot!

-Mika

> Hi Mika,
> 
> line 47-49 in eperson.js
> 
> should read:
> 
> importClass(Packages.org.dspace.eperson.EPerson);
> importClass(Packages.org.dspace.eperson.AccountManager);
> importClass(Packages.org.dspace.eperson.Subscribe);
> 
> instead of
> 
> importClass(Packages.org.dspace.aspect.eperson.EPerson);
> importClass(Packages.org.dspace.aspect.eperson.AccountManager);
> importClass(Packages.org.dspace.aspect.eperson.Subscribe);
> 
> This works for me!
> 
> --Andi
> 
> 
> [Dspace-tech] javascript.evaluator.exception
> From: Mika Stenberg <mika.stenberg <at> he...> - 2008-01-10 12:59
> 
> Im trying this again. Running Manakin 1.1a and DSpace 1.4.2. Im getting
> error below when clicking "forgot password" or trying to register as new

PSQL Error

We are experiencing the following PSQL errors quite often:

An error has occured org.postgresql.util.PSQLException: This statement 
has been closed.

I remember there has been discussion that this error itself is harmless. 
However when it occurs and Manakin throws the error dump on the screen 
for the user it creates a very unpleasant use-case experience.

Is there a way to get around this?

Thanks,
Mika

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

File upload problem

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Authorization GROUPS

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Easy way to Import Metadata from Excel into DSpace

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

SQLException how can I see the offending raw SQL

Hi

I'm getting an the following intermittent error

database_error:org.postgresql.util.PSQLException: ERROR: current transaction
is aborted, commands ignored until end of transaction block

With no clear pattern as to why

What I really would like to do is to see the raw SQL that is causing
postgres to error

Does anyone know of a way to debug this error?

Many thnaks 

Charlotte

-- 
Gall y neges e-bost hon, ac unrhyw atodiadau a anfonwyd gyda hi,
gynnwys deunydd cyfrinachol ac wedi eu bwriadu i'w defnyddio'n unig
gan y sawl y cawsant eu cyfeirio ato (atynt). Os ydych wedi derbyn y
neges e-bost hon trwy gamgymeriad, rhowch wybod i'r anfonwr ar
unwaith a dilëwch y neges. Os na fwriadwyd anfon y neges atoch chi,
rhaid i chi beidio â defnyddio, cadw neu ddatgelu unrhyw wybodaeth a
gynhwysir ynddi. Mae unrhyw farn neu safbwynt yn eiddo i'r sawl a'i
hanfonodd yn unig  ac nid yw o anghenraid yn cynrychioli barn
Prifysgol Bangor. Nid yw Prifysgol Bangor yn gwarantu
bod y neges e-bost hon neu unrhyw atodiadau yn rhydd rhag firysau neu
100% yn ddiogel. Oni bai fod hyn wedi ei ddatgan yn uniongyrchol yn
nhestun yr e-bost, nid bwriad y neges e-bost hon yw ffurfio contract
rhwymol - mae rhestr o lofnodwyr awdurdodedig ar gael o Swyddfa
Cyllid Prifysgol Bangor.  www.bangor.ac.uk

This email and any attachments may contain confidential material and
is solely for the use of the intended recipient(s).  If you have
received this email in error, please notify the sender immediately
and delete this email.  If you are not the intended recipient(s), you
must not use, retain or disclose any information contained in this
email.  Any views or opinions are solely those of the sender and do
not necessarily represent those of the Bangor University.
Bangor University does not guarantee that this email or
any attachments are free from viruses or 100% secure.  Unless
expressly stated in the body of the text of the email, this email is
not intended to form a binding contract - a list of authorised
signatories is available from the Bangor University Finance
Office.  www.bangor.ac.uk

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: SQLException how can I see the offending raw SQL

On Tue, Mar 04, 2008 at 08:40:32AM +0000, Charlotte Pollock wrote:
> I'm getting an the following intermittent error
> 
> database_error:org.postgresql.util.PSQLException: ERROR: current transaction
> is aborted, commands ignored until end of transaction block
> 
> With no clear pattern as to why
> 
> What I really would like to do is to see the raw SQL that is causing
> postgres to error
>
> Does anyone know of a way to debug this error?

The only way to do this is to change your logging level from INFO to
DEBUG in your log4j.properties (you'll need to redeploy DSpace after
making the change, of course). Once you've done that, your dspace.log
should contain all the queries sent to the db.

cheers,

Jim

--

-- 
James Rutherford          |  Hewlett-Packard Limited registered Office:
Research Engineer         |  Cain Road,
HP Labs                   |  Bracknell,
Bristol, UK               |  Berks
+44 117 312 7066          |  RG12 1HN.
james.rutherford@...   |  Registered No: 690597 England

The contents of this message and any attachments to it are confidential and
may be legally privileged. If you have received this message in error, you
should delete it from your system immediately and advise the sender. To any
recipient of this message within HP, unless otherwise stated you should
consider this message and attachments as "HP CONFIDENTIAL".

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/