Filter
Top Products
CHAPTER 4 Backup Server Error Messages
687
• Change the HP-UX kernel parameter
UNLOCKABLE_MEM. By default,
this is 0 which signifies the aforementioned 75% - 25% ratio. Consult HP
technical support before changing this parameter.
Maximum Number of DBPROCESSes Already Allocated
Two scenarios could result in this error. They are summarized in the following
table:
Error Conditions Without Messages
A programming error may occur that causes the Backup Server to hang without
issuing a message. Follow these steps:
• Determine whether the entire Adaptive Server is hung or just a single
session.
• Terminate the hung session with keyboard interrupt or
quit.
At this point, on a UNIX machine, it is necessary to check for I/O subprocesses
that remain alive, holding open dump devices. Perform this check with the
ps
command and use
kill (default signal) to kill the sybmultbuf processes whose
command lines contain device names used by the terminated session. Be
careful to kill only those processes that use the devices involved.
Each device is controlled by a pair of processes, and each pair of processes
controls just one device. Therefore, the presence of a device name in a
command line is sufficient to identify the subprocess to kill.
dump and load data
from an aborted session or Server are not usable.
The Backup Server can exit abnormally without killing its subprocesses. In this
case, use
kill to clean up the sybmultbuf processes before restarting the Backup
Server; otherwise, the devices involved may not be usable.
Scenario Action
The Backup Server
runserver file, the interfaces file,
and the
sysservers table in the master database do not
have a consistent name for the Backup Server.
Verify that all three locations contain the same Backup
Server name. Pay attention to case sensitivity.
You have hit a network limit for the Backup Server
process. Typically, this limit is set to 25.
Start Backup Server with the
-Nnn flag to change the
network limit. For example,
-N30 increases the limit to
30.