This topic lists the main error or warning messages that either display in the message section of the Hot Backup menus or log to the permanent log file.
| Error | Description |
|---|---|
| ERROR: This command applies only to Slave servers | Command can only be performed against the slave server. Certain functions cannot be performed by master servers. |
| Not a phantom. Running on PIB xxx. PID yyy | Displays when interrogating a server which is either started in foreground (for debugging purpose) or, more likely, which has aborted, or was killed, leaving an inconsistent status in the jobs file. |
| Terminated abnormally | Server phantom process has terminated without finishing properly. The process was probably logged off, or encountered a fatal error. |
| Notice from server ’servername’ | Signifies that the message in the message section of the Hot Backup menu is coming from the specified server. |
| Waiting for server ’servername’ to start | Waiting for the phantom process to start. |
| Waiting for server ’servername’ to initialize | Phantom process started and is waiting for the server to initialize itself. |
| FAILED: Cannot start phantom process | Phantom process failed to start. Check the scheduler to verify there are not too many queued jobs and use list-jobs to determine the cause of the abort. |
| FAILED: Server ’servername’ encountered an error and stopped | Phantom process started normally, but the server could not complete its initialization. Use the status option from the Hot Backup Main Menu to verify the cause of the failure. The most common cause is a BIND error, indicating that the TCP port is already in use. Often, when stopping a server, the TCP connection is not purged immediately and the TCP port remains in use. This usually cleans itself up after the various TCP protocol time outs have expired. Stop the master server and re-attempt a few minutes later. If the BIND error persists, change the port number using the Setup Server option from the Special Operations menu in Hot Backup. The port must be changed on both the master and the slave servers. |
| WARNING: Server ’servername’ is already running on PIB xxx | A start server failed because the server appears to be already
running. This has no action on a running server. If the server is not running, and this message continues to display, this might
indicate a corruption of the Hot Backup control file. Make sure the
server is not running (using the where command) and
run: delete hb.log servername |
| WARNING: Transactions are not enqueued | Issued by the master server to indicate that updates to the database are not being enqueued, and therefore are not being transferred to the slave server. The databases are now out of sync. |
| WARNING: Transaction queue has grown to xxx frames | Periodically, the master server checks if the queue has grown to more than 500 frames above the previous value, indicating that the slave server is not able to keep up with the load. Ensure that the input server is not stopped, or has not aborted. This message may be normal in situations where massive updates are performed. |
| malloc error. err=xxx | System could not allocate memory. Warning: This
is an indication of a serious UNIX problem. Check the swap space.
|
| Cannot call host ’hostname’. Errno=xxx | Master server cannot establish a communication. The error code is implementation dependent. Ensure that the host is available by using the UNIX command ping hostname. If available, the most likely reason is that the slave server has encountered an error or is not started. Use the status option from the Hot Backup Main Menu on the slave server to verify. |
| Cannot read FOF item ’xxx’ | Due to a corruption in the file-of-files file on the master server, the system is unable to identify the file being updated. 'xxx' is the file number (as known on the master server). Data is normally transferred to the slave server, but stored in a temporary hold file named hb.missing,master.name*xxx, where master.name is the name of the master server, and xxx the file number. To correct this situation, rebuild the file-of-files file on the master server by performing a full file-save (possibly a dummy save), with the (s option. The missing file-of-files file item can also be rebuilt manually if the file name can be identified from the content of the file being stored in the temporary hold file on the backup system. The data can then be copied to the real file. Instruct the slave server to close its opened files using the Close opened files option from the Special Operation menu to force it to open the new file. |