Why Must I Set File Sizes?

Note: Lawson recommends using locally-managed tablespace and automatic extent management features. If you are using these features, you do not need to set files sizes in dbdef as described in this section.

With Lawson data stored in Oracle, you must specify the expected initial size of files and the incremental amount by which to enlarge the files if they exceed the initial allotted space. These sizes are specified as numbers of records. The database driver (oradb11 / oradb12) translates these sizes into INITIAL and NEXT extent sizes specified in the CREATE TABLE statements issued to Oracle when the tables are built. Your file sizes are set using the Lawson File Size Definition form.

Because performance can be negatively affected by the presence of many extents for tables and indexes, set the initial amount large enough to hold all of your existing data plus at least one year's worth of additional data.

A reasonable setting for the incremental file size would be between ten and twenty percent of the initial amount. The incremental amount should be large enough to hold any overflow data, but not so large that space is wasted when an additional extent is required.