This chapter assumes you are familiar with the following:

• Enterprise Manager concepts including Management Agents, metrics, and collection items

• Plug-in development overview, including how to package a plug-in and its XML files

The configuration metadata XML file begins with the METADATA tag. The METADATA tag establishes the relationship between the target type and the snapshot type, and defines the UI display name.

<METADATAS>
  <METADATA SNAP_TYPE="oracle_home_config" TARGET_TYPE="oracle_home" VER="1">

       <METADATA_UI_NAME>Oracle Home Configuration</METADATA_UI_NAME>

       CONFIGURATION COLLECTION TABLE DEFINITIONS
  </METADATA>
<METADATAS>

The configuration collection table definitions are encapsulated within the METADATA tag.

For more information about the elements of the configuration metadata XML, see Overview of Configuration Management Snapshot Metadata Elements. For information about the XML Schema Definitions (XSD) that governs the configuration XML files, see the Extensibility Development Kit (EDK) specifications.

Table 7-1 describes the key elements that define configuration management.

<METADATAS>
	   One or more snapshot specifications
</METADATAS>

<INDEXES>
    <INDEX NAME="..." COLUMNS="..." />
    <INDEX NAME="..." COLUMNS="..." />
    …
</INDEXES>

The following example provides a configuration metadata XML file for an oracle_home _config snapshot. All *_IGNORE attributes keep their default values (N) because they are not specified in the file.

Example: Configuration Metadata XML File

<METADATAS>
  <METADATA SNAP_TYPE="oracle_home_config" TARGET_TYPE="oracle_home" VER="1"

  <METADATA_UI_NAME>Oracle Home Configuration</METADATA_UI_NAME>

  <TABLE NAME="EM_ECM_OH_HOME_INFO" SINGLE_ROW="Y">
    <UI_NAME>Home Info</UI_NAME>
    <COLUMN NAME="HOME_LOCATION" TYPE="STRING" TYPE_FORMAT="1024">Install Location</COLUMN>
    <COLUMN NAME="OUI_HOME_NAME" TYPE="STRING" TYPE_FORMAT="256">OUI Home Name</COLUMN>
    <COLUMN NAME="OUI_HOME_GUID" TYPE="STRING" TYPE_FORMAT="32">OUI Home GUID</COLUMN>
    <COLUMN NAME="HOME_TYPE" TYPE="STRING" TYPE_FORMAT="1">Home Type</COLUMN>
    <COLUMN NAME="HOME_POINTER" TYPE="STRING" TYPE_FORMAT="1024">Home Pointer</COLUMN>
    <COLUMN NAME="IS_CLONABLE" TYPE="NUMBER" TYPE_FORMAT="1">Is Clonable</COLUMN>
    <COLUMN NAME="IS_CRS" TYPE="NUMBER" TYPE_FORMAT="1">Is CRS</COLUMN>
    <COLUMN NAME="ARU_ID" TYPE="NUMBER" TYPE_FORMAT="10">ARU ID of the Oracle Home</COLUMN>
    <COLUMN NAME="HOME_SIZE" TYPE="NUMBER" TYPE_FORMAT="10">Size of Oracle Home (KB)</COLUMN>
  </TABLE>

  <TABLE NAME="EM_ECM_OH_DEP_HOMES">
    <UI_NAME>Dependee Oracle Homes</UI_NAME>
    <COLUMN NAME="DEP_HOME_LOCATION" TYPE="STRING" TYPE_FORMAT="1024" IS_KEY="Y">Dependee Home Location</COLUMN>
  </TABLE>

  <TABLE NAME="EM_ECM_OH_COMPONENT">
    <UI_NAME>Components installed in Oracle Home</UI_NAME>
    <COLUMN NAME="COMPONENT_NAME" TYPE="STRING" TYPE_FORMAT="128" IS_KEY="Y">Component Name</COLUMN>
    <COLUMN NAME="COMPONENT_VERSION" TYPE="STRING" TYPE_FORMAT="64" IS_KEY="Y">Base Version of Component</COLUMN>
    <COLUMN NAME="CURRENT_VERSION" TYPE="STRING" TYPE_FORMAT="64">Current Version of the Component</COLUMN>
    <COLUMN NAME="INSTALL_TIME" TYPE="TIMESTAMP" >Install Time</COLUMN>
    <COLUMN NAME="IS_TOP_LEVEL" TYPE="NUMBER" TYPE_FORMAT="1">Is a top level Component</COLUMN>
    <COLUMN NAME="EXTERNAL_NAME" TYPE="STRING" TYPE_FORMAT="128">External name</COLUMN>
    <COLUMN NAME="DESCRIPTION" TYPE="STRING" TYPE_FORMAT="1024">Description</COLUMN>
    <COLUMN NAME="LANGUAGES" TYPE="STRING" TYPE_FORMAT="1024" >Languages</COLUMN>
    <COLUMN NAME="INSTALLED_LOCATION" TYPE="STRING" TYPE_FORMAT="1024">Installed Location</COLUMN>
    <COLUMN NAME="INSTALLER_VERSION" TYPE="STRING" TYPE_FORMAT="64">Installer Version</COLUMN>
    <COLUMN NAME="MIN_DEINSTALLER_VERSION" TYPE="STRING" TYPE_FORMAT="64">Minimum Deinstaller Version</COLUMN>

      <TABLE NAME="EM_ECM_OH_COMP_INST_TYPE">
        <UI_NAME>Install Types of Components</UI_NAME>
        <COLUMN NAME="NAME_ID" TYPE="STRING" TYPE_FORMAT="128" IS_KEY="Y">Install Type Name ID</COLUMN>
        <COLUMN NAME="INSTALL_TYPE_NAME" TYPE="STRING" TYPE_FORMAT="128" >Install Type Name</COLUMN>
        <COLUMN NAME="DESC_ID" TYPE="STRING" TYPE_FORMAT="128">Install Type Description</COLUMN>
      </TABLE>

  </TABLE>

  </METADATA>
