Apache Derby 10.2.1.6 Release

Use the links below to download a distribution of Apache Derby from the archives. You should always verify the integrity of distribution files downloaded from a mirror.

There are four different distributions:

• bin distribution - contains the documentation, javadoc, and jar files for Derby.
• lib distribution - contains only the jar files for Derby.
• lib-debug distribution - contains jar files for Derby with source line numbers.
• src distribution - contains the Derby source tree at the point which the binaries were built.

db-derby-10.2.1.6-bin.zip [PGP] [MD5]
db-derby-10.2.1.6-bin.tar.gz [PGP] [MD5]

db-derby-10.2.1.6-lib.zip [PGP] [MD5]
db-derby-10.2.1.6-lib.tar.gz [PGP] [MD5]

db-derby-10.2.1.6-lib-debug.zip [PGP] [MD5]
db-derby-10.2.1.6-lib-debug.tar.gz [PGP] [MD5]

db-derby-10.2.1.6-src.zip [PGP] [MD5]
db-derby-10.2.1.6-src.tar.gz [PGP] [MD5]

There are two separate Eclipse plugins for Derby:

• derby_core_plugin - provides the Derby jar files to other plugins in Eclipse.
• derby_ui_plugin - provides an Apache Derby Nature in Eclipse for easy database application development.

derby_core_plugin_10.2.1.452058.zip [PGP] [MD5]
derby_ui_plugin_1.1.0.zip [PGP] [MD5]

Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the Using the 10.2 Core and 1.1 UI Derby plug-ins page.

These notes describe the difference between Derby release 10.2.1.6 and the preceding release 10.1.3.1.

Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs. 10.2.1.6 is a feature release.

The following improvements distinguish 10.2.1.6 from 10.1.3.1:

• Tools
  • The ij sql interpreter now has command-line help and two new commands: show tables and describe.
  • The ij connect statement now works in the J2ME/CDC environment.
  • Tools can now be invoked without specifying a classpath just by typing java -jar derbyrun.jar toolName.
• Security
  • Databases can now be re-encrypted. See DERBY-1156.
  • Secure connections can now be required. See DERBY-928.
  • Support has been added for DRDA userid/password substitution. See DERBY-528.
  • SQL Standard GRANT/REVOKE support has been added for authenticated users. See the "User authorizations" section of the Developer's Guide.
• Administration
  • New scripts have been added in the bin directory which follow Apache conventions. The scripts in the frameworks directory are deprecated and may be removed in future releases.
  • System tables have been added for access to diagnostic information previously available only through non-standard VTIs.
  • Online backup is now available through new system procedures.
  • Various Net Servlet improvements. See DERBY-117.
  • The network server now logs startup/shutdown messages to derby.log.
• JDBC
  • The network driver now supports statement timeouts.
  • Large object streaming has been improved in the network driver.
  • The FOR UPDATE clause is no longer required when declaring an updatable ResultSet.
  • Scrollable, updatable, insensitive ResultSets are now supported.
  • Network client messages have been internationalized. See DERBY-400.
• SQL
  • Expressions are now allowed in the GROUP BY clause.
  • Identity columns can be reset to start at a new value. Please consult documentation on the RESTART WITH clause of ALTER TABLE (found in the Reference Guide).
  • XPath/XQuery support has been improved.
  • New builtin math functions have been added and wired-in as JDBC escape functions. See the "Built-in functions" section of the Reference Guide.
  • Unary +/- are now allowed for ? parameters.
  • Optimizer overrides have been added.
  • Triggers can now call Java procedures.
  • The nullability of a column can be changed now.

For a comprehensive list of changes, consult the lists of new features and bug fixes below.

10.2.1.6 functionality includes:

• Embedded engine with JDBC driver
• Network Server
• Network client JDBC driver
• Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)

SQL support:

• Schemas, tables, temporary tables, views, triggers, indexes, savepoints
• Java procedures and functions
• Standard datatypes including XML, BLOB, and CLOB
• Sub-queries and joins
• Primary key, foreign key, unique and check constraints
• Referential actions
• GRANT/REVOKE support for databases with SQL authorization.

Other features:

• Full ACID transaction support with all four isolation levels
• Row and table level locking
• Configurable authentication including LDAP support
• Import/Export
• On-line backup and recovery support
• Optional on-disk encryption including re-encryption of existing encrypted databases
• Platform independent database format
• Full support for Java 2 Security Manager

JDK/JDBC support:

• JDK 1.3, 1.4, 1.5, and J2ME J2ME/CDC/Foundation Profile
• JSR-169, JDBC 2.1, and JDBC 3.0 support

Derby 10.2.1.6 comes with source code for drivers which conform to a beta version of the JDBC standard, JDBC 4.0. This source code conforms to the following state of the JDBC 4.0 specification:

• The proposed final draft of the JSR 221 spec, dated July 19, 2006.
• Beta build 99 of JDK 6.

Due to license restrictions on the beta builds of JDK 6, Derby 10.2.1.6 does not contain compiled versions of JDBC 4.0 drivers. When run on Java SE 6, Derby 10.2.1.6 exposes the same JDBC 3.0 implementation seen when run on JDK 1.4 and 1.5. You may, however, compile Derby's JDBC 4.0 support yourself. This will let you use JDBC 4.0 features when you run Derby 10.2.1.6 on Java SE 6.

To build this optional JDBC 4.0 support yourself, please download the source distribution and consult BUILDING.txt. You may also follow a simplified set of instructions for building JDBC 4.0 support, which you may find in the "Building the Optional JDBC4 Support" section of the Derby 10.2 wiki page.

If you intend to use any of the Derby XML operators, you must ensure that you have:

• A JAXP parser in your classpath
• Apache Xalan in your classpath

Apache Derby 10.2.1.6 has been tested with Xalan-Java Version 2.7.0. If you have a version of Xalan that is earlier than 2.7, the Derby XML operators may still work. However, it is possible that you will experience unexpected errors when using the Derby XML operators.

These features appear in Derby 10.2.1.6 but not in the preceding release 10.1.3.1.

List the bugs fixed by this release. These are bug fixes which turn up in Derby 10.2.1.6 but not in the preceding 10.1.3.1 release.

Please be aware of the following issues:

DERBY-253

Problem

PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream() throw SQLException when invoked after upgrading to Apache Derby 10.2.

Symptoms

Calling either of these methods will result in an exception with SQLSTATE 0A000 and message: "Feature not implemented: ..."

Cause

PreparedStatement.setUnicodeStream() and ResultSet.getUnicodeStream() have been deprecated since JDBC 2.0. Derby's implemetation of these methods was broken, and it was decided that the methods should throw a not-implemented exception instead of being fixed.

Solution

This was an intentional change. No Derby product solution is offered.

Workaround

Use setCharacterStream() and getCharacterStream() instead of setUnicodeStream() and getUnicodeStream().

DERBY-668

Problem

Sysinfo classpath information was insufficiently detailed.

Symptoms

Sometimes it was hard to tell where the Derby classes were actually being loaded from in the JVM.

Cause

The algorithm that sysinfo used for analyzing and reporting on the application classpath was not robust.

Solution

The sysinfo tool now prints additional information about the origin of the classes and jars that it examines. The origin of a class might be: an entry in the application classpath, an entry in a class loader location list, a jar fetched due to being listed in the manifest entry of another jar, a standard extension in the JRE's extensions directory, a jar installed into the application server, or any of various other possibilities.

Workaround

No workaround. The behavior is now correct.

DERBY-721

Problem

Undefined results were returned to an application which opend an InputStream twice on the same column of a ResultSet.

Symptoms

The value siphoned out of the column was erratic.

Cause

Streams were being shared between the two readers.

Solution

Now we throw an exception if the application tries to open two streams on the same column in a ResultSet.

Workaround

Users must recode Applications which open multiple streams on the same column.

DERBY-781

Problem

When optimizing a query that has one or more non-flattenable subqueries in the FROM clause, Derby will now check to see if it is possible to perform a hash join with that subquery as the inner table. Prior to Derby 10.2, the optimizer would never consider a hash join with a subquery; it only did nested loop joins.

Symptoms

Execution performance of queries containing non-flattenable subqueries may change. The expectation is that the new (10.2) query plans will show improved performance over the old ones.

Another potential symptom is that the compilation time for such queries may increase. If this happens, the increase should only occur at compilation time; execution time should either improve or, at the very least, remain the same as in earlier versions of Derby.

Cause

If the optimizer chooses to do a hash join with a subquery, Derby only has to execute the subquery a single time per statement, after which Derby can just perform the desired join against the materialized result set. Depending on how many rows are in the outer table of the join, this once-per-statement execution of the subquery can lead to major performance improvements over the once-per-outer-row execution employed by earlier versions of Derby.

