Troubleshooting BMC AMI Ops Insight
BMC AMI Ops Insight and BMC AMI Ops User Interface are in the same or different SMP/E environments
BMC AMI Ops Insight and BMC AMI Ops User Interface are in different or same environment. Users may or may not have shared DASD for BMC AMI Ops Insight and BMC AMI Ops User Interface.
Solution
Use one of the following to resolve this issue:
BMC AMI Ops Insight and BMC AMI Ops User Interface are on a shared DASD | BMC AMI Ops Insight and BMC AMI Ops User Interface are not on a shared DASD |
|---|---|
Replace the common environment file (AMIHLQ.UBBSAMP(AMICMNEV)) in BMC AMI Manager JCL of BMC AMI Ops Insight with the common environment file (AMIHLQ.UBBSAMP(AMICMNEV)) of BMC AMI Ops User Interface. |
|
The following points apply to both the cases mentioned here:
| |
View Detailed Analysis returns analysis failed message
Issue
When using View Detailed Analysis option, you get the Analysis Failed message. The View Detailed Analysis option of the product uses the existing BMC AMI Ops Monitor products (BMC AMI Ops Monitor for Db2, CICS, z/OS, and IMS) for analysis. Because the Data Preparation address space queries the BMC AMI Ops Monitor Products, the CAS to which the Data Preparation address space connects must be part of the MV Plex that includes the BMC AMI Ops Monitor watched by BMC AMI Ops Insight.
Example
Solution
If a CAS was installed for purely testing the product, but not set up to interact with the rest of the MV Plex, either connect to a CAS that is already part of the MV Plex or update the CASDEF so that it can connect to the other CAS in the MV Plex.
Training request fails and gives error
When you request for training, the request fails giving - Process ended with no output error. Owner of JAVA symlink (<install_Path>/aoihome/java) is not set to BPXROOT or there is no APF authorization for sortjni and other files at <install_path>/aoihome/tomcat8/default/lib.
Solution
- Set the file owner of BMC AMI Ops Insight JAVA 8 home directory (J8.0 and J8.0_64) symbolic link to BPXROOT.
The AMIUNTAR job for JAVA8 and JAVA864 TAR files sets the file owner to BPXROOT. You must run this job with userID having super user permission (uid=0). The generic ingest calls BMCSORT from JAVA to sort SMF records. Because BMCSORT should run in supervisor mode, to prevent SEC6 abend, you must set the JAVA path file owner to BPXROOT according to IBM's requirement. - All files under USS directory &AMIINST/aoihome/tomcat8/default/lib must be APF authorized. The AMIHLQ.BMCLINK and AMIHLQ.BMCLIB install data sets must also be APF authorized.
BMC AMI Ops Insight content not visible
When you log in to the application, the BMC AMI Ops Insight related content is not visible
Solution
You can use one of the following solutions:
- Make sure you have the relevant permissions for RACF profile BBM.AMOI.UI.ACCESS as specified in Security.
If the permissions to RACF profile are there and still the issue continues, make sure that the BMC AMI Ops UI has RACF access to BPX.SERVER as specified in RACF authorization for the BMC AMI Ops user interface started task.
When you log in to the application, you can view the administration screens, but you cannot create a new model
Solution
Make sure you have the relevant permission (CONTROL) for RACF profile BBM.AMOI.UI.ACCESS as specified in Security.
Real time data streaming stops with message PDRRH0405E in Syslog (WTO)
BMC AMI Ops Insight suddenly loses connection, resulting in the stopping of real-time data streaming. This causes socket timeout exception in tomcat servlet log.
This is a connection timeout in SMF record handler.
When Socket Timeout Exception occurs, the product retries connecting thrice, and if the connection is still not established, the streaming process stops and message PDRRH0405E is sent to operator (WTO) as follows: