Is there any limitation for the history dataset size within Sysview for Db2
search cancel

Is there any limitation for the history dataset size within Sysview for Db2

book

Article ID: 16578

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Is there any kind of limitation on the size of the Sysview Performance Management Option for Db2 for z/OS (IDB2) history dataset?
Will IDB2 be able to handle very large files allocations without performance degradation or any other issues?
Is there an option to compress IDB2 data?

Resolution

IDB2 can handle a 8TB (10 millions tracks) dataset fine without any performance degradation.

The following information is taken from the IDB2 documentation:

HISTORY-COMPRESSION=[YES|NO] 

Specifies whether to compress the records that are written to the history data sets. SYSVIEW for DB2 uses hardware compression to compress history
records, which generate little CPU overhead. The option can be turned on and off without reallocating the ACCT and STAT files. 

These files can have both uncompressed and compressed records mixed in the same file. 

Default: YES