Hello Stefan,

the

"5.0.2014.11.04 | Enable XMLWorkflow Migrati ..."
in your schema indicates that you had switched to the xmlworkflow at
some point.

This is done via the configuration in:
[dspace]/config/modules/workflow.cfg
workflow.framework=xmlworkflow
and some changes in [dspace]/config/xmlui.xconf  if you are using the xmlui.

Then
https://github.com/DSpace/DSpace/blob/dspace-5.4/dspace-api/src/main/java/org/dspace/storage/rdbms/xmlworkflow/V5_0_2014_11_04__Enable_XMLWorkflow_Migration.java

will apply the sripts in
https://github.com/DSpace/DSpace/tree/dspace-5.4/dspace-api/src/main/resources/org/dspace/storage/rdbms/xmlworkflow/postgres


As far as I understand the documentation this is an irreversible step
https://wiki.duraspace.org/display/DSDOC5x/Configurable+Workflow#ConfigurableWorkflow-InstructionsforEnablingConfigurableReviewerWorkflowinXMLUI


Claudia





Am 14.03.2016 um 15:51 schrieb Stefan Fritzsche:
Hello Claudia,

thanks for the answer. It seems to me that my git was broken.
I did not found any of the sql files in my local repo.

Now i got all scripts and run into the next error ;). I try to migrate
the db to my new schema (add a table and sequence). Before i start the
migrate operation the info command shows the following table:

  
+----------------+----------------------------+---------------------+---------+
| Version        | Description                | Installed on        |
State   |
+----------------+----------------------------+---------------------+---------+
| 1              | << Flyway Init >>          | 2015-09-02 14:57:25 |
Success |
| 1.1            | Initial DSpace 1.1 databas | 2015-09-02 14:57:26 |
Success |
| 1.2            | Upgrade to DSpace 1.2 sche | 2015-09-02 14:57:28 |
Success |
| 1.3            | Upgrade to DSpace 1.3 sche | 2015-09-02 14:57:28 |
Success |
| 1.3.9          | Drop constraint for DSpace | 2015-09-02 14:57:28 |
Success |
| 1.4            | Upgrade to DSpace 1.4 sche | 2015-09-02 14:57:29 |
Success |
| 1.5            | Upgrade to DSpace 1.5 sche | 2015-09-02 14:57:29 |
Success |
| 1.5.9          | Drop constraint for DSpace | 2015-09-02 14:57:30 |
Success |
| 1.6            | Upgrade to DSpace 1.6 sche | 2015-09-02 14:57:30 |
Success |
| 1.7            | Upgrade to DSpace 1.7 sche | 2015-09-02 14:57:31 |
Success |
| 1.8            | Upgrade to DSpace 1.8 sche | 2015-09-02 14:57:31 |
Success |
| 3.0            | Upgrade to DSpace 3.x sche | 2015-09-02 14:57:31 |
Success |
| 4.0            | Upgrade to DSpace 4.x sche | 2015-09-02 14:57:31 |
Success |
| 5.0.2014.08.08 | DS-1945 Helpdesk Request a | 2015-09-02 14:57:31 |
Success |
| 5.0.2014.09.25 | DS 1582 Metadata For All O | 2015-09-02 14:57:31 |
Success |
| 5.0.2014.09.26 | DS-1582 Metadata For All O | 2015-09-02 14:57:32 |
Success |
| 5.0.2014.11.04 | Enable XMLWorkflow Migrati | 2015-10-23 14:38:57 |
Missing |
| 5.0.2016.03.13 | Instition table and seq    |                     |
Pending |
+----------------+----------------------------+---------------------+---------+

The last entry are my changes. But migrate command fails at the step
before with the following error:

...
Caused by: org.flywaydb.core.api.FlywayException: Validate failed. Found
differences between applied migrations and available migrations:
Detected applied migration missing on the classpath: 5.0.2014.11.04
...

How can i remove the migrate step 5.0.2014.11.04? I also did not found
the sql script in script location path.

Thanks in advance
Stefan

On 03/14/2016 01:25 PM, Claudia Jürgen wrote:
Hello Stefan,

this is documented in:
https://github.com/DSpace/DSpace/blob/master/dspace/etc/postgres/README.md

"As of DSpace 5.0, we now use Flyway DB along with the SQL scripts
embedded in the dspace-api.jar to automatically keep your DSpace
database up-to-date. These scripts are now located in the source code
at:
[dspace-src]/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres

As Flyway automates the upgrade process, you should NEVER run these SQL
scripts manually. For more information, please see the README.md in the
scripts directory."

Hope this helps

Claudia Jürgen


Am 14.03.2016 um 12:19 schrieb Stefan Fritzsche:
Dear Members,

i try to find the source where the dspace db is created.
In the table schema_version exsists entries like

... | 1.2            | Upgrade to DSpace 1.2 schema
| SQL  |1.2__Upgrade_to_DSpace_1.2_schema.sql   | ...
... | 1.3            | Upgrade to DSpace 1.3 schema
| SQL  | V1.3__Upgrade_to_DSpace_1.3_schema.sql| ...

Can anybody point me to the place where *.sql scripts live?

Thanks in advance.
Stefan




--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
[email protected]
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich.
Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht
der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte
den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung
eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is
confidential. It is solely intended for the recipient. If you are not
the intended recipient of this e-mail please contact the sender and
delete this message. Thank you. Without prejudice of e-mail
correspondence, our statements are only legally binding when they are
made in the conventional written form (with personal signature) or
when such documents are sent by fax.



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
[email protected]
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to