cancel
Showing results for 
Search instead for 
Did you mean: 

Short dump "Time limit exceeded" when searching for Business Transactions

Former Member
0 Kudos
472

Hello Experts,

We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.

Number of Records:

CRMD_ORDERADM_H: 5,115,675

CRMD_ORDER_INDEX: 74,615,914

We have done these so far, but the performance is still either poor or times out.

1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy

2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records

3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)

4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".

5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.

6. Searched for notes and there are no notes that could help us.

Any idea what is causing this issue and what we can do to resolve this?

Regards,

Bala

Accepted Solutions (1)

Accepted Solutions (1)

MichaelNe
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Bala,

did you consider the SAP note 1527039 already?

Best Regards,

Michael

Former Member
0 Kudos

Hi Michael,

Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.

The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.

Regards,

Bala

Answers (0)