SARDBI23 Database Index file(s) utilization
Article ID: 16059
Updated On:
Products
Issue/Introduction
The SARDBI23 is issued when database utilization reaches or exceeds the value specified in the CA VIEW initialization parameter, DBTHRESH.
Environment
- Output Management View 14.0
Cause
High Retention: Reports kept for long periods (e.g., RETPD=3650 for 10 years) consume significant index control records.
Increased Workload: Growth in the number of jobs archived to the database.
Resolution
1.Verify Target File Component: Check the SARDBI23 console message to confirm whether INDEX or DATA exceeded the DBTHRESH settings.
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.
SARDBI23 (database name) (Index or Data file keyword) (percent of utilization)
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 accidentally 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
//STEP1 EXEC PGM=SARDBASE
//STEPLIB DD DSN=YOUR.VIEW.CVDELOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
NAME YOUR.VIEW.DB.HLQ
STATUS FULL
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
/*
//
Additional Information
For further assistance with SARDBI23 see the [OM View - Diagnostics and error messages - SARDBI23 - Documentation](https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/view-messages/messages/diagnostic-and-error-messages/sardbi23.html)
For additional guidance on how to use the SARDBASE utility see the [OM View - SARDBASE utility - Documentation] (https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-view/14-0/reference/database-utilities/sardbase-utility-to-maintain-the-database.html)
For more information regarding the SARDBASEcontrol statement STATUS see the [OM View - SARDBASE utility STATUS - Documentation] (https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-view/14-0/reference/database-utilities/sardbase-utility-to-maintain-the-database/status.html)
For more information regarding the SARDBASEcontrol statement ADDS see the[OM View - SARDBASE utility ADDS - Documentation] (https://techdocs.broadcom.com/us/en/ca-mainframe-software/traditional-management/ca-view/14-0/reference/database-utilities/sardbase-utility-to-maintain-the-database/addds.html)
Feedback
