SARDBI02 and SARBKT51 Messages Received During OM View Backup

Products

• View

Issue/Introduction

The following messages were received during Phase 2 of a standard View backup:

   SARDBI02  Data file I/O error on VIEW.SYSTEM1 - DCCB=0510E70C ECB=42000000 
   SARBKT51  Sysout group REPORTABC-R01 not deleted due to previous I/O error

Environment

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

Cause

A SARDBI02 error indicates a media problem and the presence of a database error.
A SARBKT51 error indicates that View tried to expire a report and could not.

Resolution

It is possible that the report having the problem can be deleted, with a batch run of SARBCH with transaction of "/DELETE ID=... GEN=... SEQ=... DISK". 

A SARDBASE VERIFY should be run, to see if the condition persists.

Here are steps that can be taken to VERIFY the View database with minimum user impact:

1.  Shut down all View tasks, and shut down any Deliver RMOSTC tasks that perform a direct-write to the View database (RMOPARM ARDHn=DIRECT[/...]).
2.  Run SARDBASE ADDDS and COPY, to create a new and identical database.
3.  Start the View SARSTC task, pointing to the original database.
4.  Run a SARDBASE VERIFY on the identical database.
5.  Run a View backup on the original database.
6.  Shut down the View SARSTC task.
7.  Run SARTDR /TADD, adding the original database backup tape to the identical database.
8.  Run SARDBASE RENAME, to rename the orignal database to "OLD", and rename the identical database to the original name.
9.  Start the View tasks and the Deliver RMOSTC task.

In the event that the database still has problems, the only remaining option is to:

1.  Run SARDBASE ADDDS, to create a new and identical database.
2.  Run SARDBASE RESTORE, using the last good View backup tape, to bring the database as close to the current time as possible.
3.  Run SARDBASE RENAME, to rename the original database to another name.
4.  Run SARDBASE RENAME, to rename the identical database to the original name.