Sybase 11.9.x-12.5 - Manual (Page 12)

Commonly Encountered Errors
686
isql/user_name="sa".
Similarly, the strings 'us_english' and 'iso_1' seen above in single quotes are
converted to uppercase. This causes backupserver.exe to interpret these strings
in an unexpected manner.
Note The runserver file is created in this manner by the sybinit.exe program.
To correct this problem, edit the Backup Server runserver file, enclosing the
two strings in double quotes as follows:
/LANGUAGE="us_english" -
/CHARACTER_SET="iso_1"
Unable to use Async IO when dumping to disk on HP-UX
When trying to dump a database to disk on HP the following error occurs:
Backup Server 4.86.2.1: Unable to use Async IO on
the database device 'disk device specified'.
Backup Server must use Async IO on a block special devices
because SQL Server is doing the same. Refer to the server
release notes.
Backup Server 4.27.2.1: Volume validation error:
attempt to close 'disk device specified' returned Bad file number.
This error occurs even though Async IO is configured correctly. It occurs
because of a problem in locking shared memory.
Adaptive Server, when using Async IO on HP, needs to lock its shared memory
into physical memory so that processing an Async IO request will never have
to wait for memory areas to be moved from swapspace to physical memory.
As the above error message says, Backup Server needs to do the same.
However it cannot do so because there is not enough lockable physical memory
left for the Backup Server.
On HP, lockable physical memory defaults to 75% of physical memory, not
75% of total shared memory.
To correct this problem try these options:
• Increase physical memory.
• Decrease the memory parameter for the Adaptive Server.