Last commited transaction less then backup image timestamp after restore with rollforward?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • t2581@hotmail.com

    #1

    Last commited transaction less then backup image timestamp after restore with rollforward?

    Hi ,
    I run restore with rollforward
    In job in output, last commited transaction time less then backup image
    time
    Is it normal ?

    RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
    "D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\P R_READ\LOG" WITH 2 BUFFERS
    BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
    .....
    RESTORE DATABASE PRICE_V8 CONTINUE
    DB20000I The RESTORE DATABASE command completed successfully.
    .....
    ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
    TIME AND STOP OVERFLOW LOG PATH
    (\\DB2_LOGSSERV ER\\DB_ARCHIVE_ FILES\PRICE_V8\ \)

    Rollforward Status

    Input database alias = PR_READ
    Number of nodes have returned status = 1

    Node number = 0
    Rollforward status = not pending
    Next log file to be read =
    Log files processed = -
    Last committed transaction = 2005-06-09-14.28.34.000000

    DB20000I The ROLLFORWARD command completed successfully.

  • Phil Sherman

    #2
    Re: Last commited transaction less then backup image timestamp afterrestore with rollforward?

    It's unlikely that the last committed transaction time is the same as
    the "rollforwar d to" time you picked. The status report indicates that
    there was no activity after the last committed transaction or that any
    active work completed after the time you picked and should have been
    rolled back as part of the rollforward process. It looks like this
    database wasn't very busy.


    Phil Sherman



    t2581@hotmail.c om wrote:[color=blue]
    > Hi ,
    > I run restore with rollforward
    > In job in output, last commited transaction time less then backup image
    > time
    > Is it normal ?
    >
    > RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
    > "D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\P R_READ\LOG" WITH 2 BUFFERS
    > BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
    > ....
    > RESTORE DATABASE PRICE_V8 CONTINUE
    > DB20000I The RESTORE DATABASE command completed successfully.
    > ....
    > ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
    > TIME AND STOP OVERFLOW LOG PATH
    > (\\DB2_LOGSSERV ER\\DB_ARCHIVE_ FILES\PRICE_V8\ \)
    >
    > Rollforward Status
    >
    > Input database alias = PR_READ
    > Number of nodes have returned status = 1
    >
    > Node number = 0
    > Rollforward status = not pending
    > Next log file to be read =
    > Log files processed = -
    > Last committed transaction = 2005-06-09-14.28.34.000000
    >
    > DB20000I The ROLLFORWARD command completed successfully.
    >[/color]

    Comment

    • t2581@hotmail.com

      #3
      Re: Last commited transaction less then backup image timestamp after restore with rollforward?

      Hi Phil,
      I use db2uext2 for archiving
      db backup created at 20050610095841 ,then I run insert till I see 10
      new log files in archive directory
      D:\DB2_LOGSSERV ER\DB_ARCHIVE_F ILES\PRICE_V8

      them I run restore and rollforward to time just 1 minute less then my
      last
      archived log file and expect to see new transaction...

      Thanks
      Alex


      Phil Sherman wrote:[color=blue]
      > It's unlikely that the last committed transaction time is the same as
      > the "rollforwar d to" time you picked. The status report indicates that
      > there was no activity after the last committed transaction or that any
      > active work completed after the time you picked and should have been
      > rolled back as part of the rollforward process. It looks like this
      > database wasn't very busy.
      >
      >
      > Phil Sherman
      >
      >
      >
      > t2581@hotmail.c om wrote:[color=green]
      > > Hi ,
      > > I run restore with rollforward
      > > In job in output, last commited transaction time less then backup image
      > > time
      > > Is it normal ?
      > >
      > > RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
      > > "D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\P R_READ\LOG" WITH 2 BUFFERS
      > > BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
      > > ....
      > > RESTORE DATABASE PRICE_V8 CONTINUE
      > > DB20000I The RESTORE DATABASE command completed successfully.
      > > ....
      > > ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
      > > TIME AND STOP OVERFLOW LOG PATH
      > > (\\DB2_LOGSSERV ER\\DB_ARCHIVE_ FILES\PRICE_V8\ \)
      > >
      > > Rollforward Status
      > >
      > > Input database alias = PR_READ
      > > Number of nodes have returned status = 1
      > >
      > > Node number = 0
      > > Rollforward status = not pending
      > > Next log file to be read =
      > > Log files processed = -
      > > Last committed transaction = 2005-06-09-14.28.34.000000
      > >
      > > DB20000I The ROLLFORWARD command completed successfully.
      > >[/color][/color]

      Comment

      • Pierre Saint-Jacques

        #4
        Re: Last commited transaction less then backup image timestamp after restore with rollforward?

        PMFJI, this may be a stupid comment on my part but what time zone are you
        in.
        You roll forward to LOCAL TIME but if I remember right, the output of the
        message is always in UCT time
        Regards, Pierre.

        --
        Pierre Saint-Jacques
        SES Consultants Inc.
        514-737-4515
        <t2581@hotmail. com> a écrit dans le message de news:
        1118955837.8530 04.91470@f14g20 00...legro ups.com...[color=blue]
        > Hi ,
        > I run restore with rollforward
        > In job in output, last commited transaction time less then backup image
        > time
        > Is it normal ?
        >
        > RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
        > "D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\P R_READ\LOG" WITH 2 BUFFERS
        > BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
        > ....
        > RESTORE DATABASE PRICE_V8 CONTINUE
        > DB20000I The RESTORE DATABASE command completed successfully.
        > ....
        > ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
        > TIME AND STOP OVERFLOW LOG PATH
        > (\\DB2_LOGSSERV ER\\DB_ARCHIVE_ FILES\PRICE_V8\ \)
        >
        > Rollforward Status
        >
        > Input database alias = PR_READ
        > Number of nodes have returned status = 1
        >
        > Node number = 0
        > Rollforward status = not pending
        > Next log file to be read =
        > Log files processed = -
        > Last committed transaction = 2005-06-09-14.28.34.000000
        >
        > DB20000I The ROLLFORWARD command completed successfully.
        >[/color]

        Comment

        Working...