Mike Matrigali <[EMAIL PROTECTED]> writes:
> I didn't realize there were errors, the collation stuff is new to
> 10.3. I haven't updated the upgrade tets in the past so not
> sure what is going on.
>
> Does anyone know how to tell what is going on when this failure
> occurs, ie. what software is running against what version of
> the database?
The stack trace indicates the error occurs in testTriggerInternalVTI
from Changes10_2.java which has this comment:
/**
* Triger (internal) VTI
* 10.2 - Check that a statement trigger created in 10.0
* or 10.1 can be executed in 10.2 and that a statement
* trigger created in soft upgrade in 10.2 can be used
* in older releases.
*
* The VTI implementing statement triggers changed in
* 10.2 from implementations of ResultSet to implementations
* of PreparedStatement. See DERBY-438. The internal
* api for the re-written action statement remains the
* same. The re-compile of the trigger on version changes
* should automatically switch between the two implementations.
*
The line number 121, seems to indicate it is in PH_SOFT_UPGRADE phase.
I had versions 10.2.2.0, 10.2.1.6 and 10.1.3.1 available in my path.
upgradeTests/_Suite.java tries to find these 5 old versions:
private static final int[][] OLD_VERSIONS =
{
{10, 0, 2, 1}, // 10.0.2.1 (incubator release)
{10, 1, 1, 0}, // 10.1.1.0 (Aug 3, 2005 / SVN 208786)
{10, 1, 2, 1}, // 10.1.2.1 (Nov 18, 2005 / SVN 330608)
{10, 1, 3, 1}, // 10.1.3.1 (Jun 30, 2006 / SVN 417277)
{10, 2, 1, 6}, // 10.2.1.6 (Oct 02, 2006 / SVN 452058)
{10, 2, 2, 0}, // 10.2.2.0 (Dec 12, 2006 / SVN 485682)
};
So I would presume this error happens when doing a soft upgrade to
trunk from a database created with 10.1.3.1 (since Changes10_2.java
are also run for 10.3, i.e. trunk, cf. UpgradeRun#baseSuite logic).
I don't know this test very well either, so caveats apply..
Hope this helps.
Dag
