Re: GI log sizes

From: K Gopalakrishnan <>
Date: Tue, 29 Nov 2011 17:46:40 -0600
Message-ID: <>

Hmm... Looks like its party documented in the following MOS note.. ***
Oracle Sun Database Machine V2 Diagnosability and Troubleshooting Best Practices [ID 1071220.1]

Increase the CSS log file size to avoid a premature wrap

The default size for the CSS logs in
$GI_HOME/log/<nodename>/cssdis 50M. For certain types of problems, this smaller size causes a wrap and important information is lost to debug problems. Increase the CSS log file size to 150M to save more log data needed in the evenbt of a problem. The command to increase this size is
crsctl set css logfilesize 157286400 and should be run on all nodes. The cost of this increase is about 1GB of filesystem space per node.

On Tue, Nov 29, 2011 at 5:33 PM, K Gopalakrishnan <> wrote:
> Dave,
> You can set the logsfilesize using crsctl  (crsctl set css
> logfilesize?) and this one is not documented in the reference.
> The 'logfilesize' is carefully avoided in the  crsctl utility
> reference. So I am not sure whether this is supported (!).
> -Gopal
> On Tue, Nov 29, 2011 at 3:59 PM, Herring Dave - dherri
> <> wrote:
>> Does anyone know if we can control the size of the various Grid Infrastructure logs?  Under 11gR2 it appears there are 11 logs that are rotated automatically by Oracle with 2 different max sizes:

Received on Tue Nov 29 2011 - 17:46:40 CST

Original text of this message