Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
From: "Bergquist, Brett" <BBergquist@canoga.com>
To: "derby-dev@db.apache.org" <derby-dev@db.apache.org>
Date: Tue, 16 Aug 2011 05:56:43 -0700
Subject: Question on unloading in an embedded environment
Thread-Topic: Question on unloading in an embedded environment
Thread-Index: AcxcE/LIQSJa1auxTTW9wjP3GcD6Cw==
Message-ID: <97EB699F861AD841B5908C7CA9C956560160A03B5AA7@VSERVER1.canoga.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I am writing a database copy utility that is built upon the dblook utility =
and using the SYSCS_UTIL.SYSCS_EXPORT_TABLE  and SYSCS_UTIL.SYSCS_IMPORT_TA=
BLE procedures and I have this mostly working.  When running this on a larg=
e database (110Gb) I am getting an OutOfMemory exception.  I have the utili=
ty setup to use up to 8192Mb of memory so somewhere there is a problem.  I =
am running this again with the -XX:+HeapDumpOnOutOfMemoryError switch to se=
e if I can get a picture on where it is leaking but it will take about 6 ho=
urs to get to this point.

In the mean time, assuming the error is not in my utility, I would like to =
potentially shutdown the database and restart it to try to work around the =
OOME.  I am running the database engine in embedded mode and see the docume=
ntation to shutdown the database, but I also see the following in the Derby=
 10.8 Reference manual page 293:

"With the embedded driver, if your application shuts down Derby or calls th=
e
DriverManager.unload method, and you then want to reload the driver, call t=
he
Class.forName().newInstance() method to do so:"

When I look at the Javadoc for the DriverManager class, I do not find an "u=
nload" method.  So what is this documentation referring to?

Thanks

Brett