Oracle Database creates an AWR baseline, the main purpose of which is to create an error-reported view of the workload for the database, which can later be compared with other AWR snapshots.
Performance statistics for the AWR baseline are stored in the database and are not automatically deleted. Oracle databases have two types of baselines: fixed baselines and moving baselines
Fixed Baseline The most common type is the fixed baseline, which is a single static view that represents the workload of a standard system.
Manual Baseline Creation
exec dbms_workload_reposwww.diuxie.comitory.create_baseline- (start_time>=to_date(‘2021/07/13 08:00:00′,’yyyy/mm/dd hh24:mi:ss’),- end_time=>to_date(‘2021/07/13 10:00:00′,’yyyy/mm/dd hh24:mi:ss’),- baseline_name=>’Baseline #1′); If set expiration time for baseline, add parameter expiration=30; You can also create EXECDBMS_WORKLOAD_REPOSITOR.CREATE_BASELINE (- based on the AWR snapshot ID that has been created start_snap_id=>xxx,end_snap_id=>xxx,baseline_name=>’Batch baseline #1′,- expiration=>30); Moving Baseline Measurements for moving baselines are captured over the entire AWR lifetime. For example, the default AWR retention period is 8 days, and it is captured throughout the 8 day time window. The default moving baseline is created automatically, and the baseline changes on a daily basis because the AWR window of the database given mobile game moves on a daily basis.
Exec dbms_workload_repository.modify_baseline_window_size(30); COL BASELINE_NAME FORMAT A20 COL BASELINE_ID formant 99 heading b_id col start_id heading STA col end_id heading END col end_time for a25 col start_time for a25 col expiration heading EXP set lines 200 select baseline_id,baseline_name,start_snap_id start_id, to_char(start_snap_time,’yyyy/mm/dd hh24:mi:ss’) start_time, end_snap_id end_id, to_char(end_snap_time,’yyyy/mm/dd hh24:mi:ss’) end_time,expiration from dba_hist_baseline order by baseline_id;