Error: "object_name will not be reorganized because it has a LONG column of unknown length, and F (4267149)

Error: "object_name will not be reorganized because it has a LONG column of unknown length, and FastCopy was not (or cannot be) selected for this object."

Find Long LONGs table needs to be populated before you begin using Reorg Manager and Reorg Xpert. Both reorg tools check this table for the size of LONG and LONG RAW columns. If reorg tools don't know the size of LONG columns, they exclude it from reorg

To keep the Find Long LONGs table up to date with the latest sizes of LONG columns, you should re-populate it from time to time. You should also re-populate it after you create tables with LONG columns.

A look at the Find Long LONGs procedure:

The Find Long LONGs table is populated with the Find Long LONGs Execute procedure. This is shown below:

begin

quest_spc_find_long.execute (schema=>'SCHEMA', include_sys=>'NO', tablename=>'TABLENAME');

end;

/

The Find Long LONGs procedure can scan an entire database, a certain schema, or a certain table. You specify what to scan using the parameters described below. When no parameters are used, the procedure scans the entire database (with the exception of SYS and SYSTEM objects):

- schema -> Use this parameter if you want to scan a certain schema.
- include_sys - [yes | no] -> Set this parameter to yes if you want to scan SYS and SYSTEM objects. If you do not want to scan these objects, omit the parameter or set it to no.
- tablename -> Use this parameter if you want to scan a table with a certain name. To scan all tables with a certain name, use the tablename parameter on its own, without the schema parameter. To scan a certain table in a certain schema, use the schema parameter along with the tablename parameter.

NOTE:

When Reorg Manager excludes a table with a LONG from a SQL-only reorg, you can include it by selecting FastCopy as the data movement method for that table.
Â

Â