Moving tables and indexes within an encryption-enabled database can cause data to become encrypted or unencrypted. The syntaxes of PROUTIL INDEXMOVE and PROUTIL TABLEMOVE remain unchanged. The table below describes the results of moving objects (tables or indexes) in an encryption-enabled database.

Table 1. Encryption impact of moving tables and indexes
If you are moving... To... Then...
A table or index from an unencrypted Type I area An unencrypted Type I area
  • Execution of this operation is open
  • No change in encryption policy
  • Object remains unencrypted
An encrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • No change in encryption policy (the policy for the destination area is applied to the object)
  • Object is encrypted in the destination area
A Type II area
  • Execution of this operation is open
  • No change in encryption policy
  • Object remains unencrypted
A table or index from an encrypted Type I area An unencrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • No change in encryption policy (the source policy is for the entire area)
  • Object is unencrypted in the destination area
  • User is prompted to confirm the move and the resulting decryption of the object
An encrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • No change in encryption policy (the source and target policies are for the entire area)
  • Object is encrypted in the destination area with encryption policy of the destination area
A Type II area
  • Execution of this operation is restricted to an authenticated DBA
  • A new encryption policy is created for the object (with the same cipher as the source area policy)
  • Object is encrypted in the destination area
An unencrypted table or index from a Type II area An unencrypted Type I area
  • Execution of this operation is open
  • No change in encryption policy
  • Object remains unencrypted
An encrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • No change in encryption policy (the area policy of the destination area is used)
  • Object is encrypted in the destination area with encryption policy of the destination area
A Type II area
  • Execution of this operation is open
  • No change in encryption policy
  • Object remains unencrypted
An encrypted table or index from a Type II area An unencrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • The encryption policy on the object is removed
  • Object is unencrypted in the destination area
  • User is prompted to confirm the move and the decryption of the object
An encrypted Type I area
  • Execution of this operation is restricted to an authenticated DBA
  • The encryption policy on the object is removed (and the encryption policy of the destination area is applied)
  • Object is encrypted with the policy of the destination area
A Type II area
  • Execution of this operation is restricted to an authenticated DBA
  • No change in encryption policy (the object policy remains in use)
  • Object remains encrypted