When you choose full DBSPACE reorganization, Control Center generates and submits a job to:
In order to retain hierarchical dependencies, Control Center issues all grants in the same chronological order in which they were originally issued.
In order to grant authority to an object, the grantor must first connect as the user who originally issued the grant. Therefore, the program must gather database connect passwords for all grantors. If a grantor does not have a connect password, a temporary password is assigned and later removed.
The database server does not remove grant information from the system catalogs when a user is removed from the SYSTEM.SYSUSERAUTH table. Consequently, the REORG job may need to connect as a nonexistent user in order to re-establish a grant. If this situation occurs, Control Center temporarily grants connect authority to the user and later revokes it.
Operational Note: | In some cases (such as a reload failure), temporarily granted IDs will not be revoked from the database. You should revoke these IDs at some point in time. The IDs are identified by the starting letters REOnnnnn (where nnnnn is a random number). |