Skip to Content
Author's profile photo Nicolaas Johannes Van Zyl

sql error 1105 ASE SAP transaction logs full

Hi everyone,

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:

Maximum.JPG

I immediately checked DPMON as well see all processes were in status WP_KILL which indicated a bigger problem to me.

dpmon.JPG

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[8].mutex

DpWpUnlock: unlocked wp_adm[8].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.

dump command:

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.

1>use master

2>go

3>sp_config_dump

4>go

SIDDB

SIDLOG

Kind Regards,

Johan

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Kiran Kumar Adharapuram
      Kiran Kumar Adharapuram

      We have 2 SAP Notes for the same

      1. 1836607 - SYB: How to solve error 1105 in database "saptools"

      2. 1687320 - SYB: 'saptools' database running out of space

      We can use the same guidelines which are given in the sap note even if we get error on SID database also.

      Regards

      Kiran K Adharapuram