[Dspace-tech] Migration (1.3x to 1.4x) questions
Hi, We are planning to migrate from 1.3.2 to 1.4.1. In the operational DSpace1.3.2 (http://drs.nio.org) there are lots of customisations. So we don't want to migrate directly. But to check the migration in a test server first. I have installed DSpace1.4.1 in test server. Now I want to use database assetstore of DSpace1.3.2 in DSpace.1.4.1. I have got the dspace.sql from DSpace1.3.2 using pg_dump dspace dspace.sql. I uploaded assetstore in DSpace1.4.1. But I am wandering, how to restore dspace.sql of DSpace1.3.2 in DSpace1.4.1 to reflect the database schema of 1.4.1. I tried following but unsuccessful: 1. Drop the database of 1.4.1 2. Creat new database 3. psql dspace dspace.sql (1.3.2) But it is showing problem as follows: SET SET ERROR: permission denied to set session authorization REVOKE ERROR: permission denied for schema public SET SET ERROR: function getnextid already exists with same argument types ERROR: relation bitstreamformatregistry_seq already exists ERROR: relation fileextension_seq already exists ... psql:dspace.sql:112401: ERROR: permission denied to set session authorization psql:dspace.sql:112408: ERROR: must be owner of schema public Please inform me the process of using database of DSpace1.3.2 in freshly installed DSpace1.4.1 Thanking you With regards Satya - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Migration (1.3x to 1.4x) questions
On Thu, Oct 11, 2007 at 03:47:56PM +0530, Satya Ranjan Sahu wrote: I tried following but unsuccessful: 1. Drop the database of 1.4.1 2. Creat new database 3. psql dspace dspace.sql (1.3.2) But it is showing problem as follows: SET SET ERROR: permission denied to set session authorization REVOKE ERROR: permission denied for schema public Sounds like you're having permissions problems! Did you create the new database with the correct user? Are you importing the old content as the correct user? Are you following the upgrade instructions[1]? cheers, Jim [1] http://www.dspace.org/index.php?option=com_contenttask=viewid=156#132_14 Also included in [dspace-src]/docs/. -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | 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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Migration (1.3x to 1.4x) questions
Hi Russell, First of all, should we go from our current install (1.3.2, I think) to 1.4 or 1.4.1? You would be best off going for 1.4.1 as this contains a lot of bug fixes to 1.4 You do not need to go 1.3.2 - 1.4 - 1.4.1, you can go straight to 1.4.1 Next, how much time should I allow for the migration (assuming everything goes smoothly)? It depends on the size of your database, and the availability of a test machine. In theory, on a medium-sized database such as yours (only a few thousand items), it should take less than an hour. If you have a test machine, you can test it all first, and then do it on your production machine. You can get the code on the machine and compiled in advance. All you then have to do is to stop tomcat, backup your database, run the database upgrade scripts, update your dspace.cfg file, and deploy the new DSpace code to tomcat. If things mess up (which they shouldn't!) then you have a backup of your database which you can restore, and roll back to 1.3.2 The tricky part will be if you have any customisations to the code or to the pages. If you have a test machine, you can test these in 1.4.1, but if you don't you'll have to give yourself more time to test them once you upgrade. If you don't have a test machine, another option you have is to run the two versions simultaneously by changing the names of the war files (e.g. dspace141 and dspace-oai141 and pointing them at a second copy of your database. You can then make sure you are happy with 1.4.1 whilst still running 1.3.2, and then change over one day by upgrading the 1.3.2 live database and changing the war file names back. I hope this helps, Stuart _ Datblygydd Cymwysiadau'r WeWeb Applications Developer Gwasanaethau Gwybodaeth Information Services Prifysgol Cymru Aberystwyth University of Wales Aberystwyth E-bost / E-mail: [EMAIL PROTECTED] Ffon / Tel: (01970) 622860 _ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Migration (1.3x to 1.4x) questions
We have finally identified some time to migrate from 1.3.x to 1.4.x. However, before we start the process, I would like some input from those who have made the move. First of all, should we go from our current install (1.3.2, I think) to 1.4 or 1.4.1? Next, how much time should I allow for the migration (assuming everything goes smoothly)? We are running our current deployment on a CentOS4 (2.6.9-42.0.2 kernel, Java 1.5.0_06, Postgresql 8.1.0) machine. Has anyone migrated in a similar environment? If so, any advice? Many thanks, rsk Russell S. Koonts Director, Duke University Medical Center Archives DUMC 3702 Durham, NC 27710 (919) 383-2653 | (919) 724-6735 (919) 660-1315 - with Voice Mail [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dspace-tech
