A fix is available
APAR status
Closed as program error.
Error description
DSNJ106I Log Read Error DSNAME=NB2AV.NA02.LOGCOPY1.DS01, LOGRBA=001905BF7000, ERROR STATUS=00201110 If the active log data set is striped (extended format), the ERROR STATUS could be 00500E10 RC00500E10
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2. * **************************************************************** * PROBLEM DESCRIPTION: MSGDSNJ106I with STATUS=00201110 * * reading an active log data set that * * has not been completely formatted * * (eg. HARBA > HURBA ). * **************************************************************** * RECOMMENDATION: * **************************************************************** The user had reallocated larger log data sets and REPRO'ed the original, smaller log data sets into the larger active log data sets. After the REPRO, the high-used (high formatted) RBA will be less than the high-allocated RBA (HURBA < HARBA). DB2 will format the unformatted area ahead of the log writes, but the user was running DPROPr Capture that was constantly reading up to the end of the log. DB2 attempts to maximize the read I/Os and can request a number of log CIs that will extend into the unformatted area of the data set. MMRCIERR no longer contains the error CI, so DB2 can not recover from the extent error, which results in a log read failure with MSGDSNJ106I and STATUS=00201110. ( DSNJ106I ) This problem will not occur if new log data sets are formatted with the DSNJLOGF utility, or after DB2 has completely formatted the log data set the first time it has filled.
Problem conclusion
DB2 will use the log data set high formatted RBA to limit the log reads for an active log data set that is not completely formatted. Also, an ABEND0C4 can occur in IEAVTRG1 +01C4 after FRR DSNRCAFR returns to RTM in key 7. DSNRCAFR has been changed to switch back to key 0 before returning to RTM.
Temporary fix
Comments
APAR Information
APAR number
PK30290
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-08-22
Closed date
2006-09-07
Last modified date
2008-01-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK17828 UK17829
Modules/Macros
DSNJR006 DSNRCAFR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 January 2008