</METADATAS>

When you have completed your configuration metadata XML file, save the file in the following directory in your plug-in staging directory:

oms/metadata/snapshotlive

After you save the configuration metadata file in the plug-in staging directory, it is available for automatic registration during plug-in deployment.

For information about the plug-in staging directory or plug-in deployment, see Validating, Packaging, and Deploying the Plug-in.

After you complete the configuration metadata XML file, you must register it with the Configuration Management framework. Place the configuration metadata XML file in the oms/metadata/snapshotlive directory in your plug-in staging directory. Registration takes place automatically during the installation or upgrade of the plug-in and the necessary schema objects will be created and the configuration metadata registered with the Configuration Management framework. For more information about the plug-in staging directory and registration, see Validating, Packaging, and Deploying the Plug-in.

To manually run the registration service during development of XML-only plug-ins, enter the following:

emctl register oms metadata 
-sysman_pwd sysman password 
-pluginId plugin ID
-service LiveSnapshotRegistration 
-file snapshot metadata XML file

Note: Import the plug-in into the Management Repository before the command is run.

plugin ID is the ID of the plug-in to which the snapshot metadata target types belong. The LiveSnapshotRegistration is the metadata service that creates and updates configuration management schema objects and registers configuration metadata.

This command registers the snapshot configuration file (snapshot metadata XML file) using SYSMAN credentials in your development environment.

Configuration Management provides the following utility that can be run optionally to generate some additional files:

EDK_DIR/bin/empdk generate_metadata_resource -stage_dirplugin_stage 
         -service LiveSnapshotRegistration
         -input_dir input directory
         [-out_dir output directory]
         [-file_extension list of file extensions/suffixes]
         [-debug debug file name]

where:

• EDK_DIR: Directory where EDK package is unzipped. (For more information, see Installing the Extensibility Development Kit (EDK)).

• plugin_stage: Plug-in staging directory. (For more information, see Staging the Plug-in).

• input directory: Directory containing the configuration metadata XML files.

• output directory:Directory to contain the generated resource files. If not specified, then the resource files are generated in the current directory.

• list of file extensions/suffixes: Comma separated list of file extensions or suffixes for the resource files. If not specified, then all supported resource files will be generated in the output directory.

• debug file name: File that contains debug information. If not specified, then the default log file (createplugin.logtime) is created in the output directory and stored warning and error messages only.

For each configuration metadata XML file in the input directory, the specified resource files are generated in the output directory with the file name ecm_metadata_xml_file_name as the prefix and the following supported suffixes:

• .dlf

  file_name.dlf is a file for translations of snapshot type name, table name, and column name. A generated DLF file and its translated versions should be placed in the plugin_stage/oms/rsc/ecm directory of the plug-in.

• _metrix.xml, _collection.xml

  file_name_metric.xml and file_name_collection.xml can be used as starting templates for Management Agent-side integration. For more information, see Modifications to Standard Collection Metrics and RAW Metrics.

Data Loading Format (DLF) translation files are used to support internationalization for the display strings in plug-in metadata files so that the UI can display them in the language of the end user. Usually, you provide an original (such as English) DLF file to translators who then create similar files for other locales. All such files are loaded into the Management Repository by Enterprise Manager during the installation of a plug-in.

To generate DLF files for translation of the snapshot type name, table, and column names, run the following command:

$ORACLE_HOME/emcore/pdk/partner/bin/empdk generate_metadata_resource
-stage_dir staging directory
-service LiveSnapshotRegistration
-input_dir input directory containing snapshot metadata XML file
-file_extension extension to use for generated DLF files
-out_dir output directory to which to generate the DLF files
[-debug debug output file]

You must place the generated DLF files and their corresponding translated versions in the following directory of the plug-in:

