Another crisis averted :)  I tried to export the database via Navicat's MS
Access format and it imported vi Navicat on the new box just fine (although
I'll have to re-assign primary keys, apparently).  Before, I was trying to
export in a text delimited format, but it would mess up field lengths and
primary/foreign keys. So, it seems to be working.  Thanks for your advice!

Cheers,
Stan


On Thu, Mar 19, 2009 at 3:52 PM, Stan Orlov <[email protected]> wrote:

> Hi Allen,
>
> Thank you for the suggestion.  I just would like to confirm whether it
> applies to the situation where dspace version hasn't changed?  I have dspace
> 1.5.1 on both machines.  Postgres versions are slightly different (8.3.5-1
> on the old and 8.3.6-2 on the new), but it probably isn't a significant
> difference?
>
> Dspace notwithstanding, I am trying to figure out how any postgres database
> (in this case: dspace) could be flawlessly exported to another machine with
> pretty much the same software version.
>
> Cheers,
> Stan
>
>
>
>
> On Thu, Mar 19, 2009 at 12:05 PM, Allen Lam <[email protected]>wrote:
>
>> The db schema is changed while dspace version is changed. You errors may
>> be caused by version mismatch between dspace and db.
>>
>> I suggest you re-create the old version db on the new machine, then run
>> the upgrade scripts provided by dspace to upgrade the db schema upto 1.5.1
>>
>> Hope this helps.
>>
>> Regards,
>> Allen Lam.
>> HKU Hub Administrator, http://hub.hku.hk
>>
>>
>> Stan Orlov wrote:
>>
>>> Forgot to mention - I am running the latest versions of DSpace (1.5.1)
>>> and PostgreSQL (8.3) on both machines.  And also the latest Apache and
>>> Tomcat 6.
>>>
>>>
>>> On Thu, Mar 19, 2009 at 6:26 AM, Stan Orlov <[email protected] <mailto:
>>> [email protected]>> wrote:
>>>
>>>    Greetings!
>>>
>>>    I have DSpace running on a Windows XP machine and am migrating it
>>>    to a Windows 2003 server with the same structure.  Installation
>>>    went smoothly, jspui is accessible, but I can't properly transfer
>>>    the PostgreSQL database.  I tried to dump it using command line,
>>>    backup using pgAdmin III, backup using Navicat for PostgreSQL and
>>>    also used export Wizard in PostgreSQL.  However, I can't import it
>>>    properly using the same tools on the new machine.  I have
>>>    different errors depending on the tool used and can post them if
>>>    that would help, but the root of the problem is probably in me
>>>    missing some step somewhere.
>>>
>>>    Since you probably have done this a million times, is there a
>>>    bulletproof PostgreSQL export/import command or utility you could
>>>    recommend?
>>>
>>>    Cheers,
>>>    Stanislav Orlov
>>>
>>>
>>
>>
>> This communication, including any attached documentation, is intended only
>> for the person or entity to which it is addressed, and may contain
>> confidential, personal, and/or privileged information. Any unauthorized
>> disclosure, copying, or taking action on the contents is strictly
>> prohibited. If you have received this message in error, please contact us
>> immediately so we may correct our records. Please then delete or destroy the
>> original transmission and any subsequent reply. Thank you.
>>
>
>
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to