Hi Emilio,
we did this migration when we moved from Dspace 1.4 to Dspace 1.5. Dump every
table separately. Ensure that you dump every table using INSERT INTO and not
COPY. Be sure to do that, because columns positions have changed over time.
Then we ran into all kinds of problems, when using SQLPlus to import the data.
Then check whether Oracle wants to import the table. We had to manually edit
several of the tables before we could import the table into Oracle.
The & in text fields is interpreted as command line parameter input; so you
have to SET DEFINE OFF. There are problems with those tables using a timestamp,
and values for BOOLEANs because of the differences in notation accepted by
Oracle. It is likely you run into ORA-01704: string literal too long, e.g. with
the description or abstract fields. In particular with the metadatavalue table
there are many problems. when fields contain whitespace, the ; character, empty
lines without content, records containing more than 2499 characters, fields
containing more than 4K of text. The empty string in the records in
most_recent_checksum table are seen as NULL and can't be inserted into the NOT
NULL column, and plenty more.
Then import every table into Oracle in the same order as they are created in
the Oracle schema sql, else you run into constraint violations.
Update indexes and sequences and test.
This worked in our case, but we are running Dspace jspui without any
modifications. Upgrade to 1.8 went fine. Upgrade to 3.2 also seems fine, but
I’m still testing.
Or try to use the export and import functions.
Francis Brouns
Open Universiteit | Welten Institute. Research Centre for Learning, Teaching
and Technology | Visiting address: Valkenburgerweg 177, 6419 AT Heerlen, The
Netherlands | Postal address: PO Box 2960, 6401 DL Heerlen, The Netherlands |
T: +31 45 5762152 |E: francis.bro...@ou.nl
From: emilio lorenzo [mailto:elore...@arvo.es]
Sent: 20 February 2014 14:31
To: heli...@centrum.sk
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] [Dspace-general] Database Migration Postgresql-->
Oracle
I supposed something as complicated as you description.... :-)
Anyone has attempted this "migration" ?
Thanks
El 20/02/2014 13:50, helix84 escribió:
On Thu, Feb 20, 2014 at 1:31 PM, emilio lorenzo
<elore...@arvo.es<mailto:elore...@arvo.es>> wrote:
1. Change JDBC connectors on dspace.cfg
2. Migrate the database (any tips or advices on this point?)
3. Recompile ?
No need to rebuild. You "only" need to change the configuration
(db.name<http://db.name>, db.url, db.driver, db.username, db.password,
db.schema) and transfer the data. Migrating the data will be where all the fun
is at. I'm not aware on any notes that document this mostly manual process
completely, but see below for some notes and opinions. I ranked them from the
most to least useful.
In general I would attempt the process this way:
1) pg_dump the data
2) create a fresh DSpace DB in Oracle
3) it might be necessary to drop some constraints in Oracle
4) the fun step - attempt to import each table, correcting the data for
difference in column types as you go
5) attempt to reinstate constraints
6) if all looks well, run update-sequences.sql
7) point DSpace to Oracle and restart it
8) test, test, test
Keep in mind that I have never attempted this.
http://dspace.2283337.n4.nabble.com/DSpace-database-migration-from-Postgres-to-Oracle-td3278996.html#a3278997
http://wiki.postgresql.org/wiki/Oracle_to_Postgres_Conversion
http://blogs.exeter.ac.uk/openexeterrdm/blog/2012/05/25/dspace-our-repository-software/
http://en.it-usenet.org/thread/11494/3557/
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
________________________________
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan
en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere
aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de
inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten
worden ontleend.
This e-mail is intended exclusively for the addressee(s), and may not be passed
on to, or made available for use by any person other than the addressee(s).
Open Universiteit rules out any and every liability resulting from any
electronic transmission. No rights may be derived from the contents of this
message.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
