Loading a method file forces reorg in deployed system

[ConvertFromOldNGs]

by John >> Thu, 6 Apr 2006 23:15:35 GMT

We used to be able to load urgent patches into our production system.

In 6.1.6 it forces reorg when we run jadloadb in multi-user to our deployed system, even loading just .mth files.

We can copy and paste urgent patches and press F8 to compile, but we don't want users to have access to development.

What are other developers doing for their urgent patches?

[ConvertFromOldNGs]

by Torrie >> Fri, 7 Apr 2006 1:46:54 GMT

Still getting to grips with the schema versioning but I think this is to do with the Load Style option in the loader. If this is set to "Latest Schema Version" then the method change will be created in the new version and a reorg will be required to apply those method changes. If you choose "Current Schema Version" then the method change will be applied to the existing version.

Torrie

[ConvertFromOldNGs]

by John >> Sun, 9 Apr 2006 23:01:16 GMT

Bingo!! Load Style "Current Schema Version" does what we want.

[ConvertFromOldNGs]

by dcooper@jade.co.nz >> Mon, 10 Apr 2006 0:32:35 GMT

If you haven't already, have a read of the Schema Evolution and Instantiation White Paper on the web site:

http://www.jadeworld.com/jade/whitepape ... aevolution

It covers versioning, reorgs and load styles in great detail.

Cheers,
Dean.