Forums & Discussions Home

    A place for members, communities, and committees to have discussions online and via e-mail.
    Click a category or topic to below to start the conversation...

    You are currently in view only mode for this forum. Please click the appropriate below to login as a member and participate. If you are not a member, please CLICK HERE for more information.


    Jan 16
    2001

    DB2 V6 - OS/390 Recovery Questions

    William Moss
    [Aetna, Inc]
    We have just upgraded to DB2 V6 and it crashed after running for two days.
    After a successful restart of DB2, there were 75 DSNI023 messages like this
    one:

    DSNI023I *DB3D DSNIERST PAGESET DSM1P000.XM1H0004
    PART (n/a)
    IS AREST ON BEHALF OF UR 0266D734DD3F. BACKOUT TO
    LRSN B5411CD496D4 IS REQUIRED.

    DB2 performed 74 successful backouts. The only one it didn't do was the one
    listed above. It is an indexspace for an NPI and when I display the index,
    it looks good and it is being used successfully by application programs.


    Another unrelated but unusual message we received was:

    DSNP012I *DB3D DSNPCNP0 - ERROR IN VSAM CATALOG
    LOCATE FUNCTION FOR F1BEPO3G.DSNDBC.DQFEP000.R154000.J0001.A001
    CTLGRC=00000008
    CTLGRSN=C5C7002A
    CONNECTION-ID=PSO4CICG, CORRELATION-ID=ENTRSBM10052,
    LUW-ID=*

    What is a J0001.A001 dataset ?

    Thanks,

    Bill Moss
    Aetna/US Healthcare



    James Campbell
    William,

    from a lack of experience with these problems, some items:

    DSNI023I - when you "display[ed] the index", I presume did you mean "-DIS
    DB(DSM1P000) SP(XM1H0004)". Did you include "ADVISORY" or "AREST" on the
    command? We had these (although with RESTP) in 'normal' operations and had
    to rebuild the affected indexes.

    J0001.A001 dataset - aren't these the clusters that on-line reorg creates to
    store the re-orged ts? After the reorg finishes, the I0001 cluster
    (pre-reorg) is deleted and the J0001 cluster is renamed to I0001. (BTW, I
    recall from AP IDUG (too lazy to check the foils), that, in V7, the J0001
    clusters will not necessarily be renamed. So in a DR, some of the clusters
    will be I0001 and some J0001 - only the DB2 catalog/directory will know for
    sure which is needed. But don't quote me on this.) From the return/reason
    codes it appears as though this cluster got lost or DB2 lost track of where
    it was. What were you doing?

    /* standard disclaimer */
    James Campbell
    DBA
    Hansen Corporation, Doncaster
    +61 3 9843 8442
    [login to unmask email]
    -----Original Message-----
    From: Moss, William [mailto:[login to unmask email]
    Sent: Wednesday, January 17, 2001 12:55 PM
    To: [login to unmask email]
    Subject: [DB2-L] DB2 V6 - OS/390 Recovery Questions


    We have just upgraded to DB2 V6 and it crashed after running for two days.
    After a successful restart of DB2, there were 75 DSNI023 messages like this
    one:

    DSNI023I *DB3D DSNIERST PAGESET DSM1P000.XM1H0004
    PART (n/a)
    IS AREST ON BEHALF OF UR 0266D734DD3F. BACKOUT TO
    LRSN B5411CD496D4 IS REQUIRED.

    DB2 performed 74 successful backouts. The only one it didn't do was the one
    listed above. It is an indexspace for an NPI and when I display the index,
    it looks good and it is being used successfully by application programs.


    Another unrelated but unusual message we received was:

    DSNP012I *DB3D DSNPCNP0 - ERROR IN VSAM CATALOG
    LOCATE FUNCTION FOR F1BEPO3G.DSNDBC.DQFEP000.R154000.J0001.A001
    CTLGRC=00000008
    CTLGRSN=C5C7002A
    CONNECTION-ID=PSO4CICG, CORRELATION-ID=ENTRSBM10052,
    LUW-ID=*

    What is a J0001.A001 dataset ?

    Thanks,

    Bill Moss
    Aetna/US Healthcare







    **********************************************************************
    This email and any files transmitted with it are confidential and
    intended solely for the use of the individual or entity to whom they
    are addressed. If you have received this email in error please notify
    the system manager.

    This footnote also confirms that this email message has been swept by
    MIMEsweeper for the presence of computer viruses.

    www.mimesweeper.com
    **********************************************************************



    Max Scarpa
    [Cx SpA]
    Did you ever executed a COPY DFSMSdss with RENUNC of some DB2 tablespace ?

    Regards
    Max Scarpa





    "Moss,
    William" To: [login to unmask email]
    <[login to unmask email] cc:
    COM> Subject: DB2 V6 - OS/390 Recovery Questions
    Sent by: DB2
    Data Base
    Discussion
    List
    <[login to unmask email]
    OM>


    17/01/01
    02.54
    Please
    respond to
    DB2 Data Base
    Discussion
    List





    We have just upgraded to DB2 V6 and it crashed after running for two days.
    After a successful restart of DB2, there were 75 DSNI023 messages like this
    one:

    DSNI023I *DB3D DSNIERST PAGESET DSM1P000.XM1H0004
    PART (n/a)
    IS AREST ON BEHALF OF UR 0266D734DD3F. BACKOUT TO
    LRSN B5411CD496D4 IS REQUIRED.

    DB2 performed 74 successful backouts. The only one it didn't do was the one
    listed above. It is an indexspace for an NPI and when I display the index,
    it looks good and it is being used successfully by application programs.


    Another unrelated but unusual message we received was:

    DSNP012I *DB3D DSNPCNP0 - ERROR IN VSAM CATALOG
    LOCATE FUNCTION FOR F1BEPO3G.DSNDBC.DQFEP000.R154000.J0001.A001
    CTLGRC=00000008
    CTLGRSN=C5C7002A
    CONNECTION-ID=PSO4CICG, CORRELATION-ID=ENTRSBM10052,
    LUW-ID=*

    What is a J0001.A001 dataset ?

    Thanks,

    Bill Moss
    Aetna/US Healthcare








    [login to unmask email]
    Here are a couple of earlier responses from the list about AREST status on
    a TS or IS

    <snip>
    DB2 V6 Command Reference manual indicates the following:

    AREST indicates that the object ( a table space , index space or a physical
    partition of a table space or index space ) is in a Advisory Restart
    Pending State. If backout activity against the object is not already
    underway, it should be initiated either by issuing the RECOVER POSTPONED
    command or by recycling the system with the system parameter LBACKOUT=AUTO
    ************
    We also encountered this problem after an Abend involving parallelism. We
    still have an open problem with IBM on it. I am the Sysprog, but the
    DBA's here chose to work around the AREST by Dropping/ReCreating the
    tablespace and restoring with DSN1COPY from Image Copies.
    <end snip>

    HTH




    "Moss, William" <[login to unmask email]>@RYCI.COM> on 2001/01/16 07:54:45 PM

    Please respond to DB2 Data Base Discussion List <[login to unmask email]>

    Sent by: DB2 Data Base Discussion List <[login to unmask email]>


    To: [login to unmask email]
    cc:
    Subject: DB2 V6 - OS/390 Recovery Questions


    We have just upgraded to DB2 V6 and it crashed after running for two days.
    After a successful restart of DB2, there were 75 DSNI023 messages like this
    one:

    DSNI023I *DB3D DSNIERST PAGESET DSM1P000.XM1H0004
    PART (n/a)
    IS AREST ON BEHALF OF UR 0266D734DD3F. BACKOUT TO
    LRSN B5411CD496D4 IS REQUIRED.

    DB2 performed 74 successful backouts. The only one it didn't do was the one
    listed above. It is an indexspace for an NPI and when I display the index,
    it looks good and it is being used successfully by application programs.


    Another unrelated but unusual message we received was:

    DSNP012I *DB3D DSNPCNP0 - ERROR IN VSAM CATALOG
    LOCATE FUNCTION FOR F1BEPO3G.DSNDBC.DQFEP000.R154000.J0001.A001
    CTLGRC=00000008
    CTLGRSN=C5C7002A
    CONNECTION-ID=PSO4CICG, CORRELATION-ID=ENTRSBM10052,
    LUW-ID=*

    What is a J0001.A001 dataset ?

    Thanks,

    Bill Moss
    Aetna/US Healthcare








    [login to unmask email]
    The 'J' at the start of the fifth node of the dataset name ( the 'instance
    node' ) is used for the switching of dataset names during online reorg. With
    DB2 Vers 7 the 1st char of the instance node can alternate with values of
    'I' or 'J'. This was to be used for the 'fastswitch yes' option , but I
    thought that was for version 7 and not vers 6 ( although, sometimes they
    update the prior versions with features from later releases if demand is
    there ). As Max has suggested, DSS or IDCAMS could have also been used...

    -----Original Message-----
    From: Max Scarpa [mailto:[login to unmask email]
    Sent: Wednesday, January 17, 2001 1:45 AM
    To: [login to unmask email]
    Subject: Re: DB2 V6 - OS/390 Recovery Questions


    Did you ever executed a COPY DFSMSdss with RENUNC of some DB2 tablespace ?

    Regards
    Max Scarpa





    "Moss,
    William" To: [login to unmask email]
    <[login to unmask email] cc:
    COM> Subject: DB2 V6 - OS/390
    Recovery Questions
    Sent by: DB2
    Data Base
    Discussion
    List
    <[login to unmask email]
    OM>


    17/01/01
    02.54
    Please
    respond to
    DB2 Data Base
    Discussion
    List





    We have just upgraded to DB2 V6 and it crashed after running for two days.
    After a successful restart of DB2, there were 75 DSNI023 messages like this
    one:

    DSNI023I *DB3D DSNIERST PAGESET DSM1P000.XM1H0004
    PART (n/a)
    IS AREST ON BEHALF OF UR 0266D734DD3F. BACKOUT TO
    LRSN B5411CD496D4 IS REQUIRED.

    DB2 performed 74 successful backouts. The only one it didn't do was the one
    listed above. It is an indexspace for an NPI and when I display the index,
    it looks good and it is being used successfully by application programs.


    Another unrelated but unusual message we received was:

    DSNP012I *DB3D DSNPCNP0 - ERROR IN VSAM CATALOG
    LOCATE FUNCTION FOR F1BEPO3G.DSNDBC.DQFEP000.R154000.J0001.A001
    CTLGRC=00000008
    CTLGRSN=C5C7002A
    CONNECTION-ID=PSO4CICG, CORRELATION-ID=ENTRSBM10052,
    LUW-ID=*

    What is a J0001.A001 dataset ?

    Thanks,

    Bill Moss
    Aetna/US Healthcare














    All Times America/New_York

    Copyright © 2014 IDUG. All Rights Reserved

    All material, files, logos and trademarks within this site are properties of their respective organizations.

    Terms of Service - Privacy Policy - Contact