Configurator · runs in your browser · v1.6.0
Build your run command
Every parameter of run_awr_trend.sh in five short steps. The This run panel
shows what the run will compare and what the report will contain, and updates as you type.
Nothing is sent anywhere. Prefer the terminal? ./run_awr_trend.sh --configure asks the same questions.
1Connect▸
Enter a connect string.
Any SQL*Plus logon:
user/pw@host:port/service, a TNS alias, or
/ as sysdba. Needs SELECT on DBA_HIST_* only (the report never writes).
Used locally: the password is part of the command you copy, nothing else.2Windows: what is compared with what▸
Start from a shape
A shape fills the four fields below; change any of them freely afterwards.
The diagram in the This run panel redraws as you go.
Pick a date and time, or switch back to AUTO.
AUTO resolves at run time to the most recent completed clock hour, so a
scheduled run always looks at the hour that just finished. Pin a time to study a known incident, a batch run,
or yesterday's business hours. An off-grid time snaps back to the last AWR snapshot.
Must be a positive number of hours.
Length of every window, in hours.
0.25 = 15 min, 9 = a business day.Must be a whole number of at least 1.
How many earlier windows the newest one is compared with (a count; the name is historical).
3 or more are needed for z-score findings.
The step must be a positive number.
3Content: what goes into the report▸
Changes which rows are read and scored; the Activity charts, Top SQL, segment / file I/O,
parameters and SQL Monitor sections are the same under every template.
Must be a whole number of at least 1.
Must be 0 (all instances) or a positive whole number.
Must be 0 (off) or a whole number of prior days.
0 = off. N adds a section that scores each hour of the 24 h ending at the window end
against the same hour on the N prior days (always a 1-day cadence, independent of the cadence above): an
hour-of-day × metric heatmap. 3 or more days are needed for z-scores.4Output: file, charts, console▸
Shell wrapper only. Written next to the report after the run; a failed archive never undoes a finished report (exit code 4).
5Timeline markersoptional▸
A release, a patch, an incident: each becomes a vertical line on the Activity charts, the
ASH timeline and the per-window trend charts, and a flag on the window grid when it falls between windows.
They ride inline in the command (no file to save); a straight apostrophe in a label becomes a typographic one.
Milestones outside the compared span are kept in the legend but not drawn.