Hi,
I know that if we set db cfg parameter LOGSECOND=-1,it sets up the db for Infinite logging. But what is the practical use of this infinite logging feature? In which kind of environment will I be benifitting with this feature?

Thanks,
Anirban.

Log capacity. When you configure the number primary & secondary logfiles you also limit your log (and transaction) capacity. So when you've got an update on a large table without a where clause it could hit the log limits after a few hours and do a rollback (spending that same time again).
When you have infinite logging, you are limited by disk-space only (for the logs).

Infinite logging is the devil's work. Any momentary advantages will be seriously regretted in the future.

Yes - a truly religious experience ..... what a schmuck!

@Javaharlal : i know who has created this fake id ......

Thanks for the reply. But from practical perspective is this something which we do in a transient state, say when we want to delete/update a large table which might cause huge logging? Or are there some systems where we permanently enable this infinite logging ?

Thanks,
Anirban.

That's nice! But the real question is - do you know anything about infinite logging?

P.S. I know who assassinated Gandhi! Do you?

? Stalin Died naturally or Rat Poison did the trick ?

What do you want? When, due to an application error, the system starts to modify far too much data, the "no more log space" could save you. But when you are running some kind of upgrade script in the weekend, that same message will drive you crazy. Some else cannot decide for you.