PN83421: ASN0122E ERROR READING WARM START INFO OR LOG. CAPTURE FOR MVS WILL TERMINATE RESULTING IN COLD START AND FULL REFRESH

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After stopping Capture/MVS and attempting to restart it after
    approximately 2 minutes, ASN0122E error occurred reading warm
    start info or log was received.
    Because needed RBA 000000000459F168E737 was not on active log at
    the time, this forced to Capture/MVS to coldstart and full
    refresh ALL tables.
    The real problem here is not that Capture is unable to read the
    archived log, the real problem is that the subsequent coldstart
    and read of n number of logs takes a huge amount of time.  This
    is unacceptable in a situation where Capture is shutdown only
    for two minutes.
    

Local fix

  • Create a small table with the change data capture attribute.
    Register it as any other DPropR soruce table, and write a small
    application that commits an update to this table, say, every 5
    minutes worth of log data. Capture/MVS will always be assured
    seeing a fairly-current RBA in the UOW table.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Capture/MVS Release 2.0 Customers with       *
    *                 described symptom.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: ASN1022E ERROR READING WARM START INFO  *
    *                      OR LOG.  CAPTURE FOR MVS WILL           *
    *                      TERMINATE RESULTING IN COLD START AND   *
    *                      FULL REFRESH                            *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The real problem here is not that Capture is unable to read the
    archived log, the real problem is that the subsequent coldstart
    and read of n number of logs takes a huge amount of time.  This
    is unacceptable in a situation where Capture is shutdown only
    for two minutes and logs are archived.
    

Problem conclusion

  • To remedy this problem, a new warm start function has been
    added. To use option WRMSKPM specify it instead of WARMNS or
    WARM. Two error conditions can keep user from successfully
    warm starting :
    
    1. If the warm start point is beyond the lag limit
    
    2. If log read error occurred during warm start
       because the warm start point is beyond reach ( for
       example , it has been archived in a DB2 3.1 system)
    
       With the option Capture can skip to the end of the current
       active log if option is WRMSKPM and user requests it or
       terminate if the user prefers not to skip to the end
       of the active log.
    
    The way WRMSKPM works:
    
    If error #1 the user gets message on MVS console requesting
    response:
     'LAG LIMIT EXCEEDED IN WARM START. TO START READING FROM END
     OF LOG RESPOND YES , ANY OTHER RESPONSE STOPS CAPTURE.'
    
    If error #2 the user gets message on MVS console requesting
    response:
     'ERROR READING LOG IN WARM START. TO START READING FROM END
     OF LOG RESPOND YES , ANY OTHER RESPONSE STOPS CAPTURE.'
    
    If the user replies YES,
     Capture starts reading the log at the end of the active log.
     By doing this, Capture will skip all the old log data so will
     miss any log records written between the last RBA from warm
     start and the current end of log. However, Capture does not
     DELETE from the CD and UOW tables which causes Apply to
     perform full refresh under some conditions.
    
     The data between the last RBA processed by Capture when it
     was stopped and the RBA at the end of the current active log
     when Capture receives the YES response will be skipped. Thus
     it is the user's responsibility to ensure no data of interest
     will be lost.
    
     If the user does not reply YES,
     Capture terminates (just like WARMNS today).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PN83421

  • Reported component name

    DPROPR CAPTURE/

  • Reported component ID

    565507600

  • Reported release

    120

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1996-04-12

  • Closed date

    1996-06-25

  • Last modified date

    2013-03-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UN92237

Modules/Macros

  • ASNLDB23 ASNLDB31 ASNLDB41 ASNLEMSG ASNLMN23
    ASNLMN31 ASNLMN41 ASNLWTO
    

Fix information

  • Fixed component name

    DPROPR CAPTURE/

  • Fixed component ID

    565507600

Applicable component levels

  • R120 PSY UN92236

       UP96/07/24 P F607

  • R121 PSY UN92237

       UP96/07/24 P F607



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Replication Server

Software version:

120

Reference #:

PN83421

Modified date:

2013-03-07

Translate my page

Machine Translation

Content navigation