plugin_stage/oms/rsc/ecm

The following manual additions are required in each DLF file:

<table xml:lang="en" name="MGMT_MESSAGES">
<lookup-key>
  <column name="MESSAGE_ID"/>
  <column name="SUBSYSTEM"/>
  <column name="LANGUAGE_CODE"/>
  <column name="COUNTRY_CODE"/>
</lookup-key>
<columns>
  <column name="MESSAGE_ID" type="string" maxsize="256"/>
  <column name="SUBSYSTEM" type="string" maxsize="64"/>
  <column name="LANGUAGE_CODE" type="string" language="%l"/>
  <column name="COUNTRY_CODE" type="string" language="%Cs"/>
  <column name="MESSAGE" type="string" maxsize="1000" translate="yes"/>
</columns>
<dataset>
GENERATED FILE CONTENT
</dataset>
</table>

When you are upgrading existing snapshot metadata, the following changes are supported:

• New tables

• New non-key columns (these should appear after previously existing columns)

• New list of indexes (replaces any prior indexes)

• Increasing length of STRING type columns

• Values of UI_IGNORE, COMPARE_IGNORE, COMPARE_UI_IGNORE, HISTORY_IGNORE, HISTORY_UI_IGNORE and UI_NAME attributes

Take the following metadata example:

Example: Original Metadata Definition

<METADATAS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <METADATA VER="1"
    SNAP_TYPE="sn_dbconfig"
    TARGET_TYPE="sn_oracle_database"
    UI_IGNORE="Y"
    HISTORY_IGNORE="N"
    COMPARE_IGNORE="Y"
    COLLECTION_GROUP="COL_GRP_0">
  <METADATA_UI_NAME>Database Configuration</METADATA_UI_NAME>
  <TABLE NAME="TABLESPACES" DATA_SOURCE="R">
    <UI_NAME>Tablespaces</UI_NAME>
    <COLUMN NAME="TABLESPACE_NAME" TYPE="STRING" TYPE_FORMAT="30"
      IS_KEY="Y">Tablespace Name</COLUMN>
    <COLUMN NAME="SIZE" TYPE="NUMBER">Size</COLUMN>
    <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="10">Status</COLUMN>
    <TABLE NAME="DATAFILES">
      <UI_NAME>Datafiles</UI_NAME>
      <COLUMN NAME="FILE_NAME" TYPE="STRING" TYPE_FORMAT="1024" 
        IS_KEY="Y">File Name</COLUMN>
      <COLUMN NAME="FILE_SIZE" TYPE="NUMBER" HISTORY_IGNORE="Y">Size</COLUMN>
      <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="9">Status</COLUMN>
    </TABLE>
  </TABLE>
 </METADATA>
</METADATAS>

The following example provides an example of an upgrade to the metadata definition described in the previous example. The changes are highlighted in bold text.

Example: Upgraded Metadata Definition

<METADATAS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <METADATA VER="2"
    SNAP_TYPE="sn_dbconfig"
    TARGET_TYPE="sn_oracle_database"
    UI_IGNORE="Y"
    HISTORY_IGNORE="N"
    COMPARE_IGNORE="Y"
    COLLECTION_GROUP="COL_GRP_0">
  <METADATA_UI_NAME>Database Configuration</METADATA_UI_NAME>
  <TABLE NAME="TABLESPACES"  DATA_SOURCE="R">
    <UI_NAME>Tablespaces</UI_NAME>
    <COLUMN NAME="TABLESPACE_NAME" TYPE="STRING" TYPE_FORMAT="30"
      IS_KEY="Y">Tablespace Name</COLUMN>
    <COLUMN NAME="SIZE" TYPE="NUMBER">Size</COLUMN>
    <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="10">Status</COLUMN>
    <TABLE NAME="DATAFILES">
      <UI_NAME>Datafiles</UI_NAME>
      <COLUMN NAME="FILE_NAME" TYPE="STRING" TYPE_FORMAT="1024" 
        IS_KEY="Y">File Name</COLUMN>
      <COLUMN NAME="FILE_SIZE" TYPE="NUMBER" HISTORY_IGNORE="Y">Size</COLUMN>
      <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="10">Status</COLUMN>
      <COLUMN NAME="DESC" TYPE="STRING" TYPE_FORMAT="128">Status</COLUMN>
    </TABLE>
  </TABLE>
  <TABLE NAME="TABLESPACES_1"  DATA_SOURCE="R" >
    <UI_NAME>Tablespaces_1</UI_NAME>
    <COLUMN NAME="TABLESPACE_NAME" TYPE="STRING" TYPE_FORMAT="30"
      IS_KEY="Y">Tablespace Name</COLUMN>
    <COLUMN NAME="SIZE" TYPE="NUMBER">Size</COLUMN>
    <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="10">Status</COLUMN>
    <COLUMN NAME="NOTES" TYPE="STRING" TYPE_FORMAT="128">Status</COLUMN>
    <TABLE NAME="DATAFILES_1">
      <UI_NAME>Datafiles_1</UI_NAME>
      <COLUMN NAME="FILE_NAME" TYPE="STRING" TYPE_FORMAT="1024"
        IS_KEY="Y">File Name</COLUMN>
      <COLUMN NAME="FILE_SIZE" TYPE="NUMBER" HISTORY_IGNORE="Y">Size</COLUMN>
      <COLUMN NAME="STATUS" TYPE="STRING" TYPE_FORMAT="10">Status</COLUMN>
    </TABLE>
  </TABLE>
 </METADATA>
