Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF5A5D766 for ; Fri, 17 Aug 2012 11:06:00 +0000 (UTC) Received: (qmail 34352 invoked by uid 500); 17 Aug 2012 11:06:00 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 33853 invoked by uid 500); 17 Aug 2012 11:05:55 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 33823 invoked by uid 99); 17 Aug 2012 11:05:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 11:05:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elstefanito@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bk0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 11:05:45 +0000 Received: by bkty7 with SMTP id y7so1490305bkt.31 for ; Fri, 17 Aug 2012 04:05:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=yN/6Judb8mO30rX1nERZLm8pv7VMV4705GOjeY0zLKg=; b=NDGoKFssf241cxzdP+han9Lvz/yt4cAxh/FoYQGXjguyxPLBwWMCKPJFJNj7C5rU6t +C8jpCmxroY6H5t1pie2TP15CwWfrN5TvNpryyATQ1bfiJoRjL9tET64Fys50v6+pqKA Ea+rKFXPcaZbiTU9L+N/pLQ5lhFwUqSEbTbD+4ZTDxvXw/Sacdk5oUKnpoCrBfJckhfi 9l1alz0pCNddAV05V4SJUDqHqPSWlR7CJDSOWkRTG8MFMAc5AQgUKzRablx6FX6h8ryw BMRmSBKbSH56kteslV7Y5erU7J5yMFLyMUZx/APLsbhnmZSe45xDD9gTPBYsT5Xs2iOM w/Rw== Received: by 10.204.129.16 with SMTP id m16mr1709301bks.136.1345201524531; Fri, 17 Aug 2012 04:05:24 -0700 (PDT) Received: from wallbreaker (p579D3A1C.dip.t-dialin.net. [87.157.58.28]) by mx.google.com with ESMTPS id t23sm3477822bks.4.2012.08.17.04.05.22 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Aug 2012 04:05:23 -0700 (PDT) From: "Stefan R." To: Subject: Problems with Online Backup SYSCS_BACKUP_DATABASE Date: Fri, 17 Aug 2012 13:05:19 +0200 Message-ID: <001201cd7c68$3263d9a0$972b8ce0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01CD7C78.F5EDBB10" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac18aC9eip0YnkbLRsaOCNdkHWlhKg== Content-Language: de X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. ------=_NextPart_000_0013_01CD7C78.F5EDBB10 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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: =20 CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?) =20 Randomly (every 2 or 3 days) the backup cannot complete because of the = following exception: =20 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 =20 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. =20 Do you have any suggestions? Which directories are used for running the = backup and how much space needs to be availabe? =20 Thank you, Stefan =20 ------=_NextPart_000_0013_01CD7C78.F5EDBB10 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

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

 

------=_NextPart_000_0013_01CD7C78.F5EDBB10--