Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: alert log note

Re: alert log note

From: Yass Khogaly <ykhogaly_at_us.oracle.com>
Date: Wed, 17 Nov 1999 16:31:19 -0800
Message-ID: <80vdq4$o3e$1@inet16.us.oracle.com>


Problem Explanation:


  In Oracle versions prior to 8.0.6, there was a problem associated with controlfile expansion. If MAXLOGHISTORY is set to 65535 during database   creation (this is the default value), then when log sequence number reaches 65535, LGWR dies. This problem is now fixed in 8.0.6.

  Problem References:



  BUG 636522   Search Words:

  CONTROL FILE KCCRSZ ORA-470 ORA-449 ORA-1092   Solution Description:

Records in some sections of the control file are circularly reusable while records in other sections are never reused. The "INIT.ORA" parameter "CONTROL_FILE_RECORD_KEEP_TIME" applies to reusable sections. It specifies the minimum age in days that a record must have before it can be reused. This value defaults to 7 days if not specified in your "INIT.ORA". In the event a new record needs to be added to a reusable section and the oldest record has not aged enough, then the record section expands.

The parameter that controls the expansion of this file is specified during database creation, namely "MAXLOGHISTORY". In Oracle8 versions prior to 8.0.6, there is a known issue whenever MAXLOGHISTORY = 65535. This issue is recorded in BUG 636522. You can avoid this issue by stopping the expansion of the control file by setting CONTROL_FILE_RECORD_KEEP_TIME = 0. If "CONTROL_FILE_RECORD_KEEP_TIME" is set to 0, then reusable sections never expand and records are reused as needed.

  Solution Explanation:


 If a patch for BUG 636522 is available, you should look into the feasibility of applying to your database instance or upgrade to a release of Oracle 8.0.6 or higher. If this is not an option, check the "MAXLOGHISTORY" value. This value can be retrieved by issuing the command "alter database backup
  controlfile to trace" and examining the resulting trace file in your "USER_DUMP_DEST" directory. If it is set to 65535 then you may want to consider
  setting it to a lower value. Changing the "MAXLOGHISTORY" requires recreating control file. Aftwards, you should set the parameter   "CONTROL_FILE_RECORD_KEEP_TIME" to 0 in your "INIT.ORA" and restart the database. You can also use "ALTER SYSTEM" to change the parameter's value to an one time only basis.

"The Views expressed here are my own and not necessarily those of Oracle Corporation"

dhruba <tapashc_at_my-deja.com> wrote in message news:80v0nq$at5$1_at_nnrp1.deja.com...
> Hi ,
>
> My Oracle(8.0.5) database is running on solaris 2.6,
> On the Alert log file I got this message
>
> "kccrsz:expanded controlfile section 11 from 111 to 125
> records requested to grow by 1 record(s);added 1 block(s) of records"
>
> I am not clear about the message ,I need help,
> Any help will be appreciated
>
> Thanks in advance
>
> Dhruba
>
>
>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Nov 17 1999 - 18:31:19 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US