On this page
This issue can be caused when trying to replicate between a v5.
You need to upgrade both clusters to 6.
ERROR 1832 (HY000): Restoring partitions on
Couldn’t find backup file for partition # of database
X (there are ### partitions without backup files).
This error means that there is not enough available disk in the backup directory.
Make sure that you have sufficient disk space in the designated backup directory and retry the operation.
ERROR 2523 UNKNOWN_
If multiple bottomless databases are created on S3 in the same folder, detaching and then attaching any one of the databases leads to this error.
STORAGEID clause in the ATTACH DATABASE command.
ERROR 2625: Operation 'BACKUP DATABASE' can't be executed on internal database('') utilized by SingleStore.
This error occurs when you attempt to backup the
These databases are internal system databases, and as such, they cannot and do not need to be backed up.
The most common cause for this error is an
ALTER TABLE query on a sharded table which ran partially but didn’t complete successfully.
If the cause of the issue was a failed
ALTER TABLE as described above, possible solutions are:
Recreate the table.
This can be done by insert-selecting the data into a newly created table or reloading the data. For example:
sql CREATE TABLE t_
copy AS SELECT * FROM t; DROP TABLE t; ALTER TABLE t_ copy RENAME AS t;
Find the partition(s) with inconsistent table metadata, and manually run
ALTERon the leaf partitions to correct them.
This is a general error code; however, this error can occur when your pipeline tries to execute your transform while loading your data into SingleStoreDB.
Place a shebang at the top of your transform file to invoke the correct interpreter.
#!/usr/bin/env python3 for Python 3 or
#!/usr/bin/env ruby for Ruby).
Last modified: August 28, 2023