Symptom
- Dump history file contains 'dump.error' messages with invalid timestamp at a time when ASE reports 1204 'out of locks
- Sample output from dumphist file:
3|7|db1|0|Jan 1 1900 12:00:00:000AM|Aug 20 2018 7:37:02:720AM|Aug 20 2018 7:37:02:720AM|dump.error|0|*|0|0|2| |Aug 20 2018 7:37:02:720AM
3|6|db2|0|Jan 1 1900 12:00:00:000AM|Aug 20 2018 7:37:02:796AM|Aug 20 2018 7:37:02:796AM|dump.error|0|*|0|0|2| |Aug 20 2018 7:37:02:796AM
3|7|db1|0|Jan 1 1900 12:00:00:000AM|Aug 20 2018 7:38:02:710AM|Aug 20 2018 7:38:02:710AM|dump.error|0|*|0|0|2| |Aug 20 2018 7:38:02:710AM
(repeated)
- The dumphist messages correspond exactly to timeframe of ASE reporting error 1204:
Error: 1204, Severity: 17, State: 2 occurred for User 'test1'. Client IP address is '123.456.789.123'.
Error: 1204, Severity: 17, State: 1
ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.
ckpt2: Checkpoint process temporarily out of locks.
Read more...
Product
Keywords
KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.