Database audit
Monitoring → Database audit reads the JD Edwards database live from Oracle's dictionary, the way an audit reads it: what the instance is, what the figures say, then nine sections in four tabs. It is read-only and written for Oracle.
No AWR, ASH, ADDM or SQL-monitor view is read: they belong to packs licensed separately, and reading them would itself count as a use. The activity figures therefore count since the instance started.
At a glance
The four tabs
Each tab says, beside its description, how many of its points are to review.
| Tab | Sections |
|---|---|
| Overview | The instance — version, instance, database, mode, platform and the parameters that matter (control_management_pack_access, cursor_sharing, db_block_size, open_cursors, processes, sga_target, undo_retention…) — and What the figures say. |
| Storage | Size by what each owner holds — business data, control tables, central objects, system, object librarian, data dictionary, Oracle, other —; Tablespaces with what they use and may grow to; The largest tables, their indexes and LOBs counted in, with their description from the Object Librarian. |
| Activity | Activity — cache hit ratio, hard parses, executions, commits, sorts on disk, where time was waited —; The most expensive statements and who sends them; Sessions by program — JDE kernels, JDE batches, web / AIS servers, tools; Redo logs and their switches hour by hour. |
| Objects | Objects and statistics — invalid objects, unusable indexes, JDE tables never analysed or with stale statistics. |
What the figures say
| Flagged | Meaning |
|---|---|
| A tablespace above 85 % | Of what it may grow to. |
| NOARCHIVELOG | No recovery to a point in time. |
| Redo logs with one member, or switching too often | A lost file is a lost log; the logs are small for the activity. |
| A short cache, hard parses | The buffer cache is short for what is read; statements are not shared. |
| Tools connected to the database | Sessions of programs other than JD Edwards. |
| Invalid objects, unusable indexes, statistics never taken or stale | On the JD Edwards owners. |
control_management_pack_access | Whether the Diagnostics / Tuning packs' features may be used — a licence exposure if they are not held. |
Access
The page shows to the roles that hold its menu entry and the permission plugin:nomajde.dbaudit:j_db_audit. It reads the database through the JD Edwards database connection.
Tips & best practices
- Read the Overview tab first: the amber lines are the points an auditor would raise.
- Check
control_management_pack_accesson every database of the platform:NONEkeeps the packs' features out of reach. - The activity figures count since the instance started: compare two readings a few days apart rather than one reading after a restart.
Related
- Performance — the database's blocked sessions, slow statements and waits beside the servers'.
- Platform analysis — the servers.