Raymond Kroeker wrote:
I have encountered some entries in the mailing list suggesting that
large BLOB content is not supported when using the
network client/server. By not supported I mean either the client or the
server run out of memory when the content is
sufficiently large.
My own tests
Laura Stewart wrote:
The echo commands work for me, but when I run sysinfo, my system
returns an error.
I am trying to work through the steps in the Getting Started Guide,
specifically step 4 in
http://db.apache.org/derby/docs/10.2/getstart/tgssetupjavaenvir.html
Any ideas what might be
Laura Stewart wrote:
In the Getting Started Guide, there is this sentence:
The sysinfo script sets the appropriate environment variables,
including the classpath, and runs the sysinfo tool.
1. Are the environment variable set each time you run sysinfo or just
the first time?
Each time, I
Dan Weems wrote:
Hi
I'm getting a very strange reaction when I try running any of the
scripts that comes with JavaDB/Derby. If I run either sysinfo or ij
from the command prompt, I get the following message:
'C:\Documents' is not recognized as an internal or external command,
operable
John Embretsen wrote:
So I recommend changing
CALL %~dp0derby_common.bat %*
to
CALL %~dp0derby_common.bat %*
in the scripts you use and see if that helps.
If it does, we should probably log a Jira issue for it [1] and provide a
patch, to avoid this situation in the future.
Never mind
I've been trying to use the SYSCS_INPLACE_TABLE_COMPRESSION (SCHEMA,
TABLE, 1, 1, 1) with the intent of recovering disk space and reducing
the size of the *.dat files. Our database has grown quite big, as the
combined size of the five largest .dat files is about 2 GB. I have
deleted all of the
Since I got no answers on the dev ML, and since this is probably more
a 'user' question, I'm posting thise here.
Given my discoveries in: http://thread.gmane.org/
gmane.comp.apache.db.derby.devel/39038 , I'm now trying to shrink
Derby into a minimum-size database, both as storage space, and
I have an hard limit of 255 storage entities, files and directories. Is
it possible to make derby work for a medium size database (10-20 tables,
10-100k records) with this limit?
An empty database with just system tables etc has less than 70
files/directories. Then you will use a few log
“Inplace” Compression utility, no disk space is recovered and the size
of the “*.dat” files is not reduced.
That is correct. In-place compression re-arranges the records on
the existing pages of the existing file, gathering the existing
records together and shifting all the free space to be
Hello Kristian,
Thank you for your reply. In client/server mode the derby server
currently uses no jvm memory settings, however the derby client application
uses -Xms512m -Xmx1024m.
The same blob is being written to and retreived from the database in both
the client and server software. I
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 5:42 AM
To: Derby Discussion
Subject: Re: INPLACE Table Compression
Inplace Compression utility, no disk space is recovered and the size
of the *.dat files is not reduced.
That
three operations: purge, defrag, and truncate; when truncate is used, it
releases disk space to the operating system
Oops! My mistake. Sorry about that.
Perhaps the original caller was not passing the TRUNCATE_END parameter
in their call to INPLACE compression. My answer described the
12 matches
Mail list logo
