Maximum Number of Objects Attribute

About Maximum Number of Objects Attribute

The Maximum Number of Objects attribute(s_cls_max_objects) plays an important role. When a new class is created, CES uses the information to determine the size of the class in terms of database storage requirement. This attribute defines how many objects a class should have now and in the future.

For example, a class called PARTS is now created and it has five million parts in the future. You have to report the total number of parts that a class will have in its lifetime in this attribute. Also, when an index is built, CES uses this attribute and calculates the index size requirements. If this attribute is set to a small value, then it leads to table data fragmentation and index fragmentation. You can find out how poorly the Max. Number of Objects attribute has been maintained in this database:

  • SELECT s_cls_max_objects, COUNT(*)

  • FROM s_cls_table

  • GROUP BY s_cls_max_objects;

The Maximum Number of Objects attribute for each class should show generally bigger number than the actual object count of the class. As the indexes need to be built many times, it is very important that the attribute must have right value. To set the value correctly, you have to set the Maximum Number of Objects attribute for all bottom classes to appropriately accommodate class growth. Once this is done, run the option Rollup Maximum Number of Objects, for additional information, see Rollup Maximum Number of Objects.

This utility rolls up the Maximum Number of Objects values from the bottom classes up to the CES Root class. As the database changes when more data are loaded and existing data are removed, it is important to maintain the Maximum Number of Objects attribute in all of your classes, so that index builds will correctly size the storage parameters when you generate and create indexes using Index Management options in CES.