Upgrading to Newer FairCom DB Server Versions

While FairCom strives to maintain backward compatibility whenever possible, transaction logs from earlier versions are generally not compatible with newer FairCom DB Server formats. New features frequently introduce new log entries and handling of prior entries should recovery occur over them.

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 FairCom DB Server

FairCom DB is usually easy to upgrade to newer versions with your existing data and index files, as long as you remove prior transaction logs in a safe manner. The steps shown below are appropriate any time you are upgrading server versions. Notice that you will shut down your FairCom DB 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 DB Server.

2.  Perform a normal controlled shutdown of the FairCom DB Server using one of the methods described here, depending upon your platform and installation.

Windows

• Windows Service - From the Windows Control Panel, choose “Administrative Tools”, then choose “Services”. Locate the FairCom DB c-tree 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, ctstop.
• Use the client command line utility, ctadmn, and follow the prompts.
• Server Console Window - From the FairCom DB Server console window click “Control” and then click “Shutdown the FairCom DB Server”
• Windows Toolbar - Right-click the c-tree Server icon in the Windows Tooltray and choose “ShutDown the FairCom DB Server”

Unix/Linux

• Use any site specific service start/stop scripts.
• Use the client command line utility, ctstop.
• Use the client command line utility, ctadmn, and follow the prompts.
• Remember: Administrator user ID is \"admin\" (case insensitive) and the default password is "ADMIN" (case sensitive). The default FairCom DB Server name is "FAIRCOMS".

3.  Block the ability of clients to attach to FairCom DB Server.

4.  Restart the existing c-treeACE 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. This step provides full cleanup of all background tasks, queues, etc. 

5.  Perform another normal controlled shutdown of FairCom DB as described above.

6. Remove all existing transaction logs and associated files (L*.FCS, S*.FCS, D*.FCS and I*.FCS). Note, we do not recommend removing FAIRCOM.FCS unless specifically instructed to do so in the notes accompanying the new FairCom DB version.

Security Note: FAIRCOMS.FCS contains defined users, groups, and database permissions. This is a good time to inventory your database access control list and adjust. Don't forget to change your ADMIN password on a regular basis. 

7. Copy your new FairCom DB Server directory in its entirety into your existing c-tree Server directory.

Note: Protect your existing ctsrvr.cfg and ctsrvr.set files so you don't loose any custom settings. Review the new ctsrvr.cfg file accompanying any FairCom DB Server upgrade and leverage new best practice settings.

8. Unblock the ability of any clients to attach.

9. Start FairCom DB in your usual manner and begin using your existing data.

FairCom DB logs messages to FAIRCOMS.FCS advising when transaction logs may be incompatible. Please review the section "Detection of Transaction Log Incompatibilities" in the FairCom DB Server Administrator’s Guide for details.

Perform another normal controlled shutdown of FairCom DB as described above.

Client compatibility

It is always advised to use the most recent matching client version with your faircom db server version. Versions 9 and 10 have both introduced backward compatibility changes. With some versions this can prevent connections to the new FairCom DB database engine. Review provided release notes for all compatibility information.