Error 822

Severity

20

Message text

Could not start I/O for request BLKIO flags  = 0x%lx, size = %ld, errcode = 0x%lx, %S_BUF.

Explanation

This error occurs when a read or write operation was requested and Adaptive Server encountered an error while attempting to initiate the request. Error 822 can occur for any of the following reasons:

• A database device is offline

• A database device or file has been removed or renamed

• A database device or file is inaccessible to Adaptive Server for any other reason, such as insufficient permissions or a device number higher than the number of devices configured for Adaptive Server (such a device will not be activated at startup)

The information in the error message refers to an internal Sybase structure and does not help determine which database device or file is involved. Other error messages appearing in the Adaptive Server error log just before the 822 error usually indicate the nature of the problem and the device involved. Refer to “Additional Information” for examples of this type of error message.

Action

1. Examine the availability and condition of the device involved using your standard operating system procedures, and make sure the device is accessible.

2. Adaptive Server will not be able to recover the database upon restarting because an 822 error will mark the database suspect. If you know that the database was marked suspect because the device was unavailable, reset the status of the database to allow recovery to continue.

   WARNING! Do not use these procedures if other errors in the error log near the 822 error message suggest that the database may have been marked suspect for some other reason.

   Reset the suspect status using one of the methods supplied in “Resetting a database’s “suspect” status” in the chapter “Other Useful Tasks” in the most recent version of the Troubleshooting and Disaster Recovery. After you reset the status, and start Adaptive Server, if the database is again marked suspect, examine the Adaptive Server error log for indications of other errors.

Additional information

Here are two examples of the 822 error and associated messages from the Adaptive Server error log. Examining the error messages just before the error usually helps determine the type of problem.

kernel: initializing virtual device 6, "/work/disk1"
kernel: dopen: open "/work/disk1", Permission denied 
kernel: dinit: failed to open primary device /work/disk1 for vdn6
kernel: udstartio: vdn 6 has not been set up 
server: Error: 822, Severity: 20, State: 3 
server: Could not start I/O for request BLKIO ....   

To correct an error like this:

1. Change the ownership to user “sybase”. Make sure that this user has read and write permissions on the device. In our example, check the user's permission on /work/disk1.

2. Become the “sybase” user.

3. Start Adaptive Server.

kernel: initializing virtual device 6, "/work/disk1"
kernel: dopen: open "/work/disk1", No such file or directory 
kernel: dinit: failed to open primary device /work/disk1 for vdn6
kernel: udstartio: vdn 6 has not been set up 
server: Error: 822, Severity: 20, State: 3 
server: Could not start I/O for request BLKIO .... 

To correct an error like this, make sure that the virtual device in the error message exists, and correct whatever error caused Adaptive Server not to find it. (For example, it may have been renamed or moved while Adaptive Server was shut down.)

If the virtual device no longer exists, you will have to restore from known clean backups. Merely creating an empty device with the right name will not solve this problem.

Versions in which this error is raised

All versions