As for the extra compilation time, this is due to the simple fact that the optimizer is now doing more work--i.e. in addition to considering nested loop joins with subqueries, it is now _also_ considering hash joins with those subqueries, and that means that it could potentially take longer for the optimizer to finish its work. Note again that, if it occurs, the increased time should only occur at compilation time; execution time should either improve or, at the very least, remain the same as in earlier versions of Derby.

Solution

This was an intentional change to improve the execution plans chosen by the optimizer for queries having large and/or complex subqueries. The expectation is that the new behavior--and the subsequent query plans--will lead to improved performance over the old ones, so no further solution is required.

Workaround

There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.

That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer enhancement, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

DERBY-822

Problem

Queries may fail earlier and locks may be acquired earlier when executing queries. Location where errors occur in an embedded environment is different from the location where errors occur in a network environment.

Symptoms

Errors that happen as part of the normal execution path are moved earlier. For example, code to execute a query, with executeQuery() retrieve the result set metadata and then perform a next() might fail with a lock timeout on executeQuery() instead of next(). Locking changes are observed.

Cause

Pre-fetching moves execution of retrieval of data earlier for network client/server configurations.

Solution

This was an intentional behavior change to improve performance. No Derby product solution is offered.

Workaround

Application code needs to be changed to adjust error handling if needed.

DERBY-1130

Problem

Derby's client DataSources were using a wrong database name when getting a connection in the following case:

• databaseName is not set as a Derby DataSource property
• databaseName is set as a connection attribute using setConnectionAttributes method

Symptoms

Instead of throwing an exception saying databaseName is a required Derby DataSource property and must be set, client driver was using "null" as database name and returning a connection to database named "null".

Cause

The database name was constructed wrongly in the client driver.

Solution

This was solved by setting the internal database name property in the client driver correctly. Also ensured that databaseName set as a connection attribute will not be used by Derby's client DataSources.. This fix will be available in Derby versions 10.2 and above.

Workaround

If using release prior to version 10.2, make sure database name is set only as a DataSource property when using Derby's client DataSources.

DERBY-1295

Problem

Result sets of type TYPE_SCROLL_INSENSITIVE used to implicitly close when positioned at the end in autocommit mode.

Symptoms

Calling the ResultSet.next() method when positioned on the last row of a result set of type SCROLL_INSENSITIVE in auto commit mode used to cause the result set to be closed.

Cause

The JDBC specification allows a JDBC driver to implicitly close a ResultSet when the ResultSet type is TYPE_FORWARD_ONLY and the next method of ResultSet returns false. Derby also used to implicitly close result sets of type SCROLL_INSENSITIVE when the ResultSet.next() method returns false in auto commit mode.

Solution

The behavior of SCROLL_INSENSITIVE result sets in auto commit mode has been changed to comply with the JDBC4 specification. SCROLL_INSENSITIVE result sets are not implicitly closed when calling the ResultSet.next() method in auto commit mode while positioned on the last row.

Workaround

Fix applications which rely on the previous, non-standard behavior.

DERBY-1314

Problem

The behaviour of executeQuery() and executeUpdate() did not match the JDBC specification when invoking stored procedures.

Symptoms

• When invoking a stored procedure with executeQuery() or executeUpdate(), an exception was thrown indicating that the procedure did not return the correct number of ResultSet objects, although the correct number of ResultSet objects was in fact returned.
• When invoking a stored procedure with executeQuery() or executeUpdate(), and the procedure did not return the correct number of ResultSet objects, the query executed successfully.
• With the network client driver, when invoking a stored procedure with executeUpdate(), the return value was -1, whereas the JDBC specification says it should be 0.

Cause

The methods executeQuery() and executeUpdate() were not implemented in compliance with the JDBC specification.

Solution

In Derby 10.2, the behaviour of the methods executeQuery() and executeUpdate() has been changed to match the JDBC specification.

Workaround

Use execute() instead of executeUpdate()/executeQuery() to invoke a stored procedure which does not return exactly 0 or 1 ResultSet objects.

DERBY-1323

Problem

For a JDBC ResultSet with type TYPE_FORWARD_ONLY, the methods rowUpdated, rowDeleted and rowInserted could previously be called while not on a row, i.e. before positioning in the result set, while on insertRow, after updateRow before new positioning, after deleteRow before new positioning and when after last row. This is now disallowed.

Symptoms

Calls to any of these methods while not on a row will now throw SQLException with SQLState 24000.

Cause

Derby now disallows these calls when not on a row.

Solution

