sybase service not starting anymore

[brunox]

Dear,
seen sybase was in a pending status it was rebooted, but afterwards the sybase service cannot be started anymore.

These are some messages found the errorlog :
Recovering database 'master'
server Checking external objects.
server Space available in the log segment has fallen critically low in database 'master'. All future modifications to this database will be suspended until the log is successfully dumped and space becomes available.
Database 'master' is now online.
The transaction log in the database 'master' will use I/O size of 2 Kb.
Error: 834, Severity: 20, State: 4
Illegal attempt to clean buffer: BUF pointer = '0x243B4CE0', MASS pointer = '0x243B4CE0', (Buf#: '0'), page ptr = '0x24192000', dbid = '1', Mass virtpage = '725', Buffer page = '721', Mass status = '0x44001000', Buffer status = '0x1', size = '2048', cache (id: 0) = 'default data cache'.
************************************
curdb = 1 pstat = 0x1000 lasterror = 834
preverror = 0 transtate = 1
curcmd = 0 program =
pc: 0x009EF4B4 os_get_cur_stk_desc+ 0xf1 (0x01C5F958, 0x77F3B96C, 0x77F3CC10, 0xFFFFFFFF)
pc:0x009EF4B4 os_get_cur_stk_desc+ 0xf1 (0x01C5F958, 0x01C5F710, 0x0000270F, 0x00000002)
pc:0x009C879F pcstkwalk+ 0x204 (0x000B000B, 0x00000002, 0x0000270F, 0x00000000)
pc:0x009C8429 ucstkgentrace+ 0x1f9 (0x000B000B, 0x00000001, 0x00000000, 0x00000000)
pc:0x00998B78 ucbacktrace+ 0x88 (0x00000000, 0xFFFFFFFF, 0x01C5FCA0, 0x0045C69C)
pc:0x004060A7 terminate_process+ 0xb11 (0x01C5FD0C, 0x0045C511, 0x00000008, 0x00000022)
pc:0x0045C6B9 close_network+ 0xc (0x00000008, 0x00000022, 0x00000014, 0x00000004)
pc:0x0045C69C hdl_default+ 0x38 (0x00000008, 0x00000022, 0x00000014, 0x00000004)
pc:0x0045C511 ex_raise+ 0x309 (0x00000000, 0x20FD6CE0, 0x00000000, 0x00000000)
pc:0x00542FE0 cm_dbclean+ 0x1be (0x20FD6CE0, 0x208A69E0, 0x20FD6CE0, 0x01C5FF80)
pc:0x004D370F buf_online_database+ 0xe8 (0x00000000, 0x00000000, 0x00000001, 0x00000000)
pc:0x006220BF masterrecover+ 0xd9 (0x00000000, 0x00000000, 0x00000000, 0x2001CC4C)
pc:0x00403FDC dsinit+ 0x92c (0x2001CC4C, 0x00000000, 0x00000000, 0x2001CC4C)
pc:0x009E78E7 kpntwrapper+ 0x84 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
end of stack trace, spid 1, kpid 720907, suid 0
udstartio: vdn 1 has not been set up
Error: 840, Severity: 17, State: 1
Device 'sysprocsdev' (with physical name 'D:\Bediet01\sqldata\sybprocs.dat', and virtual device number 1) has not been correctly activated at startup time. Please contact a user with System Administrator (SA) role.
Error: 2812, Severity: 16, State: 5
Stored procedure 'sp_thresholdaction' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
==================================================

What can be done to force a startup of the sybase service(when trying to start with convig server it is timed out).

Thanks.
Bruno

 

[sybaseguru]

Bruno,

It appears that it is complaining about sysprocsdev device (device No 1) has not been brought online. But before that you had an 834 error followed by stack dump. The writeup about this error is:


Error 834
Severity
20
Error message text
Illegal attempt to clean buffer: %S_BUF.
Explanation
The Adaptive Server Cache Manager works in conjunction with the Buffer Manager to manage physical disk pages while they are in memory. When a page is read into memory from the disk, a buffer header is assigned to it. The header tracks the usage and the contents of the page image. The page and the buffer header together define a buffer.
The buffers themselves are grouped together to form Memory Address Space Segments (MASSes). A buffer cache consists of MASSes linked in MRU/LRU (most recently used/least recently used) chains. The Cache Manager manages MASSes and buffer caches.
When a buffer or MASS is no longer needed (for example during a drop database, drop table, drop index, or deallocation of pages), Adaptive Server performs some cleanup tasks and releases the resources taken up by the buffer or MASS. Before these actions are carried out, Adaptive Server does a number of checks to make sure the buffer or MASS is no longer in use. Error 834 occurs when one of these checks fails. It is caused by an Adaptive Server problem.
Error 834 occurs with the following states:
State
Meaning
1
If the MASS is actively being used or if Adaptive Server is in the process of writing out the MASS when Adaptive Server tries to clean it up, Error 834 occurs with State 1. This state is only raised by diagserver.
2
If the buffer is still hashed or has not been cleaned up when Adaptive Server is ready to release it, Error 834 occurs with State 2. This state is only raised by diagserver.
3
If the buffer is actively being used or if Adaptive Server is in the process of writing out the buffer when Adaptive Server is ready to release it, Error 834 occurs with State 3. This state is only raised by diagserver.
4
If the buffer belonging to a database has been set aside for later use and Adaptive Server tries to clean it out of a cache, Error 834 occurs with State 4.
5
If a buffer belonging to an object has been set aside for later use and Adaptive Server tries to clean it out of a cache, Error 834 occurs with State 5.
Action
State 4, LTMs Running
834 errors with State 4 can occur if the Log Transfer Manager (LTM), a Replication Server component, is running during server recovery. The LTM process attempts to log in before the database is fully recovered. To avoid this error, shut down the LTM before restarting the server. Restart LTM only after all the databases have been recovered.
All Other States
Shut down and restart Adaptive Server to clear the buffer structure.
If Error 834 occurs again, call Sybase Technical Support.
Additional information
Have the following information ready when you call Sybase Technical Support:
·Server version and SWR rollup level
·Text of all error messages.
Versions in which this error is raised
All versions


Can you check the errorlog and post the full version again. You may have to use trace flags to start ASE in recovery mode (Sybase tech support can give you more on this.) As this is a priority 1 error, I strongly advise you to contact Sybase tech support. Anyway send the full errorlog for last startup.