FairCom RTG BTRV User Guide

Troubleshooting

This section provides some useful troubleshooting tips.

For troubleshooting performance issues, see the section titled Performance Tuning.

A Note About Error Codes

Most of the FairCom RTG errors are intended for developers and will seldom be seen during normal operation.

The FairCom RTG products are built upon a specialized version of the FairCom DB core database engine. The complete list of possible FairCom RTG errors can be found in the FairCom DB Error Codes document.

For error codes that are specific to FairCom RTG, see the following:

• Driver Error Codes
• Error Codes
• FairCom RTG SQL Access Errors

For error codes returned by the XDDCHECK API, see:

• XDDCHECK Errors

In This Section Error 407 Error 408 / 438 Client/Server Incompatibility File Matching Rules in ctree.conf Troubleshooting Performance

Error 407

Support has been added to the FairCom RTG ctutil utility to open files affected by error 407 so it can export data from a file that has a damaged resource chain. This support requires ADMIN permission and the OPENCRPT file mode. To use this functionality, ctutil must be renamed to ctunload407. The ctunload407 utility functions similar to ctutil ‑unload except that it automatically connects as ADMIN (with the default ADMIN password) and enables the <allowcorrupt> setting.

Error 408 / 438

Error 408 / 438 during -sqlink indicates that no record definition is available. Either the file does not have an XDD resource (-sqlinfo was not performed) or the server did not load the data conversion callback library. Possible causes are:

• LOAD_CALLBACK_LIB ctsrvr.cfg keyword was not specified or invalid.

  Or

• The callback library is not in LD_LIBRARY_PATH (UNIX).

Client/Server Incompatibility

An internal error CTE_INCOMPATIBLE (37) is returned when the client or server is outdated. An entry is sent to <log> with a logical error 37 and one of the following:

• c-tree error -3 (CTE_OLD_CLIENT) when the client is older than the server
• c-tree error -4 (CTE_OLD_SERVER) when the server is older than the client

File Matching Rules in ctree.conf

When ctree.conf contains only one <instance> element, it is not mandatory to specify a <file> rule because it is implicit that FairCom RTG needs to use the one available instance to open files.

If you specify more than one instance, you need to specify a <file> rule so that FairCom RTG knows which instance to use to open files. When specifying more than one instance, specify a default file rule into the instance you want to use:

<config>

<log>n</log>

<instance server="FAIRCOMS"></instance>

<redirinstance>

<file name="*">

</file>

</redirinstance>

</config>

Please notice that to specify a default file rule you can omit the name/dir attributes so the above configuration can also be specified as follows:

<config>

<log>n</log>

<instance server="FAIRCOMS"></instance>

<redirinstance><file/></redirinstance>

</config>

The above concept applies to all <*instance> elements: <instance>, <redirinstance>, etc.