Magento 2 error Primary db_schema doesn't exists - magento2

I am getting this error on Magento 2.3.6 when running
bin/magento setup:upgrade
Updating modules:
Schema creation/updates:
Primary db_schema file doesn`t exists
Any idea what may cause this issue ?

The file db_schema.xml should be present in app/etc

Related

magento 1 to magento 2 issue migration

run command
bin/magento migrate:data -a app/code/Vendor/Migration/etc/opensource-to-opensource/1.9.4.0/config.xml
Error migration magento 1.9.4.0 to magento2 2.3.5
Base table or view not found: 1146 Table 'magento1.customer_entity_static' doesn't exist
Find a module that you are installing that is using customer_entity_static table, disable it and try again.
Please check if You have custom attribute with backend_type == static in your eav_attribute table. Problem is in vendor/magento/data-migration-tool/src/Migration/Step/Customer/Model/AttributesDataToCustomerEntityRecords.php file in fetchAttributesData method. It gets $attributeIdsByType and based on type magento refers to table (e.g. it refers to table customer_entity_ + backend_type (in my, and your case it is type static).

Typo3 Upgrade 7.6.31 to 8.7.19 / Database Analyzer fails

during the upgrade process from 7.6 to 8.7 the database Analyzer fails in the following statement:
Error:
Database update failed
Error: Specified key was too long; max key length is 1000 bytes
can you help?
i found the solution.
drop index lookup_string on sys_refindex;
then you can run database analyzer in to steps:
ALTER TABLE ....
CREATE INDEX ....
but this is done by database analyzer in upgrade wizard

Magento 2.2.4 + Database migration Undefined offset: 1 vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 291

I am doing database migration from magento 1.9.3.7 to magento 2.2.4.
When i run below command
php bin/magento migrate:data --reset path of config.xml
Then below issue is occur's
Notice: Undefined offset: 1 in vendor/magento/data-migration-tool/src/Migration/Step/Eav/Data.php on line 291
When i re-run command then
Integrity constraint violation: 1062 Duplicate entry '1-Migration_Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_
NAME'
i have reinstall magento fresh Database and again i have found these issue.
Please suggest me how it can fix.

Call to a member function getDateFormat() on null when running php artisan passport:install

I'm getting this error message :
PHP Fatal error: Call to a member function getDateFormat() on null in /usr/local/ampps/www/project/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 2992
when I'm trying to run this command :
php artisan passport:install
I'm using a fresh installed laravel v5.3.16 with mysql and mongodb database structure.
any idea how to fix this ?
I've Found the solution, I had to install laravel and then passport package then modify mongodb migrations to make it work.
It was order of this action which made this error.

PropelBundle database:create for postgres

I've installed propel bundle for symfony2.
my database configuration is:
propel:
dbal:
driver: pgsql
user: postgres
password: postgres
dsn: pgsql:host=localhost;port=5432;dbname=test_database
options: {}
attributes: {}
When i wan to create this database from console (console propel: database:create) i have got strange error : Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] FATAL: database "pgsql" does not exist.
i created pgsql database on my localhost and everything was good. Database "test_database" was succesfull created. Can somebody explain me why i got this previous error? On mysql i've created database without any problems.
This issue was a bug in the PropelBundle, it has been fixed by the following commit (even if the commit message is about MySQL, it fixes other RDBMS): https://github.com/propelorm/PropelBundle/commit/b4475d27fb1eb846d10cc2d2e2bd164f037508e3
I 've installed new PropelBundle via Composer and everything is ok now. I think maybe it was a problem with 1.0 bundle , now I have 1.1