|
|
|
The FairCom DB startup process is usually very fast. FairCom DB logs a message of the form shown below to CTSTATUS.FCS when startup is complete and the server is ready for clients to connect:
- User# 00001 FairCom DB V12.0.0.111 SQL Server Is Operational -SN 39001664
If FairCom DB process appears in the system process list but CTSTATUS.FCS does not yet show the above message indicating the server is operational, the most likely cause is that the server is performing automatic recovery and for some reason the recovery is taking a long time.
To determine if the long startup time is due to automatic recovery occurring, check the server status log. When the server begins automatic recovery, it writes the following message to the status log:
- User# 01 Beginning automatic recovery process
When the server completes automatic recovery, it writes the following message to the status log:
- User# 01 Automatic recovery completed
If the server has logged the first message to the status log but not the second, it has begun but has not yet completed automatic recovery.
If RECOVER_DETAILS YES is present in the server configuration file when the server is started, the server logs the time spent for each phase of recovery to the server status log. This option provides a way to more specifically monitor the progress of automatic recovery. Below is an example showing the order of automatic recovery phases. The server writes the entry for each recovery phase upon completion of that recovery phase, so the current recovery phase can be determined by examining the contents of the server status log.
Mon Sep 29 10:14:34 2003
- User# 01 Transaction scan time: 1 seconds.
Mon Sep 29 10:14:34 2003
- User# 01 Beginning automatic recovery process
Mon Sep 29 10:14:34 2003
- User# 01 Index repair time: 0 seconds.
Mon Sep 29 10:14:34 2003
- User# 01 Index composition time: 0 seconds.
Mon Sep 29 10:14:34 2003
- User# 01 Transaction undo time: 0 seconds for 2 transactions.
Mon Sep 29 10:14:34 2003
- User# 01 Vulnerable data time: 0 seconds.
Mon Sep 29 10:14:34 2003
- User# 01 Vulnerable index time: 0 seconds.
Mon Sep 29 10:14:34 2003
- User# 01 Transaction redo time: 0 seconds for 843 transactions.
Mon Sep 29 10:14:34 2003
- User# 01 Automatic recovery completed
Although the current recovery phase and time spent so far during recovery can be determined using the above approach, the log entries do not indicate how much time remains until recovery is complete.
If automatic recovery appears to hang or is taking a long time, the two options are to wait until recovery completes or to abandon recovery and restore TRNLOG data and index files from a backup. See the "Automatic Recovery Fails" topic in the “Failures During System Recovery” section of this document for details on these options.
If the server startup is taking a long time or appears to hang and the cause does not appear to be automatic recovery (based on the status log messages), check the state of the server process using system utilities as described in the “Monitoring FairCom DB Process State” section. If necessary, the server can be forcibly terminated and restarted without affecting the state of FairCom DB data and index files because the files will not have been open for end user modification at this point.
