Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
yes i tried tatand it says the owner of dspace database is dspace user itself... *Thanks & Regards,* * * *Nikhil George * *Net-X Technologies* *Kochi India* *.* On Mon, Apr 25, 2011 at 9:43 PM, Mark H. Wood wrote: > On Mon, Apr 25, 2011 at 01:59:05PM +0530, Nikhil George wrote: > > psql:database_schema_13-14.sql:59: ERROR: permission denied for relation > > epersongroup > > It looks as though database user 'dspace' doesn't own or have > permission to alter the objects in that database. The first thing I'd > do is use 'psql -l' to see what DB user owns the database itself. > > -- > Mark H. Wood, Lead System Programmer mw...@iupui.edu > Asking whether markets are efficient is like asking whether people are > smart. > > > -- > Fulfilling the Lean Software Promise > Lean software platforms are now widely adopted and the benefits have been > demonstrated beyond question. Learn why your peers are replacing JEE > containers with lightweight application servers - and what you can gain > from the move. http://p.sf.net/sfu/vmware-sfemails > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
On Mon, Apr 25, 2011 at 01:59:05PM +0530, Nikhil George wrote: > psql:database_schema_13-14.sql:59: ERROR: permission denied for relation > epersongroup It looks as though database user 'dspace' doesn't own or have permission to alter the objects in that database. The first thing I'd do is use 'psql -l' to see what DB user owns the database itself. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgplvfnyaOa2d.pgp Description: PGP signature -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
anks & Regards,* * * *Nikhil George * *Net-X Technologies* Cochin, Kerela, India On Tue, Apr 19, 2011 at 10:41 PM, Jimmy Ghaphery wrote: > If you are working with two servers, production (1.4) and > future-production (1.7), would it be possible or advisable to > > 1. Copy 1.4 to the future-production server, and go through the full > upgrade steps until there is a working copy of 1.6 or 1.7 > 2. Before switching to future production, import the database and asset > store from 1.4 > 3. Run database upgrade steps > version 1.4 to 1.5: > /|psql -U dspace -f > |/[dspace-source]/|/dspace/etc/postgres/database_schema_14_15.sql dspace > |/version 1.5 to 1.6: > /|psql -U dspace -f > |/[dspace-source]/|/dspace/etc/postgres/database_schema_15_16.sql dspace > |/version 1.6 to 1.71:/| > |/ > psql -U [dspace-user] -f > [dspace-source]/dspace/etc/postgres/database_schema_16_17.sql /|dspace|/ > > Would this work in principle so that the new version could be fully > customized and tested while reducing downtime for the switch to production? > > Thanks for any direction on this. > > --Jimmy > > -- > Jimmy Ghaphery > Head, Library Information Systems > VCU Libraries > http://www.library.vcu.edu > -- > > > > Date: Tue, 19 Apr 2011 09:48:07 -0400 From: "Mark H. Wood" > Subject: Re: [Dspace-tech] Upgrading form DSpace 1.3.2 > to 1.6 To: dspace-tech@lists.sourceforge.net Message-ID: > <20110419134807.gb21...@iupui.edu> Content-Type: text/plain; > charset="us-ascii" On Tue, Apr 19, 2011 at 09:55:20AM -0300, Jason Nugent > wrote: > >>>> > >> Currently i have a running installation of Dpsace and it is > thought to be > >>>> > >> of ver 1.3.2. > >>>> > >> > >>>> > >> Few things i like to get advice from u guys are as follows: > >>>> > >> > >>>> > >> First: > >>>> > >> > >>>> > >> Is there any way to find the correct dspace version from the > installation > >>>> > >> directory files(we do't have any records of previous Dspace > installation) > >> > > >> > You can examine the HTML output of your existing DSpace site, and look > for the tag in the top part of the document. It will say something > like > >> > > >> > > >> > And from that you will have your version number. > > That was added somewhere in the 1.6 line. It doesn't exist in 1.3. > > > > If you still have the source code for what you are running, you could > > look for: > > > > o a README file. I have a copy of 1.4.2 and the README says "DSpace > >Version 1.4.2, 8-May-2007" near the top. > > > > o a CHANGES file. The version number nearest the top should be the > >one represented by the source kit you have. > > > >>>> > >> Second: > >>>> > >> > >>>> > >> Does a simple copying and restoring of asseststore and database > wrks for > >>>> > >> the upgrading process..? > >> > > >> > The assetstore directory simply exists on disk and you can just copy > it with standard unix commands. I'd suggest backing it up, and then copying > it into the assetstore directory (maintaining permissions in the process), > for the upgrade. Likewise, there are Postgres tools for backing up your > database. Please have a look at the pg_dump command, which will export the > SQL and database structure out to disk. > > Those tools work well for backup and restore *to the same version*, > > but dumping and loading a DSpace 1.3 schema will result in a new copy > > of a 1.3 schema. You need to follow the upgrade instructions in the > > manual: > > > > http://www.dspace.org/1_6_2Documentation/ch04.html > > > > to upgrade the database schema, and you need to update the dspace.cfg > > as documented in the manual. You need to carry out the schema and > > configuration updates in order for each version between the one you > > start with and the one you end at, but you don't need to install all > > of those intermediate versions. This is explained in the Upgrading > > chapter of the documentation. If that leaves you with further > > questions, ask! > > > > The assetstore layout hasn't changed in years and should require no > > updates. We've been running DSpace since 1.2 or so and I don't recall > > ever having to do anything with the assetstore except protect it > > as-is. (That includes
Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
If you are working with two servers, production (1.4) and future-production (1.7), would it be possible or advisable to 1. Copy 1.4 to the future-production server, and go through the full upgrade steps until there is a working copy of 1.6 or 1.7 2. Before switching to future production, import the database and asset store from 1.4 3. Run database upgrade steps version 1.4 to 1.5: /|psql -U dspace -f |/[dspace-source]/|/dspace/etc/postgres/database_schema_14_15.sql dspace |/version 1.5 to 1.6: /|psql -U dspace -f |/[dspace-source]/|/dspace/etc/postgres/database_schema_15_16.sql dspace |/version 1.6 to 1.71:/| |/ psql -U [dspace-user] -f [dspace-source]/dspace/etc/postgres/database_schema_16_17.sql /|dspace|/ Would this work in principle so that the new version could be fully customized and tested while reducing downtime for the switch to production? Thanks for any direction on this. --Jimmy -- Jimmy Ghaphery Head, Library Information Systems VCU Libraries http://www.library.vcu.edu -- > Date: Tue, 19 Apr 2011 09:48:07 -0400 From: "Mark H. Wood" > Subject: Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6 To: > dspace-tech@lists.sourceforge.net Message-ID: > <20110419134807.gb21...@iupui.edu> Content-Type: text/plain; > charset="us-ascii" On Tue, Apr 19, 2011 at 09:55:20AM -0300, Jason Nugent > wrote: >>>> > >> Currently i have a running installation of Dpsace and it is thought >>>> > >> to be >>>> > >> of ver 1.3.2. >>>> > >> >>>> > >> Few things i like to get advice from u guys are as follows: >>>> > >> >>>> > >> First: >>>> > >> >>>> > >> Is there any way to find the correct dspace version from the >>>> > >> installation >>>> > >> directory files(we do't have any records of previous Dspace >>>> > >> installation) >> > >> > You can examine the HTML output of your existing DSpace site, and look for >> > the tag in the top part of the document. It will say something like >> > >> > >> > And from that you will have your version number. > That was added somewhere in the 1.6 line. It doesn't exist in 1.3. > > If you still have the source code for what you are running, you could > look for: > > o a README file. I have a copy of 1.4.2 and the README says "DSpace >Version 1.4.2, 8-May-2007" near the top. > > o a CHANGES file. The version number nearest the top should be the >one represented by the source kit you have. > >>>> > >> Second: >>>> > >> >>>> > >> Does a simple copying and restoring of asseststore and database wrks >>>> > >> for >>>> > >> the upgrading process..? >> > >> > The assetstore directory simply exists on disk and you can just copy it >> > with standard unix commands. I'd suggest backing it up, and then copying >> > it into the assetstore directory (maintaining permissions in the process), >> > for the upgrade. Likewise, there are Postgres tools for backing up your >> > database. Please have a look at the pg_dump command, which will export >> > the SQL and database structure out to disk. > Those tools work well for backup and restore *to the same version*, > but dumping and loading a DSpace 1.3 schema will result in a new copy > of a 1.3 schema. You need to follow the upgrade instructions in the > manual: > > http://www.dspace.org/1_6_2Documentation/ch04.html > > to upgrade the database schema, and you need to update the dspace.cfg > as documented in the manual. You need to carry out the schema and > configuration updates in order for each version between the one you > start with and the one you end at, but you don't need to install all > of those intermediate versions. This is explained in the Upgrading > chapter of the documentation. If that leaves you with further > questions, ask! > > The assetstore layout hasn't changed in years and should require no > updates. We've been running DSpace since 1.2 or so and I don't recall > ever having to do anything with the assetstore except protect it > as-is. (That includes backing it up regularly and before upgrades!) > > -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether > markets are efficient is like asking whether people are smart. -- > next part -- A non-text attachment was scrubbed... Name: not > available Type: application/pgp-signature Size: 198 bytes Desc: not available > -- > -- -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
On Tue, Apr 19, 2011 at 09:55:20AM -0300, Jason Nugent wrote: > >> Currently i have a running installation of Dpsace and it is thought to be > >> of ver 1.3.2. > >> > >> Few things i like to get advice from u guys are as follows: > >> > >> First: > >> > >> Is there any way to find the correct dspace version from the installation > >> directory files(we do't have any records of previous Dspace installation) > > You can examine the HTML output of your existing DSpace site, and look for > the tag in the top part of the document. It will say something like > > > And from that you will have your version number. That was added somewhere in the 1.6 line. It doesn't exist in 1.3. If you still have the source code for what you are running, you could look for: o a README file. I have a copy of 1.4.2 and the README says "DSpace Version 1.4.2, 8-May-2007" near the top. o a CHANGES file. The version number nearest the top should be the one represented by the source kit you have. > >> Second: > >> > >> Does a simple copying and restoring of asseststore and database wrks for > >> the upgrading process..? > > The assetstore directory simply exists on disk and you can just copy it with > standard unix commands. I'd suggest backing it up, and then copying it into > the assetstore directory (maintaining permissions in the process), for the > upgrade. Likewise, there are Postgres tools for backing up your database. > Please have a look at the pg_dump command, which will export the SQL and > database structure out to disk. Those tools work well for backup and restore *to the same version*, but dumping and loading a DSpace 1.3 schema will result in a new copy of a 1.3 schema. You need to follow the upgrade instructions in the manual: http://www.dspace.org/1_6_2Documentation/ch04.html to upgrade the database schema, and you need to update the dspace.cfg as documented in the manual. You need to carry out the schema and configuration updates in order for each version between the one you start with and the one you end at, but you don't need to install all of those intermediate versions. This is explained in the Upgrading chapter of the documentation. If that leaves you with further questions, ask! The assetstore layout hasn't changed in years and should require no updates. We've been running DSpace since 1.2 or so and I don't recall ever having to do anything with the assetstore except protect it as-is. (That includes backing it up regularly and before upgrades!) -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgpY5m7jC62CE.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
Nikhil, >> >> Currently i have a running installation of Dpsace and it is thought to be >> of ver 1.3.2. >> >> Few things i like to get advice from u guys are as follows: >> >> First: >> >> Is there any way to find the correct dspace version from the installation >> directory files(we do't have any records of previous Dspace installation) You can examine the HTML output of your existing DSpace site, and look for the tag in the top part of the document. It will say something like And from that you will have your version number. >> Second: >> >> Does a simple copying and restoring of asseststore and database wrks for >> the upgrading process..? The assetstore directory simply exists on disk and you can just copy it with standard unix commands. I'd suggest backing it up, and then copying it into the assetstore directory (maintaining permissions in the process), for the upgrade. Likewise, there are Postgres tools for backing up your database. Please have a look at the pg_dump command, which will export the SQL and database structure out to disk. Jason -- Jason Nugent jnug...@unb.ca Programmer/Analyst, UNB Libraries (506) 447-3177 -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Upgrading form DSpace 1.3.2 to 1.6
Hello all, Currently i have a running installation of Dpsace and it is thought to be of ver 1.3.2. I have to upgrade it to 1.6.2 . Few things i like to get advice from u guys are as follows: First: Is there any way to find the correct dspace version from the installation directory files(we do't have any records of previous Dspace installation) Second: Does a simple copying and restoring of asseststore and database wrks for the upgrading process..? please advice.. *Thanks & Regards,* * * *Nikhil George * *Net-X Technologies* Cochin, Kerela, India -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
