ERR-11049 ( 69705) Too many pages were allocated#
Overview#
This document explains the cause of the ERR-11049 ( 69705) Too many pages were allocated error and how to resolve it when a memory tablespace reaches the configured memory limit and no additional pages can be allocated.
Version#
All the versions of Altibase
Symptom#
The following error occurs when INSERT, UPDATE, DELETE or other DML statements are executed on a memory table.
ERR-11049 ( 69705) Too many pages were allocated ( Maximum Number of Pages= number).
Cause#
This error occurs when the total memory used by all memory tablespaces reaches MEM_MAX_DB_SIZE and no additional memory pages can be allocated.
MEM_MAX_DB_SIZE specifies the maximum amount of memory that can be used by all memory tablespaces.
Memory usage can increase because of large-volume data modification operations. It can also increase when long-running transactions prevent old MVCC versions from being reclaimed.
Action#
First, identify the SQL statement that caused the error and the target table.
Check the usage and free pages of the memory tablespace that contains the target table. Then check whether any tables are using a large amount of memory and whether large-volume data modification operations have been performed.
Also check whether any long-running transactions are preventing old MVCC versions from being reclaimed.
If a large-volume data modification operation is in progress, stop or complete the operation. Terminate unnecessary long-running transactions so that memory can be reclaimed.
Refer to the following sections in the Altibase Monitoring Query Guide to check memory usage and GC status.
- Memory Tablespace Usage
- Total Memory Tablespace Usage
- Memory Table Usage
- Memory Database GC Gap
- Queries in the Transaction That Memory Database GC Is Waiting For
If sufficient memory cannot be reclaimed while the server is running, increase MEM_MAX_DB_SIZE and restart the Altibase server.
For instructions on changing MEM_MAX_DB_SIZE, refer to the following FAQ.