Did this article resolve your question/issue?



How to use the tablemove command.

« Go Back


TitleHow to use the tablemove command.
URL NameP8179
Article Number000148922
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: RDBMS
Question/Problem Description
How to use the tablemove command?
How to move tables out of the schema area?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Use the PROUTIL TABLEMOVE utility to move a table and its associated indexes from one storage area to another.  This command can be run while the database is online or offline but considering running it online specially for large tables. For further information refer to Articles:
TABLEMOVE can exclusively move only tables to another storage area, leaving indexes in the existing area, or move indexes at the same time to the same or a different storage area which is more efficient.  Whether indexes are moved with the table record content or not, related indexes are always rebuilt as part of the operation.

For example:

To only move a table:
proutil dbname -C tablemove [owner-name] table table-area

proutil sports2000 -C tablemove benefits misc

To move indexes at the same time to the same area as the table or to a different area from the current one, add the name of the area where to store the indexes.
proutil dbname -C tablemove [owner-name] table table-area [index-area]

proutil sports2000 -C tablemove customer "customer area" "index area"
Table Names and Area Names that contain spaces must be enclosed in double quotes.

In the current product implementation, PROUTIL database features exist to move table and/or move index database objects, but not LOB (CLOB/BLOB) database objects.  For example, when the table and related indexes are moved to another Storage Area with PROUTIL -C TABLEMOVE, the related LOBs are left in their existing Storage Area.  Prior to OpenEdge 11.6 there are no information in DBANALYS reports for lobs, which leads to the existence of these objects being forgotten in database re-organisation projects. For further advice refer to Articles:
References to Written Documentation:

OpenEdge Data Management: Database Administration, 
  • Maintaining Database Structure, Maintaining indexes and tables
  • Transparent Data Encryption, Moving Tables and Indexes

Last Modified Date11/20/2020 7:05 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.