Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Overview


Frequently asked questions and answers 

Frequently Asked Questions


 

Issues During Setup of monitoring


 

SAP Business Objects Platform (SBOP)


1. java.rmi.RemoteException: Username is not supplied or is blank 

Problem:


While configuring jobs for BI Monitoring/Job Monitoring the exception below occurs:

java.rmi.RemoteException: Username is not supplied or is blank. Check
the parameters assigned to remote OS service in the SMD agent manager.
Parameter: ENV_SID_MN1_BOE_CMS_USR

Solution:

Check whether the correct CMS administrator user name is entered in Managed System set up for this BOBJ system.
Re-start the respective agent after adding the correct user name. 

For more information on BOBJ Managed system set up, refer to this wiki

 

2. java.rmi.RemoteException: Enterprise authentication could not log you on

Problem:

While configuring jobs for BI Monitoring/Job Monitoring the exception below occurs:

java.rmi.RemoteException: Exception occurred during login.; nested exception is:

com.crystaldecisions.sdk.exception.SDKServerException: Enterprise authentication could not log you on.

Please make sure your logon information is correct. (FWB 00008)

Solution:

Check whether the correct CMS administrator's password is entered in Managed System set up for this BOBJ system.
Re-start the respective agent after adding the correct password.

For more information on BOBJ Managed system set up, refer to this wiki

 

3. java.rmi.RemoteException: Server http://vmw3228.sap.corp:8080 not found or server may be down (FWM 01003)

Problem:

While configuring jobs for BI Monitoring/Job Monitoring the exception below occurs:

java.rmi.RemoteException: Exception occurred during login.; nested exception is:
com.crystaldecisions.sdk.exception.SDKException$OCAFramework: Server http://vmw3228.sap.corp:8080/BOE/CMC not found or server may be down (FWM 01003) 

 

Solution: 

Check whether the correct CMS system is entered in Managed System set up for this BOBJ system for the CMS system input field. It should be like mentioned in the below screen shot.|
Do not enter the CMC URL in the field.

Re-start the respective agent after adding the CMS system correctly.

 

For more information on BOBJ Managed system set up, refer to this wiki

 

 

4. Diagnostics Agent run high CPU

SAP Data Services


During monitoring set up for data service jobs, the button "Get dataservices jobs from managed system" is always grey


 Problem:

 While doing the configuration of Data Services jobs for BI Monitoring / Job Monitoring, the button "Get dataservices jobs from managed system" is not selectable and always greyed out. This can be due to the fact that the repositories are either not present in the Data Services system or they are not being fetched due to some issue.


 Solution: 

Check whether the Managed System set up is done correctly for this system. To fetch jobs, its very important that below parameters are added with correct values in remoteos properties of the right agent. Refer to this wiki for further help for the correct values. In Agent Application panel, choose com.sap.smd.agent.application.remoteos, select the agent in Scope. 


 

Troubleshooting guide for data services (BODS) jobs in BI monitoring

http://scn.sap.com/docs/DOC-69764

 

 Issues in the monitoring UI


 1. Grey data shown. The monitoring UI shows GREY rating for the configured metrics

            a.  Did it ever show a rating ( green, red, yellow) data? If Yes

Metric expiry is causing the rated metrics to expire and hence show up as grey now in the monitoring UI.

What can be done:

  • Metric retention time is twice the collection frequency
    • Increase the collection frequency ( for instance from 5 mins to 30 mins) so the data is remaining in shared memory longer until the next collection brings data back.
    • This has a negative effect by increasing the latency to report a worst case
    • For instance:
      • When the job is starting at 10:00 a.m and executed for 2 hours,
        • Assume collection runs at 10:05, and then 10:35. A failure at 10.07 will be reported not earlier than 10.35 
  • Implement the below two notes via SNOTE and Execute the report program to set the "retention time" 

ii.  Is the data collector executing as expected and fetching newer data every interval?

Data collection intermittent failure.

a) Reduce the window for collection in the configuration

If the BW PC is executed once every day at 8 a.m and is typically executing for 4 hours, please reduce the collection time window from 7.00 a.m until 12 noon.

This can be setup in the advanced scheduling tab in the SOLMAN_SETUP

iii. Check if the SAP Alert calculation engine job is running every minute in solution manager (SM37)

 

2. How to Debug and analyse no data issue.

After the a monitoring object (MO) is configured successfully and activation is successful, you should ideally see the data in the Monitoring UI.

In case the Monitoring UI is grey, please follow the below instructions,

  • Need to use the data collector test function module or trouble shooting report program to check the data collection process.
  • First check whether the data is already collected in the Solution Manager system 

1. Execute TCODE SE16

2. Go to the table “ACMOTEMPLATE” to set the related CONFIG_TYPE, and then get the CUSTOM_TEMPLT_ID.

 3. 3. Go to the table “ACTEMPLATEDIR”, enter the related TMPLT_ID and find the CONTEXT_ID

4. Then go to the table "ACE_DB_EVENT" to check whether results of the data collection.

If there are NO data records in this table. follow  below steps

5. This means there is no data collect by Solution Manager, so we should go to check if the connection between SMD Agent and Solution Manager has problems

 

6. Execute the TCODE “SE38”; Run the program “AC_BIMON_MO_ANALYSIS”, with an option "Collect data now".

This process would collect the data from the managed system.


 

  • No labels