Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2007
    Posts
    3

    Unanswered: WARNING: memory usage in procedure headers

    One of our customers is using Sybase ASE 12.5.2. EBF 11798.

    We recently noticed many messages about memory usage in procedure headers.

    00:00000:00026:2010/06/17 10:15:19.40 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (114) for server process id 26.
    00:00000:00026:2010/06/17 10:15:19.40 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (114) for server process id 26.
    00:00000:00026:2010/06/17 10:15:19.42 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (114) for server process id 26.
    00:00000:00026:2010/06/17 10:15:19.42 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (114) for server process id 26.
    00:00000:00026:2010/06/17 10:15:19.43 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (116) for server process id 26.
    00:00000:00026:2010/06/17 10:15:19.43 server WARNING: memory usage in procedure headers (70)
    does not match memory usage count in Pss (116) for server process id 26.
    It seems to be continually logging this so the log file is really big too. The only advice from Sybase is to ignore the message but we cannot ignore the fact that the log is increasing by several MBs per day.

    This server will go live soon so I want to resolve this quickly. Anyone have any suggestions? I've searched all over google but couldn't find a solid answer. There is also no sp_configure "procedure headers" either...help?

  2. #2
    Join Date
    Oct 2002
    Location
    Baghdad, Iraq
    Posts
    697
    The only advice from Sybase is to ignore the message but we cannot ignore the fact that the log is increasing by several MBs per day.
    Sure you can. Just rotate your log files, and gzip the old ones.
    Last edited by sco08y; 06-25-10 at 15:48.

  3. #3
    Join Date
    Oct 2007
    Posts
    3
    Quote Originally Posted by sco08y View Post
    Sure you can. Just rotate your log files, and gzip the old ones.
    That requires stopping the ASE service, which easy as it may sound, is not so straightforward on a production system and is merely a way to get by. What if it wasnt rotated and it used up all the disk space?

    Any ideas for solving the problem at hand?

  4. #4
    Join Date
    Aug 2010
    Posts
    1
    You can suppress the messages by using the traceflag 720.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •