All,

We have got the below sybase error today while running a stored procedure.Your approach to fix this,please?

00:00000:00812:2010/02/05 09:59:03.49 server Could not grab a buffer from the 8k buffer pool in cache test_fin_db_logcache for flush ing the log. Tried 6 buffers, all the buffers in the wash section are pinned to Private Log Cache. Most likely the wash size has been incorrectly configured for this buffer pool.
00:00000:00812:2010/02/05 09:59:03.51 server Error: 875, Severity: 20, State: 1
00:00000:00812:2010/02/05 09:59:03.51 server Unable to grab a buffer to allocate a page to the log in database id 99. Tried 6 buffers in the wash but found them to be pinned (either directly or indirectly). See the error log for more information.
00:00000:00812:2010/02/05 09:59:03.51 kernel ************************************
00:00000:00812:2010/02/05 09:59:03.51 kernel SQL causing error :
00:00000:00812:2010/02/05 09:59:03.51 kernel Current Procedure: test_fin_sp
...

Sybase Error: 1619, Severity: 21, State: 1 message in the error log file

00:00000:00001:2010/01/16 07:30:01.19 server Error: 1619, Severity: 21, State: 1
00:00000:00001:2010/01/16 07:30:01.19 server Could not open TEMPDB, unable to continue.

Explanation& Resolution

If the tempdb is not intialized properly during the start up this error occurs.Please check the previous messages to see if the tempdb device intialization has failed.In my case it is the tempdb datadevice activation problem during the startup.

Sybase Error: 840, Severity: 17, State: 2 message in the error log file

00:00000:00001:2010/01/16 07:30:02.19 server Error: 840, Severity: 17, State: 2
00:00000:00001:2010/01/16 07:30:02.19 server Device 'testtempdbdatadev' (with physical name '/tmp/testtempdbdatadev.dat',
and virtual device number 6) has not been correctly activated at startup time. Please contact a user with System Administrator (SA
) role.
00:00000:00001:2010/01/16 07:30:02.19 server Error: 1619, Severity: 21, State: 1
00:00000:00001:2010/01/16 07:30:02.19 server Could not open TEMPDB, unable to continue.


Explanation


This error can occur when Adaptive Server is unable to access a device during startup.

This error 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...