Quantcast
Channel: SCN : Popular Discussions - SAP Test Data Migration Server
Viewing all articles
Browse latest Browse all 2460

Runtime Error during Phase Start Data Selection

$
0
0

Hello Forums,

 

We are using TDMS (2006_1_700) to extract a year's worth data from one client into a new client on the same ERP EhP4 system.

 

All the systems - central, sender and receiver are at the same DMIS levels(SP16) and all necessary notes have been applied.

 

During the Step 'Start Data Selection' of the Data Transfer Phase, we see around 60 of the ~12000 sub tasks abort with the below error:

 

 

Batch job for access plan calculation in sender system ended with errors

Message no. DMC_UTIL_MSG021

 

Diagnosis

The access plan calculation was executed as a background job in the sender system. In this background job, an error occurred.

 

Procedure

Check if a short dump occurred in the sender system while the access plan was calculated. If existing, this short dump contains further information about the cause of the problem.

A frequent error is that selection criteria for data reduction (for example selection groups) are wrongly defined which causes the database access that consideres these selection criteria to fail.

 

 

 

The corresponding dump in the Sender system is as below:

 

 

 

Runtime Errors         SAPSQL_WHERE_PARENTHESES

Exception              CX_SY_DYNAMIC_OSQL_SYNTAX

 

Error analysis                                                                                |

|    An exception occurred that is explained in detail below.                                      |

|    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not                |

|     caught in                                                                                |

|    procedure "/1CADMC/DMCACS00P000000001" "(FUNCTION)", nor was it propagated by a               |

|     RAISING clause.                                                                              |

|    Since the caller of the procedure could not have anticipated that the                         |

|    exception would occur, the current program is terminated.                                     |

|    The reason for the exception is:                                                              |

|    The current ABAP program has tried to execute an Open SQL statement                           |

|    which contains a dynamic condition. The part of the condition specified                       |

|    at runtime is incorrectly parenthesized.   

 

 

 

Please suggest in case any of you have encountered similar error and possible resolution.

 

Thanks in advance,

Srikishan


Viewing all articles
Browse latest Browse all 2460

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>