</METADATAS>

Older Enterprise Manager releases allowed for the "DROP_EXISTING_DATA" attribute in the METADATA element, but this should be removed as it is no longer supported.

Note that if you must have non-backward compatible changes in your ECM metadata, you must create a new snapshot type (that will not be comparable with old snapshot type). ECM only supports backward compatible changes.

Enterprise Configuration Management data is collected by regular metrics, collections and Management Agent mechanisms. This data is collected though regular RAW metrics with the following modifications:

• Add a CONFIG="TRUE" attribute to all Metric and CollectionItem tags that collect configuration snapshot information.

• Ensure that the CollectionItem NAME attribute is the same as the snapshot type name (for example, oracle_home_config).

• The schedule for data collections must not specify an interval that is more frequent than once per day.

When ancestor key columns are included in child tables, you can populate a hierarchical set of tables one at a time, without having to express the hierarchical relationships during the collection. You should list parent tables before corresponding child tables in the Collection Item.

The following example provides a metric definition from the target type metadata XML file for the EM_ECM_OH_HOME_INFO table defined in the configuration metadata XML file example in Overview of Configuration Management Snapshot Metadata Elements. The information highlighted in bold font is provided by the configuration metadata XML file.

For more information about the target type metadata XML file, see Creating the Target Type Metadata File.

Example: Defining a Metric

    <Metric NAME="EM_ECM_OH_HOME_INFO" TYPE="RAW" CONFIG="TRUE">
        <Display>
            <Label NLSID="…">Home Info</Label>
        </Display>
        <TableDescriptor TABLE_NAME="EM_ECM_OH_HOME_INFO">
            <ColumnDescriptor NAME="HomeLocation" COLUMN_NAME="HOME_LOCATION" TYPE="S">
                <Display>
                    <Label NLSID="…">Install Location</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="OuiHomeName" COLUMN_NAME="OUI_HOME_NAME" TYPE="S">
                <Display>
                    <Label NLSID="…">OUI Home Name</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="OuiHomeGuid" COLUMN_NAME="OUI_HOME_GUID" TYPE="S">
                <Display>
                    <Label NLSID="…">OUI Home GUID</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="HomeType" COLUMN_NAME="HOME_TYPE" TYPE="S">
                <Display>
                    <Label NLSID="…">Home Type</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="HomePointer" COLUMN_NAME="HOME_POINTER" TYPE="S">
                <Display>
                    <Label NLSID="…">Home Pointer</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="IsClonable" COLUMN_NAME="IS_CLONABLE" TYPE="N">
                <Display>
                    <Label NLSID="…">Is Clonable</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="IsCrs" COLUMN_NAME="IS_CRS" TYPE="N">
                <Display>
                    <Label NLSID="…">Is CRS</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="AruId" COLUMN_NAME="ARU_ID" TYPE="N">
                <Display>
                    <Label NLSID="…">ARU ID of the Oracle Home</Label>
                </Display>
            </ColumnDescriptor>
            <ColumnDescriptor NAME="HomeSize" COLUMN_NAME="HOME_SIZE" TYPE="N">
                <Display>
                    <Label NLSID="…">Size of Oracle Home (KB)</Label>
                </Display>
            </ColumnDescriptor>
        </TableDescriptor>
        <!-- TODO : EDIT: Edit the QueryDescriptor Element Template as required -->
        <QueryDescriptor FETCHLET_ID="" AGENT_MODE="">
            <Property NAME="" SCOPE=""></Property>
        </QueryDescriptor>
    </Metric>

The following example provides a definition of the metric collection from the default collection metadata file for the metric defined in the previous example. The information highlighted in bold font is provided by the configuration metadata XML file example in Overview of Configuration Management Snapshot Metadata Elements.

For more information about the default collection metadata file, see Creating the Default Collection File.

Example: Defining Metric Collection

