This is a very basic issue but I thought I would upload it anyways. Running windows 2012 environment with Windows 2012 R2 I am new to sybase myself.
Error message this morning received on system:
I immediately checked DPMON as well see all processes were in status WP_KILL which indicated a bigger problem to me.
Upon further investigation I saw the following errors in the dev_disp work processes trace file.
***LOG Q41=> DpDumpInternalTables, () [dpxxdisp.c 3299]
Tue Apr 07 08:29:12 2015
*** ERROR => DpHdlDeadWp: W1 (pid 3792) died (severity=0, status=0) [dpxxwp.c 1363]
DpWpRecoverMutex: recover resources of W1 (pid = 3792)
DpSkipSnapshot: delayed snapshot exist, skip new snapshot
*** ERROR => DpHdlDeadWp: W2 (pid 3080) died (severity=0,
| | | |
DpWpLock: locked wp_adm.mutex
DpWpUnlock: unlocked wp_adm.mutex
| 8| |DIA |WP_KILL| |1 | | |
I then reviewed a dev_w* process trace file and found the error that I was looking for indicated sybase db transaction logs were full.
C transaction aborted by server
C ERROR: failed to retrieve db and user name
B ***LOG BY2=> sql error 1105 performing CON [dbsh 1252]
B ***LOG BY0=> [ASE Error SQL1105][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Can’t allocate space for object ‘syslogs’ in database ‘SID’ because ‘logsegment’ segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.
Upon this I managed to dump the logs stop/start processes cleanly and system was running.
command 1: isql -Usa -SSID -X
command 2: dump transaction SID using config = ‘SIDLOG’
command 3: go
This runs for a few minutes.
How to identify the config SIDLOG if you are unsure, you have to do this on the master db.