My Oracle Support Banner

RDBPROD: Methods to Overcome Discarded Pages Caused by AIP Record Length Differences (Doc ID 258251.1)

Last updated on APRIL 16, 2024

Applies to:

Oracle Rdb Server on OpenVMS - Version 7.0 and later
HP OpenVMS Alpha
HP OpenVMS VAX
HP OpenVMS Itanium



Goal

There is a table in the database for which excessive discarded pages are observed during inserts. This causes performance degradation. One reason could be that the record length in the area inventory page (AIP) differs from the real record length. Adding a column to the table is one cause of this difference.

In this case, the table should be reorganized to avoid discarded pages. This can be done by changing the record length in the AIP, or by changing the threshold value for the logical area.

Other causes for excessive discarded pages could be locked free space in the area, or incorrect threshold settings on that area.

See section 3.10 in the Oracle Rdb7 Guide to Database Performance and Tuning, or the My Oracle Support article that was incorporated into the manual, which discuss excessive pages checked.

This article describes how to change the record length and/or the threshold value to fix a problem where the AIP record length differs from the real record length. See the Guide to Database Performance and Tuning for details on the other two causes.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 1. RMU/SET AIP
 2. RMU/REPAIR/INITIALIZE=LAREA_PARAMETERS=Option-file
 3. RMU/UNLOAD, DROP TABLE, CREATE TABLE and RMU/LOAD
 4. ALTER STORAGE MAP
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.