Long object names

Some Db2 objects can have names containing up to 128 characters.

Because RACF profile names are limited to 246 characters, the RACF access control module might truncate portions of the profile names when you use long object names.

Start of changeThe schema name, collection ID, or table qualifier portion of a RACF profile name might be truncated to 100 characters. The collection ID portion can be truncated for packages, and the schema name and qualifier portions can be truncated for the following objects:End of change

  • Global variables
  • Java™ archive (JAR) objects
  • Schemas
  • Sequences
  • Stored procedures
  • Tables
  • User-defined types
  • User-defined functions
  • Views

Start of changeFor example, consider the RACF profile name for the USAGE privilege on a JAR object: End of change

db2-subsystem.schema-name.JAR-name.USAGE

The schema name and JAR name can each contain a maximum of 128 characters. If the Db2 subsystem name is four characters, the length of the profile name would reach 268 characters and exceed the maximum name length unless the RACF access control module truncates the schema name to 100 characters.

Variables for INSERT, UPDATE, and DELETE operations on views are also truncated to specific lengths. The table-qualifier and the view-qualifier are truncated at 32 characters each, and the table-name and the view-name are truncated at 64 characters each. For example, consider the RACF profile name for the INSERT privilege on a view.

db2-subsystem.table-qualifier.table-name.view-qualifier.view-name.INSERT

Similarly, variables for UPDATE and REFERENCES operations on tables are also truncated to specific lengths. The table-qualifier and the table-name are each truncated at 100 characters, and the column-name is truncated at 30 characters. For example, consider the RACF profile name for the UPDATE privilege on a table. 

db2-subsystem.table-qualifier.table-name.column-name.UPDATE

When you use long object names, truncation can cause unintended results when you also use discrete RACF profiles. If truncation occurs, a single discrete profile might inadvertently protect multiple similarly named resources when the first 100 characters of the schema names are the identical and the qualified object names, such as JAR name, subsystem name, and privilege name, are also identical.