Change the application to not call these methods unless on a row. Note that using them at all is rather meaningless for a ResultSet of type TYPE_FORWARD_ONLY since the returned result will always be 'false'. This is because once you modify a row, it can no longer be accessed, you need to move to the next row, if there is one, to get a new current row. Presently in Derby, these methods are only really meaningfully used for result sets of type TYPE_SCROLL_INSENSITIVE and of concurrency CONCUR_UPDATABLE in which case updated and deleted rows can be detected.

Workaround

Fix applications which rely on this non-standard behavior.

DERBY-1357

Problem

The optimizer will now abandon sub-optimal join orders as soon as it realizes that they cost more than the best join order so far.

This fix also ensures that, in the case of short-circuited join orders, Derby will still generate (and execute) an overall plan that matches the "best path" decisions made by the optimizer--which was not always the case prior to these changes.

Symptoms

Execution performance of large queries (esp. those with nested subqueries and/or with large FROM clauses) may change. The expectation is that the new (10.2) query plans will show improved performance over the old ones.

Cause

Since the optimizer is now spending less time evaluating sub-optimal join orders, it is possible that it will be able to try out more join orders before optimizer "timeout" occurs. As a result the optimizer can sometimes find better plans than it did in earlier versions of Derby.

Solution

This was an intentional change to fix behavior that was not working correctly in earlier versions of Derby. The expectation is that the new behavior--and the subsequent query plans--will lead to improved performance over the old ones, so no further solution is required.

Workaround

There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.

That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer change, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

DERBY-1384

Problem

Default BLOB/CLOB length should be the maximum length supported by Derby (2G-1)

Symptoms

An application that used BLOB will current reject values greater than 1M, changing the default means the application will now silently accept those values.

Cause

The allowable size of Derby LOBs has been increased.

Solution

This was an intentional change to make Derby conform to its own documentation.

Workaround

Fix applications which rely on Derby rejecting LOBs that are bigger than 1M.

DERBY-1621

Problem

Trigger action statement is not recompile when there is a change that would affect it.

Symptoms

(1) Trigger action such as an INSERT statement does not get recompiled when the underlying table is affected by a CREATE or DROP INDEX statement. e.g.:

         create table t (i int);
         create table t2 (i int);
         create trigger tt after insert on t for each statement mode db2sql insert into t2 values 1;
         insert into t values 1;
         select * from t2;
         create unique index tu on t2(i);
         insert into t values 1;
         select * from t2;
         insert into t values 1;
         1 row inserted/updated/deleted

The above example creates an unique index on table t2. when the trigger is fired, it did not raise an unique constraint error.

(2) When the trigger action statement underlying view gets dropped, the trigger statement did not get recompiled. e.g.:

         create table t11 (c111 int not null primary key, c112 int);
         insert into t11 values(1,1);
         insert into t11 values(2,2);
         create view v21 as select * from user1.t11;
         create table t31 (c311 int);
         create table t32 (c321 int);
         create trigger tr31t31 after insert on t31 for each statement mode db2sql insert into t32 values (select c111 from user1.v21 where c112=1);
         insert into t31 values(1);
         select * from t31;
         select * from t32;
         drop view v21;
         insert into t31 values(1);

In the above example, a view which the trigger action references is dropped; however, the last SQL INSERT statement did not throw an error.

(3) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger. The trigger action is not being recompiled and raises SQLSTATE XSAI2 even though the table being dropped was recreated again. e.g.:

         create table t1 (id int, name varchar(20));
         create table t2 (id int);
         create trigger test_trigger after insert on t2 for each row mode db2sql insert into t1 values(100, 'hundred');
         insert into t2 values(1);
         insert into t2 values(1);
         select * from t1;
         drop table t1;
         insert into t2 values(1);
         create table t1 (id int, name varchar(20));
         insert into t2 values(1);

In the above example, a table which the trigger action references is dropped. The last INSERT statement should execute successfully but it raises SQLSTATE XSAI2: The conglomerate (896) requested does not exist.

Cause

Derby did not perform invalidation of the trigger action when object(s) that the trigger references are modified or dropped; hence, resulting in the stated problem above. The affected versions are Derby 10.0 and 10.1.

Solution

A fix to resolve the above Derby symptoms is available in 10.2.

Workaround

None.

DERBY-1652

Problem

In some cases, an after update trigger does not get fired upon itself when its trigger action contains an update statement on the trigger's subject table.

Symptoms

