Share:|

Welcome to our new monthly blog for users of BMC Capacity Management products which includes BMC Performance Assurance (BPA) and BMC Capacity Optimization (BCO).  We will be covering topics that have been trending in Capacity Management support and we'll expand upon a popular topic to hopefully provide some additional clarity to a wider audience.

 

For those of you who have been receiving the BCO Information Headquarters newsletter, you will be seeing some of that content here in the near future.

 

We receive many questions regarding data delivery to BCO from BPA, and thought that Debugging the BPA ETL would be a good first topic.

 

First check that you have the latest Service Pack & Cumulative Hot-fix installed on BCO, particularly on the ETL engine. Most of the BPA ETL CDB issues have already been solved. To see where to find the latest Service Packs for BCO, see: https://kb.bmc.com/infocenter/index?page=content&id=S:KA358729

 

Once you have installed at least BCO 4.5 SP3 or BCO 9.0 SP3, proceed to the following steps:

 

1. If scheduled, un-schedule the BPA CDB ETL or the chain containing it

 

2. Edit the ETL run configuration in advanced mode



3. Enable audit logs in the BPA CDB

 


4. Bring back the ETL lastcounter at least 1 day, to re-import some data


 

5. Run the ETL again

 

 

 

6. Access the ETL logs page

 

… and collect the audit log files named EXTRACTIONAUDIT* as explained also in https://kb.bmc.com/infocenter/index?page=content&id=S:KA350895.


 

One file is generated  for each relevant CDB table, so that the content can be easily checked by a human operator. Below is a simple explanation of the content of those files:

 

The Audit file name is like: EXTRACTIONAUDIT_ETL81_CAXPSYS__CAXPSYSD.txt and the file name points out the

ETL TASKID (81), and the names of the two tables queried. The file content is similar to the following:

 

#CAXPSYS__CAXPSYSD extraction audit
#RUN SQL Query: SELECT * FROM CAXINTVL INTVL_TBL, CAXPSYSD DNMC_TBL WHERE DNMC_TBL.INTVL = INTVL_TBL.INDEXX AND INTVL_TBL.INTTYPE = 'M'AND ((INTVL_TBL.INT_START_DATE >'13/08/24' AND INTVL_TBL.INT_START_DATE <= '13/08/31') OR (INTVL_TBL.INT_START_DATE = '13/08/24'  AND INTVL_TBL.INT_START_TIME >= '2300') )
DYNCTABLE;IDXCOL;NODE_ID;DSSYSNM;NODE_NAME;SYS_TYPE;EXTRACTED_ROWS;COMMENT
CAXPSYSD;PHYSS;641;IBM_03102D65B;IBM_03102D65B;vh:lp;25;Extracted
CAXPSYSD;PHYSS;644;IBM_02106302P;IBM_02106302P;vh:lp;0;NoDataFromExtractionQuery
CAXPSYSD;PHYSS;501;pun-esx-rds48;pun-esx-rds48;ESX;;NotIncludedInSelectedPlatform

  • The first line:

#CAXPSYS__CAXPSYSD extraction audit

lists the names of the two tables queried.

 

  • The second line:

#RUN SQL Query: SELECT * FROM CAXINTVL INTVL_TBL, CAXPSYSD DNMC_TBL WHERE DNMC_TBL.INTVL = INTVL_TBL.INDEXX AND INTVL_TBL.INTTYPE = 'M'AND ((INTVL_TBL.INT_START_DATE >'13/08/24' AND INTVL_TBL.INT_START_DATE <= '13/08/31') OR (INTVL_TBL.INT_START_DATE = '13/08/24'  AND INTVL_TBL.INT_START_TIME >= '2300') )

contains exactly the query executed by the ETL, with the correct parameters also for  temporal intervals, so it can be manually executed against the CDB if necessary. The file continues with a table in csv format, containing a list of entities. The columns in the table are:

  • DYNCTABLE: the dynamic table that contains data
  • IDXCOL: the index column
  • NODE_ID: the ID of the node in BPA
  • DSSYSNM: the lookup field in BCO for the entity
  • NODE_NAME: entity name
  • SYS_TYPE: the system type, like VMware VM, host, Solaris zone
  • EXTRACTED_ROWS: how many dynamic rows have been found for the system in dynamic table,
  • COMMENT:
    • Extracted:data for that entity have been found into dynamic table
    • NoDataFromExtractionQuery: no data for that entity have been found into dynamic table
    • NotIncludedInSelectedPlatform: the SYS_TYPE for that system is not included for extraction into the selected platform (i.e. you selected VMware platform in ETL, and this is a Solaris Zone)

 

7. If the system(s) that can't be found are marked as Extracted, try to restore the hierarchy rule associated with the BPA CDB ETL and see if this solves the issue.

 

 

 

8. In case of further issues: access BPA console, check the collection schedule or the policy files to collect the associated VIS file(s)

 

9. Send to support:

 

10. Remember!!!  -  to reschedule back the ETL and disable audit logs generation once debugging activity is completed

 

We hope this edition has helped and we would love to hear your thoughts and comments. 

Thx, timo