V9 Upgrade Quick Guide

Home ProductsV9 Upgrade Quick Guide

V9 Upgrade Quick Guide

This upgrade guide is intended as a quick reference to demonstrate how easy it is to move from previous versions of c-tree database technology to the latest c-treeACE V9. c-treeACE V9 introduces several minor compatibility issues of its own that you should be aware of when moving forward:

Extended headers now included by default on all new files created by c-treeACE.
Commit Read Lock support is default and requires record locks on any update.
Files created by c-treeACE SQL are HUGE by default.

c-tree database technology is a powerful and flexible tool and this flexibility has been a testament to its longevity. While the information outlined on this page will successfully migrate a majority of applications in use, it is impossible to anticipate every situation. As always, our outstanding engineering team is standing by to assist at every opportunity. Feel free to contact your nearest FairCom office for advice and guidance before migrating your application. We have helped successfully migrate many original c-tree applications to our very latest versions, sometimes within minutes.

Existing V4 Users

(V4.1F-V4.3C)

Existing c-tree V4 files require conversion to the updated c-treeACE format. The following steps outline this process.

Make a BACKUP of ALL OF YOUR FILES before you begin!
Convert your existing data files with the ctcv43 file conversion utility and set these converted files aside.
Use the ctexmc parameter file create utility to create empty data and index files from your existing parameter files. (We do this as the IFIL conversion will require a valid index file to be in place, even if empty.)
Copy in your newly converted data files overwriting the empty data files just created by ctexmc. (Leave the new empty index files in place.)
Convert your existing parameter files to IFIL structures with ctptoi parameter conversion utility. This utility will place an IFIL structure directly into the converted data files.
Rebuild your index files with the ctrbldif rebuild utility.
(Optional) Stamp a DODA structure (data schema) based on the ‘C’ structure definitions into your data file with the c-treeACE PutDODA() API call. The DODA makes available many higher level interfaces such as ODBC, c-treeDB, .NET and c-treeACE SQL.
Include the single c-treeACE ctreep.h header file in your application to replace the previous numerous c-tree headers:

#include "ctreep.h"

Existing V6 Users

V6 introduced updated c-tree Plus file format with extended headers for advanced feature support.

Convert your existing V6 data files with the ctcv67 conversion utility. This utility converts existing c-tree Plus data files to the extended format introduced in V7. Extended header support offers HUGE file support and segmented files.
Use the Xtd8 file creation functions to create new Extended files.
For data files supporting HUGE file support, remember to update your duplicate index keys in the IFIL definitions to include an additional 4 bytes for the associated record position.
Note that the ctreep.h header file automatically includes the ctv6v7.h header.
Cleanly shut down any existing V6 Servers and remove remaining transaction logs. (Steps for a Clean Upgrade) V9 introduces a new transaction log format.
Store a copy of the V6 dynamic dump restore utility (ctrdmp) with any remaining backup files in case of future recovery. Consider validating a fresh V9 dump and restore and review your backup procedures at this time.

Existing V7 Users

V7 introduced HUGE, segmented and partitioned file support, and many new cache options for performance. V7.12 increased the PAGE_SIZE default from 2048 bytes to 8192 bytes. Keep this in mind with indexes from previous versions, as the page size is used as the index node size.

Cleanly shut down any existing V7 Servers and remove remaining transaction logs. (Steps for a Clean Upgrade) V9 introduces a new transaction log format.
Store a copy of the V7 dynamic dump restore utility (ctrdmp) with any remaining backup files in case of future recovery. Consider validating a fresh V9 dump and restore and review your backup procedures at this time.

Existing V8 Users

V8 introduced Memory Files, Queues and Notification, and performance monitoring tools.

Cleanly shut down any existing V8 Servers and remove remaining transaction logs. (Steps for a Clean Upgrade) V9 introduces a new transaction log format.
Store a copy of the V8 dynamic dump restore utility (ctrdmp) with any remaining backup files in case of future recovery. Consider validating a fresh V9 dump and restore and review your backup procedures at this time.