Cannot run "php bin/magento setup:upgrade" command when 2 stores with different table prefixes are installed in one database.

[fedorovych]

Preconditions (*)

Magento have a default option to use a database with prefix or without prefix. Same is true that you can install multiple Magento instances into one database.
We installed one default Magento with prefix and one default Magento without prefix into one MySQL database. So we had 2 default Magento installations within one MySQL database, one with a prefix and another one without any prefix:

Store_1
Magento 2.4.2p1
PHP 7.4
Store_1/app/etc/env.php
'db' => ['table_prefix' => 'sp2_','connection' => ['default' => ['host' => '192.168.0.31:3306','dbname' => 'magento237','username' => 'root','password' => 'root','model' => 'mysql4','engine' => 'innodb','initStatements' => 'SET NAMES utf8;','active' => '1','driver_options' => [1014 => false]]

Store_2
Magento 2.3.7
PHP 7.4
Store_2/app/etc/env.php
'db' => ['table_prefix' => '','connection' => ['default' => ['host' => '192.168.0.31:3306','dbname' => 'magento237','username' => 'root','password' => 'root','model' => 'mysql4','engine' => 'innodb','initStatements' => 'SET NAMES utf8;','active' => '1','driver_options' => [1014 => false]]

Steps to reproduce (*)

1. Connect to Store_1(magento with prefix) through command-line.
2. Execute the "php bin/magento setup:upgrade" command.

Expected result (*)

It must complete the operation of the command without any error.

Actual result (*)

Table error message:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento237.sp2_catalogsearch_fulltext_scope1' doesn't exist, query was: SHOW CREATE TABLE sp2_catalogsearch_fulltext_scope1

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @Den4ik
Thank you for verifying the issue. Based on the provided information internal tickets MC-42700 were created

Issue Available: @Den4ik, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.