Feedback
Did this article resolve your question/issue?

   

Article

How to speed up the tablemove process?

« Go Back

Information

 
TitleHow to speed up the tablemove process?
URL NameP50766
Article Number000156464
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All Supported Operating Systems
Other: RDBMS
Question/Problem Description
How to improve the performance of tablemove process?
How to speed up the tablemove process?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
The tablemove command runs using a single transaction, so that in the event of failure it is capable of an undo.

Since tablemove is a transaction based operation, all adjustments for general performance recommendation are applicable.

Listed below is a summary of them:
  • Start the database in multi-user mode, even when only the tablemove process is running
  • Start APW, BIW to speed up the writes to the database files.
  • Tune the BI block size and BI cluster size.
  • Use -B, -bibufs, -spin, etc.
  • Turn off After-Imaging
  • Start the database with no-integrity, provided a valid backup of the database is taken beforehand.
IMPORTANT INFORMATION:
WHEN RUNNING DATABASE WITH THE -i PARAMETER, IF THE LOAD FAILS, THEN YOU MUST GO TO BACKUP!

For further information refer to Articles:
 
Workaround
Notes
Last Modified Date11/20/2020 7:33 AM
Attachment 
Files
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.