SARDBI23 SAR.SYSTEM2 Index file(s) at 90% utilization

Products

• Deliver
• View

Issue/Introduction

Receiving the following messages: SARDBI23  SAR.SYSTEM2 Index file(s) at 90% utilization. How can I correct the problem? 

Environment

Release:
Component: VIEW

Resolution

"Receiving the following messages: SARDBI23 SYS3.RPT Data file(s) at 82% utilization

    Due to not being familiar with this product, how can this issue be addressed?"

Instructions:  
The SARDBI23 message is generated when the percentage of utilization falls below the value specified in the CA VIEW Initialization parameter, DBTHRESH. It is an indicator on the amount of space in the database that is still available for use.

Steps to resolve the space shortage:
1. Determine if the Index or the Data portion needs more space. 
   
    SARDBI23 (database name) (Index or Data file keyword) (percent of utilization)

   The SARDBI23 message consists of the database name followed by the Index or Data indicator followed by the percentage
   of utilization. Here the keyword DATA in the message indicates that the data portion of the database is involved.  

 2. Try to determine the reason for the increased utilization.   Is it:
     a.  Due to an extremely large report being archived by mistake?
     b.  Due to a run-away job that has been collected into the database? 
     c.  Due to a very large report that was brought back from tape to the disk layer of the database?

 3.  If the increase is due to a large report(s) on the disk portion of the database, delete the disk version of these reports  
      using the "DD" (disk delete) line command

  Note: Do not use the line command of just "D".  This will remove all pointers to the location of the report on the backup
           tape and delete the database.  If the report is accidently deleted completely from the database, it will have to be 
           restored from a backup tape if the tape is still available.

4.  If the utilization is a normal increase of the amount of data stored in the database, you can run a SARDBASE STATUS FULL
     job which will provide information regarding the blocks in the database and as how space is used. 

     For comparison, after a problem report is deleted, you may want to run the STATUS FULL again, to see what space was 
     reclaimed 

 5. If you do not recover enough space or the increased utilization is the result of more reports being stored in the database,      you will need to add more space to the database. 
     a.  Run the SARDBASE ADDDS job. 
     b.  This job can be run with the SARSTC task active. 
     c.  The space will be added dynamically to either the INDEX or the DATA portion of the
          database depending on what keyword is used on the ADDDS statement.

6. Here is the JCL for the SARDBASE ADDDS job.

//STEP1 EXEC PGM=SARDBASE 
//STEPLIB DD DSN=CAI...CVDELOAD,DISP=SHR 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * 
NAME ...DATABASE NAME... 
ADDDS CYL=nnnn BLKSIZE=nnnn VOLSER=xxxxxx UNIT=xxxx INDEX 
ADDDS CYL=nnnn BLKSIZE=nnnn VOLSER=xxxxxx UNIT=xxxx DATA 
/* 
//

The SARDBASE ADDDS job is documented in the CA View Reference Guide chapter on Database utilities.

As always, please contact CA Technologies support for CA View if you have further questions.