Child pages
  • List of Errors for Backup and Restore

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Imported Korean Translation from sag76
Sv translation
languageen

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

Table of Contents

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
Sv translation
languageko

다음은 백업 또는 복구 중에 나타날 수 있는 오류 메시지 목록입니다.

Table of Contents

백업

오류의미
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: ...

 

 

BACKUP 문에 문제가 있습니다. 다시 확인하십시오.

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

 

 

백업할 수 없거나 존재하지 않는 대상을 백업하려고 합니다.

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

 

현재 사용할 수 없는 대상을 백업하려고 합니다.

Bad backup URL: ...
URL을 파싱할 수 없거나 FTP 서버에 연결할 수 없습니다.
Backup already exists in create: ...
해당 위치에 이미 백업이 있습니다.
Upload of slice was truncated on remote host: ...
백업에 기록된 파일이 실제보다 작습니다.
EXCLUDING *.* is invalid
아무것도 백업되지 않습니다.
“...” is repeated in the EXCLUDING clause
객체가 두 번 이상 제외되었습니다.

복구

오류의미
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: ...

 

 

 

RESTORE 문에 오류가 있습니다.

Bad backup URL: ...
URL을 파싱할 수 없거나 FTP 서버에 연결할 수 없습니다.
Unable to open backup for url: ...
FTP 서버에서 백업 디렉토리를 열 수 없습니다.
Backup not available for restore: ...
백업이 성공적으로 완료하지 못했습니다.
DB not found in backup: ...
백업에 없는 대상을 복구하려고 합니다.
Object not found in backup: ...
 
DB already exists in the target location: ...
Generic Backup Error: could not parse create statement: ...

객체를 생성할 수 없습니다.

Unable to validate CREATE statement: ...
생성된 객체가 백업된 객체와(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: ... 

 

백업이 손상되었습니다.

Restore truncated by incomplete read: ...
한 행에 대해 너무 적은 데이터를 읽습니다.
“...” is repeated in the EXCLUDING clause
객체가 두 번 이상 제외되었습니다.
Relation not found: While restoring object db_name.obj_name...
명시된 객체는 존재하지 않는 다른 객체를 참조합니다. 누락된 객체는 괄호 안에 표시됩니다.

예를 들어, 이 오류는 테이블이 백업에서 제외되었지만 연관된 뷰 및 트리거가 제외되지 않은 경우에 발생합니다.

Zlib 오류

오류의미
Internal Error: Unexpected buffering stop
내부 버퍼링 오류
Internal Error: Unexpected stop

FTP 오류

오류의미
File not found
 
FTP Socket Closed
 
Invalid argument to API
FTP 인터페이스의 잘못된 내부 사용
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 오류

오류의미
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
파이프의 다른 끝에서 읽는 프로세스가 없습니다.
Directory not empty, where an empty directory was expected
일반적으로 이 오류는 디렉토리를 삭제하려고 할 때 발생합니다.
File exists
새 파일이 명시되어야 할 곳에 기존 파일이 명시되었습니다.
No space left on device
디스크가 가득 차서 파일 쓰기 작업에 실패했습니다.
No such device or address
시스템이 사용자가 명시한 파일이 가리키는 장치를 사용하려고 했으나 해당 장치를 찾을 수 없습니다.
No such file or directory
 
Permission denied
 
SSH authentication failed
 
SSH timeout
SSH 서버가 시간 초과로 인해 연결을 종료했습니다. 
The socket is not connected to anything
데이터의 대상을 먼저 지정하지 않고 소켓을 통해 데이터를 전송하려고 하면 이 오류가 발생합니다.
Too many levels of symbolic links were encountered in looking up a file name
이것은 종종 심볼릭 링크의 사이클을 나타냅니다.
Unexpected SSH error
SSH 프로토콜 중에 예상하지 못한 오류가 발생했습니다.