db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-1107) For existing databases JDBC metadata queries do not get updated properly between maintenance versions.
Date Mon, 03 Apr 2006 20:26:23 GMT
Satheesh Bandaram wrote:

>>My issue is that, as of mid-March, metadata changes have been blocked
>>pending resolution of two issues:
>>
>>1) Agreement on our upgrade policy vis-a-vis metadata.
>>    
>>
I am a bit fuzzy on this still after  I reread the thread for DERBY-1107
a few times.  I was wondering if someone could summarize?   Has an
upgrade strategy been defined for metadata?  Could someone who
understands it put it on the Wiki?

>>2) Fixing the upgrade tests.
>>    
>>
I think on this one,  we just need to get the DERBY-1076 patch
committed. I think that Deepa is working to get  upgrade tests   into
derbyall so we don't have to .worry so much about regressions in this area.


>>    
>>
>It is my personal feeling
>that this "blockage" of metadata work should be lifted. 
>  
>
I think that the fact that we still don't yet have upgrade tests in 
derbyall should make metadata checkins code YELLOW.
I think folks making metadata changes should make sure the ugprade tests
pass and masters are updated.

The blockage was based on the fact that we once had an irreconcilable
downgrade bug and seemed to be set up for that again.    Where an
incompatible change was made to the metadata  statements  and that could
not be fixed.  I hope folks interested in modifying metadata will
continue to  make progress on  the metadata upgrade strategy  and get
DERBY-1107 resolved in 10.1 and trunk to avoid a similar unfortunate
situation.

Here is the  information from the release notes regarding that bug
provide context:

If you revert to a previous version of Cloudscape Version 5.1 (Versions
5.1.2 through 5.1.59) after upgrading and connecting to a database using
Cloudscape Version 5.1.60, you will receive errors when you first
connect and when you run the ALTER STATEMENT RECOMPILE ALL command.

Example error when connecting to a database after reverting:

ERROR XCW01: Database upgrade succeeded. The upgraded database is now
ready for
use. Revalidating stored prepared statements failed. See next exception
for details of failure.
Correct problem and recompile before executing the prepared statement. 
See "ALTER STATEMENT RECOMPILE".
ERROR 42X75: No constructor was found with the signature
com.ibm.db2j.drda.SQLGe
tUDTsVTI(java.sql.Connection, UNTYPED, UNTYPED, UNTYPED, UNTYPED, UNTYPED).
It may be that the parameter types are not method invocation convertible.

Example error when running ALTER STATEMENT RECOMPILE ALL after reverting:

ERROR 42X75: No constructor was found with the signature
com.ibm.db2j.drda.SQLGe
tUDTsVTI(java.sql.Connection, UNTYPED, UNTYPED, UNTYPED, UNTYPED, UNTYPED).
It may be that the parameter types are not method invocation convertible.

To correct this problem, drop the SYSIBM schema using the dropSYSIBM.bat
(Window OS) or dropSYSIBM.ksh (Unix OS) command file found in the
Cloudscape Version 5.1.60 install directories. If you are not running
Network Server, execute the SQL statements in the dropSYSIBM.sql file
rather than using the dropSYSIBM scripts.



Mime
View raw message