Database Check and Parameter_check_102
Dear Oracle Expert,
When I execute database_check via DB02 then getting Warning against following Parameters.
|DBO ARCHIVE_TOO_OLD||1 Operation: 'Archive log backup' has not been run # Operation too old or has not been run in clean-up period|
|PROF LOG_BUFFER||1 Value: 14238720 (>< 4096,512 KB) # Size of redo log buffer in bytes|
|PROF OPTIMIZER_INDEX_COST_ADJ||1 Value: 20 (set in parameter file) # Optimizer index cost adjustment|
|PROF STATISTICS_LEVEL||1 Value: TYPICAL (set in parameter file) # Statistics level|
|ORA Checkpoint not complete||100 Time: Stan-04-09 11.15.52, line: Checkpoint not complete|
while I have configured mostly parameter in initSID.ora file but still confuse about following parameters.
Parametercheck for Oracle 10.2. based on Note/Version: 830576/222
Parametercheck last changed: 2012-04-10
Parametercheck Execution: 2012-04-11 15:55:00
DB Startup: 2012-04-11 11:09:27
DB SID: PRD
DB Environment: OLTP, not RAC
DB Platform: Microsoft Windows x86 64-bit
DB Patchset: 10.2.0.5.0
Last detectable DB Mergefix: from SAP Bundle Patch (released 2011-06-10)
Reliability checks: events passed, _fix_controls passed
WARNING: Extended support for 10.2.0.5 only available with a special extended support contract (note 1431752)
|event (10411)||set with level 1 if Winbundle>=3|
|_b_tree_bitmap_plans||set to FALSE if Winbundle<=2|
|db_writer_processes||4||change default in case of dbwr problems only|
|_fix_control (4728348)||4728348:OFF||set to 4728348:OFF if Winbundle<=5|
|_first_spare_parameter||1||set to 1 if Winbundle>=3|
please find attached file parameter_check_102 for remaining parameter which i did set in initSID.ora file.
would anyone guide me about the exact value of above parameters and meaning of Winbundle?
Bhavik G. Shroff replied
I would recommend you to run "Cleanup logs" job available in DB13 and then perform "Check database" job in DB13.
If still you are getting the same warnings as you have mentioned, then you need to take actions as following.
|DBO||ARCHIVE_TOO_OLD 1||Operation: 'Archive log backup' has not been run # Operation too old or has not been run in clean-up period|
It may be possible that Archive log backup is not performed for the complained System. If not yet, then perform it.
|PROF||LOG_BUFFER 1||Value: 14238720 (>< 4096,512 KB) # Size of redo log buffer in bytes|
You can reconfigure this parameter check condition in DB17 , if still you are getting frequent warning in DB check result. You can set this parameter check with value 14238720 (this is in KB) with "less than /equal" to condition.
You can remove Active flag for this check condition in DB17
You can reconfigure this parameter check condition with check condition "<>Not equal to" and value TYPICAL in DB17
I hope the above information will be helpful to you.
Bhavik G. Shroff