Mk_oracle PDB Tablespaces

Hello,

We have cmk v2.0.0p33.cee installed for monitoring hosts with singletenant, multitenant and RAC databases.

My question is concerning the tablespace monitoring of pluggable databases. When running the tablespace query from mk_oracle directly on the database, the result set includes rows for all the pdb tablespaces but when running the check_mk_agent script, these rows are not there under the section <<<oracle_tablespaces:sep(124)>>>. Only tablespaces of CDB$ROOT show.

And for the life of me I cannot figure out where the pdb rows are “filtered” out of the result set. Can someone provide insight?

Thanks,
Julia

Hi,

I usually put this in the mk_oracle.cfg
DBUSER_SID_PDB1=‘user:password::host:port’
where SID is the CDB and PDB1 is the name of the pdb.

The output from the agent is something like this:

PRODDB.PRODDB_PDB1|.../DATAFILE/users.275.1066292851|USERS|AVAILABLE|YES|58880|4194302|58752|160|ONLINE|8192|ONLINE|2952|PERMANENT|19.0.0.0.0
PRODDB.PRODDB_PDB1|.../DATAFILE/sysaux.271.1066292877|SYSAUX|AVAILABLE|YES|2545920|4194302|2545792|1280|ONLINE|8192|ONLINE|131232|PERMANENT|19.0.0.0.0
PRODDB.PRODDB_PDB1|.../DATAFILE/system.276.1066292867|SYSTEM|AVAILABLE|YES|160000|4194302|159872|1280|SYSTEM|8192|ONLINE|4504|PERMANENT|19.0.0.0.0
PRODDB.PRODDB_PDB1|.../DATAFILE/undotbs1.272.1066292885|UNDOTBS1|AVAILABLE|YES|1838720|4194302|1838592|640|ONLINE|8192|ONLINE|936984|UNDO|19.0.0.0.0

But usually, we have only 1 pdb in the oracle databases we monitor with checkmk. So if you have many PDBs this might not be the most practical solution.
But at least is a start.

/r

The PDB tablespaces should all be displayed if you are able to discover the CDB correctly.

Possible that the c##checkmk user does not have adequate permissions to select the views that show the PDB tablespaces. Try applying the grants again for the CDB CheckMK user and see if that helps.

The other potential issue is performance when selecting from the tablespace views. How many data files and how big are the PDB’s?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.