Child pages
  • List of Errors for Backup and Restore

This is documentation for a previous version of ClustrixDB. Documentation for the latest version can be found here

Skip to end of metadata
Go to start of metadata

Here is a list of error messages that can be given during an unsuccessful Backup or Restore.

Backup

ErrorMeaning
Bad Parameter.:"Backup..." is invalid
Bad parameter.: *.* is repeated in the list
Bad parameter.: DB "..." is included multiple times
Bad parameter.: "..." is included multiple times
Bad parameter.: nothing to back up!
Unrecognized backup url scheme: ...
syntax error: ...

 

 

Something is wrong with the BACKUP statement, please double check

Generic Error: no user DB found
Bad parameter.: Hidden database '...' cannot be backed up
No such database: '...'
Not found: Object "..." does not exist
Not found: There are more than one "..."
Backup only supported for TABLES right now: ...

 

 

Trying to backup something that cannot be backed-up, or doesn't exist

Representation is unavailable: ...
Generic Backup Error: Couldn't find baserep for ...
Generic Backup Error: Couldn't find columns for ...

 

Trying to backup something currently unavailable

Bad backup URL: ...
Unable to parse URL or connect to FTP server
Backup already exists in create: ...
There is already a backup at that location
Upload of slice was truncated on remote host: ...
File written to backup was shorter than it should have been
EXCLUDING *.* is invalid
Would backup nothing
“...” is repeated in the EXCLUDING clause
Object is excluded more than once

Restore

ErrorMeaning
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: ...

 

 

 

Something is wrong with the RESTORE statement

Bad backup URL: ...
Unable to parse URL or connect to FTP server
Unable to open backup for url: ...
Cannot open backup directory on FTP server
Backup not available for restore: ...
This backup did not complete successfully
DB not found in backup: ...
Trying to restore something that is not in the backup
Object not found in backup: ...
 
DB already exists in the target location: ...
Generic Backup Error: could not parse create statement: ...

Cannot create object

Unable to validate CREATE statement: ...
Created object does not match backed-up object
Generic Backup Error: could not parse column types from backup table "..."
Column type mismatch during restore: ...
Hash layout mismatch during restore: ...
 
Unable to locate stored CRC of file: ...
Backup CRC Mismatch: ...
Unable to locate uncompressed length of file: ... 

 

Backup is corrupt

Restore truncated by incomplete read: ...
Read too little data for a row
“...” is repeated in the EXCLUDING clause
Object is excluded more than once
Relation not found: While restoring object db_name.obj_name...
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.

Zlib errors

ErrorMeaning
Internal Error: Unexpected buffering stop
Internal buffering error
Internal Error: Unexpected stop

FTP Errors

ErrorMeaning
File not found
 
FTP Socket Closed
 
Invalid argument to API
Bad internal usage of our FTP interface
Socket timeout while waiting for server response
 
Unexpected error response from server
 
Unexpected response to PASS command
 
Unexpected response to USER command
 
Unexpected temporary error response from server
 

SFTP Errors

ErrorMeaning
A file that isn’t a directory was specified when a directory is required
 
An attempt was made to modify something on a read-only file system 
 
Bad file descriptor
 
Broken pipe
There is no process reading from the other end of a pipe
Directory not empty, where an empty directory was expected
Typically, this error occurs when you are trying to delete a directory
File exists
An existing file was specified in a context where it only makes sense to specify a new file
No space left on device
Write operation on a file failed because the disk is full
No such device or address
The system tried to use the device represented by a file you specified, and it couldn’t find the device
No such file or directory
 
Permission denied
 
SSH authentication failed
 
SSH timeout
The SSH server closed the connection due to a timeout 
The socket is not connected to anything
You get this error when you try to transmit data over a socket, without first specifying a destination for the data
Too many levels of symbolic links were encountered in looking up a file name
This often indicates a cycle of symbolic links
Unexpected SSH error
Something happened during the SSH protocol that we didn't expect