<CollectionItem NAME="oracle_home_config_test" CONFIG="TRUE">
        <Schedule OFFSET_TYPE="INCREMENTAL">
          <!-- Configuration Collection is done at most once every 24 Hours -->
            <IntervalSchedule INTERVAL="24" TIME_UNIT="Hr" />
        </Schedule>
        <MetricColl NAME="EM_ECM_OH_HOME_INFO" />
        <MetricColl NAME="EM_ECM_OH_DEP_HOMES" />
        <MetricColl NAME="EM_ECM_OH_CRS_NODES" />
        <MetricColl NAME="EM_ECM_OH_CLONE_PROPS" />
        <MetricColl NAME="EM_ECM_OH_COMPONENT" />
        <MetricColl NAME="EM_ECM_OH_COMP_INST_TYPE" />
        <MetricColl NAME="EM_ECM_OH_COMP_DEP_RULE" />
    </CollectionItem>

For a plug-in, do not forget to include the metadata and default_collection XML files at both oms and agent directories within the opar file.

After integrating the configuration collection tables into the configuration management framework, you can test the configuration collection by completing the following steps:

If you are having problems with your configuration collections, do the following:

1. Check that your snapshot type is registered in the MGMT_ECM_SNAPSHOT_METADATA table:

   select * from mgmt_ecm_snapshot_metadata
    where target_type   = your_target_type
      and snapshot_type = your_snapshot_type;
   

   You should see two rows. If not, check if there are any errors during registration in the regular log files for MRS in the following directory.

   $ORACLE_HOME/cfgtoollogs/pluginca
   

2. Define the corresponding metrics to verify that collections begin and data accumulates. If you are looking at the latest collection in the UI, make sure first that the UI_IGNORE flags in the metadata are not Y for the data you are checking. If the collections are not happening, then check the following:

   • Make sure that your collection item name is the same as snapshot type and CONFIG="TRUE" is specified for both the collection item and all its metrics.

     For more information, see Modifications to Standard Collection Metrics and RAW Metrics.

   • Make sure your metrics are defined as RAW metrics and table descriptor corresponds to your ECM tables.

   • Check if the collection arrives to the Management Repository but is not updated as "current".

     In the MGMT_ECM_GEN_SNAPSHOT table, check the is_current status for your target and snapshot type. If there are no rows, then the collection did not progress. The IS_CURRENT flag should be set to Y to indicate the latest snapshot of data. Rows with other IS_CURRENT values are possible for internal purposes. For example, if there are no rows with the Y value, then IS_CURRENT values of T and D would indicate a snapshot started loading but did not finish.

   • Check the value of META_VER in agent target type metadata and default_collection XML files.

     During development, when any new metric or collection item is added, META_VER may need to be bumped up in these files for registration of these new entries to succeed. Check the latest instructions for Enterprise Management development regarding the META_VER value.

     For example, while during your development you may need to increase the version in order to register your changes, only one increase of the version per release is required, and therefore, while merging the code, META_VER may need to be the same as before if it were already incremented for the current release.

     From a collection perspective, you have to make sure that both new target type metadata and default_collection XML files are successfully registered and that the agent is restarted with latest files. The following commands can be used to register target type metadata and default_collection XML files:

     emctl register oms metadata -service targetType -file target type XML filename [-core | -pluginId Plugin Id] [ sysman_pwd "sysman password"]
     

     emctl register oms metadata -service default_collection -file default collection XML filename [-core | -pluginId Plugin Id] [ sysman_pwd "sysman password"]
     

     Finally, for a given target instance you are testing, make sure that its META_VER matches the META_VER of the loaded snapshot type in order to see the latest collected data that is based on your latest META_VER.

   • Check the Valid-Ifs defined for the target type, snapshot type, and the metric to see if the category properties of the target instance match the Valid-Ifs. If not, the target would not show corresponding data since the configuration would not be applicable to such target.

   • On the OMS Repository, check the mgmt_system_error_log table and emoms_pbs.trc/log for the snapshot type.

     You can also examine the mgmt_metric_errors table using the following command:

     select * from mgmt_metric_errors 
     where target_guid = '<your target guid>'
       and coll_name = '<your snapshot type>'
     

     At the agent, check gcagent.log and other files in agent log directory for the same string.

   • If that does not help, turn on agent backup file feature (add backupUploadedFiles=true to emd.properties and restart the agent).

     Search for your snapshot type in the following location to ensure the agent is sending data to OMS and to see what it is sending:

     agentStateDir/sysman/emd/upload/upload/succbkup/
     

   • One potential problem you may run into relates to the configuration difference feature.

     If for some reason the configuration did not load, but the agent thinks that it has, and if the configuration does not change from that point on, the agent will keep sending short "nothing-changed" files types and the loader will keep disregarding them. To clear this issue (or just eliminate it as a potential issue while debugging), clear the agent log of config by running the following comand (no spaces around comma):

     emctl clearstate agent -incrementalconfig targetName,targetType
     

     Then, to initiate the collection, run the following command:

     emctl control agent runCollection targetName:targetType snapshot type
     

     For example:

     emctl clearstate agent -incrementalconfig myOracleHomeTargetName,oracle_home
     emctl control agent runCollection myOracleHomeTargetName:oracle_home oracle_home_config
     

