Re: transaction lost when delete clog file after normal shutdown

HI Jan Wieck
> Why would you trust the other 99.999 TB if something corrupted the clog
> file?
However, on the other hand, oracle has many solutions to open the database
after the data files are damaged, and his intention should be to start the
database even if some critical files are damaged to salvage the data
inside.Because there's a lot of that going on in the real world, and you
can't change that by firing the dba.

On Tue, Dec 24, 2024 at 9:45 AM wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:

> >Why would you trust the other 99.999 TB if >something corrupted the clog
> >file?
> +1
>
> On Tue, 24 Dec 2024 at 02:06, Jan Wieck <jan(at)wi3ck(dot)info> wrote:
>
>> On 12/23/24 06:01, 章晨曦(at)易景科技 wrote:
>> > Yes, of course we can solve this by restoring from backup.
>> > But if the database volumn is large, say, 100TB or more, the cost
>> > is really too expensive just because the tiny clog file corrupt.
>>
>> Why would you trust the other 99.999 TB if something corrupted the clog
>> file?
>>
>>
>> Regards, Jan
>>
>> >
>> > Regards,
>> > Jet
>> >
>> > Daniel Gustafsson<daniel(at)yesql(dot)se> 在2024年12月23日 周一 18:43 写道：
>> > > On 23 Dec 2024, at 11:36, 章晨曦(at)易景科技
>> > <zhangchenxi(at)halodbtech(dot)com> wrote:
>> >
>> > > Human errors, disk errors, or even cosmic rays ...
>> >
>> > That sounds exactly like the scenario which backups are made for. In
>> > all these
>> > error cases there is no way of being sure that no other part of the
>> > system has
>> > been compromised, so you restore from backup with WAL replay.
>> >
>> > --
>> > Daniel Gustafsson
>> >
>>
>>
>>
>>