RE: OEM Monitoring Templates
From: Herring, David <HerringD_at_DNB.com>
Date: Mon, 12 Jun 2017 18:34:24 +0000
Message-ID: <DM5PR02MB22501983C53F2EB26149697AD4CD0_at_DM5PR02MB2250.namprd02.prod.outlook.com>
Date: Mon, 12 Jun 2017 18:34:24 +0000
Message-ID: <DM5PR02MB22501983C53F2EB26149697AD4CD0_at_DM5PR02MB2250.namprd02.prod.outlook.com>
This got me curious so I checked different "repvfy" versions to see how they handle this. Under 12c (repvfy version 2017.0206) the "dump template" clause executes "…/emdiag/12cR1/_template.sql" which in turn executes "gc_diag_ext.analyzeTemplate('&&1',0,9);". Under 11g (repvfy version 2014.0110) the same clause executions "…/emdiag/11gR1/dump/_template.sql" and that SQL script includes all the various cursors that display information on how the template is defined. If you lookup the GUID for each template you could execution this script manually, passing in the GUID as a parameter.
Regards,
Dave
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Jun 12 2017 - 20:34:24 CEST