3. At Oracle Management Service and the Management Repository, check the MGMT_SYSTEM_ERROR_LOG table and the emoms_pbs.trc file for the snapshot type. Also check the MGMT_METRIC_ERRORS table as follows:

   At the Management Agent, check the gcagent.log file and other files in agent log directory for the same string.

4. If you still have problems, turn on the Management Agent backup file feature:

   1. Open the emd.properties file.

   2. Add the following line to the file:

      backupUploadedFiles=true
      

   3. Restart the Management Agent.

      AGENT_HOME/agent/bin/emctl stop agent
      AGENT_HOME/agent/bin/emctl start agent
      

      In the preceding command, AGENT_HOME represents the Management Agent home directory.

   4. Search for your snapshot type in the following directory to ensure that the Management Agent is sending data to the OMS:

      agentStateDir/sysman/emd/upload/upload/succbkup/
      

5. A potential issue can arise relating to the configuration difference feature. If the configuration did not load but the Management Agent interprets that the configuration did load, (and if the configuration does not change), then the Management Agent sends short files indicating that nothing changed and the loader will continue to disregard the files.

   To clear or eliminate this potential issue, clear the Management Agent log as follows:

   emctl clearstate agent -incrementalconfig targetName,targetType
   

   For example:

   emctl clearstate agent -incrementalconfig myOracleHomeTargetName,oracle_home
   

   Then, to initiate the collection, run the following command:

   emctl control agent runCollection targetName:targetType snapshot_type
   

   For example:

   emctl control agent runCollection myOracleHomeTargetName:oracle_home oracle_home_config
   

6. From the Cloud Control console, test the history and comparison features to see how the results look or if any flags should be tweaked.

   1. From Enterprise Manager Cloud Control, select Targets, then select the required target.

   2. Right-click the target and select Configuration, then select History to view the configuration history or select Compare to test the comparison feature.

      Note:

      For more information about these pages, see the Cloud Control online help.

Sample Inventory Choice XML Metadata File provides an example of an Inventory Choice XML.

The following sections describe some of the sections of the XML file.

The following example provides a sample Inventory Choice XML metadata file.

Example: Inventory Choice XML

<?xml version="1.0" encoding="UTF-8" ?>
<InventoryChoice iname="SampleHostsInv" display_name="SampleHostsInv">

 <Applicable_Targettypes>
    <TargetType>all</TargetType>
    <TargetType>enterprise</TargetType>    
  </Applicable_Targettypes>
  <MasterData>
    <Query id="HOSTS_INV_MASTER_QUERY">
                
                <Enterprise_Ctx>
                
                    <Sql>
                            With InvQuery AS (
                select 
                            name, 
                            base_version,
                            vendor_name,
                            count(*) as num_hosts , 
                            decode(sum(num_patches) , 0 , ''No'',''Yes'') as patched
   from
                          (          
                            select os.name, os.name||'' ''||os.base_version as base_version, os.vendor_name,host,
                              ( select 
                                  count(*)  
                                from 
                                  MGMT$OS_PATCH_SUMMARY patch 
                                where 
                                  patch.host =os.host and 
                                  patch.target_guid = os.target_guid
                              ) as num_patches
                            from 
                              MGMT$OS_SUMMARY os
                          )m
                          
                          group by name,base_version,vendor_name
                          )
          
                %GROUP_BY_SQL%
                </Sql>
                </Enterprise_Ctx>
                <!-- target context query -->
                <Target_Ctx>
                    <Sql>
                With InvQuery AS (
 select 
           name, 
            base_version,
            vendor_name,
            count(*) as num_hosts ,
            decode(sum(num_patches) , 0 , ''No'',''Yes'') as patched 
          from
          (          
            select os.name, os.name||'' ''||os.base_version as base_version, os.vendor_name,host,
              ( select 
                  count(*)  
                from 
                  MGMT$OS_PATCH_SUMMARY patch 
                where 
                  patch.host =os.host and 
                  patch.target_guid = os.target_guid
              ) as num_patches
            from 
              MGMT$OS_SUMMARY os
            where os.snapshot_guid in
            (
            
              SELECT /*+ ORDERED */ ps.snapshot_guid
              FROM
              (
                select
                  unique t.host_name as hname
                FROM
                  mgmt$targets t,
                ( 
                 SELECT m.assoc_target_guid as mguid
                          FROM 
                            mgmt$target_flat_members  m,
                           .........
                          WHERE                             
                             
                            mem.AGGREGATE_TARGET_NAME = ? and
                            mem.aggregate_target_type= ? and
                            mem.member_target_type like ? and         
                ............................
                  ) lt1
                  WHERE
                    lt1.mguid = t.target_guid
              )lt,
             .................
                )
              )
               group by name, base_version, vendor_name                        
                )
          %GROUP_BY_SQL%    
                
                  </Sql>
                    <In_Parameters>
                    <!--Aggregate target name in which the inv choice data to be shown -->
                        <Param position="1" type="TARGET_NAME"/>
