db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan R." <elstefan...@gmail.com>
Subject AW: Problems with Online Backup SYSCS_BACKUP_DATABASE
Date Fri, 17 Aug 2012 13:00:47 GMT
Hi,

Thanks for your answer.

 

We have 18G available at the backup destination. The size of the database
directory is: 17G. The strange thing is that it works one day, the other it
doesn't.

 

Stefan

 

 

Von: Peter Ondruška [mailto:peter.ondruska@kaibo.eu] 
Gesendet: Freitag, 17. August 2012 14:44
An: Derby Discussion
Betreff: Re: Problems with Online Backup SYSCS_BACKUP_DATABASE

 

hi, there should be in the backup destination as much disk space available
as your database size without logs.

Peter


On 17. 8. 2012, at 13:06, "Stefan R." <elstefanito@gmail.com> wrote:

Hi,

We're using Derby DB (Version 10.8.2.2) in a larger project. Our database
size is now around 12GB. It is running as network service and is used as the
data backend for several Java web projects, that are connecting to the
database using the network jdbc client. One of the projects is triggering
nightly backups using the command:

 

CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)

 

Randomly (every 2 or 3 days) the backup cannot complete because of the
following exception:

 

Aug 13 00:03:14 srv- test-001 jsvc.exec[5953]: a:662)#012Caused by:
org.apache.derby.client.am.SqlException: Cannot backup the database, got an
I/O Exception while writing to the backup container file
/mnt/backup/2012-08-13-00-00-00/bd/seg0/c9b1.dat.#012#011at
org.apache.derby.client.am.Statement.completeExecute(Unknown
Source)#012#011at
org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown
Source)#012#011at
org.apache.derby.client.net.NetStatementReply.readExecuteCall(Unknown
Source)#012#011at
org.apache.derby.client.net.StatementReply.readExecuteCall(Unknown
Source)#012#011at
org.apache.derby.client.net.NetStatement.readExecuteCall_(Unknown
Source)#012#011at
org.apache.derby.client.am.Statement.readExecuteCall(Unknown
Source)#012#011at
org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown
Source)#012#011at
org.apache.derby.client.am.PreparedStatement.executeX(Unknown
Source)#012#011... 21 more#012Caused by:
org.apache.derby.client.am.SqlException: Java exception: 'No space left on
device: java.io.IOException'.#012#011... 29 more

 

The available space on the target device is more than sufficient. We already
started the derby process with the Java Option "-Djava.io.tmpdir" to point
to a directory residing on a partition with more space. This did not help.

 

Do you have any suggestions? Which directories are used for running the
backup and how much space needs to be availabe?

 

Thank you,

Stefan

 


Mime
View raw message