Database Index Space Filling Up or Full OM View
search cancel

Database Index Space Filling Up or Full OM View

book

Article ID: 46212

calendar_today

Updated On:

Products

View

Issue/Introduction

Recently, several View databases indicated that their index space was filling. This has occurred with databases on different systems. They have gone for years without the Indexes filling up on any system.

Environment

  • View®
  • OM View for z
  • Output Management View® for z/OS

Cause

Over time, it is possible for View indexes to experience usage "creep", so that at some point more index space will need to be added.  Usage "creep" is especially possible with databases that collect JCL as, though they do not contain large reports, they will contain many reports.  As approximately 2000 bytes of index records are generated for each report in the database, the index could understandably fill up over time. In a View database's SARDBASE STATUS FULL statistics, a block is consider "used" even if it is only 1% full. With that, a percent utilization of a certain value could remain the same over some time.

Resolution

They used SARDBASE ADDDS INDEX, to add index space to the affected databases.