FairCom DB V12 Updates

Steps to Upgrade FairCom Server

While FairCom always attempts to maintain backward compatibility whenever possible, transaction logs from earlier versions are generally not always compatible with newer FairCom Server formats.

Note: Unless otherwise mentioned in the version-specific Update Guides, existing data and index files are usually not affected by transaction log changes.

Removing Transaction Logs and Upgrading the FairCom Database Engine

The FairCom process makes it easy to upgrade the FairCom server using your existing files, as long as you remove prior transaction logs in a safe manner. The steps shown below are appropriate any time you are upgrading. Notice that you will shut down your server two times during this process (steps 2 and 5) to allow all files to be brought to a consistent state.

1. Have all clients cleanly exit from your existing FairCom server.
2. Perform a normal controlled shutdown of the server using one of the methods described here, depending upon your installation:
   • Server Console Window - From the FairCom Server console window click “Control” and then click “Shutdown the Server”
   • Windows Toolbar - Right-click the c-tree Server icon in the Windows Tooltray and choose “ShutDown the Server”
   • Windows Service - From the Windows Control Panel, choose “Administrative Tools”, then choose “Services”. Locate the FairCom Server in the list of services running on your machine. Right-click the c-tree Service and choose “Stop”.
   • Use the client command line utility, ctadmn, and follow the prompts.
   • Use the client command line utility, ctstop.

   Remember that the Administrator user ID is "admin" (case insensitive) and the default password is "ADMIN" (case sensitive). The default c-tree Server name is "FAIRCOMS".

3. Block the ability of any clients to attach to the FairCom server.
4. Restart the existing FairCom server with no clients attached and allow a successful automatic recovery to take place. This ensures all files are brought to a consistent state in the event there is any data remaining in the transaction logs.
5. Perform another normal controlled shutdown of the FairCom server as described earlier.
6. Remove all existing transaction logs and associated files (L*.FCS, S*.FCS, D*.FCS, I*.FCS, and *.FCT).

   Note: We do not recommend removing FAIRCOM.FCS unless specifically instructed to do so in the notes accompanying the new FairCom version.

   Several other types of log dependencies should be considered before deleting transaction logs:

   1. Replicas
   2. Deferred indexes
   3. Record update callbacks

   If these options are in use, ensure they have processed all the log data before the logs are deleted. Otherwise the dependent data could be out-of-sync. (2 & 3 don't always use the transaction logs)

7. Copy your new FairCom server directory in its entirety into the existing Server directory. Note you might want to protect your existing ctsrvr.cfg and ctsrvr.set files so you don't loose any custom settings. Also review the new ctsrvr.cfg file accompanying any FairCom server upgrade to leverage new best practice settings.

   Note: Client compatibility can prevent connections to the new FairCom Database Engine. It is always advised to use the most recent matching client version with your FairCom server version.

8. Unblock the ability of any clients to attach.
9. Start the FairCom server in your usual manner and begin using your existing data.

FairCom has added logic to notify you when transaction logs may be incompatible. Please review the section "Detection of Transaction Log Incompatibilities" in the FairCom Server Administrator’s Guide for details.