Symptom
- Execution of a SQL statement raises error 706 which may be preceded by a warning:
WARNING: memory usage in procedure headers (1) does not match memory usage count in Pss (2) for server process id 668.
Error: 706, Severity: 20, State: 3
Process 668 tried to remove PROC_HDR0x1a296d000 that it does not hold in Pss
- The stack trace indicates that the last error was 706, no previous error, and a partial of the SQL executing was 'select suser_name()":
************************************
SQL causing error : select suser_name()
************************************
SQL Text: select suser_name()
curdb = 31516 tempdb = 14 pstat = 0x10000 p2stat = 0x101000
p3stat = 0x800 p4stat = 0x0 p5stat = 0x8 p6stat = 0x10 p7stat = 0x10000
lasterror = 706 preverror = 0 transtate = 1
curcmd = 0 program = Microsoft ISQL/w
extended error information: hostname: hostname login: yourname
rm_prochdr__fdpr_1
memfree+0x88()
hdl_stack+0x0
...
- Note: The complete stack trace is available under Attachments.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 15.7
Product
Keywords
memory, cache, allocation, deallocation, corruption , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem
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.