SAP Knowledge Base Article - Preview

2918555 - Phantom locks left in tempdb after error 1105 - SAP ASE

Symptom

  • Client is using jConnect with ENALE_BULK_LOAD set to 'true' and perform bulkcopy.
  • Phantom locks left in a user defined tempdb after a process is terminated due to Error 3478: 

Error: 3478, Severity: 21, State: 1
During undo the page timestamp value is less than new timestamp from log. Page #=13445, object id = 722644652, page timestamp=0015 a6990489. Log new timestamp=0015 a799b7ef. Log record marker = (1468082, 12).
Error while undoing log row in database 'mytempdb'. Rid pageid = 1468082; row num = 12.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, range entry 0, sdesp 0x0x00002ab52381af30, objid 1451212942.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, system table entry 0, sdesp 0x0x00002ab570cde200, objid 8.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, system table entry 1, sdesp 0x0x00002ab570cd8af0, objid 1.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, system table entry 2, sdesp 0x0x00002ab570cde200, objid 8.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, system table entry 3, sdesp 0x0x00002ab570cd8af0, objid 1.
WARNING: Pss 0x0x00002ab7e5fae1c0 found with open sdes. pspid 16684, psuid 1305, pcurdb 59, system table entry 4, sdesp 0x0x00002ab570cd7e80, objid 99.
Error: 6103, Severity: 17, State: 1
Unable to do cleanup for the killed process; received Msg 3300.
WARNING: spid 16684 with suid 1305 and curdbid 59 has an active transaction in dbid 59 with xactid (1455224, 10).

  • Prior to Error 3478, many 1105 errors were reported for this user defined tempdb in the ASE errorlog, for example:

Error: 1105, Severity: 17, State: ... 
Can't allocate space for object 'syslogs' in database mytempdb' 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.

  • The following error may also reported in the errorlog when killing the connection that encounter Error 1105.

    Error: 631, Severity: 21, State: 4
    00:0006:00000:00020:2020/12/16 11:32:25.60 server The length of 352 passed to delete row routine for the row at offset 384 is incorrect on the following page of database 'tempdb1': Page pointer = 0x0x2611ec000, pageno = 2465, status = 0x101, ptnid = 47440312, indexid = 0, level = 0, pnextrno = 2. The expected row length is 16384. The offset should be no greater than 736.

    Error while undoing log row in database 'tempdb1'. Rid pageid = 9692; row num = 1.

    rec_undo_session
    abort__all
    xact__rollbackxact
    xact__rollback_local
    xact_rollback
    kill_proc
    terminate_process
    quitfn
    quitfn_indirect
    usrfill
    recvhost
    bulk_flush
    LeBulkOpOpenCleanup
    LeBulkOpOpen
    LeBulkOp::_LeOpOpen
    LeOperator::LeOpOpen
    LeEmittOp::_LeOpOpen
    LeOperator::LeOpOpen
    LePlanOpen
    exec_lava
    bulk_main

 


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0
  • SAP Adaptive Server Enterprise Cluster Edition (ASE CE) 16.0

Product

SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise 16.0 Cluster Edition

Keywords

Sybase, ASEServer, SAPASE, dataserver, CR821224, CR#821224, 821224,820521,820395 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.