[Bug]: DB-Prefix hardcoded in update procedure

[tflidd]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

During the update from NC 27.1.6 to NC 27.1.7, after the updater script runs and the occ upgrade is run, I get this error:

Repair error: There is no table with name 'cloud.oc_file_metadata' in the schema.

However, I do not use a database prefix, from config.php:
'dbtableprefix' => '',

It seems to be an issue that exists for some time, there are a few users on the forum reporting this problem:
https://help.nextcloud.com/t/there-is-no-table-with-name-nextcloud-oc-file-metadata-in-the-schema/162467/4

Steps to reproduce

1. Install NC 27.1.6 with no database prefix
2. Update to NC 27.1.7 via integrated updater on command line

Expected behavior

That the updater checks if 'cloud.file_metadata' table exists instead of ('cloud.oc_file_metadata')

Installation method

Community Manual installation with Archive

Nextcloud Server version

27

Operating system

Other

PHP engine version

PHP 8.2

Web server

Nginx

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 22.1 to 22.2)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

"system": {
        "installed": true,
        "dbtype": "mysql",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbtableprefix": "",
        "forcessl": true,
        "blacklisted_files": [
            ".htaccess"
        ],
        "allow_user_to_change_display_name": true,
        "updatechecker": false,
        "has_internet_connection": true,
        "enablebackup": false,
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "version": "27.1.7.2",
        "installedat": "1325006970.14",
        "lastupdatedat": "1329928732.51",

List of activated Apps

- activity: 2.19.0
  - admin_audit: 1.17.0
  - announcementcenter: 6.7.0
  - audioplayer: 3.4.1
  - bookmarks: 13.1.3
  - calendar: 4.6.5
  - camerarawpreviews: 0.8.4
  - checksum: 1.2.3
  - circles: 27.0.1
  - cloud_federation_api: 1.10.0
  - comments: 1.17.0
  - contacts: 5.5.2
  - contactsinteraction: 1.8.0
  - dav: 1.27.0
  - deck: 1.11.4
  - federatedfilesharing: 1.17.0
  - federation: 1.17.0
  - files: 1.22.0
  - files_accesscontrol: 1.17.1
  - files_automatedtagging: 1.17.0
  - files_external: 1.19.0
  - files_pdfviewer: 2.8.0
  - files_reminders: 1.0.0
  - files_rightclick: 1.6.0
  - files_sharing: 1.19.0
  - files_trashbin: 1.17.0
  - files_versions: 1.20.0
  - firstrunwizard: 2.16.0
  - forms: 3.4.6
  - gpoddersync: 3.8.3
  - gpxpod: 5.0.13
  - lookup_server_connector: 1.15.0
  - mail: 3.5.7
  - maps: 1.2.0
  - memories: 6.2.2
  - news: 24.0.0
  - nextcloud_announcements: 1.16.0
  - nextpod: 0.7.4
  - notifications: 2.15.0
  - oauth2: 1.15.2
  - password_policy: 1.17.0
  - photos: 2.3.0
  - polls: 5.4.3
  - privacy: 1.11.0
  - provisioning_api: 1.17.0
  - recommendations: 1.6.0
  - related_resources: 1.2.0
  - serverinfo: 1.17.0
  - settings: 1.9.0
  - sharebymail: 1.17.0
  - survey_client: 1.15.0
  - systemtags: 1.17.0
  - tasks: 0.15.0
  - text: 3.8.0
  - theming: 2.2.0
  - twofactor_backupcodes: 1.16.0
  - twofactor_nextcloud_notification: 3.8.0
  - twofactor_totp: 9.0.0
  - twofactor_webauthn: 1.3.2
  - updatenotification: 1.17.0
  - user_status: 1.7.0
  - viewer: 2.1.0
  - workflowengine: 2.9.0

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

already put in the description

Additional info

No response

[tflidd]

sorry, I was a bit too quick, the github search didn't find the topic when entering the error message in the search field. There was a report just 12h ago:
#43966

well, they had the occ repair step, I had it on the update process. So I suppose the repair step is executed automatically during the update procedure? I keep it open in case there is a second independent check.

[solracsf]

Fix on its way at #43971
Closing as it is followed at #43966