<!-- Aggregate target type -->
                        <Param position="2" type="TARGET_TYPE"/>
                        <Param position="3" type="MEMBER_TARGET_TYPE"/>
                         ........
                        
                        
                    </In_Parameters>
                </Target_Ctx>
            </Query>
        
  </MasterData>
  
  <DetailsData>
    <Query id="HOSTS_DETAILS">
                    
                    <Enterprise_Ctx>
                    
                        <Sql>
SELECT 
          hostname, 
          hwname, 
          name,
          base_version,
          update_level,
          address_length_in_bits,
          vendor_name,
          freq,
          mem,
          disk,
          cpu_count,
          distributor_version,
          physical_cpu_count,
          logical_cpu_count,
          last_collection_timestamp
        FROM
        (
                                
        SELECT 
          hostname, 
          hwname, 
          name,
          base_version,
          update_level,
          address_length_in_bits,
          vendor_name,
          freq,
          mem,
          disk,
          cpu_count,
          distributor_version,
          physical_cpu_count,
          logical_cpu_count,
          last_collection_timestamp
        FROM
        ( 
          SELECT 
            o.target_name as hostname, 
            system_config  || '' '' || MA as hwname, 
            o.name as name,
            o.name||'' ''||o.base_version as base_version,
            o.update_level,
            o.address_length_in_bits,
            o.vendor_name,
            hw.FREQ as freq,
            hw.MEM as mem,
            hw.DISK as disk,
            hw.CPU_COUNT ,  
            o.DISTRIBUTOR_VERSION ,
            hw.physical_cpu_count,
            hw.logical_cpu_count,
            o.LAST_COLLECTION_TIMESTAMP
          FROM             
              MGMT$OS_HW_SUMMARY  hw  ,  MGMT$OS_SUMMARY o
          WHERE
            hw.host_name = o.host and
            hw.target_guid = o.target_guid and
            hw.SNAPSHOT_GUID = o.SNAPSHOT_GUID
          )                    
          %FILTER_SELECT_FOR_MASTERROWS% )
          %FILTERDRILLDOWNVALUES%
                    </Sql>
                    </Enterprise_Ctx>
                    <!-- target context query -->
                    <Target_Ctx>
                        <Sql>
                   SELECT 
          hostname, 
          hwname, 
          name,
          base_version,
          update_level,
          address_length_in_bits,
          vendor_name,
          freq,
          mem,
          disk,
          cpu_count,
          distributor_version,
          physical_cpu_count,
          logical_cpu_count,
          last_collection_timestamp
          FROM
          (
                   SELECT UNIQUE
          hostname, 
          hwname, 
          name,
          base_version,
          update_level,
          address_length_in_bits,
          vendor_name,
          freq,
          mem,
          disk,
          cpu_count,
          distributor_version,
          physical_cpu_count,
          logical_cpu_count,
          last_collection_timestamp
          FROM
          (
            .....--provide the target context query here for filtering in composite target..
            ...
            
            
          ) hw_list  %FILTER_SELECT_FOR_MASTERROWS% order by hostname)
          %FILTERDRILLDOWNVALUES%
                    
                      </Sql>
                        <In_Parameters>                        
                  <Param position="1" type="TARGET_NAME"/>
                  <Param position="2" type="TARGET_TYPE"/>
                  <Param position="3" type="MEMBER_TARGET_TYPE"/>
