Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected error re. non-empty schemas #2537

Closed
juliahayward opened this issue Oct 21, 2019 · 3 comments
Closed

Unexpected error re. non-empty schemas #2537

juliahayward opened this issue Oct 21, 2019 · 3 comments

Comments

@juliahayward
Copy link
Member

@juliahayward juliahayward commented Oct 21, 2019

Reported by David Atkinson:

Confusing error here. The issue is that my HR schema is non empty, but the error also mentions the lack of schema history table, which is not relevant as HR is the second of two schemas, so shouldn't have a schema history table anyway, as this gets created and managed in the first.
Running flyway migrate failed:

Flyway Enterprise Edition (unlimited schemas) 6.0.6 by Redgate licensed to Redgate until 2020-07-01
Database: jdbc:oracle:thin:@//localhost:1521/dev1.red-gate.com (Oracle 18.0)
Successfully validated 18 migrations (execution time 00:00.042s)
ERROR: Found non-empty schema(s) "HR" without schema history table! Use baseline() or set baselineOnMigrate to true to initialize the schema history table.```
@dvdtknsn
Copy link

@dvdtknsn dvdtknsn commented Oct 21, 2019

My Flyway conf has the following: ]
flyway.schemas=CRM, HR

(so HR will never have a schema history table so suggesting this might be the problem in the error is confusing - the real problem here was the non-empty schema)

@juliahayward juliahayward added this to the Flyway 6.0.8 milestone Oct 21, 2019
@juliahayward
Copy link
Member Author

@juliahayward juliahayward commented Oct 21, 2019

We're going to revisit this after we've resolved #1328 as that will have some bearing on the relevant error messages.

@MikielAgutu MikielAgutu removed this from the Flyway 6.0.8 milestone Oct 30, 2019
@MikielAgutu MikielAgutu added this to the Flyway 6.1.0 milestone Oct 30, 2019
@juliahayward juliahayward removed this from the Flyway 6.1.0 milestone Nov 25, 2019
@juliahayward juliahayward added this to the Flyway 6.1.1 milestone Nov 25, 2019
@juliahayward juliahayward removed this from the Flyway 6.1.1 milestone Dec 5, 2019
@juliahayward juliahayward added this to the Flyway 6.2 milestone Dec 5, 2019
@juliahayward juliahayward removed this from the Flyway 6.2 milestone Dec 5, 2019
@juliahayward juliahayward added this to the Flyway 6.x milestone Dec 5, 2019
@juliahayward juliahayward removed this from the Flyway 6.x milestone Dec 18, 2019
@juliahayward juliahayward added this to the Flyway 6.1.3 milestone Dec 18, 2019
@juliahayward
Copy link
Member Author

@juliahayward juliahayward commented Dec 18, 2019

Message clarified in 6.1.3

alextercete added a commit that referenced this issue Dec 20, 2019
dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants