Did you go back and start the migration over by wiping the database as it stated in the instructions or did you try to continue the migration without starting over?
Somehow it got updated, I mean “./etsis core update” never worked before. I know the migrate is not successful as I have posted in the previous post.
But the tables have got updated in the database it went to 95 tables from 85, so I think the migration part is half successful.
and now I am getting the same error as below
[PDOException] SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'type'
migrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] [-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE]
Phinx by Rob Morgan - https://phinx.org. version 0.6.4 using config file ./phinx.php using config parser php using migration path app/migrations using environment production using adapter mysql using database PortobelloLive == 20170706151405 DbSchemaUpdate: migrating
I think there is something in change, I have been trying few things like you have suggested. So this time there is change in the error
[PDOException]
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'stuLoad' cannot be null
migrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] [-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE]
Phinx by Rob Morgan - https://phinx.org. 0.8.1
using config file ./phinx.php
using config parser php
using migration paths
- /var/www/html/app/migrations
using environment production
using adapter mysql
using database ********
== 20170706151405 DbSchemaUpdate: migrating
Yes, I ran into this issue a few weeks ago. I was working with a newly created database on an Ubuntu box. To figure out why, I did a test by doing a new installation. It was then when I found out that all the primary keys were being signed with zerofill or something of that effect.
I couldn’t figure out why that was. I waited a few days, went back to try the migration again and it worked. All I can figure is that there must be some lag time between the creation of the database and the MySQL server.
I have been trying to migrate the database from 6.2.12 version. I did all the precautions that have explained in “Database Migration to Release 6.3.0”
Everything is until step 11, but step 12 gives me some errors and that stops me going to “./etsis core update” and even if I try to update it’s not working.
[root@ip-****** html]# ./etsis core migrate
[PDOException]
SQLSTATE[HY000]: General error: 1005 Can't create table 'PortobelloLive.perc' (errno: 150)
migrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] [-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE]
Phinx by Rob Morgan - https://phinx.org. version 0.6.4
using config file ./phinx.php
using config parser php
using migration path app/migrations
using environment production
using adapter mysql
using database PortobelloLive
== 20170706151405 DbSchemaUpdate: migrating
I tried “./etsis core migrate” again after getting the above error
[PDOException]
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'type'
migrate [-c|--configuration CONFIGURATION] [-p|--parser PARSER] [-e|--environment ENVIRONMENT] [-t|--target TARGET] [-d|--date DATE]
Phinx by Rob Morgan - https://phinx.org. version 0.6.4
using config file ./phinx.php
using config parser php
using migration path app/migrations
using environment production
using adapter mysql
using database PortobelloLive
== 20170706151405 DbSchemaUpdate: migrating
The topic ‘Database migration issue’ is closed to new replies.
About eduTrac SIS
eduTrac SIS is a free and open source student information system for higher education. We believe that it is the best free system out there for higher education and specialized schools.
