Results 1 to 6 of 6
  1. #1
    Join Date
    May 2017
    Posts
    3

    Unanswered: Roll Forward pending after san disk suddenly lost

    Please advise how to fix this problem. We don't have any backup. :'(

    DB2 version 6.1

  2. #2
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Post the output of the db2level command (when run as the DB2-instance owner).
    Post the relevant recent entries in the db2diag file .

  3. #3
    Join Date
    Jul 2016
    Location
    Moscow
    Posts
    294
    Provided Answers: 45
    Rollforward pending doesn't require to restore something from a backup.
    Just run the corresponding rollforward command and post here the results.
    Regards,
    Mark.

  4. #4
    Join Date
    May 2017
    Posts
    3
    Thank you everyone
    I've attached roll forward in progress capture screen and waiting for db2diag
    Attached Thumbnails Attached Thumbnails db2.png  

  5. #5
    Join Date
    May 2017
    Posts
    3
    Quote Originally Posted by mark.bb View Post
    Rollforward pending doesn't require to restore something from a backup.
    Just run the corresponding rollforward command and post here the results.
    $ db2level
    DB21085I Instance "archive" uses DB2 code release "SQL06010" with level
    identifier "01030104" and informational tokens "DB2 v6.1.0.6", "s991030" and
    "U468276".
    -----------------------------------------------------------------------
    db2log:

    2017-03-27-18.36.02.580272 Instance:archive Node:000
    PID:17560(db2spmrm) Appid:none
    oper_system_services sqloopenp Probe:36

    errno: 0000 0011 ....


    2017-03-27-18.37.08.807316 Instance:archive Node:000
    PID:27842(db2bp) Appid:*LOCAL.archive.170327113635
    oper_system_services sqlowque Probe:5

    0000 0004 ....


    2017-03-27-18.38.37.262053 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlufrol Probe:100 Database:ARCHIVE

    Rollforward has been initiated

    2017-03-27-18.38.37.315792 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlufrol Probe:120 Database:ARCHIVE

    Invoking tablespace rollforward forward recovery

    2017-03-27-18.38.40.615721 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlpForwardRecoveryTblSpace Probe:20 Database:ARCHIVE

    Start lsn: 0058 bc6a b13c .Xผjฑ<


    2017-03-27-18.38.40.675747 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlpForwardRecoveryTblSpace Probe:20 Database:ARCHIVE

    Stop lsn: 0058 bc8d 800c .Xผ...


    2017-03-27-18.38.40.735825 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlpForwardRecoveryTblSpace Probe:20 Database:ARCHIVE

    Restarted at lsn: 0000 0000 0000 ......


    2017-03-27-18.38.40.802649 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlpALR_ReadPagesDisk Probe:160 Database:ARCHIVE
    DIA9999E An internal error occurred. Report the following error code : "
    4".

    2017-03-27-18.38.40.813827 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlprfwdt Probe:40 Database:ARCHIVE
    DIA9999E An internal error occurred. Report the following error code : "
    4".

    2017-03-27-18.38.40.837975 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlpForwardRecoveryTblSpace Probe:30 Database:ARCHIVE
    DIA1531C Roll forward recovery failed, LSN was "".

    ZRC=FFFF8578

    2017-03-27-18.38.40.902088 Instance:archive Node:000
    PID:19612(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlufrol Probe:130 Database:ARCHIVE

    Rollforward iteration completed

    2017-03-27-19.09.42.275424 Instance:archive Node:000
    PID:26066(db2bp) Appid:*LOCAL.archive.170327113834
    oper_system_services sqlowque Probe:5

    0000 0004 ....


    2017-03-27-19.21.13.985821 Instance:archive Node:000
    PID:27626(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlufrol Probe:100 Database:ARCHIVE

    Rollforward has been initiated

    2017-03-27-19.21.14.050977 Instance:archive Node:000
    PID:27626(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    data_protection sqlufrol Probe:120 Database:ARCHIVE

    Invoking tablespace rollforward forward recovery

    2017-03-27-19.21.17.364784 Instance:archive Node:000
    PID:27626(db2agent (ARCHIVE)) Appid:*LOCAL.archive.170327113834
    recovery_manager sqlpForwardRecoveryTblSpace Probe:20 Database:ARCHIVE

    Start lsn: 0058 bc6a b13c .Xผjฑ<

  6. #6
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    What was the completion code/status/message for the rollforward? If it completed, post the full command-line you used, and the final messages for rollforward in the db2diag.


    I think DB2 V6.1 was shipped around 1997 or 1998, so I've not seen one of those still running in 2017, that's quite something, even more so if there is no recent backup as you posted earlier.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •