2 Replies Latest reply: Mar 12, 2012 10:54 AM by Stefano Omini RSS

    Column Not Found Errors - Oracle OEM

    Brad Schmitt

      Hello,

       

      I just configured and ran the Oracle OEM ETL for the first time and received a bunch of "Column Not Found" errors.  Can anyone shed some light on this?  Attached is the ETL log.

        • 1. Column Not Found Errors - Oracle OEM
          Maria Benedetta Riccelli

          Hi Brad, I suggest you to open a case to BCO support for this issue. customer_support@bmc.com.

          Regards,

          MB

          • 2. Re: Column Not Found Errors - Oracle OEM
            Stefano Omini

            This error usually occurs when the connector is trying to load a column which is NOT defined in the chosen datasets.

             

            For example, in your case the loading of BYIF_BIT_RATE  is breaking...

            BYIF_BIT_RATE metric is contained in dataset 5, also called SYSNET.

             

            By reading the log, you can find out that your etl is loading only these datasets:

             

            [2012-03-12 09:54:49]  INFO  Datasetid is 2, structure: SYS

            [2012-03-12 09:54:49]  INFO  Datasetid is 4, structure: SYS

            [2012-03-12 09:54:49]  INFO  Datasetid is 14, structure: SYS

            [2012-03-12 09:54:49]  INFO  Datasetid is 15, structure: SYS

            [2012-03-12 09:54:49]  INFO  Datasetid is 16, structure: SYS

            [2012-03-12 09:54:49]  INFO  Datasetid is 59, structure:

             

            So:

            1) you can try selecting it from run configuration wizard. In the "general" tab, select the dataset 5 (SYSNET)

            2) if such operation is not possible, open a ticket to support as suggested by Maria Benedetta, but as a workaround you can enable it by configuring manually the property "general.dataset.idlist"  which is the semicolon separated list of loaded datasets

             

            The same for all the metrics which gave you an error:

            1) find the dataset they belong to (in the "admin / data warehouse" section)

            2) add the dataset id to the property