You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mk-oracle: report non-CDB Oracle jobs in the legacy row format
A CDB jobs row carries eleven fields and a non-CDB row ten, and no single
statement produces both, so a non-CDB was reported in the CDB shape. The 12.1
query is therefore tagged CDB-only, and a non-CDB falls through to the ten-field
query, which matches the legacy output.
Tagging the query CDB-only also makes its fallback branch for a non-CDB
unreachable, so that branch is removed here. It matched a con_id of 0, which only
a non-CDB reports.
Two further divergences from legacy are fixed on the way.
- the CDB query mapped :IGNORE_DB_NAME = 1 to the database name, so by default
it keyed the item on the instance name where legacy keys it on the database
name
- a job of class SCHED$_LOG_ON_ERRORS_CLASS kept the status of its last run
across a restart, in both arms, which turned a legacy WARN into a permanent
CRIT
TESTS: Manual and automated. Unit tests cover the tenant split from the section
name down to the selected statement, and cover both arms for the item key and
for the log-on-errors class. Confirmed against real Oracle databases in Docker,
using 12.1 as a non-CDB and 19.3 and 23.26 as CDBs. The non-CDB now emits
ten-field rows with a bare database item, and the CDBs keep their eleven fields.
CMK-37363
Change-Id: I4602011274c7d19afefa6597364b17877d605687
0 commit comments