Chat now with support
Chat with Support

Spotlight on SAP ASE 2.12 - Getting Started Guide

Catalog Cache Overflows alarm

The Catalog Cache Overflows alarm becomes active when an insert fails because the cache is full. Catalog cache space becomes available again when table descriptor information that is not being used is purged from the cache.

Note: Once a transaction has a catalog cache overflow event, every ensuing attempt by the same transaction to insert table descriptor information into the cache will also result in an overflow. The transaction involved will continue, but its descriptor information will not be inserted.

This alarm has been predefined with a Low severity level. The underlying metric for this alarm can be adjusted to suit your environment by using the Metric Editor.

What you can do

  • Large overflows—The cache could be of inadequate size for the workload. Try enlarging the cache to improve performance.

  • Large transactions—If you have transactions that are compiling a large number of SQL statements that reference a lot of tables, views, and aliases in a single unit of work, try compiling fewer SQL statements in a single transaction. This may improve the performance of the cache without having to increase its size.

  • Binding packages—If you are binding packages that contain a large number of SQL statements that look up a lot of tables, views or aliases, try splitting your packages to include fewer SQL statements. This may improve the performance of the cache without having to increase its size.

Click the Catalog Cache component to open the Databases drilldown. This drilldown provides details about the database or partition you are monitoring. The Caching tab on the drilldown is in immediate focus to help you pinpoint problems related to catalog cache usage in the database or partition.

 

Related topics

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating