CA View - SARDBI02 errors
Article ID: 187192
Updated On:
Products
Deliver
View
Issue/Introduction
The client receives intermittent SARDBI02 errors, during the running of a View backup cycle:
. SARDBI02 Sysout group XXXXXXXX-R01 skipped due to previous I/O error
As well, they saw a SARDBI17 error:
. *SARDBI17 Database space for file deleted or reused, SFBKEY=X'D1F4F3E7E7F2F0F760D9F0F140404040
. SARBKT50 Sysout group XXXXXXXX-R01 skipped due to previous I/O error
What can be done to stop these errors from occurring again?
Environment
Release : 12.2
Component : CA View
Resolution
A SARDBI17 message occurs when there is the browsing of a report that has been deleted (by someone or by the backup cycle).
The space the deleted report occupied is then reused, and the original report no longer owns that space.
As, most likely, it was the View backup cycle expiring the report, the condition most likely coincides with the timing of the backup cycle.
For a SARDBI02 message, there sounds is something possibly wrong with the pointers in the database.
To resolve a SARDBI02 condition, the suggestion is to run a SARDBASE VERIFY:
//XXXXXXXX JOB ...
//SARDBASE EXEC PGM=SARDBASE,PARM='VIEW_HLQ' <=== MODIFY DB NAME
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== MODIFY, IF USED
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
VERIFY
/*
//
==> Note: Before running the VERIFY, it is necessary to bring down all View tasks, as well as any CA Deliver tasks that write directly to the View database.
The space the deleted report occupied is then reused, and the original report no longer owns that space.
As, most likely, it was the View backup cycle expiring the report, the condition most likely coincides with the timing of the backup cycle.
For a SARDBI02 message, there sounds is something possibly wrong with the pointers in the database.
To resolve a SARDBI02 condition, the suggestion is to run a SARDBASE VERIFY:
//XXXXXXXX JOB ...
//SARDBASE EXEC PGM=SARDBASE,PARM='VIEW_HLQ' <=== MODIFY DB NAME
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== MODIFY, IF USED
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
VERIFY
/*
//
==> Note: Before running the VERIFY, it is necessary to bring down all View tasks, as well as any CA Deliver tasks that write directly to the View database.
Feedback
Yes
No
Powered by