(1) When defining a trigger for the first time for a table, e.g.:

  
        CREATE TABLE "TEST" ("TESTID" INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1),
                             "INFO" INTEGER NOT NULL,
                             "TIMESTAMP" TIMESTAMP NOT NULL DEFAULT '1980-01-01-00.00.00.000000');
    
        CREATE TRIGGER UPDATE_TEST
        AFTER UPDATE ON TEST
        REFERENCING OLD AS OLD
        FOR EACH ROW MODE DB2SQL
            UPDATE TEST SET TIMESTAMP = CURRENT_TIMESTAMP WHERE TESTID = OLD.TESTID;
  
        INSERT INTO TEST (INFO) VALUES (1), (2), (3);

        UPDATE TEST SET INFO = 1 WHERE TESTID = 2;

The above update statement executes successfully which it is incorrect. The system should have issued SQLSTATE 54038 since it self-triggers to its maximum depth of 16.

(2) With the above example, when an user upgrades to a higher version and issues the same update statement:

        UPDATE TEST SET INFO = 1 WHERE TESTID = 2;
        ERROR 54038: Maximum depth of nested triggers was exceeded.

The SQLSTATE 54038 is issued in this case because after database upgrade, the trigger action will be invalidated by the system and will force a recompilation of the trigger when it is fired. The system generates the correct execution plan this time and since the trigger behavior have changed, this might cause applications to break unexpectedly.

Cause

Derby's did not generate the correct execution plan for self-trigger invocation when such a trigger is declared for the first time on the subject table; hence, resulting in the stated problem above. The affected version is Derby 10.0 and 10.1.

Solution

A fix to resolve the above Derby symptom is available in 10.1 and 10.2. thrown now.

Workaround

If self-trigger invocation was not intended by the application, the application can select which column(s) on the update statement can cause the trigger to fire in the CREATE TRIGGER statement. i.e.:

   CREATE TRIGGER update_test
   AFTER UPDATE OF INFO ON test
   REFERENCING OLD AS old
   FOR EACH ROW MODE DB2SQL
       UPDATE test SET timestamp=current_timestamp WHERE testid=old.testid;

In the above statement, the trigger will only fire when an update is made to the "info" column instead of any column(s).

DERBY-1867

Problem

With IBM 1.4.1 JVM, trying to connect to the server using the derby client with security mechanism 8 (USRSSSBPWD) will result in error.

Symptoms

Connecting using the client driver with security mechanism 8 will throw the following error ERROR XJ112: Security exception encountered, see next exception for details. The stack trace will show that the problem is caused by java.security.NoSuchAlgorithmException: SHA1PRNG SecureRandom not available

Cause

Current USRSSBPWD implementation uses SHA1PRNG algorithm to generate random number(seed) that gets exchanged between client and the server. The SHA1PRNG algorithm is not available with the JCE provider that comes with IBM JVM version 1.4.1.

Solution

You must use another JCE provider.

Workaround

If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM. For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.

Derby release 10.2.1.6 was built using the following environment:

• Branch - Source code came from the 10.2 branch.
• Machine - Cygwin on Microsoft Windows XP Professional Version 2002 Service Pack 2.
• Ant - Apache Ant version 1.6.5 compiled on June 2 2005.
• JDK 1.4 - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03).
• JDK 1.3 - Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_16-b06).
• JDK 1.6 - The optional JDBC4 drivers were not compiled.
• OSGi - The osgi.jar was used to build org.apache.derby.osgi.EmbeddedActivator.
• Compiler - The 1.4.2_08-b03 javac was used to compile all classes.
• JSR 169 - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).

Tests were run on the following platforms. Results are listed separately for each platform.

Several test issues were reported, such as DERBY-937(1.5), DERBY-1221(1.5), DERBY-734(1.6), DERBY-1585(1.6), DERBY-1629(1.6), DERBY-1883(1.4), but no specific code issues were noted.

Tests for a specific platform can be run using the derbyTesting.jar file that can be found in the lib directory of the -lib or -bin distributions.

Instructions on how to run the tests can be found in the testing README.

It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.

The PGP signatures can be verified using PGP or GPG. First download the Apache Derby KEYS as well as the asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...

% pgpk -a KEYS
% pgpv db-derby-X.Y.tar.gz.asc

or

% pgp -ka KEYS
% pgp db-derby-X.Y.tar.gz.asc

or

% gpg --import KEYS
% gpg --verify db-derby-X.Y.tar.gz.asc

To verify the MD5 signature on the files, you need to use a program called md5 or md5sum, which is included in many unix distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from here, here, or here.

We strongly recommend you verify your downloads with both PGP and MD5.