SAP Knowledge Base Article - Preview

1945940 - Error 1204 followed by a stacktrace with lock_do_logical() and login() - ASE 15.7

Symptom

  • Adaptive Server Enterprise (ASE) reports an Error 1204 followed by an Internal Error and a stacktrace:

Error: 1204, Severity: 17, State: 2 occurred for User 'SAPSR3'. Client IP address is 'XXX.XXX.XXX.XXX'.
SQL Text: select top 1 name from sysobjects
SQL Text: select top 1 name from sysobjects
Error: 1204, Severity: 17, State: 2 occurred for User 'SAPSR3'. Client IP address is 'XXX.XXX.XXX.XXX'.
SQL Text:
login: Process with spid 175 could not connect to the ASE which has temporarily run out of locks.
Internal Error: login process should not acquire any lock during dirty read process for user id and user role

  • The stacktrace includes modules:

lock_do_logical()
sdes_scan_setup()
attrib_getrow()
etc_cleanup_task()
terminate_process()
quitfn()
login()


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

KBA , memory corruption , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Bug Filed

About this page

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

Search for additional results

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