Infor Technology Blog

« | Main | »

Lowering Total Cost of Ownership (TCO) – DBReorg

November 15, 2012

By Delmar Dehn

Infor is hard at work on development projects to lower the Infor Lawson applications and Infor Lawson technology’s Total Cost of Ownership (TCO). These development projects are focused on two primary areas;

1) Platform Migration Tooling
2) Lifecycle Maintenance

I am pleased to introduce the first in a series of postings that will discuss these development projects as well as existing capabilities that you may not be aware of. The objective of the series is to alert you to how you can take advantage of the new and existing capabilities and lower your Infor Lawson Total Cost of Ownership. The new capabilities will not require additional license fees or licensing and will operate with Infor Lawson System Foundation 9.0.1 and Infor Lawson System Foundation 10. Some of the new capabilities will be generally available to customers starting in November 2012 and others will follow in subsequent releases. Experts from across Infor will be contributing to this series. The first contributor is Daniel Julson, System Development Manager. Daniel’s development team builds the Infor Lawson technology stack’s database infrastructure.

By Daniel Julson, System Development Manager

Database Reorganization, or DBReorg, is the utility used to update database table definitions, usually happening during application or technology upgrades.  The Infor S3 Technology version of DBReorg contains several different options to assist in running the reorg.  This post will feature the ‘-F’ (fast mode) option and provide background on what it does.

Default and Classic processing of DBReorg dump data to disk for each file going through reorganization prior to dealing with the database table itself.  With larger data sets, the dumping of data to disk can be costly, thus, we’ve added the -F, or fast mode, option.  This option will skip dumping the data and try to alter the table instead.  If the alter succeeds, the reorg is finished for that table.


Using the -F option can save time, however, one needs to practice extra caution with their data.  Prior to running any dbreorg, a full cold backup is an absolute must.  It is more crucial with using the -F option due to the nature of the data dump not happening prior to altering the table.  Situations could arise where a dbreorg fails within the middle of an alter statement for reasons beyond anyone’s control.  The only recovery in this situation is to revert to backup and run the dbreorg again.


Leave a Reply

Your email address will not be published.