Administration troubleshooting

As you administer IBM® Business Monitor, some problems might occur. The following information will help you to troubleshoot those problems.

You can find the latest troubleshooting tips as well as information about downloads and fixes in the Support and downloads tab of the following page: IBM Business Monitor and WebSphere Business Monitor detailed system requirements.

Action services application does not start
The IBM Business Monitor action services application will not start if source data is missing from the database.
Adding the Log Trace detail level for connection, container, and transactions
You can turn-on the traces for the EJB container, transaction, and connections to help you with your troubleshooting issues.
Cannot access Business Space and its associated widgets
When the Business Process Management cluster that hosts Business Space is behind a reverse proxy server, such as WebSEAL/Tivoli Access Manager (TAM), problems can occur when you try to access Business Space and its associated widgets. These problem can occur when the WebSEAL/TAM configuration interferes with the Business Space application and its widgets.
Cannot purge a monitor model
You must complete specific steps before you purge a monitor model version and a monitor model. If an error occurred during the uninstall of a model version, these steps could have been completed but the information was not saved in the IBM Business Monitor database. If so, the Monitor Models page in the WebSphere® Application Server administrative console displays a message that purge is not available.
Cannot see information about monitor model views when data movement service is enabled
If you enable data movement services (DMS) for a monitor model version and, in the dashboard, you cannot see any information about views that are related to the model, DMS errors might be reported in the administrative console DMS (6.1.x), or Monitor Scheduled Services (6.2.x) screens, or in the IBM Business Monitor logs. The information in this topic applies to IBM Business Monitor 6.1 and later.
Cannot start application event service
If you receive an error that says could not start application EventService, you might need to activate the common event infrastructure (CEI) on one or more IBM Business Monitor servers. This problem occurs when nodes are not augmented with IBM Business Monitor capability before cluster members are created. When the node has been created or augmented with an IBM Business Monitor profile, the CEI and Startup beans services are automatically enabled when you create the cluster member.
Cannot switch from Process Portal to Business Space
If you cannot switch from Process Portal to Business Space, run the installBusinessSpace command to switch the Business Space default environment from Process Portal to Business Space.
IBM Cognos BI does not start on a clustered member
If the IBM Cognos® BI service does not start on a clustered member, the IBM Cognos BI runtime process might not be using the current settings.
A connection reset error message is recorded on systems using AIX when starting the data movement service
When the data movement service (DMS) is started on AIX systems, the exception error message "Connection reset ERRORCODE=-4499" can appear repeatedly in the SystemOut.log.
CEI distribution mode Target menu is empty
When the Common Event Infrastructure (CEI) distribution mode is changed from Active to Inactive, the drop-down menu (Target) becomes empty.
CEI distribution mode stuck between inactive and active states
When a monitor model version is transitioning from one Common Event Infrastructure (CEI) distribution mode to another, the CEI distribution mode of that model version is displayed in the administrative console as from_mode to target_mode. For example, a newly installed monitor model version has a CEI distribution mode of Inactive to Active when first installed.
Data security tab missing from administrative console
On the administrative console, under the Security tab, the Monitor Data Security option is missing.
Deployed monitor models are not startable
A deployed monitor model does not show up as startable or started in the Integration Designer or Rational® Application Developer servers view or in the WebSphere Application Server administrative console if the monitor model name or path name is too long.
Deployment of custom monitor model fails
When you deploy a custom monitor model, you might see error CWMLC0252E with a cause of LifecycleVersionSchemaExistsException in the SystemOut log, even though no version of the monitor model is currently deployed.
Error during initial filtering of event
At run time, an error that relates to the use of dayTimeDuration occurs if you deploy an EAR file that was generated in a previous version of IBM Business Monitor. Learn what the message is, what it means, and how to correctly use dayTimeDuration.
Event group profile list cannot be found or updated
If your Common Event Infrastructure (CEI) server and IBM Business Monitor server are on the same host but in different cells, you might receive an error when you are configuring CEI distribution or when you select monitor model CEI options.
Event validation error when processing XML
When event validation is enabled for the REST event emitter and an event with an invalid XML format is emitted, the REST event emitter discards the event.
Events are discarded when processed in batch mode
An error occurs when events are submitted in batch mode and at least one of the events contains malformed XML or the ATOM feed header is invalid. The entire batch of events is discarded.
Events are not being processed
If events are being emitted and associated instances are not showing up in the dashboards, you might be able to solve the issue using one of the procedures described in this section.
FFDC errors occur for events that fail with NoCorrelationMatchRetriesExceededException
When you run a process, you may encounter situations where FFDC files are logged for events that fail to correlate, but there is nothing logged in SystemOut and no events appear in the Monitor event error queue.
Granting privileges on the remote CEI server to prevent JNDI binding error
When you are deploying a monitor model with remote Common Event Infrastructure (CEI) and administrative security enabled, an error binding a queue to JNDI can occur on the remote CEI server. This problem occurs only when using queue-based event delivery and is more likely to occur when the remote CEI is included in a network-deployment environment. If the problem is not corrected, the emitted events will not reach the monitor model queue associated with the IBM Business Monitor server
Handling events that the JMS event emitter did not emit
When the JMS event emitter does not successfully emit events, you can view and manipulate the events in the error queue.
Manually confirming that the CEI event server has been restarted
If the IBM Business Monitor server cannot detect whether a Common Event Infrastructure (CEI) event server has been restarted, you must enter a command to confirm that the server hosting the CEI event server has been restarted.
Monitor database deadlocks on two or more different transactions waiting for the same database lock
When the number of events is large, the Monitor database deadlocks on two or more different transactions waiting for the same database lock. When this happens, one of the transactions fails and is retried as specified by the model version property "Maximum number of event processing failures." After the configurable number of retries fail due to deadlocks, the event and all events that follow that are related to the same instance are sent to the error queue.
Model EAR file does not appear in the list of WebSphere enterprise applications
If you deploy a monitor model from the command line, you might notice that the model appears in the WebSphere Application Server administrative console list of monitor models, but the model EAR file does not appear in the list of WebSphere enterprise applications.
Monitor model application does not process events
A monitor model application that is using table-based transport on DB2® Database for Linux, UNIX, and Windows might not process any events while an event emitter is running. At the same time, the transaction log increases until the emitter is stopped. After the emitter is stopped, the monitor model application processes events.
Monitor model deployment with remote CEI: Problem retrieving list of event group profile names
When you are deploying a monitor model with remote Common Event Infrastructure (CEI) and security enabled, an error occurs after you select Refresh List to retrieve a list of event group profile names from the remote CEI. This error is caused by a mismatch of security settings between the IBM Business Monitor server and the remote CEI.
Monitor model deployment with remote CEI: RMI connection issue caused by LTPA key mismatch
When you are deploying a monitor model with remote Common Event Infrastructure (CEI) and security enabled, an error occurs after you select Refresh List to retrieve a list of event group profile names from the remote CEI. This error can be caused by lightweight third party authentication (LTPA) keys that are different in the IBM Business Monitor and remote CEI cells.
Removing related metadata after a monitor model uninstallation process is not successful
There is a known issue that can occur when a monitor model uninstallation process does not complete successfully where metadata about the monitor model does not get removed from the Business Monitor database. As a result, any attempt to reinstall the same monitor model version will fail because existing metadata is detected.
SCA events are not being received by the monitor model
If you use Integration Designer 8.0 to generate a monitor model that monitors Service Component Architecture (SCA) events, you must enable SCA events to be emitted from Process Server 8.0 using the administrative console. Otherwise, the events are not received by the monitor model and generate error CWMRT0098E: No parent instance was found for this event in the System.out log file.
Security warnings when deploying a monitor model
When deploying the EAR file using the WebSphere Application Server administrative console, you receive application security warnings.
Setting a monitor model lifecycle step to a consistent state using the setModelStep method
You might encounter an error condition when trying to uninstall a monitor model. The error occurs when the META_MODEL_STEP_T table does not match the current state of the model. For example, you try to run the delete schema script, but the script cannot run because the step table indicates that the schema has not been created, even though the schema does exist. To resolve the error condition, you can invoke an MBean method that forces the lifecycle step into a consistent state. Use the setModelStep method with the parameters modelID, versionDate, stepName, and isComplete to set the state of the step.
SLF4J binding error in SystemErr.log
An SLF4J binding error might be posted to the System.err.log file during IBM Cognos Business Intelligence server startup. You can safely ignore this error.
Status does not show started
If the status of a monitor model application is not "started", even after manually starting the application, the lifecycle steps might not be completed.
Top-level monitoring context is not created
If you generated a monitor model from an Integration Designer application and your process is running and emitting events but a top-level monitoring context is not created when you think it should have been, you might not have created all the required events. This problem can also result in many No parent found exceptions.
Using the event flow diagnostic and validation tool to determine problems
You can use the event flow diagnostic and validation tool to troubleshoot and fix problems with consuming events.
Warnings and informational messages from the EJB validator
When a monitor model is EJB-deployed, warnings and info messages appear from the EJB validator and the Java™ compiler. These warnings and messages are harmless.

Parent topic: Troubleshooting

Related reference:

IBM Business Monitor Support