Phil,

I know that we had the same problem at V6.1 - but I couldn't tell you what
fix level we were at.  We had a special build made for us to solve the
problem.  Of course that was when V6 was supported!!

Cheers,

Jeremy


"Philip Nelson (DBA)" wrote:

> DB2 V6.1 on AIX : fixlevel U473545.
>
> I'm writing and testing a user exit for log handling.
>
> It successfully is archiving logs, both to another directory and to TSM.
>
> Now testing the retrieve processing.
>
> Last backup needs logfile 68.  Last log in archived set is 104.  Ran
> restore of backup and then issued a rollforward to end of logs.  It got
> as far as processing logfile 74 and then crashed the instance.
>
> Lots of messages in db2diag.log including -
>
> ====================== Start of edited db2diag.log =========
> Unable to initialize device /db2log/dtair001 rc=-2542
> ...
> Invoking rollforward recovery
> ...
> db2logger rc=1287 sem rc=0 type=3 area=0
> ...
> DIA9999E Internal error "507"
> ...
> Tailpage 5 does not match pagelsn .... and firstlsn ...
> ...
> DIA3714C Bad log file ""
> ...
> db2logger rc=-6899
> =================== End of edited db2diag.log ==============
>
> Restarted the instance, reran the restore and then the rollforward
> command.  It worked this time, but only used log files 68 through 70 :
> in other words I've lost the data from log files 71 through 104.
>
> Any clues as to the reason for the crash ?
>
> Any way to get DB2 to recognize the log files 71 to 104 as being valid
> for processing to "end of logs" ?
>
> TIA
>
> Phil Nelson
>
> -
> :::  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

-
:::  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

Reply via email to