Try OpenEdge Now
skip to main content
New Information
RDBMS
 

RDBMS

Release 11.7.1 includes the following enhancements to the OpenEdge RDBMS:
*Diagnostic Data Collection — Diagnostic Data Collection allows for a variety of critical information to be saved when certain events, such as lock table overflow, BI threshold, or a system error, occur. Collecting this data can aid in the analysis of the root cause of an event. Almost all aspects of this feature are customizable, including: the events for data collection, the amount of data collected, and the formatting of the data.
For more information, see the Web paper, Database Diagnostic Data Collection.
*PROUTIL IDXCHECK Validate index against free cluster — The Validate index against free cluster option provides a quick, deterministic check of index errors in special schemas (encryption, auditing, and key events).

PROUTIL IDXCHECK details

Running the Validate index against free cluster option of PROUTIL IDXCHECK detects if index entries for the special schemas have been incorrectly deleted by PROUTIL MVSCH. These errors only exist if you executed PROUTIL MVSCH on your database with OpenEdge Releases between 11.6.0 and 11.6.3 (with no hotfix). Any 11.6.3 hotfix or a later release of OpenEdge does not cause this issue.

Running PROUTIL IDXCHECK

To run PROUTIL IDXCHECK with the new option, use the following steps:
1. Start PROUTIL as shown:
proutil my-dbname -C idxcheck
The following menu appears:
Index Check Utility
===================

Select one of the following:
--------------------
All (a/A) - Choose all the indexes
Some (s/S) - Choose only some of the indexes
By Area (r/R) - Choose indexes in selected areas
By Schema (c/C) - Choose indexes by schema owners
By Table (t/T) - Choose indexes in selected tables
--------------------
Validation (o/O) - Change validation options
--------------------
Quit (q/Q)

Enter your selection:
2. Select Validation by typing o or O. The following menu appears:
Validation Options
----------------
* 1 - Validate physical consistency of index blocks
* 2 - Validate keys for each record
3 - Validate record for each key
* 4 - Validate key order
5 - Validate tree
6 - Validate index against free cluster
R - Reset error limit, current: 500
C - Continue to execute
Q - Quit
3. Select Validate index against free cluster by entering 6. You can also de-select the default options (1,2,4) by entering those numbers.
4. After selecting and de-selecting options, enter C to return to the main menu.
5. From the main menu select the indexes to check and execute the check.

PROUTIL IDXCHECK output

Running the new check writes the following to the screen and log file:
Validate index against free cluster

Index -1610 (PUB._Constraint-Keys, _Con-Key-Ord): Validating the tree.
If any errors are detected, the following is written to the screen and log file:
*If the index is a non-multi-tenant or table-partitioned index:
Index (index number)(owner.table, index name): object not found in the area.
*If the index is a multi-tenant index:
Index (index number)(owner.table, index name) for tenant name: object not found in the area.
*If the index is a table-partitioned index:
Index (index number)(owner.table, TP index info): object not found in the area.
Warning: If any errors are reported, contact Progress Technical Support for guidance on a recovery strategy for your database.