RESTORE Errors for MariaDB Xpand
This page is part of MariaDB's Documentation.
The parent of this page is: Errors for MariaDB Xpand
Topics on this page:
Overview
MariaDB Xpand supports a RESTORE
statement. The statement can raise errors in certain circumstances.
RESTORE
Errors
Errors indicating something is wrong with the
RESTORE
statement:Bad parameter.: "RESTORE ..." is invalid
Bad parameter.: Global wildcard *.* is used together with other targets
Bad parameter.: DB "..." already exists on server or in the target list
Bad parameter.: Target "..." already exists
Bad parameter.: "..." is repeated in the target list
Generic Backup Error: newdbnames array length must be same as dbnames
Unrecognized backup url scheme: ...
syntax error: ...
Errors indicating that Xpand is unable to parse URL or connect to FTP server:
Bad backup URL: ...
Errors indicating that Xpand cannot open backup directory on FTP server:
Unable to open backup for url: ...
Errors indicating that the selected backup did not complete successfully:
Backup not available for restore: ...
Errors indicating that you are trying to restore something that is not in the backup:
DB not found in backup: ...
Object not found in backup: ...
Errors indicating that Xpand cannot create the object:
DB already exists in the target location: ...
Generic Backup Error: could not parse create statement: ...
Errors indicating that the created object does not match backed-up object:
Unable to validate CREATE statement: ...
Generic Backup Error: could not parse column types from backup table "..."
Column type mismatch during restore: ...
Hash layout mismatch during restore: ...
Errors indicating that the backup is corrupt:
Unable to locate stored CRC of file: ...
Backup CRC Mismatch: ...
Unable to locate uncompressed length of file: ...
Errors indicating that Xpand read too little data for a row:
Restore truncated by incomplete read: ...
Errors indicating the object is excluded more than once:
"..." is repeated in the EXCLUDING clause
Errors indicating that the object noted references another that does not exist. The missing object is shown in parenthesis.
For example, this error occurs if a table was excluded from the backup, but the associated views or triggers were not.
Relation not found: While restoring object db_name.obj_name...