Troubleshooting

The following message is reported in the ETL log:

This error occurs when the host name specified for the CDB Server address in the mainframe ETL Custom Properties tab was not found.

Provide the correct host name in the CDB Server address field on the mainframe ETL Custom Properties tab and re-submit the ETL run.

The following message is reported in the ETL log:

This error occurs the data source name specified for the CDB Server Data source name in the mainframe ETL Custom Properties tab was not found on the target CDB Server.

Provide the correct data source name in the CDB Server Data source name field on the mainframe ETL Custom Properties tab and re-submit the ETL run.

The following messages are reported in the ETL log:

Start and Stop Date/Time taken from parameters.
Start: 2022/09/29 00:00
Stop: 2022/09/29 24:00
Heap Free before TSQ 231747080
SYSMFCLS 0
Mem increase: 0
OBJREL 0
CDB TSQ executed.
Extract OK. Total records extracted: 0
CDB TSQ returned error.
ETL Engine: LOAD step
CDB TSQ last message: No records found
Processing table OBJREL
Loader: Dataset is empty
[FlatFileLoader] OBJREL is empty.

This error occurs when the ETL does not find data for the requested interval in the specified CDB data source.

Confirm that the correct interval has been requested. 

Verify that the data for the requested interval has been populated into the CDB data source before the mainframe ETL has executed.

For more information, see Scheduling-the-ETL-task-to-run-automatically.

The following messages are reported in the ETL log:

Application data extraction start.
CDB TSQ request created.
strtInsAppls: -1
limitNAppls: 100
CDB TSQ executed.
CDB TSQ returned error.
CDB TSQ last message: No records found
CDB TSQ last debug message: null
Execution stopped.

Classes data extraction start.
CDB TSQ request created.
CDB TSQ executed.
CDB TSQ returned error.
CDB TSQ last message: No records found
CDB TSQ last debug message: null
Execution stopped.
Service Classes ended.

Extraction done. Records sent to data sets:
SYSCNF 1029
SYSGLB 1979
SYSMFCNF 2027
SYSMFGLB 1646
SYSMFOS 6744
SYSMFAPP 0
SYSMFLCP 3201
SYSMFSUT 3749
WKLMFAPP 0
SYSMFCLS 0
SYSMFSTG 5393
SYSMFPOOL 9923
OBJREL 563

This error occurs when the ETL does not find data for a requested mainframe object in the specified CDB data source.

The Universal Information Exchange batch job extracts data from the RMF/SMF mainframe data sets and creates a number of Mainframe objects by default – CPCs, LPARs, z/OS Images, and Sysplexes.

Some Mainframe objects are optional, as follows:

• Applications
• Suites
• Service/Report Classes
• Storage Pools

These optional objects are included in the CDB data source if the required data is processed by the UIE batch job and the UIE job contains the appropriate commands to create these objects.

Confirm that the UIE job is processing data for the object for which the mainframe ETL did not find any data. 

The following messages are reported in the ETL log:

System.NullReferenceException: ExecuteHelper.ExecuteLongRunningTask: There are no CDBWorkflowServices bound to the CDBServices. The job will not be placed on the Pending Queue. Service/Bridge/Method: ObjectServices:SchemaBridge:ExecuteTimeSpanQueryDirect
at BMCSoftware.PASM.CDB.Common.ServiceHelpers.ExecuteHelper.ExecuteLongRunningTask(String request, String DSN, String serviceBridgeMethod, String machinenameUsername, RealTimeActivityManagerItem rtaitem)

This error occurs when the CDB Workflow Services are not running.

The BMC AMI Capacity Database Web Services CDBWorkflowService task must be running for the ETL to request and extract data from the CDB data source. Services may have been stopped due to data base maintenance or IIS issues. The CDB Workflow services must be restarted manually. 

To verify the status of the CDBWorkflowService task:

1. Login to the server where BMC AMI Capacity Database Web Services is installed. 
2. Open the  Computer Management application and navigate to Services and Applications > Services. 
3. Find the CDBWorkflowService task.  The status column should display a status of Running. 
4. To restart the CDBWorkflowService task, right click on the CDBWorkflowService task name and select restart.

The following notification is displayed in the Mainframe View:

To view the chart data, select a system, domain or tag filter or configure a page-level or chart-level entity filter.

This error occurs when the Domain Filter is empty.

The No Domain Selected is displayed.

Mainframe View, select the Domain filter from the top of the page and select the domain that contains the mainframe data.

The following notification is displayed in the Mainframe View:

No data available for the selected metrics.

This error occurs when there is no data for the selected mainframe object or time filter.

Verify that you have data for the selected mainframe object for the selected Domain and time filters.

If this is an optional mainframe object – Application, Business Application, Suite, Storage Controller/Pool, Service/Report Class, verify that the mainframe ETL is extracting the data for this object.

The following notification is displayed in the Mainframe View:

Unable to perform the requested operation. 
Details: BCO_PRV_ERR012 - Error while retrieving data for the data mart Mainframe CPC Configuration Metrics (id 1903).

This error occurs when the CPC Configuration Metrics data mart (1903) has not been materialized.

Verify that the Helix Continuous Optimization Data Mart Materialization task has executed after the mainframe ETL has completed. 

If this is the first time you are accessing the Mainframe View, you can also materialize the Mainframe CPC Configuration Metrics (1903) data mart by going to the Administration > DATA MARTS page, select Data mart 1903 and click on Materialize now. 

When the data mart has been materialized, click on Preview to verify that data was found for this data mart. Return to the Mainframe View and verify that data is displayed in the CPC Configuration table.