Printable View
Read up on the control_file_record_keep_time parameter. Control file can only expand to a certain limit. Bs, bp information is reusable.
If your database generates tons of logs and you back'em up frequently, you'll soon start seeing "denied expansion of controlfile" followed by "following controlfile record written over" messages in your alertlog.
I think these two metalink notes would give a vivid picture of what happens with the control_file_record_keep_time parameter setting. I think the controlfile will keep expanding on the circular section to satisfy the minimum record keep time condition.
Metalink note #s: 1034884.6 and 125303.1
Thanx,
Sam
A clarification - It won't expand indefinitely. It'll get circularly reused. There are hard set limits, beyond which controlfile will get overwritten. Say you set the control_file_record_keep_time to 10000 days on a large/active database. He's not gonna automatically retain 10000 days worth of information, in his controlfile a few years from now. That was the point I was trying to convey.Quote:
I think the controlfile will keep expanding on the circular section to satisfy the minimum record keep time condition.
I think the max limit is 365 :DQuote:
Originally posted by Axr2
A clarification - It won't expand indefinitely. It'll get circularly reused. There are hard set limits, beyond which controlfile will get overwritten. Say you set the control_file_record_keep_time to 10000 days on a large/active database. He's not gonna automatically retain 10000 days worth of information, in his controlfile a few years from now. That was the point I was trying to convey.
Cheers,
Sam
I presume that this is what you were trying to tell.
Metalinl Note:134234.1
Which talks about how oracle cautions when it cannot expand beyond the maxlog history limit.
Thanx,
Sam
> Metalinl Note:134234.1
Exactly. I often get those messages.
My values(control_file_record_keep_time = 31)is very much with with in 0 - 365. And I am not worried about the hard limit too, sinceQuote:
Originally posted by Axr2
A clarification - It won't expand indefinitely. It'll get circularly reused. There are hard set limits, beyond which controlfile will get overwritten. Say you set the control_file_record_keep_time to 10000 days on a large/active database. He's not gonna automatically retain 10000 days worth of information, in his controlfile a few years from now. That was the point I was trying to convey.
The records_used maximum value is nowhere near to the hard limit 65535.Code:
SQL> l
1* select * from v$controlfile_record_section order by RECORDS_USED
SQL> /
TYPE RECORD_SIZE RECORDS_TOTAL RECORDS_USED FIRST_INDEX LAST_INDEX LAST_RECID
----------------- ----------- ------------- ------------ ----------- ---------- ----------
CKPT PROGRESS 4084 8 0 0 0 0
RESERVED1 56 62 0 0 0 0
RESERVED2 1 1 0 0 0 0
DATAFILE COPY 404 141 0 0 0 0
OFFLINE RANGE 180 90 0 0 0 0
BACKUP CORRUPTION 44 185 0 0 0 0
PROXY COPY 596 191 0 0 0 0
RESERVED4 1 8168 0 0 0 0
COPY CORRUPTION 40 204 0 0 0 0
DATABASE 316 1 1 0 0 0
REDO THREAD 228 8 1 0 0 0
REDO LOG 72 32 3 0 0 3
TABLESPACE 68 62 20 0 0 20
DATAFILE 428 62 21 0 0 30
FILENAME 268 127 28 0 0 0
BACKUP DATAFILE 116 1126 1126 1079 1078 4455
BACKUP PIECE 480 1140 1140 1128 1127 3354
BACKUP SET 40 1225 1225 294 293 3354
ARCHIVED LOG 328 23383 23383 11520 11519 63811
LOG HISTORY 36 26319 26319 9694 9693 80481
BACKUP REDOLOG 76 27083 27083 2622 2621 81611
DELETED OBJECT 20 28588 28588 21003 21002 80218
22 rows selected.
Hope now you understand the re-registering is not harmfull to my backup information.
Thanks Sam and Axr2.