You can easily identify tables not enabled for multi-tenancy in a database connection. The tables appear in a list, and you can select one or more of the tables that you want to enable.

To select a table for enabling as multi-tenant:

  1. Select Database Administration > Configure > Enable Multi-tenancy for Tables in the management console menu.
    The Enable Multi-tenancy for Tables page appears
  2. In the Database connection field, enter a database connection name.
    By default, the last used database connection name appears in the Database connection field.
    Note: If you type the name of the database connection, follow the format used by OpenEdge Management to define a connection: AdminServer-name.database-name. A database server must be running for you to connect to the database.

    You can also click the Search icon to choose a database for which you are creating the tenant from the Connection Selection dialog.

    The Connection Selection dialog displays the connections details in a grid. You can perform the following:

    • Filter the connections in the grid by Connection name.

      You can also select the drop down arrow beside the Search icon to filter the connections by AdminServer, or Category.

    • Select the column heading and click the drop-down to choose the order (ascending or descending alphabetically) for the connections to appear in the grid.
  3. From the list of tables, select one or more tables, or click the Select All check box to select all the tables listed in the page.
  4. Click Preview to make partition allocation decisions, by tenant, for the tables now enabled for multi-tenancy. The schema selection page appears.
  5. Select a tenant in the Tenants list. (Note that only regular tenants are listed.)
  6. Expand the PUB node under Schema Selections, and expand the table you have enabled for multi-tenancy to view its schema.

    Note that the schema shown in the area panels includes the full schema for the database, not just the schema for the newly enabled tables.

  7. Select a table whose area or allocation state you are able to modify, and make the changes to the tenant partition area or the allocation state in the Properties pane. If space for a partition has already been allocated, you cannot make changes.
  8. Click Commit to save the changes. The Confirm commit enabling multi-tenancy dialog appears.
  9. Choose from the following options:
    • To commit the changes, click Commit.
    • To cancel the changes, click Cancel.
    • To force allocation of new partitions that otherwise would not be allocated, select that option. This allows you to force allocation of partitions that otherwise would not be allocated when the changes are saved. This option overrides a tenant's default allocation for new partitions, but any changes applied to individual partitions will also be allocated if you select this option.

      If you select this option, you have an additional choice to make between the following two selections:

      • Force allocation of all partitions with an allocation state of Delayed — Forces allocation of partitions whosedefault allocation setting is to delay.
      • Force allocation of all partitions with an allocation state of Delayed or None — Forces allocation of all partitions whose default allocation setting is to either delay or not allocate space at all.

      For example, if a tenant has an object allocation default of no allocation (None) and a partition for the tenant is changed to delay allocation (Delayed), this partition will be allocated if Force allocation is specified. If a tenant has its default allocation set to delay and a partition is changed to no allocation, the partition will be allocated only if Force allocation is selected.

Note that it may take some time to commit the changes to the database. The length of time may vary, depending on the complexity of the changes (the number of tables converted to multi-tenancy, for example) as well as the number of existing tenants in the database.

The dashboard appears and displays a viewlet that allows you to monitor the status of the task. For more information, see Monitor data definition file updates to the database.