Client Import taking log time

[Former Member]

Hi all,

Client Export has been completed successfully from Production system,

windows 2008 r/2 64 Bit

ECC 6.0, EHP 5

DB size : 260 GB

Export TR size: 10 GB

Export Time: 6H

Also i Imported the same to Quality system (SAME LEVEL), but it took more then 12H now.

I checked TP processor in domain controller also quality system, but there is no process running in this name.

Also i have checked ST22, there i got huge number of dumps as like below, also kindly let me know how to check the log file.

kindly advice how to solve this issue..

Regards,

Vino

[Former Member · Accepted solution]

Hi Vino

you said there are no tp running, can you check in \\saptranshost\trans\tmp if there is a log that is still being updated? Also, in SCC3 what can you see in the log of the copy?

What export profile did you use and can you also upload full dump?

Let me know

a

[Former Member · Accepted solution]

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

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

[Former Member · Accepted solution]

Hi

I usually consider import time roughly 3times the export (without the deletion, otherwise it's longer) but in your case it looks it's going really slow

Have source and target same hardware architecture (cpu mem disks) characteristics? (this could make a  big difference) Network? I mean is the file phisically on the drive of target system or is somewhere else (sometimes the network between prod and rest of landscape has not good bandwitdth and speed)

What's your db engine? (Check also db space even if this should not be the problem for your import)

Then, the dump. You said there are plenty, can you describe me the frequency. Basically, it could be a job from previous client that is trying to insert records and clashing wiht the import(so there should be a precise frequence) or it's your import

First case, stop the job! Second case, it looks that your import is going on and at the end of the import you'll receive a list of error that you probably will need to fix

Let me know

a

[Nibu · Accepted solution]

Hi Vinoth,

Every Hr 1000 tables are getting imorted ? So Import still running I guess. Better be patient I would reccomend , and check tmp directory too, it should increse time by time if import is running .

The error you mentioned is because of duplicate entries and it wont stop your import I feel .

Since export took 6 Hrs , you should expect around 18 Hrs for import from normal experience .

Next time , when you do you can increase the number of parallel processes etc while importing, you cn exclude tables which are not necessary to be a part of export ,update the latest tp & R3trans etc can speed up the process.

[Former Member]

Do you still have batch jobs running in your target client?  That would explain all the dumps.

As others have said, the import is always much slower than the export.  It helps a lot, if you delete the client using SCC5 before starting the import.  Also, you might want to make sure to turn database logging and/or archiving off during the delete/import to reduce the overhead.

[Former Member]

Hi Vinoth,

               Did you excluded tables which are not required in target system like log tables which will be of huge size and will  not  be required in target system.

            Plesae look at Serivce Market place for notes which will suggest  to exclude such tables.

            Also if possible during import try to add more CPU's if that option is available to reduce the time.

Thanks and Regards,

Kunal Gahlot

[Reagan]

Good Day

Andrea has already mentioned where you can find the import log.

Also do you see R3trans process running at the OS level ?

I believe there is an option to use parallel processing, are you using it ?

Consider these SAP Notes:

Note 68896 - R3trans: Performance problems and cluster

Note 1127194 - R3trans import with parallel processes

Regards

RB