Converting to Split LOB Storage

The use of split LOB storage can dramatically improve upgrade processing performance by eliminating the need to copy LOB data. It is the default configuration for a new installation of Landmark 10.0.x or greater. However, if you upgraded to Landmark 10.0.x rather than doing a new installation, your system may not use split LOB storage. If you want to convert a data area or tables within a data area to use split LOB storage, you can use the dbsplitlobs utility as described in the following procedure.

This procedure assumes that the only changes being made involve moving one or more business classes to split LOB storage. If there are any other types of pending database changes, you will need to process them separately after you have finished the conversion to split LOB storage.

To convert to split LOB storage

  1. Determine if there are any issues with the current database configuration. At the Landmark command line, type

    dbverify dataarea

    If the output from dbverify indicates that there are issues, resolve those issues before proceeding. (Note that discrepancies with business classes that implement S3ClassicTable, M3ClassicTable, or ForeignTable can be ignored in this case.)

  2. Configure the data area to use split LOB storage. At the Landmark command line, type

    Run changeda -d splitlobstorage=yes dataarea

    If you would like to configure split LOB storage for a specific business class, run changeda -f splitlobstorage=yes dataarea businessclass instead of the changeda -d command shown above. You may want to convert business classes that have large amounts of data as a separate process in order to ensure that the system can be returned to production use in a timely manner or to minimize the amount of free space required in the database.

  3. Rebuild the product line to capture the configuration change. At the Landmark command line, type

    buildda dataarea

  4. Run dbsplitlobs to make the database changes. At the Landmark command line, type

    dbsplitlobs dataarea

    Note that dbsplitlobs can be interrupted and restarted, but must be run to completion before the Landmark environment can be returned to full use.

    Note: 

    While dbsplitlobs is executing, the database must have enough free space to hold a copy of all the non-LOB data of all the business classes being converted. When dbsplitlobs is complete, the overwhelming majority of that extra space will be free space once again.

  5. Verify the new database configuration. At the Landmark command line, type

    dbverify dataarea

For the full syntax of the dbsplitlobs utility, see the Infor Landmark Utilities Reference Guide.