Re: RE: truncating listener.log on Windows
From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Wed, 27 Jul 2011 18:03:44 +0100
Message-ID: <CABe10sb3iSoVTrEg_yZnaZ1S5-YdTAHxu0eQV3CfPejhWVi=Og_at_mail.gmail.com>
Alex's example has the advantage of preserving the entire log stream should your auditors require it, mine will lose some small amount of data, but that maybe acceptable, but I agree if the requirement is to periodically truncate, like the *nix example, then not logging in the first place seems sensible.
Date: Wed, 27 Jul 2011 18:03:44 +0100
Message-ID: <CABe10sb3iSoVTrEg_yZnaZ1S5-YdTAHxu0eQV3CfPejhWVi=Og_at_mail.gmail.com>
Alex's example has the advantage of preserving the entire log stream should your auditors require it, mine will lose some small amount of data, but that maybe acceptable, but I agree if the requirement is to periodically truncate, like the *nix example, then not logging in the first place seems sensible.
On 27 Jul 2011 17:53, "Powell, Mark" <mark.powell2_at_hp.com> wrote:
Why not just turn off logging, delete or reduce the file size, and then re-start logging?
set log_status off
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.o...
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jul 27 2011 - 12:03:44 CDT