Quantcast
Channel: SCN: Message List - SAP NetWeaver Administrator
Viewing all articles
Browse latest Browse all 8487

Re: Client Import taking log time

$
0
0

Hi Andrea,

 

thanks for the replay,

 

Yes tem log file being updated, and i am not able to view any import message in SCC3 T-code.

 

Export Profile: SAP_ALL

 

But when i check STMS_IMPORT -> Logs it show the table information as like below

 

IMP_LOG.png

Total No tables is: 62,647

Here it took 12 H to import 16,000 tables.

Every hours it will import only 1000 tables.

 

kindly advice, the import in running properly or it has any problem.

 

Below the Dump details:

 

 

Category               ABAP Programming Error

Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC

Except.                CX_SY_OPEN_SQL_DB

ABAP Program           SAPLKAUP

Application Component  CO-OM

Date and Time          06.07.2013 07:17:18

 

Short text

     The ABAP/4 Open SQL array insert results in duplicate database records.

 

What happened?

     Error in the ABAP Application Program

 

     The current ABAP program "SAPLKAUP" had to be terminated because it has

     come across a statement that unfortunately cannot be executed.

 

What can you do?

     Note down which actions and inputs caused the error.

 

     To process the problem further, contact you SAP system

     administrator.

 

     Using Transaction ST22 for ABAP Dump Analysis, you can look

     at and manage termination messages, and you can also

     keep them for a long time.

 

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

     in

    procedure "INSERT_TABLES" "(FORM)", 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:

    If you use an ABAP/4 Open SQL array insert to insert a record in

    the database and that record already exists with the same key,

    this results in a termination.

 

    (With an ABAP/4 Open SQL single record insert in the same error

    situation, processing does not terminate, but SY-SUBRC is set to 4.)

 

How to correct the error

    Use an ABAP/4 Open SQL array insert only if you are sure that none of

    the records passed already exists in the database.

 

 

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

 

 

    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"

    "SAPLKAUP" or "LKAUPF01"

    "INSERT_TABLES"

 

    If you cannot solve the problem yourself and want to send an error

    notification to SAP, include the following information:

 

    1. The description of the current problem (short dump)

 

       To save the description, choose "System->List->Save->Local File

    (Unconverted)".

 

Information on where terminated

 

    Termination occurred in the ABAP program "SAPLKAUP" - in "INSERT_TABLES".

    The main program was "RSM13000 ".

 

    In the source code you have the termination point in line 464

    of the (Include) program "LKAUPF01".

    The program "SAPLKAUP" was started in the update system.

    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

    procedure "INSERT_TABLES" "(FORM)", but it was neither handled locally nor

     declared

    in the RAISING clause of its signature.

 

    The procedure is in program "SAPLKAUP "; its source code begins in line

    397 of the (Include program "LKAUPF01 ".

 

 

 

Regards,

Vino


Viewing all articles
Browse latest Browse all 8487

Trending Articles



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