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

oro_reminder table does not exist in migrations (fresh installation OroCommerce 3.1.15) #347

Open
sundbry opened this issue Nov 12, 2019 · 4 comments

Comments

@sundbry
Copy link

sundbry commented Nov 12, 2019

While installing a fresh OroCommerce-CE 3.1.15:
php ./bin/console oro:install --env=dev --drop-database --timeout=900

It looks like the script is trying to run a migration on a table that doesn't exist.

  > Oro\Bundle\CRMBundle\Migrations\Schema\OroCRMBundleInstaller
    ERROR: An exception occurred while executing 'UPDATE oro_reminder SET related_entity_classname = REPLACE(related_entity_classname, 'OroCRM', 'Oro')
                    WHERE related_entity_classname LIKE '%OroCRM%'':

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mydb.oro_reminder' doesn't exist

oro-install-error.txt

I don't find any other references to the oro_reminder table, perhaps this migration is obsolete?

@sundbry
Copy link
Author

sundbry commented Nov 12, 2019

It looks like this migration more properly belongs in https://github.com/oroinc/platform/tree/master/src/Oro/Bundle/ReminderBundle/Migrations/Schema with the rest of the reminder schema evolution

@anyt anyt added the question label Nov 15, 2019
@anyt
Copy link
Contributor

anyt commented Nov 15, 2019

This is not a regular schema migration, but it updates data records that are related to OroCRM, so we can't place the migration to the platform package, as th platform should not know about OroCRM.

@Baachi
Copy link

Baachi commented Jan 15, 2020

If someone also entered this issue, this might help. In my case, the installed parameter in the paramters.yml wasn't set to null so Oro thinks it was an upgrade, not a fresh install.

@mbessolov
Copy link
Member

@Baachi yes, correct. The installer oro:install after detecting that the application is already installed, shows a warning but does not stop. This will be fixed (not stopping after the warning).

In either case you need to follow the instructions contained in the warning before trying to reinstall an already installed application:

ATTENTION: Oro Application already installed.
To proceed with install:

  • set parameter installed: false in config/parameters.yml
  • remove caches in var/cache folder manually
  • drop database manually or reinstall over existing database
    ...

internal ticket ID: BAP-19576

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants