Rakesh,
The problem is that once I've recovered the database to the other machine,
it's only going to know about any transaction logs that have been created
up to the time of the database backup that I've restored to. It doesn't
know about any subsequent logs that have been created since the backup was
taken. I have to physically retrieve these logs from TSM and put them in
the SQLOGDIR directory, and then figure out how to roll forward through
these logs. My question/problem is how do I figure out what timestamp I
should use to roll forward through the end of the latest log that I have
available. I would have thought that "rollforward to end of logs" would
have done that for me, but as my original post below states, that failed
with an SQL1268N error.
-------------------------------------------------------
Bill Gallagher
Database Administrator
Information Technology
Infrastructure / Operations
Phoenix Life Insurance Company
860-403-1773
[EMAIL PROTECTED]
"Rakesh Madan"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
E.COM> cc:
Sent by: "DB2 Data Subject: Re: Finding a Good Timestamp
to Rollforward To
Base Discussion
List"
<[EMAIL PROTECTED]
ASSOC.COM>
03/12/03 09:21 AM
Please respond to
"DB2 Data Base
Discussion List"
Did you do a rollforward database query status. THis should tell you the
rollforward point in time that you need. Also I believe that if you have
already done a rollforward to end of logs and then want to do a point in
time you may have to redo the restore. Then issue a query status and then
rollforward to a point in time.
Rakesh
> -----Original Message-----
> From: Bill Gallagher [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 12, 2003 8:47 AM
> To: [EMAIL PROTECTED]
> Subject: Finding a Good Timestamp to Rollforward To
>
>
> Our environment: DB2 v7.2 fixpack 7 running on AIX 4.3.
>
> This past weekend, we lost one of our production AIX DB2
> database servers
> and needed to recover/rebuild the databases that had lived on it on a
> different AIX server. We had full online database backups
> archived via
> TSM, as well as a number of log files also archived via TSM.
>
> I was able to restore the databases in question to the second
> server, but
> because they were online backups, the database was left in rollforward
> pending. My thought was to do a rollforward database to end
> of logs and
> stop, but that failed because the rollforward was still
> looking for one log
> file past the latest one that I had available.
>
> My next option was to rollforward to a point in time that was
> at the end of
> the latest log file that I had available, but I had a lot of
> difficulty in
> determining what that timestamp was. I knew what time the
> log file was
> archived to TSM via the "db2adutl query logs" command, so I
> tried to use a
> timestamp that was a few minutes earlier than the archive
> time (adjusted to
> CUT). That worked for some databases, but not for others (it
> was still
> looking for the next log, which I didn't have).
>
> My question is: is there any way to determine what the latest
> timestamp
> that is contained in a particular log file that can be used
> for rollforward
> processing? My guess is that the last information written to
> the log file
> may have been hours earlier than when the archive was taken (which was
> taken when the database was closed before our weekly server reboot).
>
> I wasted a lot of time with "hit-and-miss" guessing of
> rolling forward the
> logs to recover as much data as possible in our disaster
> recovery situation
> this weekend.
>
> Any thoughts or comments will be greatly appreciated.
>
> -------------------------------------------------------
> Bill Gallagher
> Database Administrator
> Information Technology
> Infrastructure / Operations
> Phoenix Life Insurance Company
> 860-403-1773
> [EMAIL PROTECTED]
>
> ================================================
> To change your subscription options or to cancel your
> subscription visit the DB2-L webpage at
> http://listserv.ylassoc.com. The owners of the list can be
> reached at [EMAIL PROTECTED]
>
================================================
To change your subscription options or to cancel your subscription visit
the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can be reached at [EMAIL PROTECTED]
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
