RE: Resized overflow buffer to xxxK (for xxxxK LWN) in trace file

Looks like it could be an existing or new bug associated with redo log
corruption

 

See info on bugs 6270459 and 5688052

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guang Mei
Sent: 26 September 2007 22:06
To: oracle-l@xxxxxxxxxxxxx
Subject: Resized overflow buffer to xxxK (for xxxxK LWN) in trace file

 

We are running oracle 10.2.0.1 on Solaris 5.10

 

 

SQL> select * from v$version;

 

BANNER

----------------------------------------------------------------

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi

PL/SQL Release 10.2.0.1.0 - Production

CORE    10.2.0.1.0      Production

TNS for Solaris: Version 10.2.0.1.0 - Production

NLSRTL Version 10.2.0.1.0 - Production

 

 

But in udump directory, I see lots of small trace files, and typically
it has something like

 

*** 2007-09-19 08:59:23.924

*** ACTION NAME:() 2007-09-19 08:59:23.917

*** MODULE NAME:(SQL*Plus) 2007-09-19 08:59:23.917

*** SERVICE NAME:(DS10ORA2) 2007-09-19 08:59:23.917

*** SESSION ID:(1000.8924) 2007-09-19 08:59:23.917

Resized overflow buffer to 10240K (for 9352K LWN)

Resized overflow buffer to 9216K (for 8235K LWN)

Resized overflow buffer to 9216K (for 8310K LWN)

*** 2007-09-19 09:02:28.434

Resized overflow buffer to 10240K (for 9352K LWN)

Resized overflow buffer to 9216K (for 8235K LWN)

Resized overflow buffer to 9216K (for 8310K LWN)

 

 

Does anyone know why I am getting these? I am curious what the root
cause is. 

Thanks.

 

Guang




BJSS Limited, 1st Floor Coronet House, Queen Street, Leeds LS1 2TW.
Registered in England with company number 2777575.
http://www.bjss.co.uk

Other related posts: