Diagnostics

Core

The Outboard Service creates an application log entry for each incoming request.

Log object: /DVD/CRP
External ID:<Source ID>.<URL Command>.<Document ID>.<Comp ID>

Performance statistics

In case of performance problems, there is an expert setting WRITE_PERFORMANCE_STATS for tool: CRP to enable performance statistics. Statistics are then available in the transaction /DVD/CRP → Goto → CRP Statistics. For more information please check the performance statistics section.

Log explorer

The Outboard Service is generating application logs for each usage of the service. Sometimes it happens that you need to find a specific phrase in logs but standard SAP functionality doesn't provide such function. Therefore, our Log explorer could become very handy. By using Log explorer you are able to find all logs that contain specific text.

Transaction: /DVD/CRP_LOGEXP

Log reference in HTTP response

In case of an internal processing error, the service will return HTTP code 500 with the response message containing a reference (log handle) to the service application log. Based on this log reference, you are able to get more information regarding the error.

When you have a log handle, you are able to display a referenced log by using the cockpit transaction:

Open transaction /DVD/CRP
Choose Goto menu
Choose Display application log by a handle

Example of error message with log reference

HTTP error: 500 Internal server error WrsUNhF2ibxX0000mAWm80 Storage ID 'ZHDP_TEST1' does not exist.

Log reference is 22 characters long string.

Disable application logs based on external ID

Each content repository access creates application logs on the SAP system. This can cause issues with memory consumption. You can define which application logs shouldn’t be created.

Transaction: /DVD/CRP_LOGR

In table maintenance, you can define patterns for application log external id which will be excused from logging.

External id is created as follows: <Source ID>.<URL Command>.<Document ID>.<Comp ID>

If you switch off logging, in case of an error, there will be limited or no information for further troubleshooting.

Retention management

If the functionality is not working as expected or described in the documentation, please check processing logs using transaction SLG1 for the following objects:

Log object: /DVD/CRP
- subobject: /DVD/CRP_RM
Log object: /DVD/RMX_SARA

For an issue resolution or more details, please check the error message long text when available.

ICM parameter health check

Transaction will check whether important ICM parameters have the recommended values.

Transaction: /DVD/CRP_ICM

Content server health check

This functionality will check the configuration of the content server.

Location: /DVD/CRP → Goto → Content serv. check

Checks that are included in the functionality

Check the license
HTTP service checks all services that have our HTTP handler
- whether active
- user is filled for the service
- user has assigned our service role
Check all Sources
- mapping to SM exist
- no signature parameter is OFF
- certificate is received and valid
- parameters are filled like (Source SID, Client, Cont. rep, RFC destination)
- storage checks
  - storage is binary
  - hash calculation is enabled
Application log excluding rules
- for which external id it is switched or not
Statistics check
- whether are switched ON or OFF
- size of statistics on DB
Retention management
- archiving object customizing check whether both legal entity and retention date field are defined

Information system

If the functionality is not working as expected or described in the documentation, please check processing logs using transaction SLG1 for the following objects:

Log object: /DVD/CRP
- subobject: AIND
- external id:
  - /DVD/CRP_AIND_CHECK_STATUS
  - AIND_ERROR

Mass archiving

Structure IBCOMP is not known in the ABAP Dictionary

If you get this error message during archiving, please implement the following SAP Note 2352441.

Analyzer

Memory issues during analysis execution

If you experience a short dump where the system cannot allocate more memory and gets i.e. following exception DBSQL_SQL_INTERNAL_DB_ERROR with detail error SQL message: cannot allocate enough memory, you can try to set a lower package size that is used for analysis. The default size of package size is 10000 rows even when there is no analysis-specific customizing created.

First, find Archiving analysis ID. You can find it when you create a new run in the column Analysis ID:

Start transaction /DVD/RL_ANL_DEF.
Select Application ID: OBTTS.
Double-click on Analysis ID from the tree.
Select Analysis ID: You can find one in Analyzer.
Double-click on Analysis Customizing.
Create new value/edit existing:
1. Analysis application: OBTTS
2. Analysis ID: <selected analysis id>
3. Customizing param.: PACKAGE_SIZE
4. Customizing value: <desired package value>
Click Save.

Now you can re-execute failed Analysis tasks or create a new archiving run and execute the analysis.

Browser not supported