.....................
                        </In_Parameters>
                    </Target_Ctx>
                </Query>
        
    
    
  </DetailsData>
 
 
  
  <ShowByList>
    <ShowBy iname="Platform" display_name="PLATFORM" default_selection="true">
      <MasterTableData>
        <SqlQuery bindid="HOSTS_INV_MASTER_QUERY">
                        
    <!-- Group by sql will replace %GROUP_BY_SQL% given in the main query -->
        <Group_By_Sql>
                  select name , patched, sum(num_hosts) as num_hosts from InvQuery %FILTERDRILLDOWNVALUES% group by name,patched order by name
            </Group_By_Sql>
              
                </SqlQuery>
        <UiColumnMapping id="Platform" backend_column="name" isKey="true" visible="true" uiColumn_nls_id="Platform"/>
        
        <UiColumnMapping id="num_hosts" backend_column="num_hosts" isKey="false" uiColumn_nls_id="Hosts" countColumn="true"/>
        <UiColumnMapping id="patched" backend_column="patched" isKey="false" uiColumn_nls_id="Patched"/>
         
      </MasterTableData>
      <DetailsTableData>
        <SqlQuery bindid="HOSTS_DETAILS"/>
            <UiColumnMapping id="Host Name" backend_column="hostname" isKey="true" visible="true" uiColumn_nls_id="Host Name"/>
        <UiColumnMapping id="Platform" backend_column="name" isKey="true" visible="true" uiColumn_nls_id="Platform"/>
        <UiColumnMapping id="Version" backend_column="base_version" isKey="true" visible="true" uiColumn_nls_id="Version"/>
        <UiColumnMapping id="Vendor" backend_column="vendor_name" isKey="true" visible="true" uiColumn_nls_id="Vendor"/>                
        <UiColumnMapping id="Hardware" backend_column="hwname" isKey="true" visible="true" uiColumn_nls_id="Hardware"/>
        <UiColumnMapping id="Update Level" backend_column="update_level" isKey="true" visible="true" uiColumn_nls_id="Update Level"/>       
        
        
      </DetailsTableData>
      
      
      
    </ShowBy>
    <ShowBy iname="Version" display_name="VERSION" default_selection="false">
          <MasterTableData>
            <SqlQuery bindid="HOSTS_INV_MASTER_QUERY">
                                 
            <!-- Group by sql will replace %GROUP_BY_SQL% given in the main query -->
                <Group_By_Sql>
                          select base_version , patched, sum(num_hosts) as num_hosts from InvQuery  %FILTERDRILLDOWNVALUES% group by base_version,patched order by base_version
                    </Group_By_Sql>
                      
                </SqlQuery>
        
            <UiColumnMapping id="Version" backend_column="base_version" isKey="true" visible="true" uiColumn_nls_id="Version"/>
            <UiColumnMapping id="num_hosts" backend_column="num_hosts" isKey="false" uiColumn_nls_id="Hosts" countColumn="true"/>
            <UiColumnMapping id="patched" backend_column="patched" isKey="false" uiColumn_nls_id="Patched"/>
            </MasterTableData>
          <DetailsTableData>
            <SqlQuery bindid="HOSTS_DETAILS"/>
                    <UiColumnMapping id="Host Name" backend_column="hostname" isKey="true" visible="true" uiColumn_nls_id="Host Name"/>
                <UiColumnMapping id="Platform" backend_column="name" isKey="true" visible="true" uiColumn_nls_id="Platform"/>
                <UiColumnMapping id="Version" backend_column="base_version" isKey="true" visible="true" uiColumn_nls_id="Version"/>
                <UiColumnMapping id="Vendor" backend_column="vendor_name" isKey="true" visible="true" uiColumn_nls_id="Vendor"/>                
                <UiColumnMapping id="Hardware" backend_column="hwname" isKey="true" visible="true" uiColumn_nls_id="Hardware"/>
                <UiColumnMapping id="Update Level" backend_column="update_level" isKey="true" visible="true" uiColumn_nls_id="Update Level"/>
            
          </DetailsTableData>
         
    </ShowBy>
    
    <ShowBy iname="Vendor" display_name="VENDOR" default_selection="false">
              <MasterTableData>
                <SqlQuery bindid="HOSTS_INV_MASTER_QUERY">
                                        
                    <!-- Group by sql will replace %GROUP_BY_SQL% given in the main query -->
                        <Group_By_Sql>
                                  select vendor_name, patched, sum(num_hosts) as num_hosts from InvQuery %FILTERDRILLDOWNVALUES%  group by vendor_name,patched order by vendor_name
                            </Group_By_Sql>
                              
                </SqlQuery>
                <UiColumnMapping id="Vendor" backend_column="vendor_name" isKey="true" visible="true" uiColumn_nls_id="Vendor"/>
                
                <UiColumnMapping id="num_hosts" backend_column="num_hosts" isKey="false" uiColumn_nls_id="Hosts" countColumn="true"/>
                <UiColumnMapping id="patched" backend_column="patched" isKey="false" uiColumn_nls_id="Patched"/>
                 
              </MasterTableData>
              <DetailsTableData>
                <SqlQuery bindid="HOSTS_DETAILS"/>
                <UiColumnMapping id="Host Name" backend_column="hostname" isKey="true" visible="true" uiColumn_nls_id="Host Name"/>
                   <UiColumnMapping id="Platform" backend_column="name" isKey="true" visible="true" uiColumn_nls_id="Platform"/>
                   <UiColumnMapping id="Version" backend_column="base_version" isKey="true" visible="true" uiColumn_nls_id="Version"/>
                   <UiColumnMapping id="Vendor" backend_column="vendor_name" isKey="true" visible="true" uiColumn_nls_id="Vendor"/>                
                   <UiColumnMapping id="Hardware" backend_column="hwname" isKey="true" visible="true" uiColumn_nls_id="Hardware"/>
                   <UiColumnMapping id="Update Level" backend_column="update_level" isKey="true" visible="true" uiColumn_nls_id="Update Level"/>
                                
              </DetailsTableData>
            
              
    </ShowBy>
  </ShowByList>
</InventoryChoice>